Capture the current tab, mask sensitive details, and export a screenshot, short demo, asset, or bug report without sending data anywhere.
One local-only workflow for screenshots, short demos, launch assets, and GitHub-style bug reports.
Safe Capture stays intentionally narrow: fast browser capture with explicit review steps before anything leaves the device.
Capture the current tab and automatically blur or mask sensitive information before sharing.
Record concise walkthroughs with cursor highlights and lightweight editing.
Turn a live page into changelog cards, README visuals, and shareable launch images.
Export a reproducible issue bundle with screenshots, metadata, console errors, and failed-request details.
Define your own regex, selector, and keyword rules for on-device redaction.
Keep a device-local trail of generated screenshots, assets, recordings, and reports.
Sensitive content review is not an afterthought. The tool starts from explicit user actions and keeps evidence on-device until you choose to export.
Every export is staged locally first, with visible redaction and evidence review before anything leaves the browser.
Screenshots, recordings, bug reports, console errors, and masking rules stay on this device.
Safe Capture does not upload screenshots, bug reports, recordings, or custom rules.
Inspect the screenshot, Markdown, ZIP, or report bundle before sharing it externally.
Failed-request capture keeps metadata only. No bodies, cookies, or auth headers are exported.
The base release stays useful on its own. Pro adds more control over templates, rules, and export history.
Core screenshots, short demos, and bug-report flows for individual developers.
Expanded template controls, reusable rules, and stronger export management for heavier teams.
Production pricing and store availability remain configurable while the public launch is still forming.
The first release is narrow by design, so the answers stay concrete.
No. The workflow is local-only. You review the result on-device before exporting it anywhere else.
Screenshots, selected metadata, console errors, and failed-request metadata. Request bodies, response bodies, cookies, and auth headers stay out.
Yes. Custom masking rules are part of the planned reusable-rules surface and already shape the shared architecture.
Safe Capture is for teams that need practical screenshots and bug reports without introducing a remote review service.
Static landing, local-first product. Store URL and production endpoints can be swapped in site config later.
This static page reuses the same sanitizer, bug-report builder, intent model, and asset template catalog extracted from the extension.
Sanitized URL
https://internal.demo.example/admin/users?access_token=%5Bhidden%5D&page=1
Bug report draft
Bug report: Checkout failure
Asset template
Safe Screenshot
Capture intent
Bug Report