VIEW THIS AS

Auto mode follows the Route Engine until you choose a viewpoint.

YOU ARE HERE

ROUTE CHECK

CONNECTED TO

WHAT NEXT

Use the canonical route for this room, or HELP if you are unsure.

How to Redact a PDF and Check That the Information Is Gone

Three learners review open books together at a classroom table, with stacks of textbooks, stationery and a whiteboard in the bright room.

To redact a PDF, use a dedicated redaction tool that removes the selected content from the file. Make a working copy, mark the sensitive text or image areas, apply the redactions and save a separate copy for sharing. Check the new file for hidden information as well as the visible marks. In Acrobat Pro, Adobe documents both applying redactions and sanitising a PDF.

A black rectangle drawn over text can hide it from view while leaving the words selectable, searchable or otherwise recoverable. Open the final PDF and test it. Search for the original words, try copying the area around the redaction, and review comments, attachments and other possible locations where the information might appear. For an official disclosure, use the approved workflow and review process.

  • Preserve the original in its approved location and work on a separate copy.
  • Use a Redact tool and apply the marks before you share the file.
  • Review hidden information such as metadata, comments, attachments and hidden text using the approved tool.
  • Reopen the exact release copy and check all pages and repeated occurrences.
  • Use an independent review for a formal release or when the consequences of missing information are significant.

Decide what the recipient needs to see

Start with the purpose of the document. A recipient may need the date, transaction and total on a record while having no need for a separate reference number. A teacher may want to show how a student solved a problem without identifying the student. Before making any changes, check the issuer’s instructions and whether you have authority to create and send a redacted copy.

Some requests require a complete original, including the very details you were planning to remove. Follow the recipient’s stated format. Where an original must remain intact, retain it and ask whether a redacted reference copy is accepted for a different purpose. A redaction workflow is appropriate when the recipient can use the copy without the removed material.

Set the scope before you open the tool

Record what should remain and what should be removed. For a sample worksheet, the method, diagram and answer may need to remain visible. The name, class identifier and identifying comments may need to be removed. Check the first page, margins, footer and any repeated labels. A surname might appear once on a cover sheet and again on every page footer.

Consider details that identify someone in combination. A short note may include a name, a unique role or an exact reference. The release decision belongs to the relevant policy and owner. When working under an organisation’s procedure, use its list of required checks and get the designated review before sending. Keep the checklist and the original in the approved location.

Identify which files the recipient will receive

You may need to send a PDF and a separate image or spreadsheet. Redacting the PDF has no effect on those other files. Examine each deliverable on its own. A screenshot attached separately can show the very details removed from the document. Check the filename, email attachment list and any linked folders as part of the final handoff.

Back to contents · Next section


Understand why covering words with a black box is unsafe

A PDF can contain text, page images, annotations and other objects. A shape can sit above the text, like a label placed on top of a transparent sheet. The words below may still be present. Depending on the viewer, someone may be able to search for them, copy them, hide the annotation or access the underlying document information another way.

A genuine redaction operation removes the selected content according to the tool’s workflow. The visible bar or label signals where something was removed. Some tools first mark areas for review and remove the content only after you apply the marks. A file that still contains pending marks is a working copy. Save and verify the release copy after applying the redactions.

Common look-alikes

Highlighting text in black, drawing a filled rectangle, setting a font colour to white and writing over a field can all change how a page looks. Those edits do not establish that the underlying content is gone. Printing, flattening or taking screenshots is also a poor substitute for a validated workflow. The result may keep unwanted information, expose it through a separate attachment or lose useful features the recipient needs.

If you have already made a copy using a visual overlay, return to the original in an approved editor. Apply actual redactions to the content that needs to be removed. Then use the appropriate hidden-information review. Verify the exact file you plan to release, rather than relying on what you saw in the editing window.

Treat scans as images and as potential text

A scan may contain a photo of the page and a searchable OCR layer. Redacting selectable text alone can miss a visible part of an image if the selected area does not cover it. Covering the image visually can leave recognised text behind. Use an approved tool that can redact the relevant page area and check the visual content and the remaining text separately. Review the whole line if a long character or punctuation mark extends beyond the box.

Back to contents · Next section


Apply redactions in Adobe Acrobat Pro

Make a working copy and mark the right areas

Open the file in Acrobat Pro and choose the tool for redacting a PDF. Adobe’s guidance describes selecting text or dragging over a text or image area. Mark what your release decision requires. For several occurrences, you can use appropriate search features where available, then review each match in context. Search can miss text in images, spelling variants or poorly recognised scans, so it is only one part of the review.

Zoom in where a word is close to text that needs to remain visible. Check each line the mark touches. For a chart or screenshot, review the entire area including labels near the edge. Confirm the boxes on all pages before applying. If a whole page should be withheld and the procedure allows page removal, use the approved way to omit it and recheck the remaining page sequence.

