H
HidePDF
Redact PDFs in your browser. Nothing leaves your device.
100% local · fully local

Do You Need To Redact This PDF, or Send Something Else?

Somebody has asked you for a document, and parts of it are nobody's business. The reflex is to reach for a redaction tool. But redacting is only one of four ways to answer that request, and it is not always the cheapest or the safest — sometimes the right move is to send three pages instead of forty, or to answer the question in a sentence and send nothing at all. This guide is about the decision you make before you draw the first box, and about the cases where that decision has already been made for you.

PDF
Drop a PDF here, or click to choose
Your file never leaves your device.
Burning in redactions…
Preparing pages…

Almost everything else on this site starts one step later than this page does. Those guides assume the decision is made — you are redacting, and the questions are which marks to draw, whether the text underneath really is gone, and what else in the file might give it away. That is the right assumption most of the time. But a surprising share of the redaction jobs people undertake never needed to happen, and some of the ones that go wrong went wrong because redaction was a poor fit for the situation and got used anyway.

The underlying problem here is not technical. It is that "send the document" and "answer the request" are different acts, and people conflate them. A request arrives phrased as a document — send me your bank statement, send me the contract, send me the report — and the natural response is to produce that exact artefact with the awkward parts covered. Often that is right. Often it is overkill, and the overkill costs you: every extra page you send is another page of content you had to review, another surface where something can survive, and another copy of material about other people that is now in someone else's hands.

The four ways to answer a request for a document

Laying them out side by side makes the trade-offs visible. Each is correct in some situations and wrong in others.

1. Send the document whole. The baseline. Costs nothing, reveals everything. Correct when the recipient is entitled to the whole thing and the document contains nothing about anyone else. Worth pausing over that second clause: a statement, a letter or a report very often carries information about third parties who never agreed to the disclosure — other account holders, other patients, other employees, a co-signer. Their presence is what turns a trivial send into a decision.

2. Send the whole document, redacted. The recipient gets every page, in the original form and layout, with specific content permanently covered. This is the right answer when the document's completeness is part of what is being asked for — when the reader needs to see the shape of the whole thing, or when a rule or a form requires the document itself rather than the information in it. It is also the most work: every page has to be reviewed, not just the interesting ones, and the work scales with length rather than with how much is sensitive.

3. Send an excerpt. Extract only the pages that bear on the request and send those, redacted if they still need it. This is the option people forget, and it is frequently the best one. It cuts review effort roughly in proportion to what you drop, it removes whole categories of risk rather than covering them, and it gives the reader a shorter document they are more likely to actually read. Its cost is context: a page pulled out of a forty-page agreement can mislead, and an excerpt with no explanation invites suspicion about the rest.

4. Send no document at all. Answer in your own words, or supply a different artefact that carries the same fact — a letter confirming your employment dates rather than six months of pay slips, a figure in an email rather than the statement it came from. This is right far more often than people expect, particularly with informal requests, because the requester usually wants a fact and asked for a document out of habit. Its cost is that your word is doing the work: a summary is your characterisation of a document, and it carries less weight than the document itself, which is exactly why it is unavailable in formal processes.

The order of questions that picks between them

Run these in order. The first one that gives a firm answer ends the process.

  1. Is the form of the answer dictated? Look at what generated the request. An order, a discovery obligation, a records request, an audit, a statutory form or a grant condition will usually tell you what must be produced and how — and if it names the document, options 3 and 4 are off the table unless the requester agrees otherwise in writing. Requirements vary by jurisdiction and by process, so read the one that governs your matter rather than reasoning from a general rule.
  2. What does the requester actually need to learn? Write it in one sentence: my income, that this clause exists, the date of the accident. If you cannot write that sentence, ask them. The answer to this question usually reveals that most of the document is irrelevant.
  3. Which pages carry that? If it is a small minority, an excerpt is probably the answer. If it is scattered across the whole file, redacting the whole file probably is.
  4. Does anything on those pages belong to someone else? If yes, you are redacting regardless of which route you take — third-party data is the one thing you should not pass along just because it was convenient to leave in.
  5. Would a plain statement do? Only reach this step for informal requests. If it would, offer it, and let the requester ask for the document if they need it.

Notice that the technical work comes last in every branch. That is deliberate. Redaction is the step people start with because it feels like the step where the risk lives, but the scope decision above it determines how much risk there is to manage in the first place.

Making an excerpt properly

If step 3 pointed you at an excerpt, the order of operations matters. Make the shorter document first, then redact it — not the other way round. Most PDF viewers will print a page range to a new PDF, which is the simplest way to produce one; HidePDF does not split documents, and when you download here it rebuilds every page of whatever file you opened, so the output always has the same page count as the input. Cutting first also has a real safety benefit: content on a page you removed cannot survive anything, whereas a page you meant to cover and overlooked is still sitting in a full-length file waiting to be found.

