Compress Screenshots Without Blurry Text

Updated: September 29, 2026

Quick answer: Crop dead space first, export PNG or WebP at quality 90+, never shrink below twice the rendered width, skip JPEG for UI text, and read the smallest label at 100% zoom before uploading.

Screenshots fail compression the opposite way from photos. A photo degrades gracefully; a screenshot looks fine until a price turns into a smear. Its text was rendered at exact pixels, and any encoder that guesses at those pixels costs you.

The settings that keep text sharp

Screenshot type	Format	Quality floor	Avoid
UI, docs, settings panels	PNG or WebP	Lossless or 90+	JPEG, quality below 90
Charts and diagrams	PNG or WebP	Lossless	Resampling below text size
Screenshot with photo areas	WebP	85-90	JPEG below 85
Game or photo capture	WebP or JPEG	85	Aggressive one-shot resize

Two rules do most of the work. Keep flat-color screenshots lossless or at WebP 90+ — they encode to a fraction of the original anyway, so dropping quality buys almost nothing. And treat JPEG as a last resort: its 8×8 pixel blocks create ringing halos around letters that vanish at thumbnail size and glare at 100%.

Compress a screenshot in four steps

1. Crop before you compress. Trim browser chrome, blank margins, and unrelated panels — cropping removes bytes without touching a single text pixel.
2. Export PNG or WebP at 90+. Flat UI compresses well even losslessly; start high because there is little to gain below it.
3. Resize only to twice the display width. A screenshot shown at 700px stays sharp from a 1400px file; going lower makes the device blur your letters.
4. Read the smallest text at 100% zoom. Check the smallest label, price, or timestamp — compression shows there first, not in the headline.

Scale, don't resample

One big dimension cut is where screenshots die. Forcing a 2880px capture down to 600px destroys every 12px label in a single resample. If you must go small, step down in stages — 50%, then 75% of the remainder — and re-read the text after each pass.

When a long capture holds more detail than readers need, split it into sections instead of shrinking the whole thing. And keep the original capture: re-saving from an already-compressed copy compounds the damage, and sharp edges cannot be rebuilt from a blurry source.

Reading the symptoms

Symptom	Cause	Fix
Ghost outline around letters	JPEG ringing or WebP below 85	Re-export PNG or WebP 90+
Everything slightly soft	Upscaled or over-resampled	Start again from the master
Colored speckle on flat areas	Chroma noise from low quality	Raise quality or go lossless
Sharp locally, blurry on the page	Site serving a smaller variant	Check srcset, not the file

Compress without uploading the screen

Screenshots are the most revealing files people compress: internal dashboards, error logs, unreleased UI, a customer's personal data in a support ticket. Upload one to a typical online compressor and that screen is copied to a server you do not control.

LessMB compresses JPG, PNG, WebP, AVIF, and HEIC entirely in your browser with WebAssembly — nothing uploads, no sign-up, no watermark. Its SSIM check confirms fine text detail survived, and the same LessMB tab handles full batches. For store listings and marketing shots specifically, see App Store and Google Play screenshot sizes and limits.

FAQ

What quality should I use for screenshots?

Lossless PNG or WebP at 90+. Flat-color UI encodes cheaply, so high quality costs little and protects small text.

Why does text get fuzzy outlines after compression?

Lossy halos — usually JPEG. Re-export from the original at PNG or WebP 90+; sharpening cannot remove ringing.

Can I shrink a screenshot's dimensions?

Yes, down to about twice the rendered width. Below that, letters lose the pixels they need to stay crisp.

Is JPEG ever right for screenshots?

Only for mostly-photographic captures. Test the text regions at 100% zoom either way.

Related guides

• App Store and Google Play screenshot sizes and limits
• Compress PNG files and keep transparency