The best screenshot size for documentation is the size it will actually be displayed at: for most help centers and online manuals that means images 800 to 1200 pixels wide, captured from a window or region rather than shrunk down from a full-screen capture. Keep text in the screenshot at roughly the same size as the body text around it, save interface screenshots as PNG, and use the same window size and width for every image in a manual so the set looks consistent. Shrinking a 1920-pixel screenshot to fit a 700-pixel column is the main reason documentation screenshots end up unreadable.
This guide covers widths for different kinds of documentation, how to capture at the right size, which format to choose, and how to keep a whole manual consistent.
Why size matters more than it seems
Screenshots in documentation have one job: to show the reader what they should see on their own screen. That only works if the reader can read the labels and buttons in the image. Three things decide that:
- The capture size: how many pixels the screenshot contains.
- The display size: how wide the image is shown on the page or in print.
- The scale between them: if a screenshot is shown at half its captured width, every word in it is half as tall.
A full-screen capture at 1920 pixels shown in a 760-pixel content column is scaled to about 40 percent. Menu text that was 12 pixels high becomes about 5 pixels: unreadable. Capturing only the relevant window or area at, or near, the display width avoids that.
Recommended sizes by destination
| Destination | Typical display width | Capture |
|---|---|---|
| Help center or knowledge base article | 700 to 900 px | Region or small window, 800 to 1000 px wide |
| Online manual with a wide layout | 900 to 1200 px | Window, 1000 to 1200 px wide |
| Inline detail (a button, a field, a menu) | 200 to 500 px | Tight region around the element |
| Printed or PDF manual, letter or A4 | About 6.5 inches of text width | Window or region around 1300 to 2000 px wide for 200 to 300 ppi |
| Slides | Half to full slide width | Window or region, enlarged app zoom if needed |
High-density screens show images at a fraction of their pixel width, so capturing at around one and a half to two times the display width gives a sharper result on those screens, as long as the text is still large enough when scaled down. When in doubt, check the image on the published page at normal zoom and see whether you can read it comfortably.
How to capture at the right size
- Resize the app window, not the screenshot. Make the window just large enough to show what matters, around the width you will display. Smaller windows produce screenshots with larger, more readable text relative to the image.
- Use window or region captures. Capture only the app or the relevant panel. Full-screen captures include the taskbar and other windows, which then shrink everything else. See screenshotting the active window.
- Zoom the app for detail. For a small control, increase the app's zoom before capturing rather than enlarging the screenshot afterward. Enlarging makes it blurry; see why screenshots are blurry.
- Keep display scaling fixed for the whole manual. Changing Windows scaling between sessions changes the size of the interface in your captures.
Format: PNG for interfaces
Documentation screenshots are mostly text, flat colors and sharp edges, which is exactly what PNG handles best.
- PNG: lossless and sharp. The default for interface screenshots.
- WebP: much smaller files with very good quality. A good choice if your help platform supports it and page weight matters.
- JPG: creates fuzzy halos around text. Use it only for screenshots that are mostly photos.
Our comparison of PNG vs JPG for screenshots explains the differences in more depth.
Keeping a whole manual consistent
A manual where every screenshot is a different width, crop and style looks unfinished. Consistency comes from fixing a few things up front:
- One window size for the app, used for every capture. Note it down so you can match it when updating the manual later.
- One display width for full-window screenshots, and one for detail crops.
- Saved regions for screenshots of the same panel across several steps, so every image has identical dimensions.
- One border style: a thin light gray border separates white interfaces from white pages. See adding a border to screenshots.
- Consistent file names that follow the step order, so images are easy to place and update.
Keep your full-size originals. If your help platform changes its layout or you move to a new format, you can resize originals again instead of recapturing every screen.
Capturing documentation screenshots faster
Bulk Captures is useful for documentation work because it takes care of the repetitive parts. Each capture mode, the active window, a saved region you draw once, a freehand selection or the full screen, has its own hotkey, and every capture is saved straight to a file named by your pattern, such as a counter that follows your step order. You can resize captures to a fixed width as they are saved, add the same border or drop shadow to every image, and save as PNG or WebP. A countdown capture helps with open menus and tooltips.
That combination means a 40-step guide comes out as 40 consistently sized, consistently framed, correctly ordered files. Bulk Captures does not include annotation tools, so arrows, callouts and highlights are added afterward in your editor or help platform.
Updating screenshots when the software changes
Documentation screenshots go out of date every time the interface changes. A few habits make updates painless:
- Record your capture settings (window size, display scaling, theme and app zoom) in a note alongside the manual.
- Name files by topic and step, not by date, so a replacement image can keep the same file name and drop straight into the page.
- Use the same light or dark theme throughout. Mixing themes after an update makes a manual look patched together.
- Recapture whole sections at once, rather than single images, so neighboring screenshots match.
Quick reference
| Question | Short answer |
|---|---|
| Best width for help articles | 800 to 1200 px, captured at or near that size |
| Best format | PNG, or WebP where supported |
| Full screen or window? | Window or region, almost always |
| How to keep sizes identical | Fixed window size and saved regions |
| Biggest mistake | Shrinking full-screen captures into a narrow column |
Frequently asked questions
How wide should screenshots be in documentation?
Capture at the size you will display, often 800 to 1200 pixels wide for a help center page. Avoid shrinking full-screen captures, which makes text unreadable.
Should documentation screenshots be PNG?
Yes, for interface screenshots. PNG keeps text and edges sharp. Use WebP if your help site supports it and file size matters.
How do I keep screenshot sizes consistent across a manual?
Capture the same window size or a saved region for every step, and resize every image to the same width.
