How to Remove Metadata from PDF Files

Where PDF metadata can live

The familiar fields shown in a PDF reader—title, author, subject, keywords, creator application, producer, creation date, and modification date—are commonly exposed through the document information dictionary. A PDF may also contain an XMP metadata packet and application-specific custom data.

Beyond metadata, PDF files can include annotations, attachments, form values, JavaScript actions, layers, comments, signatures, and content that was visually covered but not securely redacted. The Adobe PDF technical references describe these as distinct structures. Clearing the author field does not inspect all of them.

How to remove supported PDF metadata

1. Keep the original. Work from a copy, especially if the document is signed, encrypted, form-enabled, or part of a legal workflow.
2. Open the PDF tool. Select the file in the browser. metapeel reads it locally with the PDF library; the document is not uploaded to a metapeel processing server.
3. Review the detected properties. Check title, author, subject, keywords, creator, producer, and the date fields shown.
4. Create and download the cleaned copy. The current PDF path clears its supported property set together; it does not selectively preserve unchecked fields.
5. Open and inspect the output. Confirm that pages render correctly and that the targeted document properties no longer contain the original values.

The exact boundary of the current PDF cleaner

The implementation uses the documented pdf-lib PDFDocument property methods. That makes the supported property set auditable, but it also gives the article a firm limit: metapeel should not claim to remove every hidden element in a PDF.

Metadata removal is not PDF redaction

If a PDF contains a name in visible text, an image, a comment, an attachment, or text underneath a black rectangle, metadata cleaning will not make that information safe. Redaction changes or removes page content; sanitization reviews active and hidden structures; document-property cleaning handles descriptive fields. Treat them as separate checks.

Adobe's guidance on removing sensitive PDF content separates redaction from finding and removing hidden information. For a high-risk document, follow an approved redaction/sanitization process and validate the final export independently.

How to verify the cleaned PDF

1. Reopen the cleaned copy in metapeel and compare the detected standard properties with the original.
2. Open Document Properties in a desktop PDF reader and check title, author, subject, keywords, creator, producer, and dates.
3. Use a second metadata parser for sensitive sharing; different tools can expose different structures.
4. Review annotations, attachments, forms, layers, signatures, and redaction separately.
5. Open every page and confirm that the saved copy still renders and behaves as expected.

Verification should be scoped: “the standard author and date properties are cleared” is testable. “Nothing hidden remains anywhere in the PDF” requires a much broader examination.

What if the PDF came from Word, Excel, or PowerPoint?

Clean the editable source file separately before sharing it. OOXML and ODF documents have their own package metadata, comments, tracked changes, hidden sheets, and embedded content. metapeel's document tool clears supported core/application properties, but it does not replace Microsoft's Document Inspector or an equivalent application-native review.

For the distinction across all file types, return to the file metadata field guide. If the source includes photos, inspect those separately with the photo metadata workflow before placing them into a document.