1. Decide what a screenshot is for when you take it
Most screenshots are one of four things: evidence (a bug, a failed test, a customer’s error), reference (a design you like, a setting you’ll need again), communication (something to paste into a chat right now), or record (a receipt, a confirmation). Communication shots rarely need keeping. The other three do, and they need a name.
2. Name it in words you’ll search for
The OS gives you Screenshot 2026-09-14 at 10.42.17.png. Replace it with the words future-you will type into a search box:
| Role | Pattern | Example |
|---|---|---|
| QA / support | area-what-happens-platform | checkout-coupon-500-safari18 |
| Developer | service-error-context | auth-token-expired-staging |
| Designer | product-screen-state-version | pricing-hero-mobile-v3 |
| Everyone | date first, only if time matters | 2026-09-14-invoice-aws |
Keep ticket numbers and people’s names out of the title and in a note or tag; they change, and they make titles unreadable.
3. One collection, several tags
Give every screenshot exactly one home: a collection for the project, release or client, nested as deep as helps (QA / Sprint 42 / Safari). Then use tags for the other ways you’ll slice it: type (#bug, #reference), severity (#p1), platform (#ios), status (#fixed). Collections stop the heap; tags stop the duplication. Three or four tags per screenshot is plenty; a tag used once is noise.
4. Make the pixels searchable
The most useful information in a screenshot (an error code, an order number, a line of copy) is locked inside the image. Extract it once and it becomes searchable forever. In ScreenVault, open a screenshot and press “Read text & suggest tags”; the screenshot to text tool does the same for a one-off.
5. A QA evidence workflow
- Capture the defect at a known viewport (from the browser or with the OS shortcut and paste).
- Mark it up: one box on the defect, numbered steps, and solid redaction over customer data.
- File it under the build, tag severity and platform.
- Compare against the last good build with a pixel diff and attach the diff.
- Close the loop: when the fix ships, capture again, tag both
#fixed, and keep the pair as the regression baseline.
Frame-by-frame evidence is a small piece of storytelling: each capture should show one step, in order, so the reader never has to guess what changed between them. Want to see a sequence carried by narration done well? ahaboo takes why the Moon shows phases through narrated steps, and it’s a useful model before your next multi-screenshot bug report.
6. Clean up weekly, back up monthly
Once a week, filter to Unfiled and Untagged, give each survivor a home, and delete communication shots that did their job. Once a month, export a ZIP backup: a vault that lives in one browser should never be the only copy of evidence you may need later.
7. Share without scattering copies
Every upload to a screenshot-hosting service is another copy you can’t delete later. When the audience is known, send the file itself: a ZIP, a PDF, or ScreenVault’s single-file HTML gallery, which opens in any browser with no server. Before you send, strip metadata from photos and shrink oversized captures.