Home/Answers/Screenshots
SHOT LAB / Screenshots

Before Screenshots Processing

Before Screenshots, back up the original, confirm format/size/quality requirements and close programs that lock the file.

Updated 2026-10-31About 3 minLocal test
Quick answer

Before Screenshots, back up the original, confirm format/size/quality requirements and close programs that lock the file. Screenshots are mostly text/UI; preserve edges instead of copying photo settings.

Why it matters

Poor preparation leads to overwrites, failures and rework.

PNG/WebP are friendlier to text.

Step by step

  1. Crop sidebars, empty space and unrelated windows first.
  2. Prefer PNG/WebP for text; use JPEG around 85% for photo-like screenshots.
  3. Export at the actual display width instead of uploading a 4K screenshot.
  4. Zoom in after compressing to check text/UI edges.
  5. Keep the original; use the compressed copy only for publishing.

Common mistakes

  • Compressing code screenshots to 50% JPEG and blurring text.
  • Uploading a 4K screenshot displayed only 800px wide.
  • Recompressing and dirtying the edges.
  • Converting transparent UI to JPEG, turning the background white/black.

Checklist

  • Sensitive areas cropped/masked.
  • Text screenshot not saved as low-quality JPEG.
  • Dimensions match the actual display width.
  • Zoomed in on the target page.
  • Original kept.

Key facts

  • PNG/WebP are friendlier to text.
  • Cropping often helps more than lowering quality.

FAQ

How should I prepare before Screenshots?

Before Screenshots, back up the original, confirm format/size/quality requirements and close programs that lock the file. Screenshots are mostly text/UI; preserve edges instead of copying photo settings.

How long does it take?

Usually 1-3 minutes; for intermittent issues, run 30 seconds and retest elsewhere.

Is data uploaded?

Runs locally and does not upload video/audio; extensions may still read the page.

Source: Web.dev images