Images & photos · Browser Image & Drawing Editor
Why annotated screenshots go blurry: resampling and re-encoding
· How it works
image-editing canvas browser-processing
A crisp screenshot can come out soft after a quick edit, and the causes are almost always resizing or lossy encoding. This post separates the two, shows how to spot each, and explains how to keep interface text sharp.
Sharp in, soft out — the screenshot that looked fine until it was edited and saved
Screenshot sharpness has two different failure paths. Start with sharp in, soft out: the screenshot looked fine until it was edited and saved. For this soft-output diagnosis, the relevant mechanism is The document keeps true image dimensions while the visible preview scales to fit, so zoom softness is not automatically export damage. Resize resamples every layer, using repeated halving for large reductions and a final exact drawImage step.
Save one native-size PNG and one resized or lossy copy, then inspect interface lettering at one image pixel per screen pixel. PNG export receives no quality value; JPEG and WebP use a browser encoder quality between 0.1 and 1, defaulting to 0.92. A fitted preview is not a valid sharpness verdict, and no fixed compression saving follows from the quality slider.
Resampling: what happens when pixel dimensions change — interpolation, why a 1-pixel line cannot survive a 90 percent scale, and how HiDPI screens complicate this
Screenshot sharpness has two different failure paths. Resampling is the first culprit: changing pixel dimensions introduces interpolation, so a 1-pixel line cannot survive a 90 percent scale unchanged, and HiDPI screens can hide the difference. For this soft-output diagnosis, the relevant mechanism is Resize resamples every layer, using repeated halving for large reductions and a final exact drawImage step. PNG export receives no quality value; JPEG and WebP use a browser encoder quality between 0.1 and 1, defaulting to 0.92.
Save one native-size PNG and one resized or lossy copy, then inspect interface lettering at one image pixel per screen pixel. The repository promises no particular file-size saving, sharpening result or browser encoder artefact. A fitted preview is not a valid sharpness verdict, and no fixed compression saving follows from the quality slider.
Re-encoding: what lossy compression does to flat colour and text — ringing and blocking around high-contrast edges
Screenshot sharpness has two different failure paths. Re-encoding is the second culprit: lossy compression can introduce ringing and blocking around flat colour and high-contrast text. For this soft-output diagnosis, the relevant mechanism is PNG export receives no quality value; JPEG and WebP use a browser encoder quality between 0.1 and 1, defaulting to 0.92. The repository promises no particular file-size saving, sharpening result or browser encoder artefact.
Save one native-size PNG and one resized or lossy copy, then inspect interface lettering at one image pixel per screen pixel. The document keeps true image dimensions while the visible preview scales to fit, so zoom softness is not automatically export damage. A fitted preview is not a valid sharpness verdict, and no fixed compression saving follows from the quality slider.
Telling the two apart — zooming to 100 percent and reading the artefacts to know whether scale or format is the culprit
Screenshot sharpness has two different failure paths. Tell them apart by viewing the download at 100 percent and reading the artefacts: softened geometry points to scale, while halos or blocks around text point to encoding. For this soft-output diagnosis, the relevant mechanism is The repository promises no particular file-size saving, sharpening result or browser encoder artefact. The document keeps true image dimensions while the visible preview scales to fit, so zoom softness is not automatically export damage.
Save one native-size PNG and one resized or lossy copy, then inspect interface lettering at one image pixel per screen pixel. Resize resamples every layer, using repeated halving for large reductions and a final exact drawImage step. A fitted preview is not a valid sharpness verdict, and no fixed compression saving follows from the quality slider.
Worked example: the same dialog box exported at native size and after scaling — a side-by-side that shows where sharpness went
Screenshot sharpness has two different failure paths. Compare the same dialog box at native size and after scaling; the side-by-side makes the loss visible instead of blaming the preview. For this soft-output diagnosis, the relevant mechanism is The document keeps true image dimensions while the visible preview scales to fit, so zoom softness is not automatically export damage. Resize resamples every layer, using repeated halving for large reductions and a final exact drawImage step.
Save one native-size PNG and one resized or lossy copy, then inspect interface lettering at one image pixel per screen pixel. PNG export receives no quality value; JPEG and WebP use a browser encoder quality between 0.1 and 1, defaulting to 0.92. A fitted preview is not a valid sharpness verdict, and no fixed compression saving follows from the quality slider.
What this does not cover — sharpening filters, vector screenshots and upscaling that claims to add detail
Screenshot sharpness has two different failure paths. This does not cover sharpening filters, vector screenshots, or upscaling that claims to add detail. For this soft-output diagnosis, the relevant mechanism is Resize resamples every layer, using repeated halving for large reductions and a final exact drawImage step. PNG export receives no quality value; JPEG and WebP use a browser encoder quality between 0.1 and 1, defaulting to 0.92.
Save one native-size PNG and one resized or lossy copy, then inspect interface lettering at one image pixel per screen pixel. The repository promises no particular file-size saving, sharpening result or browser encoder artefact. A fitted preview is not a valid sharpness verdict, and no fixed compression saving follows from the quality slider.
Takeaway: keep native pixels, choose a lossless export — how to edit in the Browser Image & Drawing Editor without touching dimensions
Screenshot sharpness has two different failure paths. The takeaway is to keep native pixels and choose a lossless export when interface text matters. For this soft-output diagnosis, the relevant mechanism is PNG export receives no quality value; JPEG and WebP use a browser encoder quality between 0.1 and 1, defaulting to 0.92. The repository promises no particular file-size saving, sharpening result or browser encoder artefact.
Save one native-size PNG and one resized or lossy copy, then inspect interface lettering at one image pixel per screen pixel. The document keeps true image dimensions while the visible preview scales to fit, so zoom softness is not automatically export damage. A fitted preview is not a valid sharpness verdict, and no fixed compression saving follows from the quality slider.