API keys & tokens
API keys, OAuth tokens, bearer/session tokens, and other credential-shaped strings that leak in terminal and config screenshots.
Screenshot Redaction
Redact a screenshot before you post it
Pasting a screenshot into a bug tracker, Stack Overflow, or a vendor support ticket is one of the easiest ways to leak an API key, token, or customer email. RedactVault redacts a screenshot in your browser — the image is processed on your device and is not sent to RedactVault servers for redaction.
Free to start. No subscription required to redact a single screenshot.
What gets caught
The secrets a screenshot exposes
Opening a screenshot turns on detection tuned for posting-before-you-think leaks — API keys, OAuth tokens, cloud and database credentials, private keys, emails, names, addresses, and account numbers are recognised in the image and highlighted automatically for your review.
Cloud & service credentials
Cloud access keys, connection strings, and database URLs that carry embedded usernames and passwords.
Private keys & secrets
Private key blocks and secret-shaped values pasted into editors, .env files, and CI logs.
Emails & names
Email addresses and personal names visible in inboxes, account menus, commit authors, and chat screenshots.
Addresses & phone numbers
Home or billing addresses and phone numbers that show up in account, profile, and support screens.
Cards & account numbers
Payment card numbers and labelled account numbers caught in billing and dashboard screenshots.
Detection finds common secret and PII patterns, not everything on screen. Review the highlighted boxes, then draw your own over anything else you do not want public — internal URLs and hostnames, ticket or order numbers, server names, and any UI details that identify your account or environment. You can black these out in the same editor.
How it works
Three steps, all in your browser
Open the screenshot in your browser
Select your PNG, JPG, or other image. It is processed locally by your browser and is not sent to RedactVault servers for redaction.
Review the highlighted secrets and PII
RedactVault recognises text in the image and highlights API keys, tokens, credentials, emails, names, and addresses for your review. You confirm, add, or remove boxes before anything is final.
Draw boxes over anything else, then export
Black out anything visible that detection cannot find on its own — internal URLs, hostnames, ticket numbers, or UI details — then export a flattened copy with the marked content removed.
Why browser-local matters
Your screenshot does not leave your device to be redacted
Most online image tools transfer your file to a server first — exactly the thing you are trying to avoid when the screenshot contains a live credential. RedactVault runs the redaction in your browser, so the image content is not sent to RedactVault servers for redaction. Account, billing, and support data are still handled server-side like any normal web app.
Before you post it
Always review the redacted copy before sharing. Screenshots rely on text recognition (English-focused), and long random strings such as API keys and tokens do not always recognise cleanly — so check every secret yourself and draw a box over any the detector missed. Detection helps you find common values but is not guaranteed to catch everything, and image-based exports cannot be verified by re-reading a text layer. If a secret appeared in a real screenshot you already shared, treat it as compromised and rotate it.
Further reading
Redaction guides for screenshots and sensitive images
Practical reading on redacting screenshots without leaking secrets or personal data.
Why drawing black boxes over a PDF is not real redaction
The trap behind phone-markup black rectangles, and what actually removes the content underneath.
The biggest PDF redaction mistakes people still make
Common ways a screenshot still leaks data after it looks redacted, and how to avoid them.
Redact financial documents without uploading them to the cloud
Why browser-local redaction matters when the thing you are about to share is sensitive.
How the processing works
Check the security and accuracy details
Read how RedactVault processes images locally and where its detection limits are, so you know exactly what the tool does and does not do before trusting it with a screenshot.
Ready when you are
Redact your screenshot now
Open your screenshot and review the highlighted secrets and PII. Nothing is shared until you export the copy you choose to post.
Just need it once?
Get 24-hour Professional individual access for one urgent redaction job. Includes a 50-document cap with unlimited pages and excludes team and high-volume batch features.