Last updated: July 17, 2026
PDF Metadata Export Test: What Remained and What Was Removed
Visible page text is only part of a PDF. We generated a synthetic document with deliberate metadata, created a cleaned copy, and inspected both files. The first exposed five descriptive values; the second retained only a neutral title. This provides a concrete checklist for users who share resumes, contracts, invoices, and forms.
The before file
The metadata-before sample contains these deliberate values: title “Draft Contract Notes,” author “Example Author,” subject “Synthetic metadata inspection sample,” creator “JUST FREE PDF Test Generator,” and producer “JUST FREE PDF Synthetic Test.” None is private, but each represents a category that can expose real information in an ordinary document.
The cleaned file
The metadata-cleaned sample retains a neutral title, “Shared PDF,” while author, subject, creator, and producer values are blank. Both files retain the same visible page text. The change therefore demonstrates why visual inspection alone cannot confirm metadata privacy.
| Property | Before | Cleaned copy |
|---|---|---|
| Title | Draft Contract Notes | Shared PDF |
| Author | Example Author | Blank |
| Subject | Synthetic metadata inspection sample | Blank |
| Creator | JUST FREE PDF Test Generator | Blank |
| Producer | JUST FREE PDF Synthetic Test | Blank |
Why metadata appears
Source applications often write the document title, author account, application name, creation date, modification date, and producer library automatically. An exported resume can reveal a workstation username. A contract draft can retain an internal project title. A converted scan can reveal the scanning software or workflow.
Metadata is not the only hidden content
PDFs can also contain comments, attachments, layers, form values, bookmarks, JavaScript actions, OCR text, embedded files, and previous revision data. Removing the author field does not sanitize those items. High-risk documents need a dedicated inspection and sanitization process.
Failure case: changing the filename only
Renaming “Draft-Client-A.pdf” to “document.pdf” changes the download name but not the internal title or author metadata. Some viewers display the internal title in the tab instead of the filename. Inspect both.
Failure case: a PDF printer adds new metadata
Printing to PDF may flatten fields and annotations, but the new PDF driver can add its own producer and creation data. It may also reduce accessibility, remove links, change page size, or rasterize content. Treat printing as a transformation that must be reviewed, not a guaranteed privacy tool.
JUST FREE PDF boundary
Do not assume the editor automatically removes all metadata or hidden content. The product can support visible edits and exports, but users should inspect the downloaded file and use a dedicated metadata or sanitization tool when the document is sensitive.
Export review steps
- Use a non-sensitive copy for testing.
- Open document properties in the exported file.
- Check title, author, subject, keywords, creator, producer, and dates.
- Inspect comments, attachments, layers, bookmarks, and form values.
- Search for old names and project terms.
- Open the file on another device or viewer.
- Share through the recipient’s approved channel.
When not to use a general browser workflow
Use approved enterprise or offline sanitization for client-confidential material, medical information, legal discovery, identity records, security reports, unreleased financial information, or documents subject to retention and disclosure rules. Metadata removal can have legal consequences when records must be preserved.
Reproduce the result
The exact metadata captured by the automated inspection is published in the JSON result file. File hashes are included so a reviewer can confirm that the inspected files match the downloads.
Keep evidence when metadata must be preserved
Metadata is not always something to remove. Records-management, litigation, audit, design, and publishing workflows may require creator, date, version, or producer information. Before cleaning a file, determine whether the recipient expects those properties. Keep the original and record what was changed so privacy cleanup does not become accidental evidence destruction.
Check the receiving channel too
A clean PDF can gain new context when it is attached to an email, uploaded under an identifying account, stored in a shared cloud folder, or renamed by a portal. Metadata review should therefore include the transmission method. Use the recipient’s secure channel and avoid placing confidential names or identifiers in the filename, subject line, or public share link.
Hash the final copy when integrity matters
A SHA-256 hash can identify the exact file that was inspected and delivered. The synthetic result file publishes hashes for this reason. In an organizational workflow, record the hash only when policy permits and store it with the review record, not as a substitute for access control or secure transmission.
Repeat the properties check after any conversion, merge, print-to-PDF step, or portal download because those operations can create new metadata.