Best for
developers, maintainers, support engineers, and technical founders sharing issue examples.
Privacy-first redaction
Redact a GitHub issue screenshot
Hide repository names, private issue titles, usernames, internal URLs, stack traces, and tokens in GitHub issue screenshots.
Edit and preview locally for free. Pay only when the redactions are placed and you need the downloadable PNG or WebM export; only the code is sent to the license service, never the media.
Buy only when the file is ready
Use the free workspace to place redaction boxes first. The $19 Pro export is for the moment you need to download the cleaned screenshot or recording for a client, support thread, public tutorial, bug report, or team handoff.
What to check
- Private repository and organization names
- Usernames and avatars
- Stack traces and internal URLs
- Tokens, keys, and issue IDs
Redaction risk checklist
- Repository paths can reveal private products
- Logs may include secrets
- Comments and linked issues may expose internal context
Export review
- Scan sidebars, breadcrumbs, labels, and comments.
- Use cover for secrets and internal paths.
- Rotate any credential that appeared in the issue.
Workflow
- Open the screenshot.
- Cover repo, org, user, and private issue details.
- Hide logs and internal URLs.
- Export and zoom in before posting.
Why local processing matters
BlurClipAI's first version runs the redaction workflow in your browser, which keeps raw media off our servers and makes it easier to handle private demos.
Does BlurClipAI scan code or logs automatically?
No. You manually identify and cover sensitive regions.
Should I cover public usernames?
Cover usernames when the screenshot context should not identify people or accounts.