Define a small set of file roles
Use distinct roles such as original, annotated and reviewed-for-sharing. Include a date and a meaningful page or issue label. You can rename downloaded files in your file manager; this guide does not claim an automatic screenshot library manager.
Local history keeps a capped recent collection, while downloads live in your chosen folders. A copy on another device or in an external service is another separate file. Renaming one file does not update those copies.
Save and inspect each necessary version
- Download the original if you need to retain it.
- Export the annotated or cropped result separately.
- Open the actual file intended for sharing and check privacy.
- Use a clear final name and folder, then select that file deliberately.
Put actual scope in the name or note
If a capture is partial or only a visible region, include that scope in the name or accompanying note. A file called “complete” can mislead a reader if the viewer reported a limit. Keep capture warnings in your review notes when they matter.
Choose the next step from the actual result
Keep your naming convention small enough to use consistently. A date, subject and role often suffice. For a sequence of panel states or feed sections, include a sequence number and actual range. A vague suffix such as final-final does not help when two files contain different private information. Review content when selecting a shared file instead of relying on the newest modification time.
Separate the review note from the image where useful. Record mode, relevant warnings and scope in that note rather than cluttering every screenshot with administrative labels. Preserve official source documents separately when needed. The extension’s history and your project folder are not interchangeable archives. A deliberate file check at the end makes the workflow reliable even after recent captures have rotated out.
A worked example
A project folder contains checkout-original.png and checkout-annotated-v2.png. The second file shows the issue clearly, but both include an address. Create a reviewed shareable copy through a suitable permitted workflow or recapture a non-sensitive region. Open that copy before sending, and keep the private originals separate according to your own needs.
Add your observations. This template processes no files and sends no report.
Check the result
If something is wrong
| Observation | Next step |
|---|---|
| Several similar names | Add a date, role and version in your file manager before choosing the shared copy. |
| Wrong file shared | Review the actual selected file; do not infer its contents from a similar thumbnail. |
| History used as archive | Download needed files; the recent collection is capped and local. |
Common questions
Does naming remove private data?
No. Inspect and prepare the actual image; a safer file name does not change its pixels.
Will renaming update every copy?
No. Downloads and externally shared copies are separate files.