Redact a PDF — remove the text, don’t cover it
Black out — and actually remove. On these pages the marked words are deleted from the file’s own instruction list, the result is verified twice, and you can run the extractor on the output yourself. Your file never leaves this tab.
This page loads a PDF rendering engine (≈0.5 MB, from this site) when you drop your first file — it draws your pages and reads their text layout.
All the tools
Why a black rectangle is not redaction
A PDF page is a list of drawing instructions: put these characters here, draw this line there. Drawing a black rectangle adds one more instruction on top — the characters underneath are still in the file, still selectable, still one copy-paste away from anyone you send it to. You can demonstrate this in ten seconds with any PDF whose text was "hidden" that way: select across the black bar, copy, and paste into a text editor. The text falls out, byte-identical.
What this tool does instead
On pages with real text, marked words are removed by content-stream surgery: the drawing instructions for those exact glyphs are deleted from the page's instruction list. The secret is not obscured — it is gone, and every other word on the page remains real, selectable text. On scanned pages there are no glyphs to delete, so the tool destroys the marked pixels and rebuilds the page as an image. That path has a stated cost: the redacted page loses its selectable text, search, and working links. Untouched pages keep everything, and the receipt tells you exactly which pages took which path.
Verified twice — and one thing only you can verify
After redacting, the tool extracts the text back out of its own output and checks the marked content is not in it; then it renders the output and checks the marked region is opaque. If either check cannot pass, the result is thrown away and you are told — you never get a file that claims to be redacted and is not. One check remains yours: the tool can prove the mark is opaque, but only you can confirm it covered the right thing. That is why your marks snap to the words they cover, why the mark list names what each mark removes, and why the preview shows the exact region that will be destroyed before you commit.
Scans that were OCR'd
A scan that went through text recognition carries the recognized text as an invisible layer over the picture — the secret exists twice. Deleting only the text layer would leave it plainly readable in the image, so such pages always take the pixel-destroying path. This is enforced in the engine; there is no way to switch it off, on purpose.
Questions people actually ask
- Why does a redacted PDF sometimes still show the text?
- Because covering is not removing. A rectangle drawn over text is just one more drawing instruction; the characters are still in the file underneath it and can be selected, copied, or extracted. Redaction has to delete the text from the file itself, which is what this tool does — and then proves by extracting its own output.
- Can text be recovered from a PDF redacted here?
- Run the check yourself — the page offers to extract the text of your redacted file right after committing. Marked content comes back as zero characters. That check is also run automatically before the file is handed to you, and if it cannot pass, you get an error instead of the file.
- What happens on a scanned page?
- A scan has no text to delete, so the marked pixels are destroyed and the page is rebuilt as an image. Cost, stated up front: that page loses selectable text, search, and links. Pages you didn’t mark keep everything.
- Does the rest of my document stay selectable text?
- On pages redacted by surgery, yes — only the marked glyphs are deleted; everything else remains real text. Try selecting around the mark in the output.
- Is my document uploaded for redaction?
- No. Marking, removal, and both verifications run in your browser. The file never leaves your device — which for a document worth redacting is rather the point.
We invite you to double-check our work
Open your browser’s developer tools, switch to the Network tab, and run any tool on this page and nothing leaves your device.
The whole source is on GitHub. Read it.
Found a bug, or a claim that doesn’t hold up? Tell us: pdf@geodeforge.com. An example file turns a guess into a quick fix — and if yours is too sensitive to share, we understand; a description still helps.
That’s the difference between a privacy policy and a fact.
This slot pays for the page
One static, labeled sponsor link — an image we host and a plain link. No ad network, no tracking script, no third-party request. That is the entire business model, and it is why nothing above has a price.
Sponsor this slot →More from GeodeForge
GeodeForge is a one-person studio that crafts open-source tools that do what they say, and let you check — in your browser.