Skip to content
ForgePlug — Logo
image100% Browser-BasedNo SignupNo WatermarkUpdated Oct 2026

Smart Screenshot Redactor

Auto-detects emails, phone numbers, card numbers, and API keys in your screenshot, then hides them in one click — 100% in your browser, free, with no signup and no caps. Competitors like Scribe's Smart Blur and Snagit's AI redact gate automatic detection behind a paid plan; here it's free for everyone, and your screenshot never leaves your device.

100% in your browser — nothing is uploaded

Detection and redaction both run on your device. No signup, no limits, no watermark.

Drop a screenshot here, or click to browse

PNG, JPG, or WebP · Add as many as you like

Or paste with Ctrl+V / Cmd+V — works right now, no click needed

How to redact a screenshot before sharing it

Auto-detect emails, phone numbers, card numbers, and API keys, then hide them — all in your browser, in three steps.

Sharing a screenshot — a support ticket, a bug report, a payment confirmation — is one of the easiest ways to accidentally leak something you didn't mean to: an email thread's full address, a card number sitting in a payment app, an API key visible in a code editor. Manually drawing boxes over each one is slow and easy to get wrong. This tool reads the text in your screenshot with OCR, runs it through a set of detectors built for exactly this kind of leak, and lets you hide everything it finds — or anything you point at yourself — in one click.

How it works

  1. Drop, paste, or pick a screenshot. Paste (Ctrl+V / Cmd+V) works the instant the page loads — no need to click anything first.
  2. Automatic detection runs locally. Tesseract.js (an open-source OCR engine compiled to WebAssembly) reads every word in the image inside a Web Worker, so the page never freezes. A set of pattern- and checksum-based detectors then scans that text for emails, phone numbers, card numbers, IBANs, UPI IDs, URLs, API keys, and ID numbers like PAN, Aadhaar, and SSN.
  3. Review and redact. Each match shows up as an outlined, color-coded box. Click any box to toggle it, flip a whole category on or off, hit "Redact all detected" for everything at once, or draw your own rectangle or freehand mark over anything the detector missed — then export.

Why solid blocks are safer than blur or pixelation

Blur and pixelation don't actually erase the underlying pixels — they average or smear them, and averaging can sometimes be reversed, especially on short, structured text like a 16-digit card number or a 4-digit PIN. Security researchers have repeatedly shown this with both deblurring and depixelation attacks. A solid block instead paints over the pixels with a flat color, permanently destroying the original data with nothing left to reconstruct. This tool defaults to solid for exactly that reason, and shows a warning whenever you switch to blur or pixelate.

What stays on your device

The entire pipeline — reading the image, running OCR, detecting sensitive text, and rendering the final redacted image — happens in your browser tab. Nothing is uploaded at any point, which you can verify yourself in your browser's Network tab. The exported file is drawn fresh onto a new canvas, so there's no hidden layer under the redaction and no EXIF or location metadata carried over from the original.

Redaction Features

Everything you need to hide sensitive info in a screenshot before sharing it

Auto-Detection

Emails, phones, cards, API keys & more

Luhn & IBAN Checks

Checksums cut down on false positives

Click to Toggle

Turn any detected box on or off

Category Toggles

Hide a whole type at once, with counts

Manual Tools

Draw a rectangle or freehand brush mark

Solid / Pixelate / Blur

Solid is the safest, permanent choice

Undo / Redo

Full history, per image

Batch Processing

Redact as many screenshots as memory allows

Zero Metadata

Exported images carry no EXIF data

Supported Formats

Upload any common screenshot format

PNG

Most common screenshot format

JPG

Compressed photos and screenshots

WebP

Modern, smaller web format

Smart Screenshot Redactor — Frequently Asked Questions

Everything you need to know about redacting sensitive info in a screenshot

Is my image uploaded anywhere?
No. Everything — reading the text in the screenshot (OCR), detecting sensitive info, and rendering the redacted image — runs locally in your browser tab using WebAssembly. Your screenshot is never sent to a server. You can confirm this yourself: open your browser's Network tab while using the tool and you'll see zero requests carrying image data.
What does it detect automatically?
Email addresses, phone numbers (including Indian 10-digit mobiles), payment card numbers (validated with a Luhn checksum so random 16-digit numbers aren't flagged), IBANs (checksum-validated), UPI IDs, URLs and IP addresses, API keys and tokens, PAN numbers, Aadhaar numbers, US Social Security numbers, and — off by default — amounts next to a currency symbol. Each category can be toggled on or off.
Why solid blocks instead of blur or pixelation?
Blur and pixelation are reversible under the right conditions — deblurring and pixel-averaging attacks on card numbers and text have been demonstrated repeatedly. A solid, opaque block destroys the underlying pixel data completely, so there's nothing to reconstruct. We still offer blur and pixelate (sometimes you just want to soften something that isn't truly sensitive), but we show a warning next to both and recommend solid for anything you actually need gone — card numbers, IDs, API keys.
Does it work on phone screenshots?
Yes — Gmail, WhatsApp, banking apps, UPI payment confirmations, and code editor screenshots all work. OCR runs on whatever resolution you give it, so a sharp, in-focus screenshot (rather than a photo of a screen) will get the most accurate detection.
Can it miss things?
Yes — automatic detection can miss things, especially on blurry text, unusual formats, or very small text that OCR struggles to read. Always look over the image yourself before sharing it, and use the manual rectangle or brush tool to redact anything the automatic detection didn't catch.
Does the exported image remove metadata like EXIF/location data?
Yes. The redacted image is drawn onto a fresh canvas and exported from that canvas — canvases only ever hold decoded pixel data, with no metadata channel, so EXIF, GPS location, camera info, and anything else in the original file's metadata is stripped automatically. There's also no separate 'redaction layer' ever created or exported — just the final pixels.
Is there a limit on how many screenshots I can redact?
No page cap, no file-count cap, no daily limit, no watermark, and no signup. The only honest limit is your own browser's memory — a very large image (over 25 megapixels) will show a warning, since that's genuinely how much your device can handle, not an artificial restriction we've added.

Redaction Guide

Tips and best practices for hiding sensitive info

Why automatic detection usually costs money elsewhere

Competing tools like Scribe's Smart Blur and Snagit's AI redact both gate automatic sensitive-info detection behind a paid tier — the free versions make you draw every box by hand. Because this runs entirely on your own device's CPU instead of a server somewhere, there's no per-scan cost to us, so there's no reason to ration it.

Checksums beat plain pattern-matching

A 16-digit number isn't automatically a card number — most random 16-digit strings fail the Luhn checksum every real card number satisfies. Rather than flagging any digit string that's roughly the right length, card and IBAN detection here run the actual checksum algorithm, which cuts down on flagging things that just happen to look like one.

Getting better detection

OCR accuracy depends on image quality: a sharp, in-focus screenshot at its native resolution reads far more reliably than a blurry photo of a screen or a heavily compressed re-upload. If detection seems to be missing obvious text, try a higher-resolution capture of the same screen.

Automatic detection is a first pass, not a guarantee

No detector catches everything — unusual formats, handwriting, very small text, or text OCR simply misreads can all slip through. Treat the automatic pass as a fast first draft, give the image a once-over yourself, and use the manual rectangle or brush tool for anything it missed before you share it.

Was this tool helpful?

Your feedback helps us improve Smart Screenshot Redactor for everyone.

Share this tool

Share