Guide Clarity

Why are my screenshots blurry?

Screenshots can look blurry because the source was already soft, the image was resized or compressed after capture, or a preview is displaying it at an awkward scale. Compare the untouched local file with the version you are viewing or sharing before changing capture settings. The first stage where the detail changes tells you which fix to try.

Published

Share

For a support ticket or design review, the useful test is whether someone can read the error, label or annotation that explains the issue. A small chat preview and an enlarged slide can make the same file look very different.

Why are my screenshots blurry? Start with the original

Follow the image from capture to delivery. Keep the files separate so you do not overwrite your best copy while investigating.

  1. Find the original screenshot. Use the untouched file saved by your capture tool, before editing, conversion or sharing. If you only have a received image, ask the sender for their original.
  2. Open it directly in an image viewer. Inspect a specific word, thin border or icon. Use an actual-pixel view if available, and avoid judging only from a thumbnail or a fit-to-window overview.
  3. Compare it with the source. Look at the same content in the page or app. If the source is already soft, capture settings alone may not be responsible.
  4. Open the edited export beside the original. Use the same viewer, display and viewing scale. Note whether the image dimensions changed and whether text edges became rough or smeared.
  5. Download the received copy. Compare the actual attachment with the local export. A message preview is not enough to establish that the file lost detail.
  6. Fix the first changed stage. Test one adjustment, then compare the same detail again. This makes it easier to tell whether the adjustment helped.
What you observe Check next What the check tells you
The source and local capture both look soft Source text size, rendering and relevant display settings The problem may begin before saving
The local capture is clear but the edited export is not Saved resize settings and JPEG export Editing or export may have discarded detail
The downloaded file is clear but its preview is blurry Viewer scale or thumbnail size The underlying file may be intact
The recipient’s downloaded copy is smaller or softer Sharing method and destination processing The delivered copy may differ from your export

Treat a viewer’s “100%” label carefully. Its meaning can depend on the app and display. For example, Apple lets users configure how Preview defines 100% scale. Compare consistently rather than assuming that every 100% view maps image pixels to physical screen pixels in the same way.

When the original is already soft

Check the source content and capture area

Look at the page before taking another screenshot. Does the source already have blurry text, or is the text simply too small for the intended use? Is the chart itself a small image stretched by the website? Capturing a low-resolution source does not recover detail that the source never contained.

If page text is too small, try increasing the page zoom and recapturing the relevant section. This can make the text render larger, but it also changes how much content fits on screen and may change the layout. Check the saved result; the effect on screenshot resolution depends on the capture tool and its settings.

For a long page, separate the overview from the evidence. Keep the full capture as a reference, then provide readable excerpts for the parts someone must inspect. A whole-page image squeezed into a narrow message card cannot show every label at a useful size.

Check pixel density and display settings when the symptom points there

If text looks wrong throughout the source app, or captures differ between a laptop and an external monitor, check the relevant display rather than repeatedly exporting the image.

On Windows, open Settings → System → Display, select the display you are using, and review its resolution and scale. Microsoft recommends the settings marked Recommended in its display guidance. A non-native resolution can soften text. Do not automatically turn scaling off or force every screen to the same percentage.

Pixel density helps explain why similarly sized screens can render text differently. Browser layout pixels and physical display pixels are not always equivalent, and page zoom can affect their relationship, as MDN explains. That does not mean every capture tool produces a fixed multiple of the page’s dimensions.

For a useful cross-display test, capture the same content with the same tool on each display and compare the saved pixels. Pixel density is context for the result, not a guarantee that a high-resolution display will solve every capture problem. Avoid changing several display and export settings at once.

When editing or exporting introduced blur

Separate viewing zoom from a saved resize

Zooming in a viewer changes how the file is displayed. Saving a resized copy changes the image itself. If you reduce the pixel width and height, fine detail may be discarded; enlarging that smaller copy afterward does not put the detail back.

Return to the original and make the edit again at a suitable size. When placing the image in a slide or document, preserve its aspect ratio so letters and icons are not stretched. If you need it to fill a larger space, check whether the source has enough detail for that use.

Cropping can help the relevant content occupy more of the available space without shrinking the entire page. It removes the outside area rather than adding detail. Crop the screenshot around the necessary context, then judge the saved crop at its intended reading size.

Choose an export that suits the content

For text-heavy instructions, PNG is a useful starting point because it preserves the bitmap without JPEG’s lossy compression. Keep original PNG files when you have them, especially while experimenting with edits.

JPEG can be useful for image-heavy captures or a destination that requires it, but compression can affect small text, colored edges and arrows. Compare the exported copy with its source, and use a higher available quality setting if needed. Avoid repeatedly opening and saving the same JPEG while making revisions; work from the best original and export when the edits are ready.

