About
Built to keep my clients safe.
unredact.tools didn't start as a website. It started as an internal tool I wrote for my clients, so nothing they sent out could give them away.
Where it came from
My clients send files to people they can't fully trust: a photo to a stranger, a filing to a court, a document to a reporter. Each of those files can carry far more than what's on screen. A phone photo can hold the exact spot it was taken and the serial number of the phone. A PDF can hold the text under its black boxes. A Word file can hold every edit and every name that touched it.
Checking all of that by hand, file by file, was slow and easy to get wrong. So I wrote a tool to do it. Before anything left a client's hands, it went through this first: scan it, see exactly what it gives away, then send a clean copy instead.
Every time a new kind of leak turned up, I added a check for it. It started with GPS coordinates and device serials. Then came failed redactions, tracked changes and hidden text, then printer tracking dots, faces, license plates and even shadows that can date a photo.
None of these mistakes are unique to my clients. They happen to anyone who shares a file. So the tool is now public, free to use and open source.
Who it's for
Anyone whose safety, case or livelihood depends on what their files don't say:
- Journalists and their sources, who need a leaked document to reveal the story without revealing whose copy it was.
- Whistleblowers handing over evidence without handing over their identity.
- Lawyers and paralegals filing redacted documents that have to stay redacted.
- People escaping stalking or abuse, sharing photos without giving away where they live now.
- Activists and organizers posting from protests and meetings without exposing the people in the shot.
- Content creators posting photos and videos without revealing where they live, where they film, or the device they use.
- Investigators and researchers who handle sensitive material and need to pass it on cleanly.
- Everyone else who sells something online, posts a photo, or emails a document and would rather it didn't say more than intended.
This happens to real people
| Year | What happened |
|---|---|
| 2012 | John McAfee was located while hiding from authorities, from the GPS data in a photo a journalist posted. |
| 2017 | The source of a leaked NSA document was identified from printer tracking dots on the scan, which revealed the printer and when it printed. |
| 2019 | Paul Manafort's lawyers filed a “redacted” PDF with black boxes drawn over text that was still there. Reporters copied it out within minutes. |
What it does
- Scan. Finds what's leaking and explains it in plain English: where, who, which device, when, what software, which organization, what's hidden and what's tracking you.
- Sanitize. Rebuilds a clean copy from the visible content only, then re-scans that copy to prove nothing survived. Your original file is never modified.
Your files
Pages load through Cloudflare's network so they're fast everywhere, but uploads and contact messages go straight to our own server and never pass through Cloudflare. Uploads are processed in a temporary folder that is deleted before the response is sent. Nothing is stored or logged except a running count of files checked and cleaned, and the site uses no cookies, analytics or third-party scripts. For anything truly sensitive, run it on your own machine instead:
pip install "unredact-tools[web]" && unredact.tools web
Open source
The whole thing is MIT-licensed and on GitHub. Questions, bug reports or a file it got wrong? Get in touch.
Who builds it
unredact.tools is built and run by Legit Biz Consulting, which builds internal tools, lead engines and security basics for small businesses and creatives. More free tools, including the in-browser security toolbox, are at legitbiz.xyz/tools.