Apply, sanitise and save the release copy

Choose Apply to commit the marked redactions. Adobe describes a prompt offering to sanitise and remove hidden information. Use the organisation’s approved settings. Give the released file a distinct name and save it in the intended folder. Keep the unredacted source and any pending-mark version away from the release location.

Reopen the new copy and inspect every redaction in context. The surrounding sentence, heading or table should still serve its purpose, where the release allows it. If you accidentally remove something necessary, rebuild the release copy from the protected original and repeat the checks. An applied redaction is intended to be permanent in that output.

Keep two checks separate

The first check is removal of the text or image selected for redaction. The second is removal or review of sensitive data elsewhere in the file. A successful black bar proves neither on its own. For a formal release, review the sanitised output using the approved method and have the designated reviewer open that exact copy.

Back to contents · Next section


Use Preview on Mac only for a workflow it can support

Apple documents a Redact Selection tool in Preview on Mac and states that the redaction becomes permanent when the document is closed. Use a duplicate so the original stays intact. Open the Markup controls and use the dedicated redaction tool on the required content. Save or close the working copy as appropriate, then reopen it and check the areas that were redacted.

Use the control labelled for redaction. A shape tool may produce a visually similar black rectangle, with a different effect on the file. If the document contains images, comments, attachments, metadata or other elements that require removal, verify what your tool handles. Use the approved editor and release process for the full scope of a formal disclosure.

If you have only a phone or a browser viewer

Check whether you have an approved tool that performs actual redaction and supports verifying the saved file. A general drawing or PDF annotation feature is insufficient evidence of removal. If you can only add marks on screen, keep the file private and move the job to a suitable environment. Use the storage and transfer method allowed for the underlying document.

Keep the redacted copy separate from the original

For a household task, names such as Activity-Original.pdf and Activity-Redacted-Share.pdf can help you distinguish copies. Follow any filename requirements set by the recipient or organisation. If both versions appear together in the picker and their names are truncated, place the release copy in a separate approved folder. Open the file you selected before sharing, or inspect the final attachment list when the workflow permits it.

Back to contents · Next section


Look for sensitive data outside the visible page

Some PDFs contain metadata such as author or title, comments from review, attachments, form values, bookmarks or other hidden material. The exact set depends on how the file was made. Adobe’s documentation describes a sanitisation workflow in Acrobat Pro for hidden content. Use the controls required by your organisation and verify the resulting file rather than treating a clean page preview as the entire document.

Check comments and attachments explicitly

A reviewer may have left a comment that repeats a name removed from the page. A PDF can also include an attached copy of a source document. Look for the comments and attachments areas in an approved viewer. Remove items the recipient should not receive using the approved procedure. If an attachment is required, check and prepare that attachment on its own.

Check titles, bookmarks and filenames

Metadata or navigation labels may mention an individual or a private project name. Review the document properties and bookmark text where relevant. A redacted worksheet named with the student’s full name still exposes the name to the person receiving the file. Give the output a name allowed by the task, then confirm it in the final attachment list.

Check forms, links and scannable codes

A visible page can include links or codes that point to material outside the file. A QR code might contain a unique reference or lead to a document the recipient should not be able to access. Check those elements against the release scope. If a PDF includes forms or related structured information, use the approved sanitisation workflow and verify what remains. Avoid opening a sensitive link on an unapproved service just to see what it contains.

Back to contents · Next section


Review the whole document for repeated or indirect identifiers

A search for an exact name is a useful starting point in a text-based file. It can miss initials, a shortened name, a spelling variant or a name embedded in an image. Use the release scope to decide which variants matter. Review the cover, footers, page headers, labels, tables and captions. Look at pages even if the exact search returned no matches.

A detail may appear in a different form

Suppose a full name appears on the cover, an initial and surname appear in the footer, and an email address is printed on a reference page. Each location can identify the same person in a different way. If the release scope requires removing all three, mark each one. Search for the exact strings when the file supports it, then inspect the pages visually. If a name appears inside a screen capture, a text search may never find it.

Phone numbers can appear with spaces, punctuation or country prefixes. A reference might be repeated beside a barcode or as part of a link. Decide which forms need review, then check each location in the release copy. Do this in an approved environment. Avoid moving sensitive material into a separate app just to see whether it matches.

Decide how much nearby information can stay

A row can include a name, role, date and amount. Removing the name may leave enough information to identify the person when the other fields are unusually specific. The appropriate scope depends on the release decision and who will receive the file. Follow the responsible organisation’s process for indirect identifiers. If you are working on a family document, confirm with the issuer which fields it needs and which may be removed.

