Why Your Full-Page Screenshot Came Out Blurry
The image looks soft, the text has fuzzy edges, and the page looked perfectly sharp in the browser. There are three separate causes, and they need different fixes.
·6 min read
The page was crisp in the browser. The screenshot of it is soft — text has fuzzy edges, thin lines have gone grey, and zooming in makes it worse rather than better.
There are three separate causes. They produce a similar-looking result and they need completely different fixes, so the first job is working out which one you have.
Cause one: the image is smaller than the screen it was taken from
Most laptop and phone screens pack two or three physical pixels into every pixel a web page thinks it has. A page that reports itself as 1,440 across is really being drawn at 2,880 or 4,320 on the glass. That ratio has a name — device pixel ratio — and it is the single most common reason a screenshot looks worse than the page.
If the capture records the page at its own reported size rather than the screen’s real one, every pixel of detail on that screen is thrown away before the file is written. Nothing downstream can bring it back.
How to recognize it. Check the pixel dimensions of the file. If a page you know is about 1,400 wide produced an image 1,400 wide, you are looking at a one-to-one capture on a screen that deserved two or three times that. On a retina or high-DPI display, a sharp capture of that page should be around 2,800 or 4,200 across.
Cause two: the page was too tall, so it got scaled down to fit
A full-page screenshot is drawn onto a canvas, and a canvas has a maximum size. Very long pages — a documentation page, a long thread, a report — can exceed it. When that happens there are only two honest options: cut the image off, or shrink the whole thing until it fits.
Shrinking keeps everything in the picture, which is usually what people want, but it is a real loss of detail across the entire image rather than in one region. A page that needed to come down by a third produces body text that is legible but not sharp.
How to recognize it. The softness is perfectly even from the top of the image to the bottom, and the page was unusually long. If the blur varies down the image, this is not your cause.
There is a fuller explanation of the height limit, including why a sharper screen runs out of room sooner, in why your full-page screenshot is cut off at the bottom.
Cause three: the browser was zoomed
Browser zoom changes what the page reports about itself. At 80% you fit more on screen, and a capture faithfully records that smaller rendering — everything is genuinely drawn at a smaller size, so the text has less detail in it to begin with. At 150% the opposite happens and the file is larger than you expected.
This one catches people because zoom is sticky per site in Chrome. You set it on one page weeks ago and it has been applied every visit since.
How to recognize it. Ctrl or Cmd and 0 resets zoom to 100%. If the page visibly jumps when you press it, that was your problem. Capture again afterwards.
The order to check them in
- Reset zoom. Ctrl or Cmd and 0. Ten seconds, and it rules out the cause that is easiest to fix.
- Check the file dimensions. If the width matches the page’s reported width rather than a multiple of it, the capture threw away your screen’s detail.
- Check the page length. If it ran to tens of thousands of pixels, something scaled it to fit, and the fix is to capture it in sections instead.
What to do when the page really is too long
Capture it in two or three passes rather than one. Scroll to a sensible break, take an on-screen capture of what is visible, move down, repeat. Each piece keeps full detail because none of them needs scaling. It is more work, and it is the only way to have both the whole page and the sharpness.
If the destination is print or a document rather than the web, a PDF is usually the better answer. A PDF holds the page at full resolution and stays sharp when someone zooms in, which is exactly the case where a scaled-down PNG disappoints.
What PageStill does
It captures at the screen’s own pixel ratio, so a high-DPI display produces a high-DPI image rather than a one-to-one one.
On a page tall enough to exceed the canvas limit it does not silently shrink the image. It tells you the page is too long, says how many pieces it would take at full sharpness, and lets you choose between splitting it and accepting a softer single image. The choice is yours and you make it knowing which one you picked.
Something out of date or wrong here? Device specs and interface details shift with every release. Tell me and I'll fix it.
Related reading
- Why Your Full-Page Screenshot Is Cut Off at the BottomThe same page captures fine on a desktop and loses its last third on a laptop. The reason is a height limit counted in device pixels, which means a sharper screen runs out sooner.
- Why Your Screenshot File Is So LargeTwenty megabytes for a picture of a web page, and the mail client will not send it. The size is not a mistake — it follows from what a full-page capture is. Here is how to bring it down.
- How to Save a Screenshot as a PDF in ChromeThere are two different things people mean by this, and picking the wrong one is why the result looks nothing like the page. Here is the difference, and the method for each.