Bulk Captures
Windows 10 & 11 Buy license · $39.95
Website screenshots

How to Screenshot a Website at Different Screen Sizes on Windows

Screenshot a website at different screen sizes, from phone to desktop widths. Which viewports to pick, how to use DevTools, and how to batch them all.

Updated 5 minute read The Bulk Captures team

To screenshot a website at different screen sizes, render the page at each viewport width you care about, typically a desktop, a laptop, a tablet and a phone, and capture each one. You can do this one size at a time in your browser's developer tools, or capture every page at every width in a single batch with a screenshot tool that supports multiple viewports. This guide covers which sizes to choose, both methods, and how to keep the results organized.

Why screen size changes the screenshot

Most websites are responsive: their layout changes depending on the width of the browser window. A three-column desktop layout becomes a single column on a phone, menus collapse into a hamburger icon, and images are swapped or hidden. A desktop screenshot tells you nothing about how the page looks on a phone, which is where most visitors to many sites arrive.

Capturing the same page at several widths lets you:

  • Spot layout bugs, such as overlapping text or a button pushed off screen, at one particular size.
  • Show clients how their site works across devices in a report or proposal.
  • Keep a before-and-after record when a theme or template changes.
  • Present your work in a portfolio with desktop and mobile views side by side.

Which screen sizes to capture

You do not need dozens of sizes. A small set of widths covers the main breakpoints most sites use. Height matters less, because a full-page capture includes the whole length anyway.

Device classViewport widthWhy this size
Desktop monitor1920 pxThe most common full HD desktop resolution
Laptop1366 pxA long-standing common laptop width, just above many desktop breakpoints
Tablet (portrait)768 pxA classic tablet width and a common layout breakpoint
Phone390 pxTypical of current mid-size phones; most phones fall between 360 and 430 px

If you know your audience well, check your analytics for the most common screen sizes and add those. Our reference of common screen resolutions for testing lists more options.

Viewport width is not the same as screen resolution. A phone with a 1170 pixel wide display reports a viewport of around 390 CSS pixels, because each CSS pixel is drawn with several physical pixels. Always think in viewport widths for website screenshots.

Method 1: Browser developer tools, one size at a time

Chrome and Edge both include a device toolbar for previewing pages at other sizes.

  1. Open the page and press F12 to open developer tools.
  2. Press Ctrl+Shift+M to turn on the device toolbar.
  3. Choose a device from the Dimensions list, or select Responsive and type a width and height.
  4. Reload the page so it loads as it would on that size.
  5. Open the three-dot menu in the device toolbar and choose Capture full size screenshot for the full page, or Capture screenshot for the visible area.
  6. Change the width and repeat for each size.

This is accurate and needs nothing extra, but it is slow: four sizes for one page is four rounds of clicks, and each file lands in Downloads with a generic name. For a ten-page site that is forty screenshots to take and rename by hand. The DevTools approach is covered in more depth in our guide to full page screenshots in Chrome.

Method 2: Capture every size in one batch

When you need several pages, or you repeat the job after every release, a batch tool is much faster. Bulk Captures can capture each website at desktop, laptop, tablet and phone widths in the same run, using presets of 1920, 1366, 768 and 390 pixels or your own custom widths.

  1. Choose the URL capture mode and paste or load your list of pages.
  2. Tick the viewport widths you want. Each URL will be captured once per width.
  3. Choose full page or visible area only.
  4. Set a load delay of a few seconds so fonts and images finish loading.
  5. Set a naming pattern that includes the page and the width, and pick a format and folder.
  6. Click Capture.

Ten pages at four widths is forty consistently named images, captured while you do something else. For the general list-of-URLs workflow, see how to screenshot multiple websites at once.

Naming and organizing multi-size screenshots

With several images per page, the file name has to tell you both which page and which size. Two layouts work well:

  • One folder per width, such as 1920, 768 and 390, with the page name as the file name. This makes it easy to flip through every page at one size.
  • One folder per run, named with the date, with the width in each file name, such as example.com_390_001.png. This keeps all sizes of a page next to each other when sorted by name.

Pick one approach and stick with it, especially if you will compare runs over time.

In Bulk Captures you set this up once: a naming pattern built from tokens such as the domain, the date and a running counter, and an output folder that can include the date so every batch lands in its own sub-folder. Existing files are never overwritten; if a name is already taken, a number is added. That matters when you rerun the same list after a release and want to keep both sets side by side.

Limits to be aware of

  • Width is not everything. Most responsive layouts depend on width, but some sites also detect touch support or the device type and behave differently on a real phone. For final sign-off on critical pages, check on a real device too.
  • Pop-ups vary by size. Cookie banners and sign-up boxes often cover more of a phone screenshot than a desktop one. That is a real part of the visitor experience, so note it rather than hiding it.
  • Phone screenshots are tall. A single-column layout makes a full-page phone capture much taller than the desktop one. PNG handles very tall images; WebP has a lower maximum height.
  • Logged-in pages will not appear in a batch capture, which visits pages as a new visitor. Capture those in your browser with the device toolbar.

Once you have a set of sizes you trust, reuse it for every site and every release. Consistent sizes are what make screenshots comparable over time.

Frequently asked questions

What screen sizes should I test a website at?

A sensible starting set is 1920, 1366, 768 and 390 pixels wide, covering a desktop monitor, a laptop, a tablet in portrait and a modern phone.

Is a narrow browser window the same as a phone screenshot?

Close, but not identical. Width drives most responsive layouts, but some sites also check the device type, so a resized window can occasionally differ from a real phone.

Can I capture several screen sizes in one run?

Yes. Bulk Captures can capture each URL at desktop, laptop, tablet and phone widths in the same batch.

Get three guides like this every month, plus software update notices.Subscribe →