Redact only what the authorised scope calls for. If a key amount is beside a sensitive reference, remove the reference while preserving the amount where the tool permits that. Confirm the meaning of the surviving fields against the original. For a larger area, make sure the redaction covers every relevant line, including trailing characters beyond the expected boundary.

Check the first and last pages again

The first page may include a cover or a notice copied from a different source. The last may be a receipt, appendix or page that was added after the main report. A search limited to the centre of the document misses those edge cases. When you merge or reorder files after redaction under an approved workflow, review the combined copy again. A later operation can bring an earlier unredacted page back into the final packet.

Back to contents · Next section


Choose the right workflow for a born-digital file, scan or mixed packet

Start from the type of page you have

A document exported from a writing app can contain selectable text, links, author information and other structure. Dedicated text redaction can remove selected content where the tool supports it. A scan may contain a page image and recognised text. Use the approved tool’s image or area redaction controls when needed and verify both the visible image and the searchable layer. A mixed packet can contain both types of page, so use the checks relevant to each.

A signature, handwritten correction or photograph may cover part of a page without being selectable as text. Inspect it visually. If the release scope requires removing a signature or visible identifying detail from a photo, make sure the redaction area covers it fully. Check the parts of the image near the edges of the mark. If you cannot use a tool that supports the needed removal, get an approved copy through the document owner.

Work carefully with layered files

A PDF may contain annotations over a source page, a hidden text layer under a scan, or other structures the ordinary view does not show. Sanitisation can address hidden content when the approved tool supports it. A practical release check combines the redaction tool’s confirmation, a visual page inspection, the appropriate hidden-content review and an independent review where required.

If the document came from a design tool, spreadsheet or presentation, you may have an approved route to create a clean version from the source. Verify the exported PDF just as carefully. A source edit can leave comments, author information or embedded material in the export. The PDF you release is the deliverable to review.

Keep approved versions for distinct audiences

A complete document for an issuer and a redacted reference copy for another reader can both be valid. Use filenames and folders that make the intended audience obvious to the person handling the files. Follow any rules for release labels or recordkeeping. Check access to the release location. A redacted file stored next to an unrestricted original can defeat the purpose of preparing it.

Back to contents · Next section


Verify the exact PDF you are about to share

Close the working file and open the saved release copy from its final folder. Check the name and page count. Look at each marked area at a comfortable zoom and make sure nothing remains visible at the edges. Read the neighbouring text to check that you retained what the recipient needs. Inspect repeated occurrences in headers, tables, captions and footnotes.

Run searches and copy tests in an approved environment

Search the final PDF for the removed text and useful variants, such as a surname alone or the digits of a reference. Select around a redacted area and copy into a permitted local text field to see what comes through. If that test exposes protected information, handle the test text under the same rules as the original. A failed search can mean the words are gone or that the viewer could not search that part of the document. Combine the tests with a visual inspection and the tool’s hidden-content checks.

Ask for the right review

For a formal release, use the organisation’s independent check and approval procedure. Give the reviewer the exact release copy and the approved scope. If a version changes after review, repeat the necessary checks on the replacement. A quick review of the editing file is not equivalent to opening the saved deliverable.

Check the sharing destination

Confirm the attachment or link points to the release copy. A link to a folder can give the recipient access to more than the single redacted document. Use the sharing method and access settings required for the task. Keep the original and working copies in their permitted location and do not place them alongside public material.

Back to contents · Next section


Work through two common redaction examples

A sample worksheet for another class

The teacher wants to show a worked answer while following the school’s procedure for sharing student work. The source has a name at the top, the same surname in the filename and a note from the teacher in the margin. The working copy uses the approved redaction tool on the name and any details required by the policy. The teacher reviews the visible note and the PDF’s comments separately. The final name refers to the worksheet topic, and the copy is checked before distribution.

After saving, the teacher searches for the surname, checks the top and margins, and opens the exact file that will be shared. The worked method and required diagram remain visible. If there is a second attachment, it receives the same release check. The source stays in the approved school location.

A receipt with an unrelated identifier

A recipient requests the date, merchant and total, and confirms that an unrelated account reference may be removed. The page includes the number in two places and a code that may contain the same information. The person preparing the file checks the scope with the recipient, uses a dedicated redaction tool on the allowed areas and reviews the code according to that scope. They keep the original in case the issuer needs it through a separate process.

The released file retains the requested evidence. The reference is checked visually and through search where the text is searchable. If a form or portal requires an original receipt with all details, that requirement leads to a different submission. The accepted redaction scope comes before the edits.

Back to contents · Next section


Respond when the saved copy fails a check

Search still finds the original text

Stop using that copy as the release candidate. Check whether you opened the marked working copy, forgot to apply the redactions or missed a duplicate elsewhere. Rebuild or repair the copy in the approved editor. Apply, sanitise as required and reopen the new output. Run the same search and review every matching location.

