Home/Answers/Screenshot crops
CROP LAB / Screenshot crops

Why Handle Screenshot crops?

Handling Screenshot crops is usually about compatibility, sharing, archiving or saving space; define the goal before choosing an approach.

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

Handling Screenshot crops is usually about compatibility, sharing, archiving or saving space; define the goal before choosing an approach. Crop unrelated UI from screenshots, then resize to display width.

Why it matters

Different goals imply different formats, tools and quality settings.

Keep key toolbars/context.

Step by step

  1. Confirm where and how large the image will be displayed.
  2. Drag a box at the target ratio; center the subject and leave safe margins.
  3. Keep selection pixels at or above the display size.
  4. Export PNG/WebP for text/UI, JPEG 85-90% for photos.
  5. Keep the original; use the crop only for publishing.

Common mistakes

  • Cropping too tight and cutting avatars/products.
  • Ignoring safe areas so cover text gets cropped.
  • Cropping low-resolution images then enlarging, causing blur.
  • Overwriting the original and losing re-crop ability.

Checklist

  • Target ratio/size confirmed.
  • Subject intact with safe margins.
  • Selection pixels >= display size.
  • Format/quality meets the platform.
  • Original kept.

Key facts

  • Keep key toolbars/context.
  • Do not enlarge text screenshots.

FAQ

Why should I handle Screenshot crops?

Handling Screenshot crops is usually about compatibility, sharing, archiving or saving space; define the goal before choosing an approach. Crop unrelated UI from screenshots, then resize to display width.

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