Changing the image format to PNG does not sharpen a source that is already blurry. MDN’s image format guide explains the PNG and JPEG tradeoffs. If JPEG is required, use an explicit JPEG export and inspect the output rather than changing the filename extension.

When a document, preview or shared copy is blurry

Compare the received file, not just its preview

Ask the recipient to download and open the image. If the downloaded copy is clear, the preview may simply be scaling it down. Sending another compressed copy is unlikely to improve that preview.

If the received file has fewer pixels or changed detail, try file attachments or an original-file sharing option where the destination supports them. Verify the new download afterward: attaching a file does not universally bypass every service’s processing.

Check the pixel width and height as well as the file size. A smaller number of bytes does not, by itself, tell you how much visual detail changed. Use the same word or edge from your initial comparison to judge the result.

Check compression in Windows desktop Office

If the screenshot becomes softer after placing it in a document, inspect the document’s image handling. In supported Windows desktop versions of Word, PowerPoint and Excel, Microsoft provides this path:

  1. Open File → Options → Advanced.
  2. Find Image Size and Quality.
  3. Select the document you intend to change.
  4. Enable Do not compress images in file.
  5. Reinsert the original capture if the existing image has already lost detail, then save and check the document or exported output.

Microsoft’s picture-compression instructions explain the document selection and setting. The menu path is not universal across Mac, web and other Office apps. Disabling compression can increase the document’s size and does not restore pixels that were already discarded.

A PDF also contains whatever image detail was supplied to it. Packaging a small bitmap in a PDF does not make that bitmap sharper. Open the final document at a practical reading scale and check the screenshot inside it.

A repeatable workflow for client feedback

Suppose you need to show a developer an error after submitting a form. Keep the original capture, then make a focused copy containing the message, the submit button and enough surrounding form context to identify the location.

Add an arrow and a short instruction without covering the evidence. For a text-heavy screenshot, export a PNG where available, open the saved image and read the exact error text. Attach it to the ticket, then download the attachment once to confirm that the intended version arrived. Keep the full-page reference separate if it helps explain the broader flow.

If your installed Screenshot Extension editor includes Add image, crop and annotation controls, you can use that editor for the same workflow: open the PNG or JPEG, make and apply the edits, choose the available PNG download option, and inspect the output. These steps depend on the controls in your version; they are not a claim that every published release includes the editor.

An older PNG/PDF-only popup can still provide a PNG capture to inspect and edit in a desktop app. Copy and paste is another delivery route, but the destination may handle the pasted image differently from a saved download. Compare the actual result instead of assuming either route always preserves clarity.

Common symptoms and fixes

Symptom Practical next step Expected result
Sharp local image, blurry chat preview Download and open the received image You can distinguish a preview issue from changed file content
Soft text in both the source and capture Improve the source rendering or capture a larger, focused view A new capture may contain more readable text
Smaller pixel dimensions after sharing Try an original-file option, then compare the download You can verify whether that route retained the source dimensions
Screenshot looks stretched on a slide Restore proportions and check placement size Letters and controls return to their intended shape
Rough outlines appear around JPEG text Export again from the original with suitable settings or PNG You can avoid carrying earlier compression damage forward
Full-page overview is too small to read Add focused excerpts alongside the full reference The recipient can read the evidence while retaining context

A “high resolution” label is less useful than checking the necessary detail in the actual delivered image. Use pixel density and display settings to explain a specific symptom, not as a substitute for that comparison.

Frequently asked questions

Why are my screenshots blurry only after I send them?

The receiving app may show a scaled preview, or the sharing process may resize or compress the image. Download the received file and compare it with your local export in the same viewer. If only the preview is soft, the file may be intact. If the file changed, try an original-file sharing option and verify the new result.

Does changing DPI make a screenshot sharper?

Changing a stored DPI value alone does not add missing pixels. It may affect how an app interprets print size, but it cannot recover detail from a small bitmap. For clearer screen text, use a better source capture or avoid reducing the image before sharing.

Is PNG always sharper than JPEG?

No. PNG preserves the pixels it is given, including any existing blur. JPEG compression can affect sharp text and annotation edges, so PNG is often useful for those screenshots. Compare the actual files rather than expecting a format change to repair a poor source.

Can I recover the missing detail?

Look for the original capture, an earlier version or a way to recapture the source. Enlarging a low-resolution image cannot reliably recover an exact error message. Enhancement tools may generate plausible-looking detail, so do not treat reconstructed text as trustworthy evidence for a support or debugging task.