Screenshots for public troubleshooting
Keep the error and reproduction steps readable while covering private details around them. Review the whole image, export a new PNG, and inspect that saved copy before posting.
Manual marks, no automatic detection. The exercise loads a public fictional PNG from this site; editing stays in your browser. Recent sessions can retain originals on this device—clear history on a shared browser.
A specific problem, with files you can inspect
In this invented app, CSV export fails after 12 seconds. The useful evidence is POST /reports/export · 502 Bad Gateway, the upstream error, export.ts:88:12, the demo version and the Reports → Export → CSV steps. The URL query, account panel, other workspaces, home-directory path and unrelated notification are separate areas to cover.
Download original debugging PNGDownload protected debugging PNGDownload the local export recordFor this 1120 × 760 sample, every pixel in the five marked areas is opaque, and every unmarked pixel matches the original. The source’s fictional Author and Description metadata fields are removed. This verifies these chosen marks and this saved file; it does not establish that every private detail in another screenshot has been found.
The original also has two invented PNG text metadata fields. This actual metadata-only download removes them but keeps every original image pixel, even though five marks were present in the editor. The token, account, path and messages still show. Choose Export redacted image to apply marks; a metadata-clean label alone is not a sharing decision. Inspect its separate local record.
Look beyond the error box
Capture only the useful app area when possible. Close unrelated tabs or dismiss notifications before taking a new screenshot. If private information remains in the capture, inspect these areas manually—including repeated occurrences. What is appropriate to reveal depends on your document and audience.
Swipe the review table sideways to read every column.
| Area | Consider covering | Keep useful context where shareable |
|---|---|---|
| Account | Emails, account IDs, profile names and avatars | The error message and relevant app version |
| URL and request details | Tokens, session values, private hostnames and identifying query values | A shareable endpoint, HTTP method and status |
| Local paths | User directories and private project/customer names | A shareable module and line number, or a short sanitized explanation |
| Sidebar and background | Other workspaces, customer lists, document titles and unrelated tabs | The menu or control needed to reproduce the issue |
| Notifications | Senders, message previews, codes and unrelated activity | The debugging context underneath, if you can capture it separately |
Repeat the complete workflow
Choose Try the fictional debugging screenshot, then Load fictional debugging screenshot in the editor. Navigation alone imports nothing. Download the original to compare. Inspect Source metadata to find Fictional screenshot author and the invented account description.
Use the five Cover buttons to add one solid mark per sample area. Repeating a button selects its existing mark. These are fixed coordinates for this invented PNG, not recognition of accounts or secrets. Toggle Show original and Show protected, zoom in and review the edges. Keep the error, endpoint, version, stack location and reproduction steps readable.
Open an image from your device, or paste a copied image where supported. On a phone, saving and choosing the image file is the fallback. Use solid Redact rectangles or Brush marks with a margin around every private area; blur and pixelation are weaker obfuscation. Your screenshot needs its own geometry and review. Blivion does not request background clipboard access or fetch pasted image URLs.
Keep PNG selected and choose Export redacted image. Save it under a distinct name, open it at readable zoom, and check every bar, edge and remaining detail. Compare the diagnostic context with your original. Review Verification details and the JSON record for supported cleanup checks; the record is not independent privacy certification.
Attach the newest protected download and a short, sanitized description of the expected result, actual result and reproduction steps. Review the text you paste as well. Do not also attach an original, older export or unreviewed log. Changing a source, mark, profile or output setting requires a fresh export; already saved files elsewhere are not updated by the editor.
For the exact 1120 × 760 original only: add a centered redaction for each row, set Width and Height, then X and Y. The guided buttons apply the same rectangles. These values are not a preset for your own screenshots.
| Area | X | Y | Width | Height |
|---|---|---|---|---|
| URL query | 544 | 56 | 528 | 40 |
| Account | 24 | 150 | 244 | 72 |
| Sidebar | 24 | 298 | 244 | 116 |
| Local path | 342 | 420 | 718 | 44 |
| Notification | 704 | 628 | 368 | 84 |
An image is one part of a report
Hiding its pixels in a new image does not invalidate the secret or remove copies already shared. Follow the affected service’s revocation or rotation process. For GitHub credentials, GitHub’s exposure guidance puts revocation or rotation before repository cleanup. Blivion does not change credentials or account settings.
Review those files and pasted commands separately. The screenshot export does not sanitize them. Chrome documents sanitized HAR export excluding headers such as Cookie, Set-Cookie and Authorization; that description is not proof that every URL, response body or app-specific value in your attachment is safe to publish.
Solid marks cover the areas you choose. Private details outside them—including avatars, filenames and repeated IDs—can remain. Reopen the saved output and review the whole image. If it is unclear what can be public, pause sharing and use the intended support channel’s data-handling instructions.
The screenshot redaction hub covers paste/file import and ordinary marks. For hidden file fields, use the metadata guide; for review and local storage limits, read the safety notes. If your evidence is a document, see PDF redaction.
