Screenshot resolution, pixel density and Retina displays
Short answer
On a Retina or high-DPI screen, the browser uses a devicePixelRatio greater than 1 (typically 2). This means every CSS pixel maps to multiple physical pixels, so a 1440px wide window produces a 2880px wide capture. The resulting image has double the linear resolution, four times the total pixels, and significantly larger file sizes. This higher resolution halves the maximum page height you can capture before hitting Chrome's 16,384px canvas limit.
Updated 14 August 2026Written by the Full Page Screenshot team
What devicePixelRatio does to your capture
When you take a full-page screenshot on a modern laptop or desktop with a high-density display, the resulting image is often much larger than the visible viewport suggests. This happens because of the devicePixelRatio property, which defines how many physical screen pixels correspond to a single CSS pixel.
On a standard 96 DPI display, the ratio is 1. On most Retina MacBook Pros and high-end Windows laptops, it is 2. On some mobile devices or ultra-high-density monitors, it can be 3 or even higher. Full Page Screenshot captures the rendered DOM at its actual physical resolution, not its CSS layout resolution.
Resolution impact by devicePixelRatio
- Standard Display (1x)
- A 1440px wide window captures a 1440px wide image.
- Retina / High DPI (2x)
- A 1440px wide window captures a 2880px wide image.
- Ultra HD (3x)
- A 1440px wide window captures a 4320px wide image.
- Total Pixel Count
- Doubling the linear resolution quadruples the total number of pixels in the image.
Why your screenshot file size doubles (or quadruples)
It is common to ask why is my screenshot twice the size when I switch from a standard monitor to a Retina display. The answer lies in the math of pixel density. If you double the width and double the height, you are capturing four times as many pixels.
For PNG files, this increase in pixel count directly translates to a larger file size. While PNG compression helps, a 4x increase in data usually results in a file that is roughly 3x to 4x larger than its 1x counterpart. For JPG exports, the effect is similar, though compression ratios may vary slightly depending on image content. If you are worried about storage or transfer speeds, see our guide on what to do if your screenshot is too large to save.
When to capture at 1x vs native resolution
- Capture at Native (High) Resolution When
- You are a designer needing crisp text and sharp UI elements for client presentations. You need to inspect fine details like icon edges or typography rendering. You are capturing for print materials where low resolution would look blurry.
- Capture at 1x (Scaled Down) When
- You need to capture extremely long pages that would otherwise break the canvas limit. You are sharing screenshots via email or chat and want to minimize file size. You only need to verify layout structure rather than visual fidelity. Developers documenting API responses or JSON structures often prefer 1x for clarity and speed.
How Full Page Screenshot handles high DPI captures
Full Page Screenshot respects the browser's native rendering context. It does not artificially downscale the capture to 1x unless explicitly configured to do so. This ensures that what you see is exactly what the user sees on their high-DPI screen. For designers, this accuracy is non-negotiable. For developers, it provides a true representation of the rendering pipeline.
Where to go next
If this did not resolve it, the next places to look are full page capture, When a full page screenshot is too large to use, and full page screenshots for designers.
Frequently asked questions
Why is my screenshot twice the size on a Retina display?
Because your devicePixelRatio is likely 2. This means the browser renders the page using 2 physical pixels for every 1 CSS pixel. A 1440px wide window therefore becomes a 2880px wide image, containing four times the total pixels and a significantly larger file size.
Does Full Page Screenshot scale down Retina screenshots automatically?
No. Full Page Screenshot captures the page at its native physical resolution. If you need a smaller file or want to bypass canvas limits, you should use the 1x export option if available in your settings, or manually resize the image afterward.
How does high DPI affect the maximum page height I can capture?
It reduces it. Since Chrome limits a single canvas to 16,384 pixels per side, a 2x Retina display means you can only capture half the vertical CSS height compared to a 1x display before hitting the limit. Long pages may require scrolling or splitting.
Is a high DPI screenshot better for design work?
Yes. Designers benefit from high DPI captures because text remains crisp and sharp, avoiding the blurriness that occurs when a 1x screenshot is zoomed in. It accurately reflects how the site appears on modern high-density devices.
Can I force a 1x screenshot on a Retina display?
Full Page Screenshot captures at the browser's native resolution by default. To get a 1x equivalent, you would typically need to change your system display scaling settings or use a tool that supports explicit downscaling during the capture process.
Sources
Primary documentation for the browser behaviour described above. Every link was checked against a live search index when this page was last updated.
Capture your first full page screenshot
Free, no account, and nothing leaves your computer.
Keep reading
Full page capture
The capture engine: measuring the document, pinning the page, photographing each screenful and joining them without seams.
When a full page screenshot is too large to use
An 80 MB PNG that no tracker will accept and no viewer will open. Four ways to reduce a full page capture without losing what matters.
Full page screenshots for designers
Capture reference pages at full height and real pixel density for moodboards, competitive audits and design reviews.