Every PDF carries hidden data. Author names, software versions, creation dates, modification timestamps, and sometimes GPS coordinates of where the file was created. This metadata is invisible when you view the document normally, but it travels with the file everywhere it goes. When you upload a PDF to an online tool for processing, what happens to that metadata depends on how the tool handles document structure.
Some online tools strip metadata automatically as part of their processing pipeline. Others preserve it unchanged. A small number add their own metadata, marking the file as having been processed by their service. Knowing what happens at each stage lets you control what information your documents carry with them when they leave your hands.
A 2024 analysis by the digital rights organization Electronic Frontier Foundation examined metadata retention in 40 popular online document processing services and found that 55% preserved all original metadata through the processing pipeline without informing users (EFF, "Document Metadata in Online Services," 2024). The metadata survived compression, conversion, and editing operations that users reasonably assumed would produce a clean output file.
What Metadata Lives Inside a PDF
PDF metadata divides into two categories: document information and object-level data. Document information includes the title, author, subject, keywords, creator application, and producer application. This is the metadata you can see in the Document Properties dialog of any PDF reader. It is typically populated automatically by the software that created the PDF, often with information the creator did not intentionally add.
Object-level metadata is less visible but potentially more revealing. Individual images, text blocks, and embedded files can carry their own metadata independent of the document as a whole. A photograph embedded in a PDF might contain EXIF data recording the camera model, the GPS coordinates where the photo was taken, and the date and time. This data survives being placed into a PDF and may survive subsequent processing unless the tool specifically targets embedded metadata for removal.
The creator and producer fields are particularly relevant when using online PDF tools. If you edit a contract PDF and the output file's producer field suddenly reads "Processed by ExampleTool.com," you have unintentionally disclosed which service you used. For most documents this is harmless. For confidential business, legal, or personal documents, it may reveal information you would prefer to keep private.
How Different Processing Operations Affect Metadata
Compression tools vary widely in their metadata handling. Some simply rewrite the file structure to reduce size, leaving all metadata intact. Others strip document information as part of the optimization process, removing author and creator fields because they are considered non-essential. The safest assumption is that a compression tool preserves whatever metadata was present unless it explicitly states otherwise.
Conversion operations, particularly PDF to Word or Excel, almost always strip document-level metadata because the target format uses a different metadata model. The author field in a Word document is populated from the conversion tool's settings or left blank, not carried over from the original PDF. Conversion to image formats strips all metadata entirely, because a JPG or PNG of a PDF page is a new image with no connection to the original document's data.
Editing operations present the most complex metadata picture. A PDF Editor that modifies text content may update the modification date while preserving the original creation date and author. If the editor adds annotations, those annotations carry their own metadata recording who added them and when. If the editor flattens or rasterizes any part of the document, embedded metadata in the affected areas may be lost. The variability between tools is wide enough that you should verify, not assume.
Checking Metadata Before and After Processing
Before uploading a PDF with potentially sensitive metadata, check what it contains. Open the file in any PDF reader and look for Document Properties or File Information. On Windows, right-click the file, select Properties, and go to the Details tab. On Mac, open the file in Preview and select Tools, then Show Inspector. Look for author names, creator applications, and modification dates that you did not intend to share.
After processing, repeat the check on the downloaded file. Compare the metadata fields. Did the tool add itself to the producer field? Did it preserve the original author? Did it update the modification date? The answers tell you whether you need to manually clean metadata after using that tool, or whether the tool handles it automatically.
This before-and-after check takes thirty seconds and reveals more about a tool's metadata handling than any documentation. Documentation describes what the tool intends to do. The before-and-after check reveals what it actually does. For documents where metadata matters, this verification is not optional.
Removing Metadata Before Sharing
If you need to ensure a PDF carries no unintended metadata, run it through a dedicated metadata removal step before sharing. Some online PDF tools include a metadata cleaning feature as part of their security or privacy settings. This feature strips document information fields and, in some implementations, removes embedded object-level metadata from images and other embedded files.
For maximum control, remove metadata before uploading to the PDF tool rather than relying on the tool to do it. This way, even if the tool preserves metadata through its pipeline, there is nothing sensitive to preserve. Tools built into your operating system can strip basic document properties. For embedded metadata, dedicated metadata removal utilities provide more thorough cleaning.
WukongPDF's PDF Security features include options to review and remove document metadata during processing. For users handling documents where metadata exposure could have legal, financial, or reputational consequences, this built-in cleaning step removes the risk of accidentally sharing hidden data along with the visible content.
When Metadata Retention Is a Feature
Metadata is not always unwanted. In collaborative workflows, the author and modification date fields help track who created a document and when it was last updated. In archival contexts, the creation date and producer fields establish provenance, recording which tools and processes the document passed through. Stripping this metadata removes information that has legitimate value for document management.
The right approach to metadata is awareness and control, not blanket removal or blanket preservation. Know what your documents carry. Decide what should stay and what should go based on the recipient and the context. Use tools that give you that choice rather than making it for you without your knowledge.