PDFJadoo › Blog › Share a PDF Safely

Before you share a PDF: redact it, clean it, protect it

Every so often, a court filing, a report or a contract makes the news because someone “blacked out” a secret by drawing a black box over it — and anyone could copy the words from underneath. A drawn box is a sticker, not a shredder. Here is the honest three-step routine for before a PDF leaves your hands: redact what must be gone, clean what the file quietly carries, protect what remains.

Free, in your browserFiles never uploadedThe privacy routine, in the right order
PDFJadoo logoBy the PDFJadoo Team6 min read
Diagram: text hidden under a drawn black box still copying out word for word, beside the same text truly redacted — deleted, with nothing left to copy
If you can still copy it, it is not redacted. True redaction removes the words themselves.

Step one — redact means delete

A PDF page is layers. The text sits on one layer; anything you draw sits on top of it. When you drag a black rectangle over a salary figure in an ordinary editor, you have added a shape — the words are still in the file, untouched, underneath. Anyone who opens the document can select past the box, copy the text, or simply remove the rectangle. This is not a rare edge case; it is the standard way "redacted" documents keep embarrassing their senders.

True redaction works the other way: it deletes the content itself. PDFJadoo's Redact PDF re-renders each redacted page, so the words under your black marks are gone from the file — there is nothing left to copy out. Then prove it to yourself: open the redacted copy, drag your cursor across where the secret was, and copy. Nothing should come out. That ten-second test is the whole difference.

Step two — clean what you cannot see

The visible page is not the whole file. A PDF quietly carries metadata — the author's name, the software that made it, dates — plus, in files that have lived a life, embedded attachments, JavaScript, and annotations and comments that were never meant to travel. Sharing the document shares all of that too.

Sanitize PDF strips exactly those categories: metadata, embedded files, JavaScript and annotations. What remains is the document you meant to send — the pages, and nothing riding along inside them.

One kind of passenger deserves its own decision: the hyperlinks. Links inside a document you received can point anywhere — including places you would never vouch for — and they stay clickable for everyone you forward the file to. If the copy is headed for print, a portal, or a stranger, take the clicks out and leave the words standing: how to remove hyperlinks from a PDF walks through it, step by step.

Step three — protect what remains, knowing its limits

Last, if the document is sensitive, Protect PDF adds a password — real AES encryption, applied in your browser; the password never leaves your tab. Understand what that buys you, honestly: it stops the casual opener and the wrong inbox. It does not control anyone you give the password to — they can read, copy and re-share freely. A password guards the door; it is not a leash on the reader.

And the reverse rule, for portals: protection is for sharing with people. Some official portals refuse protected files outright — USCIS says do not encrypt, and Australia's ImmiAccount rejects secured PDFs. If the file's destination is a portal, send the unlocked copy (that direction is covered in USCIS evidence over 12 MB and ImmiAccount won't attach). Protect for people; unlock for portals.

The order matters: remove first, clean second, lock last — each step works on the output of the one before, and the file you protect at the end is the file you actually meant to share. All three tools run entirely in your browser; a document you are trying to keep private is never uploaded to do it.

Start with the shredder, not the sticker

Redact PDF deletes the words themselves — then sanitize the hidden data, then protect the clean copy with a password.

Open Redact PDF

Worked example: one salary letter, shared two ways

Make it concrete. Your employer issues a salary letter, and two people need it this week: a landlord, who needs to see the employer, the role and the salary band — but not your bank account number or your full ID number — and a government portal, which needs the letter complete but refuses protected files. One document, two destinations, and the routine above splits cleanly. Start from the master and save a copy named for sharing. On that copy, run Redact PDF over the account number and the ID digits for the landlord's version, then do the copy test with your own cursor until nothing comes out where the numbers were. Run Sanitize PDF so the file stops carrying its author history and anything embedded. For the landlord — a person — finish with Protect PDF and send the password by a different channel than the file itself. For the portal, stop before the password step and send a clean, unlocked copy; the portal direction is covered in USCIS evidence over 12 MB and ImmiAccount won't attach.

Three versions now exist — master, landlord copy, portal copy — and that is not clutter, it is the system working. The master never leaves your folder. Each travelling copy carries exactly what its destination needs and nothing it does not, and if a copy is ever forwarded further than you intended, what travels is the redacted version, not your life story. Name the copies so the difference is visible at a glance (salary-letter-landlord.pdf, salary-letter-portal.pdf); the most dangerous redaction failure after the black-box mistake is simply attaching the wrong twin.

The mistakes that survive good intentions

Beyond the drawn black box, three habits keep leaking information from people who genuinely meant to protect it. The highlighter that isn't: covering text with a dark highlight or a white box in a word processor, then exporting to PDF, leaves the words in the exported file exactly as a drawn box does — the test is always the same copy test, never how the page looks. The helpful filename and the chatty metadata: a file can be perfectly redacted on the page and still announce its author, its edit history and an embedded earlier draft to anyone who opens its properties — which is why the clean step is a step, not an afterthought. The crop that only hides: trimming a page's visible area in a viewer can leave the full original page stored in the file, recoverable by anyone who widens the frame again; if part of a page must be gone, treat it like any other secret and remove the content itself, then test.

Build the habit at the level of the folder, not the document: one folder for masters that never travel, one for sharing copies that have been through the three steps. Sharing then becomes a route you walk — redact, clean, protect — instead of a fresh act of judgement, under time pressure, every single time.

Before you upload: the 60-second check

Fair questions

Is drawing a black box over text enough?

No. The box is a shape on top of the page; the text stays in the file underneath it, selectable and copyable. It is the single most common redaction failure, and it keeps appearing in published documents. True redaction deletes the content — test yours by trying to copy where the secret was.

How do I test whether a redaction really worked?

Open the redacted copy and drag your cursor across the blacked-out area, then copy and paste somewhere. If words come out, the redaction failed. Also use Find for the secret itself — a name, an account number. A real redaction returns nothing, both ways.

What is metadata, and why should I care?

It is information stored inside the file but not shown on the page: who authored it, what software made it, when it was edited — and in some files, embedded attachments, scripts or comments. Sharing the PDF shares all of it. Sanitizing removes those categories before the file travels.

Should I put a password on every PDF I share?

No. Protect the ones whose content is genuinely sensitive and whose reader needs the key — and remember the password only guards opening; anyone you give it to can re-share the contents. And never send a protected file to a portal that refuses secured documents — USCIS and ImmiAccount both do.

I already shared a badly redacted PDF. What now?

You cannot unshare a file — be clear-eyed about that. What you can do: send a properly redacted replacement straight away, ask the recipient to delete the first copy, and if the content is serious, tell whoever is affected while you still can. Then make the three steps above your habit, so it happens once.

Does emailing the PDF inside a password-protected zip do the same job?

No. A zip protects the journey, not the document: once the recipient extracts it, the PDF inside is exactly as exposed as before — unredacted text, metadata and all. Redact and clean the document itself first; any protection on top is the final step, not a substitute.

I only need to hide one page of a long document. Is that enough?

Only if the secret lives on that page alone. Names, numbers and totals repeat — in headers, in summaries, in appendices. Search the whole file for the secret with Find before you share, and redact every occurrence, not just the obvious one.

No official numbers on this page: the redaction fact is a property of the PDF format itself — drawn shapes sit on top of the text layer, which stays in the file until a redaction tool removes it. The portal direction (protected files refused) is quoted in this site's USCIS and ImmiAccount guides, from those agencies' own published pages.

Keep reading