How to Update Every Screenshot After a Redesign
A redesign invalidates every image in your help centre at once. Here is how to find them, fix the ones that matter, and avoid doing it all again next time.
Screenshots for documentation
Capturing, standardising and maintaining the images in your help centre - including what to do when a redesign invalidates all of them at once.
8 guides
Free PDF
The Screenshot Handbook
All 8 guides on screenshots for documentation in a single PDF, plus a one-page checklist to print and a short opener on which three things matter most. Formatted to read on screen or on paper.
How to Take Screenshots for Documentation
The settings and conventions to fix before you capture anything, so forty images end up looking like one set rather than forty separate decisions.
How to Capture a Full-Page or Scrolling Screenshot
Capturing a page taller than the screen, without the stitching seams, duplicated headers and cut-off text that most scrolling-capture tools produce.
How to Redact Customer Data in a Screenshot
Blurring is not redaction. What to remove, how to remove it so it cannot be recovered, and why the reliable answer is never to capture it in the first place.
How to Screenshot a Dropdown or Hover State
Menus close the moment you reach for the capture key. Three reliable ways to freeze a transient interface state long enough to photograph it.
How to Keep Screenshots Consistent Across a Help Centre
Readers notice inconsistency long before they notice imperfection. The five variables that cause it, and how to hold them steady across authors and years.
What Size Should Documentation Screenshots Be?
One capture width, one display width, and a decision about retina. The three numbers that determine whether your images look sharp or soft.
How to Compress Screenshots Without Blurring the Text
JPEG is the wrong format for a screenshot. Why interface text smears under lossy compression, and what to use instead to get small files that stay sharp.
Stop doing it by hand
Every image in this guide has to be re-captured the next time your interface moves. SupportPages renders them from your codebase instead, so a redesign triggers a re-render rather than an afternoon.
Start free