Web Profiles

Device and resolution

The window the page is rendered in. Either a desktop browser at a size you choose, or one of around 200 real phones and tablets, emulated down to its viewport and pixel density.

Desktop or emulated

These settings are in the Device & viewport section of the Web Profile form. Device has exactly two settings, and it decides which of the fields below it you get.

Value	Meaning
`Desktop`	A desktop browser window. You set the resolution yourself, either from the presets or as a custom width and height. This is the default.
`Emulate`	A named phone or tablet, chosen under Phone model. Its viewport, pixel density and user agent all come from the device, so the resolution buttons are greyed out and marked Set by the phone.

Emulated profiles show N/A for resolution

In the profile list, a mobile profile has no resolution of its own — the device sets it. That is why the column reads N/A rather than being empty.

Desktop resolution

Under Resolution you pick one of five preset sizes. They are the common display resolutions, and 1920 × 1080 is what a new profile starts with.

1920 x 10802560 x 14403840 x 21605120 x 28807680 x 4320

The resolution is the browser window, not the file. A full-page capture at 1920 × 1080 produces an image 1920 wide and as tall as the page turns out to be.

Big resolutions cost more than they look

7680 × 4320 is sixteen times the pixels of 1920 × 1080. The capture takes longer, the file is very much larger, and it counts against your included storage at that size. Reach for it when you genuinely need the detail, not by default.

Custom sizes

Press Custom size… and the preset buttons are replaced by two number fields, W and H. Use a preset takes you back to the buttons.

Field	Type	Default	Description
`W (width)`Required	Number	1920	250 to 7680 pixels.
`H (height)`Required	Number	1080	250 to 4320 pixels.

Custom sizes are worth it when you are reproducing a specific viewport — a client’s laptop, a kiosk screen, an embedded frame — or when you want a narrow window to force a responsive layout without emulating a particular phone.

Emulated devices

Choosing Emulate switches on the Phone model picker, which holds around 200 entries. Most exist in both orientations, listed as the device name and the same name with landscape appended.

The list covers, among others:

iPhone — 6 through 17, including the Plus, Pro, Pro Max and e variants, plus iPhone Air and both iPhone SE generations.
Pixel — 2 through 10, including Pro, Pro XL and a models.
Galaxy — S, Note and A series, the Tab tablets, and the folding Z Flip and Z Fold 6 and 7 with their separate cover screens.
iPad — generations 5, 6, 7 and 11, iPad Mini and iPad Pro 11.
Older reference devices — Nexus, Moto G4, Kindle Fire HDX, Lumia, BlackBerry — for testing what a small or dated screen does to a layout.

Folding phones have two entries

A Galaxy Z Fold 7 and a Galaxy Z Fold 7 Cover are different screens with different widths. If you are checking a responsive layout on a folding device, the cover screen is the one that will break first.

Which to choose

Archiving and compliance — desktop at 1920 × 1080. It is what most people saw, and it keeps files a sensible size for long retention.
Checking a responsive layout — emulate a real device rather than picking a narrow custom width. Emulation also changes the user agent and pixel density, so you see what the phone sees rather than a squeezed desktop.
Print or presentation — 2560 × 1440, or a higher device scale factor at 1920 × 1080. Both give you more pixels; the scale factor keeps the layout identical.

Above 2560 × 1440, the scale factor switches off

Device scale factor is only available for desktop image captures at or below 2560 × 1440; above that it is fixed at 1. Past that the resolution is already doing the job, and the two together would produce a file nobody wants.

Did this page answer your question?

Tell us what is missing