Legal PDF work has a different failure profile from ordinary document work. The problem is rarely that a tool cannot do something; it is that a tool appears to have done something it did not do. Redaction that hides rather than removes, metadata that travels with a filing, form fields that are still editable when they reach the other side. This page is organised around those failure modes, because they are what actually causes damage, and only then around which software avoids them.
Drawing a filled black rectangle over a name produces a page that looks redacted and a file that is not. If the page was copied into the output document rather than re-rendered, the text object is still there, underneath the rectangle, and it can be recovered by selecting the area and pasting it elsewhere or by running any text extraction tool over the document. This is not a theoretical risk. It is one of the most reliably recurring categories of inadvertent disclosure in public court filings.
Every general-purpose drawing tool has this problem, ours included, and we would rather say so here than let you find out from opposing counsel. Do not use RaptorPDF's redaction tool on privileged or protected material. It draws an opaque rectangle. The text survives.
What a real redaction engine does is different in kind: it removes the content objects covering the redacted region and rewrites the page, and a serious implementation also offers a separate sanitisation step that strips metadata, embedded attachments, bookmarks, deleted-but-retained content from earlier saves, and any hidden text layer. That second step exists because redaction alone is insufficient, which tells you something about how many places a document can hide text.
If you must use a drawing tool, the only reliable way to destroy the underlying text is to rasterise every page afterwards, which converts the whole document to images. In our editor that means redacting and then running Compress, which re-renders each page as a JPEG. It works, and the cost is total: the entire document loses its text layer, so nothing is searchable, nothing is copyable, and it becomes inaccessible to screen readers. For a small exhibit that may be acceptable. For a filing it is usually not, and buying real redaction software is the correct answer.
Every PDF carries an information dictionary and usually an XMP block: Title, Author, Subject, Keywords, the creating application, and creation and modification timestamps. The Author field is normally filled in automatically from the operating system account of whoever exported the document, so a filing frequently names the associate who drafted it. Timestamps record when it was really written.
Check yours before filing. Document properties in any reader will show it, and
exiftool yourfile.pdf on a command line shows everything. If you export from Word, be aware
that Word document properties and, depending on export settings, comments and tracked changes can carry
through into the PDF.
One trap worth knowing: exiftool -all= file.pdf reports the metadata as deleted but writes the
change as an incremental update appended to the file, leaving the original values recoverable in the earlier
revision. Follow it with a rewrite such as qpdf --linearize, or use software that rebuilds the
document. As it happens, our rebuild-based tools such as merge and split drop the original Title, Author and
Keywords as a side effect, because they copy page objects into a new empty document. Our password
protection and form filling tools do not, because they load the original file. That is a quirk rather than a
feature, and it is not a substitute for a deliberate sanitisation step.
A completed court form whose AcroForm fields have not been flattened arrives as an editable form with values typed into it. Different readers render unflattened fields differently, some print them and some do not, and anyone can change them. Flatten before filing. Our form filler reads the AcroForm fields out of the PDF, lets you fill them, and flattens on download, which is the correct behaviour.
The mirror-image problem: annotations that are flattened when they should not be, or the reverse. Markup written as real PDF annotation objects appears in a reader's comment pane, carries an author name, and can be removed or replied to. Markup flattened into the page cannot be removed by anyone. Which you want depends entirely on whether the markup is a comment for a colleague or a permanent mark on an exhibit. Our annotation tool always flattens, so it is right for the second case and wrong for the first.
Bates numbering assigns a unique, prefixed, sequential identifier across a production set, so that SMITH000001 refers to exactly one page in the world and page 4,312 of a production has a number that makes sense in a deposition transcript. A page-number stamp is not this. Our page-number tool offers position, a few formats and a starting number. It has no prefix field and no concept of a production set, so it is not Bates numbering and should not be used as a substitute in discovery.
The only widely deployed product that covers the whole legal requirement list: redaction that removes content, a separate document sanitisation function, Bates numbering across a set, PDF/A output with validation, searchable-PDF recognition, and certificate-based digital signatures. It is a subscription and it is not cheap. It is also the thing that keeps you out of the four failure modes above, which is a different kind of value from a feature comparison. If you handle privileged material, treat this as infrastructure rather than as software you are shopping for.
Several commercial editors cover redaction, Bates numbering and PDF/A at lower cost, and are common in mid-size firms. The purchasing question worth asking a vendor is specific: does redaction remove content objects, is there a separate sanitisation step that strips metadata and hidden layers, and can PDF/A output be validated rather than merely labelled. Ask in those terms and the answers become informative.
A separate category and a genuinely different job. For marking up a deposition transcript or a bundle in a hearing, a stylus-based tablet app beats any desktop editor, and the reason is speed of input rather than features. Look for real PDF annotation output so the marks survive into the file, and check how the app handles a 2,000-page bundle before you rely on it in court.
Underrated for legal work. qpdf splits, merges, decrypts with a known password, and rewrites
files deterministically, which makes it useful in a repeatable production workflow. exiftool
reads and writes metadata, subject to the incremental-update caveat above. Both are free and both are more
predictable than a GUI when you are processing a few hundred documents the same way.
Suitable for day-to-day handling where the document is not privileged or where the operation is structural: assembling exhibits, splitting a long agreement, filling and flattening a form, placing a signature, applying a password before emailing. It runs entirely in the browser, so client documents are not uploaded anywhere, which for a professional-confidentiality duty is a meaningful property rather than a marketing one. Free covers three operations a day with files up to 50 MB; Pro is $4.99 a month or $39.99 a year with a 300 MB ceiling.
Not suitable for: redaction of privileged material, Bates numbering, PDF/A, certificate signatures, searchable-PDF recognition, metadata sanitisation, or editing text already in a document. For a practice handling any volume of protected material, this is a supplement to real legal PDF software, not a replacement for it.
PDF/A is an ISO standard for archival PDFs. The variants differ in what they permit:
E-filing requirements vary by court and are set in local rules rather than by a single national standard. Some accept ordinary PDF, some prefer or require PDF/A, and many impose their own constraints on file size, page dimensions and whether the document may be encrypted. A password-protected PDF will typically be rejected outright. Read the local rules for the specific court, and validate the output rather than trusting that a save dialog labelled PDF/A produced a conformant file.
These are routinely conflated and they are not the same property.
Electronic signature is a legal concept. Under the US ESIGN Act and state adoptions of UETA, a signature in electronic form is generally as enforceable as one on paper, provided the parties intended to sign and consented to transact electronically. Enforceability here is a question of intent and of your evidence that a particular person signed. It is not a question of cryptography. A drawn image of a signature can satisfy it. So can typing a name.
Digital signature is a technical mechanism. A private key signs a hash of the document, so a verifier can establish that the document has not been altered since signing and that the signature was made with a key bound to an identity by a certificate. This gives you integrity and attribution evidence, which is a different thing from enforceability.
The practical consequence: a drawn signature is usually enough for enforceability and weak on evidence. If a signature is likely to be contested, what you want is either a dedicated e-signature platform, which produces an audit trail recording who signed, when, from where, and what they saw, or certificate-based signing, which makes subsequent alteration detectable. Our signature tool provides neither, and for contested or high-value instruments you should not be using it.
Also note the categories where electronic signatures are commonly excluded by statute or practice: wills, codicils and testamentary trusts, certain family law orders, and various court orders and notarised instruments. These vary by jurisdiction. Check before you rely on one.
Merging, splitting, form filling, signing and password protection in the browser, with no upload. Not for redaction of privileged material.
Open the editorAdobe Acrobat Pro, for one specific reason rather than a feature count: it is the widely available product that combines redaction which removes content objects, a separate sanitisation pass, Bates numbering across a production set, validated PDF/A output and certificate-based signatures. Those are the capabilities whose absence causes real harm. Commercial alternatives such as Foxit cover much of the same ground at lower cost; verify redaction and sanitisation behaviour specifically before buying.
For structural work, yes: assembling exhibits, splitting agreements, filling and flattening forms, placing a signature, applying a password. A browser-based tool has the additional advantage of not uploading client files anywhere. What free tools must not be used for is redaction of privileged material, Bates numbering, PDF/A filing output, certificate signatures or metadata sanitisation.
No. If the page was not re-rendered, the text object remains in the file beneath the rectangle and can be recovered by copying the area or by running a text extractor over the document. This is a recurring source of inadvertent disclosure in public filings. Real redaction removes the content objects and is normally paired with a sanitisation step that also strips metadata, attachments and hidden layers.
Bates numbering assigns a unique prefixed sequential identifier across a whole production set, such as SMITH000001, so any page can be referenced unambiguously in a deposition or brief. A page-number stamp adds a number per document with no prefix and no concept of a set, so it is not a substitute in discovery.
Generally yes for contracts, under the ESIGN Act and state UETA adoptions, where the parties intended to sign and consented to transact electronically. Enforceability turns on intent and on your evidence of attribution rather than on any cryptography. Commonly excluded categories include wills, codicils, testamentary trusts, some family law orders and notarised instruments, and the exclusions vary by jurisdiction. For anything likely to be contested, use a platform that produces an audit trail or certificate-based signing, both of which give you evidence a drawn signature does not.
It depends on the court, because e-filing requirements are set in local rules. Some accept ordinary PDF and some prefer or require PDF/A, and many add their own constraints on file size and page dimensions. Encrypted PDFs are usually rejected. Check the local rules for the specific court and validate the output rather than assuming a save dialog labelled PDF/A produced a conformant file.
Open document properties in any reader, or run exiftool on the file for the full picture, including the Author field, which is usually populated automatically from the exporting computer's account name. Note that exiftool -all= on a PDF writes an incremental update rather than rewriting the file, so the old values stay recoverable until you rewrite it with something like qpdf --linearize.