Home/Answers/Long screenshots
SHOT LAB / Long screenshots

Long screenshots FAQ

The most common Long screenshots questions are format, quality, permissions, batch failures and privacy.

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

The most common Long screenshots questions are format, quality, permissions, batch failures and privacy. Split long screenshots by section and cap width; break into multiple images if too large.

Why it matters

Checking these high-frequency issues solves most cases.

Very long images get crushed in chat.

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

  • Very long images get crushed in chat.
  • Splitting by section is easier to read.

FAQ

What are common Long screenshots questions?

The most common Long screenshots questions are format, quality, permissions, batch failures and privacy. Split long screenshots by section and cap width; break into multiple images if too large.

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