or drop files / folders here
PDF, DOCX, JPG, PNG — single, multiple, or whole folders
View, edit, strip, audit, and unredact — all in your browser. PDF + Word.
or drop files / folders here
PDF, DOCX, JPG, PNG — single, multiple, or whole folders
Remove author, title, producer, creation date, XMP, bookmarks, embedded files, and the document outline — anything that could identify the source.
See every field in the /Info dictionary, the XMP stream, the outline tree, attached files, and form data — laid out cleanly, not buried in a PDF reader's preferences.
Change Author, Title, Subject, Keywords, Producer, or Creation Date and save. Useful for compliance, white-labeling, or fixing wrong defaults from your PDF generator.
Was your "redacted" PDF actually redacted? We check for selectable text under black bars, leftover bookmark titles, XMP residue, embedded source files, and seven other failure modes.
If text was just covered with a black rectangle, we extract what's underneath — so you can see what a journalist or opposing counsel would see if you shipped the file.
All five tools run entirely in your browser via WebAssembly. No upload. No account. Disconnect from Wi-Fi after the page loads — it still works.
No. Every operation runs in your browser. You can verify by disconnecting from Wi-Fi after the page loads — the tool keeps working.
Author, Title, Subject, Keywords, Creator, Producer, CreationDate, ModDate (the /Info dictionary); the XMP metadata stream; document outline / bookmarks; embedded files and file attachments; optional content group names; and form field data. You pick which to remove.
Yes — drop a .docx and the tool reads the same way: core/app/custom properties, tracked changes, comments, hidden text runs, and embedded objects. Strip them all in one click.
Most "redacted" PDFs aren't actually redacted — someone drew a black rectangle on top and the text underneath is still selectable. The audit mode finds every case of that, plus seven other ways redactions leak (bookmark titles, embedded files, XMP residue, etc.).
To see what a journalist, opposing counsel, or court clerk would see if you released the file. It's a verification step before you ship. We don't recommend using it on other people's documents.
Your browser's memory. Most desktops handle 200+ MB PDFs without issue; mobile is more limited. We don't cap.