Redacting Headers, Footers, Watermarks and Stamps in a PDF
Body content appears once and you deal with it once. Page furniture appears on every single page, often needs to be kept rather than covered, and sometimes is not really on the page at all.
Almost everything written about PDF redaction assumes the sensitive thing is in the body of the document: a name in a paragraph, a figure in a table, an address on a form. You find it, you cover it, you move on. Page furniture breaks that assumption in three separate ways at once, and it is why a document can be redacted carefully and still leak on page nineteen.
By page furniture I mean everything that is placed on the page by the document's layout rather than by its content: the letterhead with a direct dial number on it, the running header carrying a client name or a matter number, the footer with a document-management string like Smith_v_Jones_draft7_jbrennan.docx, a diagonal DRAFT or CONFIDENTIAL watermark, a received-and-date-stamped block from a clerk's office, production numbering down the bottom right corner, and the header a court's filing system adds along the top of every page after submission.
The three ways this is a different job: the same item recurs on every page, so a single mistake is multiplied by the page count rather than being isolated; a good share of it must be preserved rather than covered, which inverts the usual instinct; and some of it is not part of the page content at all but an annotation or an optional-content layer, which means it can behave differently from how it looks. Each of those needs handling separately.
Make an inventory before you draw anything
Open the document and look at three pages that are far apart — say the first, something near the middle, and the last. Page furniture is identifiable precisely because it does not change, so comparing distant pages separates it from body content very quickly. Write down what you find and mark each item cover or keep:
- Letterhead and logos. Usually fine, except where the letterhead itself carries a direct phone number, a private email address or a home-office address that identifies an individual rather than an organisation.
- Running headers and footers. The usual offenders are matter names, client names, internal reference codes, and file paths or filenames inserted by a word processor. A footer that reveals a filename is a leak of exactly the kind covered on the filename question elsewhere on this site, except it is on the page rather than in the metadata, so renaming the file does nothing about it.
- Watermarks. Rarely sensitive in themselves, frequently significant — a DRAFT marking changes what the document is, and a confidentiality designation may be required to remain visible.
- Stamps. Received stamps, approval stamps and signature stamps often carry an individual's name, an internal routing number or a handwritten initial.
- Pagination and production numbering. Almost always keep. These exist so a page can be referred to unambiguously later, and removing them tends to create a dispute rather than avoid one.
Doing this first matters more here than for body content, because the cost of changing your mind is per page rather than per item. Deciding on page thirty that the footer should have been covered means thirty pages of rework.
The three places a marking can actually live
This is the part that surprises people, and it is worth understanding because it determines what you are able to do about an item.
In the page content. Most furniture is simply drawn into the page like any other text or graphic. It behaves exactly as you would expect: it shows in the preview, a box over it covers it, and the covered pixels are gone from the export.
As an annotation. Stamps and some watermarks are annotation objects sitting on top of the page rather than inside it. If such an annotation is meant to be displayed, it gets drawn while the page is being rasterized and so becomes permanent pixels in the exported file — flattened rather than removed. If it carries the hidden or no-view flag, the renderer leaves it out of an on-screen draw; because the export is built from the same kind of draw, it is then missing from the finished file as well. A stamp set to print but not display is the textbook case, and it will not be in the PDF you send.
In an optional content group. These are what viewers call layers. The PDF carries its own default configuration saying which groups start visible, and that default is what gets honoured here — there is no layer panel in this tool to override it. So a watermark on a layer that is on by default is drawn, appears in your preview, and is burned in permanently. A watermark on a layer that is off by default is not drawn at all, does not appear in your preview, and does not reach the export. The useful consequence is that the preview is an accurate predictor of the output in both cases. The uncomfortable consequence is that a designation someone parked on a hidden layer can silently fail to make it onto the copy you deliver, and you would have no sign of it from this side.
One more structural point applies regardless of the above: the exported document is assembled fresh from page images, and nothing from the original object tree is copied into it. The file you download therefore contains no annotations, no form fields, no bookmarks and no attachments at all. Anything that needs to remain legible has to be visible as pixels.
The page-furniture pass, step by step
- Do the body content first, in one pass. Mixing the two jobs is what produces skipped pages. Read for content, cover what you find, and ignore the margins entirely.
- Settle your window before the second pass. The page is scaled to fit the width of the viewer, so the window size is effectively the zoom, and resizing mid-job rescales rectangles you have already placed. Fix the window, then do not touch it.
- Start the furniture pass at page one and never jump. Use Next only, so the page counter is a running record of where you have been. Jumping around is how pages get missed.
- Cover the whole band, not the words. For a header or footer, drag a rectangle across the full strip from margin to margin rather than tracing the text. It is faster, far easier to repeat identically, and it avoids the tell that a tightly-fitted box gives about the length of what is underneath.
- Overshoot the page edges deliberately. Coordinates are clamped to the page, so pulling past the margin lands the box flush against it. For a repeated band this is the easiest way to get the same result on every page without aiming.
- Watch the box count, every page. The status bar's count for the current page is your only confirmation a rectangle was stored. A rectangle under roughly three pixels in either direction is discarded silently, so a stray click leaves nothing behind — and neither does a drag you thought you completed.
- Verify in the downloaded file, page by page. The editor shows what you intended; only the export shows what happened. Scroll the whole document and look specifically at the band you were covering. A single uncovered header is the failure mode this entire workflow exists to prevent.
What you are expected to keep
The instinct to cover more is sound for body content and actively unhelpful for furniture. If the requirement you are working to is a court filing rule, the thing being regulated is personal identifiers rather than page identifiers. Federal Rule of Civil Procedure 5.2(a) provides that unless the court orders otherwise, a filing that contains an individual's social-security number, taxpayer-identification number, or birth date, the name of an individual known to be a minor, or a financial-account number may include only the last four digits of the social-security and taxpayer-identification number, the year of the individual's birth, the minor's initials, and the last four digits of the financial-account number.
Two things to take from that. It is an abbreviation rule, so the expected output keeps part of the identifier rather than blacking out the whole field. And it says nothing about headers, footers or page numbers, because those are governed by local rules, standing orders and protective orders instead. Rule 5.2 also allows a court to require more extensive redaction for good cause, so the rule is a floor and not a ceiling. If you are redacting against an order, read the order — the conventions around production numbering and confidentiality designations vary by jurisdiction and by matter, and nothing on this page is a substitute for the specific one you are under.
Common mistakes and misconceptions
Expecting an apply-to-all-pages button. There isn't one. Boxes are held per page, and Undo and Clear page both act on the page in front of you only. A repeated header is a repeated rectangle, drawn by hand, as many times as there are pages.
Assuming an identical-looking header is in an identical position. Section breaks, landscape inserts and scanned pages that went through the feeder at a slight angle all shift the band. Draw generously rather than trusting the previous page's geometry.
Thinking a watermark sitting on top of the text protects it. Layering is irrelevant to what survives. Everything visible is flattened into one image per page, so a watermark over a paragraph hides nothing and covers nothing — only your rectangles remove anything.
Renaming the file to deal with a filename in the footer. Those are two different things in two different places. The footer is drawn on the page and needs a rectangle; renaming changes only the name of the file.
Covering the production numbering along with the sensitive content. Tempting when you are working quickly down a page corner, and it removes the one reference everybody downstream needs.
Treating the preview as optional. With layers and hidden stamps, the preview is doing real work for you: it shows exactly what the export will contain, which is the fastest way to discover that a marking you expected is not actually going to be there.
Assuming the last page is the same as the rest. Signature pages, exhibit sheets and certificate-of-service pages routinely drop the running header or carry a different one. Check the ends of the document specifically.
Worrying that a long job means sending the file somewhere. It does not. Every page is rendered and rebuilt inside your browser however many pages there are, and no upload is required at any point.
Related guides
See also, or use the redaction tool above:
- How Many Pages Can You Redact in a PDF at Once?
- Redact the Same Name or Number Consistently Across Multiple PDFs
Frequently asked questions
Can I apply one redaction box to every page at once?
No. Boxes are stored per page, keyed to the page number you were viewing when you drew them, and there is no copy-to-all-pages control anywhere in the toolbar. The buttons you get are Prev, Next, Undo, Clear page, New PDF and Download Redacted PDF — and both Undo and Clear page act only on the page currently on screen, which is why their tooltips say so explicitly. For a letterhead or a footer that repeats forty times, that means forty deliberate rectangles. The workflow that survives this is a dedicated second pass: redact the body content first, then go back to page one and walk forward with Next, drawing the furniture box in the same place on every page without stopping to read anything. Watch the page counter and the box count in the status bar as you go. Those two numbers are the only confirmation you have that a page was actually treated rather than skipped, and a missed page in the middle of a run is the single most common way this kind of redaction fails.
If a watermark sits on a layer I can switch off in Acrobat, does HidePDF remove it?
There is no layer switch in HidePDF, but the behaviour is predictable. Optional content groups — what viewers present as layers — carry a default configuration inside the PDF itself, and the renderer the tool uses honours it: groups are visible unless the document's default state turns them off. Neither the on-screen render nor the export render overrides that default, so both agree with each other. The practical consequences run in two directions. A layer that is on by default is painted, so your preview shows it and it is burned into the exported pixels permanently — nobody downstream can toggle it back off, because by then it is not a layer any more. A layer that is off by default is never painted at all, so it is absent from your preview and absent from the export too. That second case is the one to watch: it means a designation the author parked on a hidden layer can quietly fail to appear on the copy you send. If a document matters and you suspect it has layers, open it in a viewer that exposes them before you redact, so you know what the default state is actually hiding.
Should I redact the Bates numbers and the court's header stamp?
Usually the opposite — those identifiers are normally the part you are expected to preserve, because they are how everyone refers to a page later. Production numbering and pagination exist so that a page can be cited unambiguously, and covering them tends to create the argument you were trying to avoid. The requirement that does bite is about personal identifiers rather than page identifiers. Federal Rule of Civil Procedure 5.2(a) provides that unless the court orders otherwise, a filing containing an individual's social-security number, taxpayer-identification number, or birth date, the name of an individual known to be a minor, or a financial-account number may include only the last four digits of the social-security and taxpayer-identification number, the year of birth, the minor's initials, and the last four digits of the financial-account number. Note that it is an abbreviation rule, not a delete-everything rule. Rule 5.2 also lets a court require more extensive redaction for good cause, and numbering conventions themselves come from local rules and protective orders rather than from the federal rule, so check the specific order governing your matter instead of generalising from this page.
A CONFIDENTIAL stamp looks like an annotation rather than part of the page. Will it be flattened or dropped?
It depends on the flags the stamp carries, and the answer is worth knowing because the two outcomes look nothing alike. A stamp or watermark annotation that is meant to be seen on screen is drawn into the page while the page is being rasterized, so it becomes ordinary permanent pixels in the export — flattened, not removed, and no longer separable from the page. A stamp carrying the hidden or no-view flag is a different story: the renderer excludes it from an on-screen draw, so it is missing from your preview, and because the export is built from that same kind of draw it is missing from the finished file as well. The classic example is a stamp configured to print but not display. Separately, and regardless of flags, the export is assembled as a brand-new document from page images, and nothing from the original object tree is carried across — so the file you download has no annotation objects of any kind, no comments, no form fields and no bookmarks. Anything you still need to see has to be visible as pixels, which is a good reason to check the downloaded PDF rather than the editor.