Redact a PDF for a FOIA Request
Prepare responsive PDFs by blacking out exempt material while keeping release-ready pages readable for requesters.
FOIA and public-records responses often require agencies and contractors to produce PDFs that balance transparency with statutory exemptions—personnel details, law-enforcement techniques, trade secrets, and personal privacy data frequently must be removed before release. Sloppy redaction can leak exempt text under black shapes or trigger appeal disputes.
HidePDF runs entirely in your browser, which matters when you redact a PDF for a FOIA request on controlled workstations. Your source records never upload to our servers; processing happens locally so responsive sets are not copied to third-party PDF clouds during exemption review.
How HidePDF works
Open your responsive PDF
Load the record in the redaction tool on this page before you finalize a FOIA release. The file stays local while you redact a PDF for a FOIA request on agency equipment.
Draw permanent black boxes
Click and drag over exempt personal data, law-enforcement details, trade-secret lines, and deliberative passages. Each box is burned into the rasterized page so the original text layer cannot be recovered.
Download and verify
Save the redacted PDF, then try select-all and search in a viewer. Redacted regions should not return readable text.
Guide: Redact PDF for FOIA Request
FOIA and public-records responses often require agencies and contractors to produce PDFs that balance transparency with statutory exemptions—personnel details, law-enforcement techniques, trade secrets, and personal privacy data frequently must be removed before release.
Exemption coding and attorney review still belong in your official process; the technical step is ensuring covered passages cannot be recovered with copy-paste or search. Consumer upload redactors may retain full documents in logs. HidePDF burns redactions into flattened pages on hardware you control.
Document which exemptions you applied. Scanned annexes with embedded photos may need HideShot for faces; camera originals benefit from MetadataWipe before inclusion in a release packet.
What a FOIA packet should withhold from the public copy
A Freedom of Information Act file is not one PDF. The agency keeps an official record that still contains exempt passages. The copy that leaves the reading room, the portal, or a contractor’s mailbox is a public-facing export with those passages covered so they cannot be copied, searched, or read back from a text layer. Mixing those two files is how an exemption review turns into an accidental release.
Requesters sit on the other side of that split. The PDF you receive from an agency is already a public copy. If you forward it to a reporter, a coalition list, or a blog, you may still need to cover your identifiers—home address on the request letter, a personal email in the correspondence trail, a bank routing line you attached as proof of interest, or a third party’s phone number that arrived in an exhibit. Covering those fields does not change what the agency withheld. It only keeps your working copy from becoming a second leak.
Practically, the public copy usually needs boxes over personnel contact lines, Social Security fragments, medical notes mixed into personnel files, confidential-source names, investigative techniques spelled out in memos, and commercial data marked as proprietary. Headers, fax banners, and OCR sitting under a scan can repeat the same string the body already covered. The job is visual covering plus a search test, not a legal memo about which exemption number applies. Counsel and the FOIA officer still own that coding.
How to black out a FOIA PDF in the on-page tool
Keep the official record closed. Open only the working copy you intend to release or forward. Load it in the FOIA redaction tool on this page. The PDF stays in this browser tab on the workstation you already use for records work, so the responsive set is not copied to a consumer PDF service during exemption review.
- Page through the assembled packet the way a requester will see it: cover letter, main record, and every annexed scan in the same file.
- Draw a box over each exempt or personal string, including running headers, Bates-style stamps that encode a case name, and table cells that look empty until you zoom.
- Export a new PDF. Leave the official file untouched in the records system.
- Open the export in a viewer that did not draw the boxes. Search names, account fragments, and phrases you meant to withhold. Try select-all and copy across a black region. Readable text means the export is not ready.
If a scanned annex still shows a face or a license plate after the text is gone, that image needs a separate screenshot workflow. HidePDF only burns the boxes you draw on the PDF pages in front of you.
Three FOIA handoffs that need separate files
An agency shop posting a reading-room PDF should export from the reviewed working copy, then post only that export. The unredacted official record stays in the records system with its retention schedule. Posting the working file “because the boxes already look black on screen” is how text under shapes reaches the public docket.
A requester who wants to share a packet with a journalist should start from the agency’s public PDF, cover remaining personal lines that belong to the requester or to bystanders, and send the new export. Forwarding the original attachment from the FOIA portal mailbox keeps every identifier the agency already released plus anything in your request letter.
A contractor supporting a component often receives a subset that is still too broad for a public docket. That subset should be covered on hardware the contract already authorizes, then returned as a distinct public copy. Sending the contractor’s unredacted drop to a web redactor—or emailing it to a personal account “just to finish boxes”—creates a copy the agency cannot inventory.
FOIA redaction mistakes that reopen a dispute
Treating the requester copy and the agency copy as interchangeable is the structural error. One is a public release; the other is the official record. Overwriting the official file with black boxes destroys the unredacted original you may need for an appeal file or an internal review.
Drawing highlighter rectangles in a previewer looks finished and still leaves selectable text. Appeal counsel and journalists will search the PDF. If a name returns a hit, the covering failed regardless of how opaque the shape looked on a projector.
Missing the OCR layer on a faxed annex, a running footer with a home address, or a bookmark title that restates a withheld subject line will undo a careful body pass. Review the assembled file as one object, not as isolated pages. HidePDF is a browser tool for permanent visual covering. Exemption logs, certification, and records schedules remain the agency’s process—not something this page replaces.
Related guides
Explore more ways to redact PDFs privately, or use the redaction tool above:
Frequently asked questions
How do agencies redact PDFs for FOIA releases?
Teams typically mark exempt passages under their exemption schedule, export a public version, and verify that covered text is not selectable. HidePDF supports manual blackout with permanent flattening when upload-based tools are not approved.
Can I avoid uploading records to a FOIA redaction vendor?
Yes—HidePDF processes PDFs locally in the browser. That reduces one off-site copy of sensitive government records, though your agency may still require certified tools for high-volume production.
How do I test a FOIA redaction before publication?
Search the exported PDF for names, account numbers, and phrases you intended to withhold. Attempt copy-paste across redacted areas. If text returns, rebuild the export before posting the release.
What FOIA edge cases are easy to miss?
Headers, footers, OCR layers on scans, and exhibit bookmarks can re-expose withheld data. Review multi-page tables and attachment merges as a single assembled file before release.
Is HidePDF a records-management system?
No. It is a browser tool for permanent visual redaction. Retention, exemption logging, and official certification remain your organization's responsibility.