I built a ** PDF redaction tool**, and the thing that surprised me most wasn’t
It isn’t. And once you understand why, you’ll never trust a black box on
a PDF again.
The problem with covering text
Most online PDF editors “redact” by drawing a rectangle over the text you
want hidden. Visually, it looks gone. But the original text is often still
sitting in the PDF’s data layer, underneath the box — selectable,
copy-pasteable, and extractable with a script in seconds. The box is
cosmetic. The data isn’t touched.
I didn’t want to ship that. So the redaction tool I built doesn’t draw over
anything — it rebuilds the page.
What actually happens to the file
When you mark an area for redaction, the tool doesn’t hide it. It re-renders
that entire page as a flattened image — at 1.75x scale in Standard mode,
2.5x in High — and re-encodes it as a JPEG before embedding it back into
the PDF at the original page dimensions. The rebuilt page has no text layer,
no annotations, no form fields, no links. There’s nothing left to extract,
because there’s nothing left that’s text.
The tradeoff is real, and I don’t pretend otherwise: you lose
selectability and the page gets a bit heavier. But you gain something
almost no competing tool offers — actual, structural certainty that the
information is gone.
The part I’m most proud of: it checks its own work
Join The Writer's Circle event
Before the tool ever lets you download a file, it re-reads its own output
and verifies it. If the PDF signature is malformed, if the page count
changed, if any extractable text remains on a page you marked for redaction,
or if any annotation survived — it throws an error instead of handing you
a file. You get told something went wrong. You don’t get a silently broken
redaction.
That’s the one thing I haven’t found on a competing “redact your PDF
online” page: a tool that proves its own result before trusting you with it.
Where the real risk actually is
Here’s the honest limitation. The verification only checks pages you
explicitly marked. If you forget to mark a page — miss a signature block
on page 12, say — that page gets copied through untouched, text layer
intact, and the built-in check has nothing to say about it because it was
never told to look.
The failure mode isn’t “the redaction gets reversed.” It’s “you never
told the tool to redact it in the first place.” That’s a much more common,
much more human mistake, and it’s worth knowing before you rely on any
redaction tool, mine included.
Why blur and pixelation aren’t redaction either
A quick related note, because I see this misunderstanding constantly:
blurring or pixelating a sensitive value — a license plate, a phone
number — feels like redaction, but it usually isn’t. Pixelation is a
deterministic transformation. If the original value comes from a small,
guessable set (a 10-digit phone number, a plate format), you can pixelate
every candidate value the same way and compare block patterns until one
matches. You’re not un-blurring the image — you’re brute-forcing it. The
pixels are genuinely destroyed; the exposure comes from a different angle
entirely.
If something needs to be irrecoverable, it needs the full rebuild-and-verify treatment, not a filter.
If you want to try it The tool is free, runs entirely in your browser (nothing is uploaded, ever),
and the redaction tool specifically is at filotool.com/redact-pdf. I’d
genuinely like to know if this changes how you think about redaction tools
you’ve used before — I learn a lot from what breaks people’s expectations.