Before Retina/2x screenshots, back up the original, confirm format/size/quality requirements and close programs that lock the file. Export 2x screenshots at twice the CSS display width, not blindly at 4K.
Why it matters
Poor preparation leads to overwrites, failures and rework.
1600px is usually enough for an 800px display width.
Step by step
- Crop sidebars, empty space and unrelated windows first.
- Prefer PNG/WebP for text; use JPEG around 85% for photo-like screenshots.
- Export at the actual display width instead of uploading a 4K screenshot.
- Zoom in after compressing to check text/UI edges.
- 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
- 1600px is usually enough for an 800px display width.
- Pixels beyond 2x are mostly wasted.
FAQ
How should I prepare before Retina/2x screenshots?
Before Retina/2x screenshots, back up the original, confirm format/size/quality requirements and close programs that lock the file. Export 2x screenshots at twice the CSS display width, not blindly at 4K.
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: MDN responsive images