SnapFrame STUDIO

Screenshot quality that survives a blog post

Guide 01 · capture, crop, export · Updated 16 November 2026

A screenshot is a technical document. It is also, usually, the first thing a reader looks at on a page about software. The difference between a screenshot that helps and one that hurts is rarely artistic: it is resolution, edges and consistency.

1. Capture at 2x, not at 1x and scaled up

Most laptops and every modern phone render at a device pixel ratio of 2 or 3. If you capture with a tool that grabs the CSS pixel grid — some browser extensions do — you get an image that is already half the resolution your reader's screen can show. It will look soft the moment it is displayed at full width.

Capture at the display's native density instead:

A 1440×900 CSS-pixel viewport captured at 2x is a 2880×1800 image. That is the file to keep. Downscale on export, never upscale.

2. Pick viewport sizes that match where the image will live

ContextViewport to captureWhy
Documentation body1280×800 or 1440×900Reads as a desktop app without forcing a scrollbar in a 760px column.
Product / landing page1440×900Matches the most common desktop layout width.
Mobile app store390×844 or 430×932Current iPhone logical sizes; crisp when exported at 3x.
Slide deck1600×900Exactly one 16:9 slide at 2x-friendly resolution.
Dashboard marketing shot1600×1000Leaves room for a frame and a caption without crowding.

3. Crop to intent, not to edges

Two habits make a screenshot look deliberate:

When you crop, crop to a ratio you will reuse — 16:10 and 16:9 cover most UI. Mixed ratios in one article look accidental even when every individual image is fine.

4. Remove what should not be published

Screenshots leak. Account names, email addresses, internal URLs, API keys in a terminal, customer rows in a table. Before an image goes anywhere, scan it at 100% zoom, not as a thumbnail.

Two practical options: re-take the shot with a demo account, or cover the values with a solid block that matches the background. Blur is not a redaction — most blurred text in a screenshot can be inferred from length and position, and some can be recovered outright.

One advantage of a local tool is worth stating plainly: if you clean up a screenshot in the browser and export it there, the original never passed through a third-party server on the way. Screenshot cleanup is exactly the kind of image people should not be uploading to a random web service.

5. Frame it consistently

Once the image is clean, the frame is what makes a set of screenshots look like one product. Consistency beats decoration: the same padding, the same corner radius, the same shadow strength, the same background across every image in a document.

Numbers that work at 1600px wide: 8% padding of the shorter side, a 20–28px corner radius, a shadow with 60–80px blur at 12–18% opacity, and no tilt unless the surrounding layout is playful. The composition guide has the full ranges.

6. Export for the display, not for the file

Publish a 2x image and constrain it with CSS so it renders at the size you intended:

<img src="shot@2x.png" width="1280" height="800" alt="…">

PNG is the safe default for interface text. WebP cuts 25–35% off the same image with no visible loss at quality 90 and above; the format guide explains when each one wins.

Checklist

Keep reading

Try it on your own screenshot

Free, no sign-up, and the image never leaves your browser.

Open the studio