# Website to JPG: spot the difference by quality

> Which of six crops is the lossless PNG? A website-to-JPG test at 12 quality levels, with bytes for each and the level to pick for email, slides and proof.

Spot the difference by Serghei Pogor, founder of CurlShot (https://curlshot.com/about/serghei-pogor). Published 13 November 2026. Page for people: https://curlshot.com/blog/website-to-jpg-quality

For a website to JPG, quality 80 is a good default: on a 1280 x 720 test page it gave 85,076 bytes against 429,833 for the PNG, and at actual size I saw no difference at 80 or even 40; the first one I saw was at 20, as bands in a gradient. Enlarged three times, the damage shows first on thin coloured lines (from quality 80), then on small text and button edges (from 40). Use PNG for pages of text and for evidence, quality 60 to 70 when size matters, and nothing below 50 for text. Measured on 12 November 2026.

## Key facts

- Quality 80 gave 85,076 bytes on the test page, 20 percent of the 429,833 byte PNG. Quality 95 gave 167,475, nearly twice as much, for 1.3 dB more PSNR.
- Photo areas hid the loss until quality 20; a 1 px teal line kept 58 percent of its colour at 80 and 26 percent at 10. Thin lines and small text are the first to go.
- A text-only page was smaller as PNG (96,203 bytes) than as JPEG at quality 90 (112,256); a photo page was 16 times smaller as JPEG at 80 than as PNG.
- Even quality 95 changed the pixels (34.2 dB against the PNG), so keep PNG for evidence and for pictures you compare.
- CurlShot takes image_quality from 1 to 100, default 80. When image_width or image_height is set, the JPEG is resized and encoded by mozjpeg, 16 to 43 percent smaller at the same number.

## The exercise
The page has four boards. Each shows the same 180 x 120 pixels of one test page in six ways: the lossless PNG and five JPEGs. The reader picks the tile they think is the PNG, and the quality and bytes of every tile are revealed. Here the answers are written out.
### Round 1: Small text
A serif heading and two lines of 14 px grey text, from the left column of the test page. Six tiles, one of them the PNG. The space around the letters. A JPEG puts a faint grey haze next to sharp edges, and the haze grows as the quality drops.
| Tile | What it was | Crop PSNR vs PNG | Whole page file |
| --- | --- | --- | --- |
| A | JPEG, quality 40 | 23.6 dB | 47,636 bytes |
| B | The PNG | reference | 429,833 bytes |
| C | JPEG, quality 10 | 20.9 dB | 21,003 bytes |
| D | JPEG, quality 80 | 25.8 dB | 85,076 bytes |
| E | JPEG, quality 20 | 22.3 dB | 31,894 bytes |
| F | JPEG, quality 60 | 24.6 dB | 60,324 bytes |
Text is forgiving down to quality 60: at this zoom I could not tell 80 or 60 from the PNG. The first faint haze I saw was at 40, and 20 and 10 are plainly smeared. The crop PSNR falls from 25.8 dB at 80 to 20.9 dB at 10.
### Round 2: A button on a coloured panel
The orange "Book the trail" button on the blue panel, with the panel edge on the left. Six tiles, one of them the PNG. The border between orange and blue. JPEG keeps brightness at full detail and colour at half detail, so colour spills over an edge.
| Tile | What it was | Crop PSNR vs PNG | Whole page file |
| --- | --- | --- | --- |
| A | JPEG, quality 20 | 22.2 dB | 31,894 bytes |
| B | JPEG, quality 80 | 25.7 dB | 85,076 bytes |
| C | The PNG | reference | 429,833 bytes |
| D | JPEG, quality 10 | 21.4 dB | 21,003 bytes |
| E | JPEG, quality 60 | 24.6 dB | 60,324 bytes |
| F | JPEG, quality 40 | 23.9 dB | 47,636 bytes |
The edge held at 80 and 60. At 40 I saw a faint halo around the button, and at 20 and 10 the orange smudges into the blue and the white label turns noisy. Every file here keeps colour at half detail, even the quality 95 one (see the encoding table below).
### Round 3: A photo and a mountain edge
A mountain peak against a cloudy sky, from the hero picture, which carries fine film grain. Six tiles, one of them the PNG. Two things: the grain in the sky, and square blocks in smooth areas. JPEG throws grain away first and builds blocks last.
| Tile | What it was | Crop PSNR vs PNG | Whole page file |
| --- | --- | --- | --- |
| A | JPEG, quality 60 | 38.2 dB | 60,324 bytes |
| B | JPEG, quality 10 | 30.9 dB | 21,003 bytes |
| C | JPEG, quality 40 | 36.9 dB | 47,636 bytes |
| D | The PNG | reference | 429,833 bytes |
| E | JPEG, quality 80 | 40.4 dB | 85,076 bytes |
| F | JPEG, quality 20 | 34.3 dB | 31,894 bytes |
This is the case JPEG is made for, and the loss is still there: every JPEG in the set smooths the grain, quality 80 included, and that is the only tell between the PNG and 80. Blocks of 8 x 8 pixels show in the sky at 20 and are plain at 10. The crop PSNR stays above 34 dB down to 20.
### Round 4: Thin coloured lines
Three 1 and 2 px lines (orange, dashed blue, teal) on a light grid, from the chart card. Six tiles, one of them the PNG. The colour of the thinnest line. A line one pixel wide has almost no colour data of its own, and JPEG keeps colour at half detail.
| Tile | What it was | Crop PSNR vs PNG | Line colour left | Whole page file |
| --- | --- | --- | --- | --- |
| A | The PNG | reference | 100% | 429,833 bytes |
| B | JPEG, quality 40 | 27.3 dB | 43% | 47,636 bytes |
| C | JPEG, quality 80 | 30.4 dB | 58% | 85,076 bytes |
| D | JPEG, quality 20 | 25.7 dB | 34% | 31,894 bytes |
| E | JPEG, quality 10 | 24.3 dB | 26% | 21,003 bytes |
| F | JPEG, quality 60 | 28.4 dB | 48% | 60,324 bytes |
The hardest crop. Already at 80 the teal line is paler and the orange line has a faint halo. At 40 the teal line is nearly grey. The colour column counts how much of the line colour is left, averaged over the 780 pixels where the PNG has a strong colour: 58 percent at 80, 26 percent at 10.
## Bytes at 12 quality levels
One 1280 x 720 page. The PNG was 429,833 bytes. PSNR compares each JPEG with the PNG; a higher number is closer.
| Quality | Bytes | Share of the PNG | PSNR (dB) |
| --- | --- | --- | --- |
| 95 | 167,475 | 39% | 34.2 |
| 90 | 120,120 | 28% | 33.8 |
| 85 | 98,218 | 23% | 33.3 |
| 80 | 85,076 | 20% | 32.9 |
| 75 | 76,395 | 18% | 32.5 |
| 70 | 70,494 | 16% | 32.2 |
| 60 | 60,324 | 14% | 31.5 |
| 50 | 53,996 | 13% | 31.0 |
| 40 | 47,636 | 11% | 30.5 |
| 30 | 40,573 | 9% | 29.9 |
| 20 | 31,894 | 7% | 28.8 |
| 10 | 21,003 | 5% | 27.2 |
From quality 95 to 80 the file fell 49 percent for 1.3 dB. From 80 to 50 it fell a further 37 percent for 1.9 dB, and from 50 to 10 a further 61 percent for 3.8 dB.
## The same quality, on three pages
| Page | PNG | JPEG 90 | JPEG 80 | JPEG 60 | JPEG 40 |
| --- | --- | --- | --- | --- | --- |
| The mixed page (photo, text, chart, button) | 429,833 | 120,120 | 85,076 | 60,324 | 47,636 |
| A page of text and one small table | 96,203 | 112,256 | 84,422 | 61,620 | 49,640 |
| A page that is one big picture | 829,993 | 93,475 | 51,860 | 30,897 | 22,503 |
## Two JPEG paths in one renderer
| Request | Who writes the JPEG | Mode | Colour detail |
| --- | --- | --- | --- |
| No image_width or image_height | Chromium writes the JPEG itself | Baseline | 4:2:0 (colour at half detail) |
| image_width or image_height set | Chromium takes a PNG, sharp resizes it and writes the JPEG with mozjpeg | Progressive | 4:2:0 (colour at half detail) |
| Quality | Bytes, no image_width | Bytes, with image_width | Smaller by | PSNR without / with (dB) |
| --- | --- | --- | --- | --- |
| 95 | 167,475 | 135,094 | 19% | 34.2 / 34.0 |
| 90 | 120,120 | 100,385 | 16% | 33.8 / 33.5 |
| 85 | 98,218 | 81,512 | 17% | 33.3 / 33.1 |
| 80 | 85,076 | 70,792 | 17% | 32.9 / 32.6 |
| 75 | 76,395 | 61,859 | 19% | 32.5 / 32.2 |
| 70 | 70,494 | 55,933 | 21% | 32.2 / 31.9 |
| 60 | 60,324 | 46,889 | 22% | 31.5 / 31.2 |
| 50 | 53,996 | 41,120 | 24% | 31.0 / 30.5 |
| 40 | 47,636 | 35,284 | 26% | 30.5 / 30.0 |
| 30 | 40,573 | 28,847 | 29% | 29.9 / 29.2 |
| 20 | 31,894 | 21,228 | 33% | 28.8 / 27.9 |
| 10 | 21,003 | 12,065 | 43% | 27.2 / 25.9 |
At the same quality number the image_width path was 16 to 43 percent smaller and about 0.2 to 1.3 dB lower in PSNR.
## Which quality for which use
| Use | Pick | Why |
| --- | --- | --- |
| Send a page in an email, a chat or a slide | JPEG, quality 80 (the default) | On the mixed page it was 85.1 KB, 20 percent of the PNG, and at actual size I saw no difference. |
| A size limit or a grid of many pages | JPEG, quality 60 to 70, and set image_width | Quality 60 was 60.3 KB; with image_width set the same number gave 46.9 KB. Thin lines lose colour first, so check a chart before you go lower. |
| A page that is mostly photographs | JPEG, quality 70 to 80 | The photo page was 51.9 KB at 80 and 830 KB as PNG, 16 times more. |
| A page that is mostly text, tables or a dashboard | PNG, or JPEG at 90 and up | The text page was 96,203 bytes as PNG and 112,256 as JPEG at 90, so JPEG saved nothing and added a haze. |
| Evidence, an archive, a picture you will compare with another | PNG | Even quality 95 changed the pixels (34.2 dB against the PNG). A comparison reads that noise as a difference, and a record of a page should not be edited by its encoder. |
| Anything with small text or thin coloured lines | Never below quality 50 | In the boards the text gets a haze at 40, the lines lose colour from 80, and quality 30 and lower smears both. |
## One request
```bash
curl "https://curlshot.com/api/v1/screenshot?access_key=YOUR_ACCESS_KEY&url=https://example.com&format=jpeg&image_quality=80" \
  --output page.jpg
```
`image_quality` takes 1 to 100 and defaults to 80. `jpg` is accepted as another spelling of `jpeg`. A JPEG cannot be transparent: `omit_background` with `format=jpeg` is refused with invalid_options. Try it on the [web page to JPG tool](https://curlshot.com/tools/webpage-to-jpg) or the [URL to image tool](https://curlshot.com/tools/url-to-image); the Free plan needs no card, see [pricing](https://curlshot.com/pricing).
## How it was tested
A test page was served from a local port and drawn by the renderer process of the product (the code the service runs), Chromium 153.0.8010.12 and sharp 0.35.5 on a Linux server, at 1280 x 720 pixels. The picture was taken once as PNG and then as JPEG at 12 quality levels, on both of the JPEG paths the renderer has. Each file was read back: its bytes from the file, its pixels with sharp, its JPEG header for the encoding mode. The renderer was the product's own process, started locally; no request went to the hosted service. The test page is made up, with a generated picture, and shows what Chromium and these encoders do with those shapes, not with your page. The columns that say what I saw are my own reading of crops enlarged three times; the PSNR and byte columns are measured.

## Questions

### How do I turn a website into a JPG?

Paste the address into the CurlShot web page to JPG tool and download the file, or send a request with format=jpeg. The quality is image_quality, from 1 to 100, and it defaults to 80.

### What JPEG quality should I use for a screenshot of a web page?

Start at 80. On a test page that gave 85.1 KB against 430 KB as PNG. Use 60 to 70 when the file must be small, 90 or more for pages that are mostly text, and PNG when the picture is evidence.

### Is a JPG or a PNG better for a web page?

It depends on the page. A photo-heavy page was 16 times smaller as JPEG at quality 80. A page of plain text was 96,203 bytes as PNG and 112,256 as JPEG at 90, so PNG was both smaller and sharper.

### Why is the text in my JPG screenshot blurry or hazy?

JPEG compresses 8 x 8 pixel blocks and leaves a faint haze beside sharp edges. In the test the haze appeared around quality 40 and was plain at 20. Raise image_quality, or use PNG for a page of text.

### Can a JPG screenshot have a transparent background?

No. JPEG has no transparency, and CurlShot refuses omit_background together with format=jpeg with an invalid_options error. Use png or webp for a transparent picture.

## Sources

1. Playwright, "Page: screenshot (quality option)": https://playwright.dev/docs/api/class-page (checked 12 November 2026)
2. sharp, "Output options: jpeg and the mozjpeg defaults": https://sharp.pixelplumbing.com/api-output/ (checked 12 November 2026)

## Go deeper

- [Web page to JPG](https://curlshot.com/tools/webpage-to-jpg)
- [URL to image](https://curlshot.com/tools/url-to-image)
- [All options](https://curlshot.com/docs/options)
- [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.
- [URL to image quiz: 8 questions, explained](https://curlshot.com/blog/url-to-image-quiz.md): Eight requests that turn a URL into an image. Guess what each one returns, then read why: formats, size, crop, full page, cache. Score yourself.
- [Website thumbnail sizes: how small can it get](https://curlshot.com/blog/website-thumbnail-sizes.md): Thumbnail sizes for link lists, cards and previews, the viewport to capture from, 2x files for sharp screens, and the width where text stops being readable.
