Secrets
API keys, bearer tokens, JWTs, URL tokens, webhook secrets, credentials, and .env values.
Mac guide
The safest Mac screenshot workflow is simple: find sensitive data before the screenshot leaves your machine, cover it with opaque redaction, flatten the output, and share only the clean copy.
Open, paste, drag, capture with Redaktr, watch a selected folder, or batch scan a group of images.
Check API keys, tokens, PII, faces, QR codes, customer data, and custom policy terms before deciding what stays visible.
Export or copy a flattened, metadata-stripped image with active redactions applied. Keep the original separate.
API keys, bearer tokens, JWTs, URL tokens, webhook secrets, credentials, and .env values.
Email addresses, phone numbers, faces, card-like numbers, personal notifications, and profile details.
Customer data, account IDs, internal labels, confidential terms, codenames, private metrics, and QR codes.
Preview is useful for manual markup, but it does not act like a screenshot sanitizer. It does not scan for secrets, explain likely findings, manage policy terms, or build a repeatable review workflow for AI, Slack, support, docs, and public sharing.
Redaktr is built for the review step: scan locally, show possible leaks, let you adjust or draw boxes, and export a separate clean copy.
If the screenshot contains sensitive data, use opaque redaction and a flattened export. Avoid relying on blur or pixelation for API keys, PII, credentials, or customer data.
You can manually cover parts of an image in Preview, but Preview does not scan for API keys, PII, faces, QR codes, customer IDs, or custom policy terms before sharing.
Capture or import the screenshot, let Redaktr scan locally, review the findings, add manual boxes for anything unique, and export only the flattened clean copy.
Redaktr leaves the original untouched. Keep it if you need it privately, but share the cleaned copy when sending screenshots into AI, Slack, support tickets, email, docs, or public posts.