# How much storage do daily screenshots take?

> Measured sizes of 7 real pages as PNG, JPEG and WebP at 4 widths, plus an estimator: GB a month, a year and held, with and without dedupe.

Estimator by Serghei Pogor, founder of CurlShot (https://curlshot.com/about/serghei-pogor). Published 15 November 2026. Page for people: https://curlshot.com/blog/screenshot-storage-estimator

Storage is pictures a day times the size of one picture times the days you keep them. At 1280 px wide, the mean of the seven pages measured was 231 KB as PNG, 155 KB as JPEG and 103 KB as WebP for a first screen, and 1.68 MB, 904 KB and 610 KB for a whole page. A CurlShot plan counts one screenshot per render whatever its size, so file size changes only what you store.

## Key facts

- At 1280 px wide, 100 captures weighed 10.3 MB as WebP first screens and 168 MB as PNG whole pages: about 16 times apart for the same pages.
- WebP at quality 80 was smaller than JPEG at quality 80 in 56 of 56 measured cases, and 20% to 96% of the PNG.
- A whole page weighed 5.9 to 7.2 times its first screen, so the choice between the two moves storage more than the choice of width.
- JPEG was as large as PNG or larger in 6 of 56 cases, on text-heavy pages. A WebP file cannot be longer than 16,383 px, so a very long page must be cut.
- A hash of the file finds a repeat only when every pixel matched: 3 of 7 pages gave the same file five times over 12 minutes, and 4 did not.
- One successful render is one screenshot on a CurlShot plan whatever its size, and dedupe does not lower the count of screenshots you ask for.

## The formula

Pictures a day = pages × captures per page a day × widths. Bytes written a day = pictures a day × the size of one picture. Storage held at once = bytes written a day × days kept, once that many days have passed. Older pictures are deleted, so the total stops growing. Dedupe means dropping a capture that is byte for byte the same as the one before; it lowers bytes, not the number of screenshots you ask for. A GB here is 10^9 bytes, a month is 30 days.

## What 100 captures weigh at 1280 px

The mean of the seven pages measured.

| What is captured | Format | One picture | 100 pictures |
| --- | --- | --- | --- |
| First screen | WebP | 103 KB | 10.3 MB |
| First screen | JPEG | 155 KB | 15.5 MB |
| First screen | PNG | 231 KB | 23.1 MB |
| Whole page | WebP | 610 KB | 61.0 MB |
| Whole page | JPEG | 904 KB | 90.4 MB |
| Whole page | PNG | 1.68 MB | 168 MB |

The dearest way to store the same 100 captures is about 16 times the cheapest.

## One capture of each page at 1280 px

| Page | What it is | Whole-page height (px) | First screen PNG | First screen JPEG | First screen WebP | Whole page PNG | Whole page JPEG | Whole page WebP |
| --- | --- | --- | --- | --- | --- | --- | --- | --- |
| example.com | A nearly empty page | 1,024 | 86.3 KB | 62.2 KB | 40.7 KB | 86.3 KB | 62.2 KB | 40.7 KB |
| Hacker News front page | A plain text list | 1,183 | 232 KB | 142 KB | 100 KB | 248 KB | 157 KB | 108 KB |
| MDN: CSS reference | Documentation, mostly text | 4,274 | 194 KB | 205 KB | 138 KB | 532 KB | 549 KB | 369 KB |
| GitHub repository page | A web app with a long README | 8,527 | 222 KB | 164 KB | 99.7 KB | 1.19 MB | 936 KB | 568 KB |
| Wikipedia: Web server | A very long article | 16,000 | 392 KB | 193 KB | 133 KB | 3.96 MB | 2.78 MB | 1.95 MB |
| BBC News front page | News with many photos | 6,630 | 253 KB | 148 KB | 96.7 KB | 2.91 MB | 1.04 MB | 679 KB |
| Wikipedia: Featured pictures | A photo gallery | 6,905 | 241 KB | 169 KB | 112 KB | 2.81 MB | 808 KB | 555 KB |

Wikipedia: Web server is 29,470 px tall at 1280 px wide. The whole-page captures of it were cut at 16,000 px, because a WebP file can be at most 16,383 px on a side: at 20,000 px the WebP encoder refused it.

## Mean size by width

| Width (px) | First screen PNG | First screen JPEG | First screen WebP | Whole page PNG | Whole page JPEG | Whole page WebP |
| --- | --- | --- | --- | --- | --- | --- |
| 390 | 116 KB | 79.4 KB | 57.6 KB | 1.01 MB | 573 KB | 412 KB |
| 768 | 174 KB | 116 KB | 80.5 KB | 1.53 MB | 809 KB | 571 KB |
| 1280 | 231 KB | 155 KB | 103 KB | 1.68 MB | 904 KB | 610 KB |
| 1920 | 250 KB | 170 KB | 109 KB | 1.80 MB | 1.00 MB | 656 KB |

## Format and quality

- WebP at quality 80 was smaller than JPEG at quality 80 in 56 of 56 cases, and smaller than PNG in 56 of 56. It was 20% to 96% of the PNG.
- JPEG was 28% to 125% of the PNG, and as large as the PNG or larger in 6 of 56 cases: MDN: CSS reference and BBC News front page.
- Quality, as a share of the size at quality 80 (mean of the seven pages, 1280 px):

| Format | Capture | Quality 60 | Quality 90 |
| --- | --- | --- | --- |
| JPEG | First screen | 72% | 135% |
| JPEG | Whole page | 72% | 135% |
| WebP | First screen | 78% | 135% |
| WebP | Whole page | 77% | 136% |

## Do identical captures come out as identical files

| Page | Different pictures in 3 captures, 4 seconds apart | Different pictures in 5 captures, 3 minutes apart |
| --- | --- | --- |
| example.com | 1 | 1 |
| Hacker News front page | 1 | 4 |
| MDN: CSS reference | 1 | 1 |
| GitHub repository page | 1 | 2 |
| Wikipedia: Web server | not run | 5 |
| BBC News front page | 1 | 5 |
| Wikipedia: Featured pictures | 1 | 1 |

A page that did not change gave the same bytes each time, so a hash of the file finds a repeat. A page with a clock, a news list or a rotating block gave a new file every time. The share of captures that repeat over days is yours to enter: it was not measured here.

```bash
#!/usr/bin/env bash
# keep.sh NEW_FILE DIR: keep NEW_FILE in DIR only when it differs from the last kept picture.
set -euo pipefail
new=$1
dir=$2
mkdir -p "$dir"
hash=$(sha256sum "$new" | cut -d' ' -f1)
if [ -f "$dir/latest.sha256" ] && [ "$hash" = "$(cat "$dir/latest.sha256")" ]; then
  rm "$new"
  echo "same as last, dropped"
else
  mv "$new" "$dir/$(date +%F-%H%M%S).png"
  echo "$hash" > "$dir/latest.sha256"
  echo "kept"
fi
```

The script was run four times on the lab host with small files: the same bytes twice (the second was dropped), then different bytes (kept), then the first bytes again (kept, because it differs from the last kept picture). It passed bash -n.

## Three setups, worked out

| Setup | Screenshots a month | Smallest plan | New data a month | Held at once | Held, with dedupe | Storage a month, with dedupe |
| --- | --- | --- | --- | --- | --- | --- |
| Landing page watch: 20 pages, once a day, desktop and phone, WebP first screens, kept 30 days, 80% identical | 1,200 | Starter | 96.4 MB | 96.4 MB | 19.3 MB | < $0.01 |
| Agency, client sites: 200 pages, once a day, desktop and phone, JPEG whole pages, kept 90 days, 60% identical | 12,000 | Growth | 8.86 GB | 26.6 GB | 10.6 GB | $0.16 |
| Proof archive: 100 pages, four times a day, desktop, PNG whole pages, kept 2 years, 50% identical | 12,000 | Growth | 20.1 GB | 490 GB | 245 GB | $3.67 |

Storage is priced at $0.015 per GB-month, the Cloudflare R2 Standard price read on 12 November 2026. One successful render is one screenshot of your plan, whatever its size, so a bigger file never uses more of the plan. Plans: Free 100, Starter 3,000, Growth 15,000, Scale 60,000 screenshots a month. See [pricing](https://curlshot.com/pricing).

## How it was measured

Seven public pages were opened in Chromium at four widths (390, 768, 1280 and 1920 px) with a window 1024 px tall, scale 1. Each page was scrolled down and back to load lazy pictures, then captured twice: the first screen (1024 px tall) and the whole page (cut at 20,000 px, or 16,000 px for the long article). Each capture was written the way the renderer writes it: PNG straight from Chromium, JPEG straight from Chromium at the quality given, and WebP re-encoded from the PNG at the quality given. The size of every file was recorded in bytes. Quality 80, the default of the image_quality option, was used everywhere; 60 and 90 were added at 1280 px. Tool versions: Chromium 153.0.8010.12, Playwright 1.63.0, sharp 0.35.5 (libwebp 1.6.0). Run on 12 November 2026. Seven pages are a small sample, and a page changes: the same address weighs something different next month. Scale 2 (retina) captures, pages behind a login, transparent PNGs and video were not measured. The figures are the size of the file on disk, before any compression your storage provider applies, and before the extra cost of backups or copies.

## Questions

### How much storage does one website screenshot take?

It depends on the page, the width and the format. At 1280 px wide the mean of seven real pages was 103 KB as a WebP first screen and 1.68 MB as a PNG whole page, measured on 12 November 2026. Single files in the run ranged from 37.3 KB to 4.32 MB.

### Which screenshot format uses the least storage?

In this run WebP at quality 80 was the smallest in 56 of 56 cases against JPEG at quality 80, and 20% to 96% of the PNG. WebP files cannot be longer than 16,383 px, so a very long page needs JPEG or a lower full_page_max_height.

### How do I estimate monthly screenshot storage?

Multiply pages, captures per page a day and widths to get pictures a day, multiply by the average size of one picture, then by 30 for a month or by the days you keep each file for the amount held at once. The estimator on this page does it from the measured sizes.

### Does deduplicating screenshots save space?

Only for pages that do not change. In the lab, captures of the same unchanged page came out as identical files, so a hash of the file finds repeats. 4 of 7 pages gave a different file at least once in five captures over 12 minutes. Deduplication saves storage, not screenshots: each capture still counts on your CurlShot plan.

### Does a bigger screenshot use more of my plan?

No. On CurlShot, one successful render is one screenshot whatever its size, and failed renders and cache hits are not counted. Only the storage you keep grows with file size.

## Sources

1. Cloudflare Docs, "Cloudflare R2 pricing: Standard storage $0.015 per GB-month, 10 GB-month free": https://developers.cloudflare.com/r2/pricing/ (checked 12 November 2026)

## Go deeper

- [Bulk screenshots](https://curlshot.com/tools/bulk-screenshots)
- [Screenshot API](https://curlshot.com/tools/screenshot-api)
- [Usage and limits](https://curlshot.com/docs/usage-and-limits)
- [Pricing](https://curlshot.com/pricing)

## Read next

- [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.
- [Website change monitoring with screenshots](https://curlshot.com/blog/website-change-monitoring-with-screenshots.md): How to get told when a web page changes: the capture and compare loop, three ways to detect a change, a noise checklist, a cron and Node.js setup, and tools.
- [How to screenshot a list of URLs in bulk](https://curlshot.com/blog/bulk-screenshots-list-of-urls.md): Screenshot hundreds or thousands of URLs: a queue simulator that says how long it takes, a short Node.js script, and what fails at scale.