A black bar covers part of an adjacent field

Start from the protected original if the underlying content has already been removed from the working copy. Mark the sensitive area more precisely, taking care that all its characters are covered by the redaction. Inspect the surrounding text after applying. If the disclosure procedure calls for a broader area to be removed, follow that scope.

You think the wrong file was already shared

Follow the organisation’s reporting and containment process promptly. Record the file, recipient or access location and what information may have been exposed. If you have authorised controls to restrict a shared link, follow the approved process for doing so. Sending a replacement does not remove a copy someone already downloaded. For a personal exchange, use the recipient’s official channel and the service’s available access controls.

Back to contents · Next section


Practise redaction and verification on a harmless example

Create a short test PDF with a fictional name on the first page, the same name in a footer and a fictional reference in a paragraph. Add a review comment containing the name if your app supports comments. Use made-up details that you are comfortable copying in the test. Save one original and two working copies.

Compare a shape with a redaction

In one test copy, draw an ordinary filled shape over the name. Reopen it and see whether you can still search for the name or copy the text around the shape. In the other copy, apply the dedicated redaction tool to both instances and save the output. Reopen it and repeat the tests. Use the hidden-information workflow on the comment as appropriate and check that the final copy does not expose it.

The visual difference between the two files may be small. The search and copying tests reveal why the tools are different. The mark you draw on top of a page can leave information underneath. The tool that applies the redaction is designed to remove the selected content. A complete release check also includes a review of the file elements your test does not show.

Try a second example with a scanned page

Print or create an image of a short fictional note with a date and code. Make a PDF from it. If your tool supports OCR, create a searchable copy of the image before applying redaction. Redact the code using the approved area tool and check the saved copy visually. Search for the code afterward and inspect the neighbouring words. The test should show you how the tool handles visible pixels and any recognised text.

Set a clear stop point for the real task

The release copy should pass the required review before it is shared. If one check still shows sensitive content, stop and correct the output. If you cannot tell whether a hidden element was removed, use the approved workflow or have the responsible person review it. Keep the source protected while you work. Once the release copy has passed, share only that file through the required channel.

Back to contents · Next section


Use a final handoff check for formal releases

Identify the exact approved copy by its name, location and version. Reopen it after review and compare it with the item selected in the upload or message. When a second person verifies the file, give them the scope of the review without putting the sensitive values into an unapproved note. Use the organisation’s recordkeeping procedure to capture the approval.

If you have to regenerate the PDF because a page changed or an attachment was added, treat it as a new release candidate. Apply the required checks again. An earlier approval belongs to the file that was actually reviewed. Confirm the recipient and access level before sharing the replacement. In an ordinary household exchange, the same habit of checking the saved file and its destination helps prevent confusion between similarly named copies.

Back to contents · Next section


Prepare a clean copy when the source has revision history

If you control the original document and the owner approves a new release version, you may be able to remove private material at the source and export a new PDF. Review the export from the point of view of the recipient. A clean-looking source document can still contain comments, revision information, links or references outside the visible text. Use the organisation’s approved settings for the source and repeat the PDF checks on the exported file.

Keep the editable source in its approved location. If the request is for a PDF only, confirm that the attachment is the final PDF and that you have not also attached the editable source. A share link to a working folder can expose versions beyond the one you intended to release. Confirm the scope of access from the sharing interface you are authorised to use. For formal disclosure, use the review and release route the document owner specifies. Record which copy passed that check so a later replacement is reviewed on its own merits.

Back to contents · Frequently asked questions


Frequently asked questions

Is a black rectangle enough to redact a PDF?

A rectangle can leave the underlying text or image data in the file. Use a dedicated redaction tool, apply the marks and verify the saved output.

Does searching the file prove the information is gone?

Search is one check. It can miss image text, recognition errors or hidden information. Inspect the final file visually and use the approved hidden-content checks.

Can I redact a scanned PDF?

Yes, with a suitable tool that supports redacting the relevant page area. Check the visible image and any searchable text layer after saving.

Can I undo a redaction after applying it?

Applied redaction is intended to remove content permanently in the released copy. Keep the protected original so you can rebuild the output when necessary.

What is the difference between redacting and sanitising?

Redacting removes selected page content. Sanitising addresses hidden information that may remain elsewhere in the PDF. Review both as required by the release scope.

Will redaction affect a digital signature?

Changing the file can affect signature verification. Keep the signed original and follow the issuer’s instructions before preparing or sharing a redacted copy.

Can I use a free online redaction tool?

Check whether the tool performs permanent removal and whether the document can be uploaded to that service under your rules. Use the approved local or managed workflow when the content requires it.


Helpful reading

Release the checked copy

Open the file you intend to send, verify the visible and hidden content, and confirm that the attachment or link points to that copy. Keep the original and working files in their approved location.