Why Your Screenshots Go Blurry When You Share Them

September 12, 2026 · 6 min read

You take a screenshot of an error message. On your screen it is perfectly readable. You send it to a colleague and they cannot make out the text. You look at your copy again — still fine. Something happened in between.

Most articles about this tell you that platforms compress images, then suggest running the result through an AI enhancer. The first half is true and the second half mostly is not. Compression that has destroyed text cannot be undone, and the more useful question is why screenshots suffer so much more than photos do.

Screenshots are the worst case for JPEG

Photographs and screenshots look like the same kind of thing but compress completely differently.

JPEG was designed for photographs. It works by discarding detail your eye is unlikely to notice, and its assumptions are built around continuous tone — the gentle gradients of skin, sky and shadow. Two specific behaviours cause the problem:

It throws away colour detail. JPEG stores brightness at full resolution but colour at half resolution or less, because human vision is far more sensitive to brightness than to colour. On a photograph this is invisible. On coloured text against a coloured background it smears the edges.

It works in 8x8 pixel blocks. Within each block it keeps the broad shapes and discards fine variation. A hard black-on-white edge is nothing but fine variation, so the encoder approximates it and you get faint ripples spreading out from every letter. This is called ringing, and it is why compressed screenshots look slightly fuzzy and grubby around text rather than simply soft.

A photograph at quality 70 looks fine. A screenshot at quality 70 looks like it was faxed.

The fix is usually the format

Use PNG for screenshots. PNG is lossless — every pixel comes back exactly as captured — and it happens to compress flat colours and repeated patterns extremely well, which is precisely what an interface is made of. A screenshot of a settings page is often smaller as a PNG than as a JPEG, and perfectly sharp.

Most operating systems already save screenshots as PNG by default. The damage usually happens later, when something re-encodes it as JPEG on the way out.

If you need to compress a screenshot, use our compressor and choose PNG as the output format rather than JPG. If the file is still too big, reducing the dimensions costs you far less than dropping JPEG quality does.

WebP is a reasonable middle ground where it is accepted — it handles sharp edges better than JPEG at similar sizes.

What each app does to your screenshot

Messaging apps re-encode images as JPEG to save bandwidth. This is the most common cause. On WhatsApp, use the HD option before sending, or attach the file as a document instead of a photo, which skips the compression entirely — the recipient gets a download rather than a preview.

iMessage has a Low Quality Image Mode in Settings → Messages. If it is on, everything you send is heavily compressed. Worth checking, though most people find it already off and the compression happening anyway on cellular.

Social platforms resize to a fixed width and re-encode. Uploading at exactly the dimensions the platform displays gives it less to do.

Email does not usually compress attachments, but some clients offer to "resize images for faster sending". Decline it for screenshots.

Slack and Teams generally preserve the original if you upload as a file rather than pasting inline.

The high-resolution display problem

There is a second cause that has nothing to do with compression, and it is worth recognising because the fix is different.

A modern laptop or phone screen packs several hardware pixels into each logical point on the interface. A window that looks 1200 points wide can produce a screenshot 2400 pixels wide. That is good — you captured extra detail — but anything that then displays it at 1200 has to scale it down, and poor downscaling softens text.

If your screenshot looks sharp at full size and fuzzy in the document or chat where you pasted it, this is what happened. Resize it deliberately to the size it will actually be shown at, using the resizer, rather than letting whatever software it lands in stretch it around.

The reverse also causes trouble: capturing at a low screen resolution and then viewing on a bigger display means stretching too few pixels, which no format choice will fix.

Crop instead of shrinking

Most blurry screenshots are really screenshots of the wrong thing.

If you capture an entire 2560-pixel-wide desktop to show one error dialog, then send it into a chat window that displays images at 400 pixels, the dialog ends up about a twentieth of its original size. It was never going to be readable.

Crop to the part that matters before you send. A tight crop of one dialog stays legible at any size a chat window throws at it, and the file is smaller as a bonus. This single habit fixes more blurry screenshots than any tool does.

What about AI enhancers?

Several sites recommend running a degraded screenshot through an AI upscaler. Be realistic about what that can do.

An upscaler invents plausible detail; it does not recover the original. On a mildly soft image it can genuinely help. On text that compression has already turned to mush, it will produce sharp-looking characters that may be the wrong characters — which for a screenshot of an error code or a phone number is worse than a blurry image, because it looks trustworthy and is not.

If the text is unreadable, the right move is almost always to take the screenshot again from the source and send it properly. That takes ten seconds and is guaranteed to be correct.

A checklist before you send

  1. Crop to the relevant area rather than sending the whole screen
  2. Keep it as PNG — do not convert screenshots to JPG
  3. If it must be smaller, reduce the dimensions rather than the quality
  4. Send through a route that does not re-encode: as a file or document rather than an inline image
  5. Check the received copy once, then trust that route in future

The short version

Screenshots are made of exactly what JPEG handles worst: text, hard edges and flat colour. Keep them as PNG and most of the problem disappears. Crop tight so the important part survives being displayed small. And when an app has already destroyed the text, retake the screenshot rather than trying to repair it — nothing genuinely restores detail that has been thrown away.

Tools used in this guide