# Six screenshot myths, tested in Chromium

> Six beliefs about website screenshots, run through Chromium on test pages: width, height, retina size, transparency, full page and repeatability.

Myth list by Serghei Pogor, founder of CurlShot (https://curlshot.com/about/serghei-pogor). Published 9 November 2026. Page for people: https://curlshot.com/blog/screenshot-myths-tested

None of six common beliefs about website screenshots held without a catch in a run on 9 November 2026. Three broke outright: a full-page picture can be wider than the viewport, a retina picture is 1.9 to 3.9 times the bytes and not twice, and a very tall viewport is not a full-page capture. Three held only in part: the same page gives the same picture only while nothing moves, PNG and JPEG went to 40,000 px tall while WebP stops at 16,383, and omit_background clears only the default white. CurlShot options named here come from its documentation and were not sent in this run.

## Key facts

- The same still page drawn 30 times gave 1 file; a page that prints the time gave 30. Compare captures with a tolerance, not by hash.
- A page with one 2,000 px block gave a 2,000 px wide full-page picture in a 1280 px viewport, and hiding the overflow on body or html changed nothing.
- PNG and JPEG came out whole at 40,000 px tall; WebP returned an empty file from 16,384 px, in line with the 16,383 px limit of the format.
- At device_scale_factor 2 the files grew from 1.9x to 3.9x, not 2x, because the picture holds four times the pixels.
- omit_background took 100 percent of a bare page transparent and 0 percent of a page that paints its own white. CurlShot counts one render as one screenshot whatever its size.

## The scoreboard
| Claim | Verdict | What the run showed |
| --- | --- | --- |
| The same page gives the same picture every time. | Partly true | True for a still page: 1 file in 30 captures. False as soon as something moves: up to 30 different files in 30. |
| The picture is as wide as the viewport. | Breaks | A full-page picture of a page with one 2,000 px block came out 2,000 px wide in a 1280 px viewport, and 4,000 px wide at scale 2. Hiding the overflow did not change it. |
| Chromium cannot draw a picture taller than 16,384 px. | Partly true | False for PNG and JPEG: 40,000 px tall came out whole. True for WebP: it stops at 16,383 px, and above that the file was empty. |
| A retina picture is twice the file size. | Breaks | It has four times the pixels at scale 2 and nine times at scale 3. The files grew 1.9 to 3.9 times at scale 2, depending on the page and the format. |
| omit_background makes any page transparent. | Partly true | It removes the browser default white and nothing else. A bare page came out fully transparent; a page that paints its own white came out with 0 percent transparent pixels. |
| A full-page picture is the same as a very tall viewport. | Breaks | On a page made of three 100vh sections, a 2,400 px viewport made the page 7,200 px tall, and the plain picture showed one third of it. |
## 1. The same page gives the same picture every time.
Each page was drawn 30 times, and the files were compared by hash.
| Page | Different files in 30 pictures |
| --- | --- |
| A still page: text and a gradient | 1 |
| A focused text field with a caret | 1 |
| A box that spins forever | 3 |
| A block that fades in over half a second | 4 |
| A line that prints the time of the load | 30 |
Do not compare captures byte for byte. Turn animation off with reduced_motion, wait for the element you care about with wait_for_selector, and compare with a tolerance.
## 2. The picture is as wide as the viewport.
Full-page pictures at a viewport of 1280 px.
| Page | Picture (width x height, px) |
| --- | --- |
| A block 2,000 px wide | 2,000 x 1,043 |
| The same, overflow-x: hidden on body | 2,000 x 1,043 |
| The same, overflow-x: hidden on html | 2,000 x 1,043 |
| The 2,000 px block at device_scale_factor 2 | 4,000 x 2,086 |
| A page whose blocks are 100% wide | 1,280 x 2,000 |
Find what is wider than the screen (document.documentElement.scrollWidth tells you), fix it, or ask for a fixed area with clip_width.
## 3. Chromium cannot draw a picture taller than 16,384 px.
Pages of one gradient, 400 px wide, drawn full page. "Empty file" means the browser returned no data.
| Page height (px) | PNG | JPEG | WebP |
| --- | --- | --- | --- |
| 8,000 | 8,000 | 8,000 | 8,000 |
| 16,383 | 16,383 | 16,383 | 16,383 |
| 16,384 | 16,384 | 16,384 | Empty file |
| 16,385 | 16,385 | 16,385 | Empty file |
| 20,000 | 20,000 | 20,000 | Empty file |
| 30,000 | 30,000 | 30,000 | Empty file |
| 40,000 | 40,000 | 40,000 | Empty file |
A 16,384 px page at scale 2 came out 32,768 px tall as PNG. The WebP format allows at most 16,383 px on a side.
Use png or jpeg for a tall page. The API cuts a full-page capture off at 20,000 px unless you set full_page_max_height, which goes up to 30,000.
## 4. A retina picture is twice the file size.
Bytes at scale 1, 2 and 3 for a 1280 x 800 viewport.
| Page | PNG 1 / 2 / 3 | PNG at 2 | JPEG 1 / 2 / 3 (quality 80) | JPEG at 2 |
| --- | --- | --- | --- | --- |
| Text page | 121 KB / 320 KB / 524 KB | 2.6x | 139 KB / 362 KB / 574 KB | 2.6x |
| Flat colour | 4.7 KB / 15.6 KB / 32.7 KB | 3.3x | 6.8 KB / 24.8 KB / 54.8 KB | 3.7x |
| Gradient | 185 KB / 719 KB / 1,489 KB | 3.9x | 15.4 KB / 38.6 KB / 69.9 KB | 2.5x |
| 900 coloured circles | 265 KB / 939 KB / 1,608 KB | 3.5x | 114 KB / 222 KB / 358 KB | 1.9x |
Use scale 2 where the picture is shown small and sharp, not by default. Of the four test pages, the one with many circles grew least as JPEG, 1.9 times. One render counts as one screenshot whatever its size, but a bigger file takes longer to send.
## 5. omit_background makes any page transparent.
Share of transparent pixels in an 800 x 400 picture, with the option on and off.
| Page | Option on | Option off |
| --- | --- | --- |
| A bare page, no background set | 100% | 0% |
| body { background: #fff } | 0% | 0% |
| html { background: #fff } | 0% | 0% |
| A full-height wrapper with a white background | 0% | 0% |
| A white 400 x 200 card on a bare page | 75.1% | 0% |
Check what paints the background: body, html or a wrapper. Your own page can clear it; a page you do not own stays opaque. Use png or webp.
## 6. A full-page picture is the same as a very tall viewport.
A page of three sections, each 100vh tall.
| Setup | Picture height (px) | Page height (px) |
| --- | --- | --- |
| Viewport 1280 x 800, full page | 2,400 | 2,400 |
| Viewport 1280 x 2400, no full page | 2,400 | 7,200 |
| Viewport 1280 x 2400, full page | 7,200 | 7,200 |
Keep a normal viewport and set full_page. If a hero is 100vh, expect it to be one screen tall in the result.
## How it was tested
Test pages were drawn by Chromium 153.0.8010.12 through Playwright, on a Linux server, with a new browser context for every picture. Each picture was read back from the file: its size from the header, its pixels with sharp, its identity as a SHA-256 hash. Every test page is small and made for the question, so the numbers show what Chromium does with that page, not with yours. The calls to the API of CurlShot were not sent in this run: the options named above come from its documentation. Start on the Free plan, which needs no card: see [pricing](https://curlshot.com/pricing).

## Questions

### Is a full-page screenshot the same as a very tall viewport?

No. In a run on 9 November 2026, a page of three 100vh sections was 2,400 px tall at a viewport of 1280 x 800 and 7,200 px tall at 1280 x 2400, because 100vh grew with the viewport. A normal viewport with full-page capture shows the page as a visitor scrolls it.

### Why is my full-page screenshot wider than the viewport?

Something on the page is wider than the screen, such as a table, a code block or an image with a fixed width. A full-page picture covers the whole scrollable area, and in the run here, hiding the overflow on body or html did not shrink it. Find the wide element and fix it, or capture a fixed area.

### How tall can a full-page screenshot be?

In Chromium, PNG and JPEG came out whole at 40,000 px in the run on 9 November 2026. WebP is limited to 16,383 px on a side by the format. CurlShot cuts a full-page capture at 20,000 px by default and allows up to 30,000 with full_page_max_height.

### Does a retina screenshot double the file size?

No. At device_scale_factor 2 the picture holds four times the pixels, and the files in the run grew from 1.9x to 3.9x, depending on the page and on whether it was PNG or JPEG.

### Why is my screenshot background not transparent?

omit_background removes the browser default white. If the page, its body or a wrapper paints its own background, that stays. A bare page came out fully transparent in the run, and a page with a white body came out with no transparent pixels. Use png or webp.

## Sources

1. Playwright, "Screenshots: full page screenshots": https://playwright.dev/docs/screenshots (checked 9 November 2026)
2. Google for Developers, "WebP FAQ: maximum pixel dimensions": https://developers.google.com/speed/webp/faq (checked 9 November 2026)

## Go deeper

- [Full-page screenshot](https://curlshot.com/tools/full-page-screenshot)
- [High-resolution screenshot](https://curlshot.com/tools/high-resolution-screenshot)
- [All options](https://curlshot.com/docs/options)
- [Pricing](https://curlshot.com/pricing)

## Read next

- [Why website screenshots look wrong, and the fixes](https://curlshot.com/blog/why-website-screenshots-look-wrong.md): A field guide to 11 ways a website screenshot goes wrong, from blank lazy images to cookie banners and cut-off pages, with the cause and the fix for each.
- [PNG, JPEG, WebP or PDF for website screenshots](https://curlshot.com/blog/png-jpeg-webp-pdf-for-screenshots.md): A decision flow, a comparison table and our own file-size measurements for choosing PNG, JPEG, WebP or PDF when you save a screenshot of a web page.
- [Visual regression testing, explained in pictures](https://curlshot.com/blog/visual-regression-testing-guide.md): How screenshot comparison works, why visual tests go flaky and how to fix each cause, the tools, and a set-up checklist with a Playwright example.