Then label what you sent. One line in the covering email — which pages, out of what, and what the rest contains in general terms — does most of the work of reassuring a reader that the gap is not evasion. Keep a note of it for yourself too, alongside the untouched original.

Common mistakes and misconceptions

Treating redaction as the cautious default. It feels like the careful option because it involves effort and black rectangles. But redacting a forty-page file when four pages were responsive means reviewing thirty-six pages you did not need to send, and a missed mark on any of them is a disclosure that an excerpt would have made impossible. Effort is not the same as safety.

Covering so much that the document stops being an answer. The failure mode at the other end: you keep the full document because it seemed safer, then black out so much of it that the recipient cannot use it, and in a formal process may be entitled to challenge what you withheld. If you find yourself covering the majority of a page, that is a signal you picked the wrong option two steps earlier. The specific harms of covering too much — rejected productions, unreadable results, marks you cannot justify — are worked through in our guide to over-redacting a PDF.

Reaching for a password instead of a decision. Sending the unedited file with a passphrase feels like a middle path, and it is not one: the complete content is still inside the file, and anyone who gets the password — or who works around weak protection — sees everything you were trying to withhold. Encryption controls who opens a document; it does nothing about what is in it. The distinction matters enough that we cover it separately in does password protecting a PDF count as redaction.

Summarising when the document was the point. Retyping the relevant figure into an email is efficient and completely inappropriate in a process that asked for the record. If there is a deadline, a form, or a rule about what you withheld, your summary is not a production — it is a failure to produce, and it may be treated as one.

Forgetting that a shorter document still needs checking. An excerpt is not automatically clean. Page headers, footers, running totals and cross-references can carry content from the pages you dropped, and the file's own properties travel with it regardless of how many pages you kept. Review the excerpt as a document in its own right before you send it.

Letting the requester's phrasing make the decision. "Send me your bank statement" is a sentence someone typed quickly. It is not necessarily a considered specification of what they need. In informal contexts it is entirely reasonable to reply asking what the document is for — and the answer often turns a forty-page redaction job into a two-line email.

Related guides

Explore more ways to redact PDFs privately, or use the redaction tool above:

Frequently asked questions

Won't sending fewer pages look like I am hiding something?

A page of solid black looks far more like hiding something than a short, labelled excerpt does. The thing that makes an excerpt suspicious is not its length but its silence: an unexplained three pages out of forty invites the reader to wonder what the other thirty-seven said. Say what you are sending and why — "pages 8 to 11, the payment schedule you asked about; the rest of the agreement covers unrelated services" — and the gap stops being a mystery. Redaction has the same requirement, incidentally. A marked-up document with no note about what the marks cover is exactly as opaque. In both cases what reassures the reader is the explanation, not the volume of paper.

Can HidePDF pull out just the pages I want to send?

No — it works on one PDF at a time and always processes the whole document. When you download, every page of the file is rebuilt, including pages you never looked at, so the output has the same page count as the input. If you want to send an excerpt, make the excerpt first and redact it second. Most PDF viewers can print a page range to a new PDF, which is the simplest way to do it. Then open that shorter file here and cover whatever still needs covering. Doing it in that order also has a safety benefit: the pages you removed cannot leak from a document that no longer contains them, whereas a page you meant to cover and forgot is still sitting in a full-length file.

If I answer in a letter instead of sending the document, do I still need to keep the original?

Yes, and keep it untouched. Whichever route you take, the unmodified original is the thing that lets you show later what you actually held and what you actually said about it. Summarising is the route where this matters most, because a summary is your characterisation of a document rather than the document itself, and the obvious way to test a characterisation is against the source. Store the original where you can find it, note the date you answered and what you sent, and do not edit the original in place to make the redacted or summarised version — work on a copy. Keeping the two versions clearly separated is its own small discipline, and it is worth setting up before you are under time pressure.

How do I tell whether redaction is required rather than merely one option?

Read the instrument that produced the request. A court order, a discovery request, a records request, an audit letter, a benefits form or a grant condition will usually specify what has to be produced and in what form, and that specification is what removes your discretion. The signals to look for are an obligation to produce a particular document rather than the information in it, a required format, a deadline, or a rule about noting what was withheld. When any of those are present, treat substitution as unavailable unless the requester agrees otherwise in writing. When none of them are — an informal request from a colleague, a landlord, an insurer's intake form — you are choosing between options and the whole question in this guide is live. If you genuinely cannot tell, ask the requester what they need the document for. The answer usually settles it.