What Is the PDF Info Dictionary?
The PDF Info Dictionary is one of the classic places where file metadata lives. Runs locally in your browser. No uploads.
If you send PDFs outside your immediate team, these fields are worth understanding because they often survive routine document handling.
Trust box
- Local processing: Core document handling runs in local browser memory on your own device.
- No uploads: Runs locally in your browser. No uploads.
- No tracking: No behavioural tracking is required for the local PDF workflows described here.
- Verify this claim: /verify-claims
Table of contents
Trust explainer framework
The PDF Info Dictionary is one of the classic places where file metadata lives. Runs locally in your browser. No uploads.
When this explainer helps
- You need to validate privacy claims before adopting a document tool.
- You are handling sensitive files and require no-upload controls.
- You need practical trade-offs between local and hosted workflows.
Verification workflow
- Run one representative workflow and inspect network traffic in DevTools.
- Document what is verifiable versus what is policy-only.
- Choose the processing model that matches your risk class.
Trade-offs and caveats
- Local-first processing reduces exposure but is not a full security programme.
- Device security, access control, and governance still matter.
- Tool behaviour can change over time and should be re-verified.
Privacy note
Local processing: Core document handling runs in local browser memory on your own device. Runs locally in your browser. No uploads.
Related tools and comparisons
Related questions
- Is the PDF Info Dictionary visible on the page?
- Can the Info Dictionary identify who created a document?
- Do I need to clean both XMP and the Info Dictionary?
- Is metadata cleanup always appropriate?
Contextual links
Apply this guide directly: Use Metadata Purge locally, then Compare Plain Tools with cloud alternatives and verify no-upload claims yourself. If your issue is service availability, run a quick site-status check before deeper troubleshooting.
What the Info Dictionary does
The Info Dictionary stores basic descriptive properties for a PDF, such as title, author, subject, keywords, creator, and producer.
These fields can be harmless, useful, or sensitive depending on the workflow and recipient.
Common fields that can leak context
Author, creator, producer, and timestamps are the usual places to start. They can reveal who made the file, with what software, and sometimes when it moved through a workflow.
That is often more context than the recipient needs.
How it differs from XMP
The Info Dictionary and XMP are related but separate metadata layers. A PDF can hold overlapping information in both places.
That is why a proper metadata cleanup workflow should consider more than one field set.
How to review and clean it
Before external sharing, inspect metadata and decide whether those properties are still needed.
If not, remove them locally so the visible document and the hidden metadata tell the same story.
FAQ
Is the PDF Info Dictionary visible on the page?
No. It is part of the file structure, not the visible document body.
Can the Info Dictionary identify who created a document?
Yes. Author, creator, producer, and related fields can expose workflow details or authorship clues.
Do I need to clean both XMP and the Info Dictionary?
Often yes. If the goal is metadata minimisation, it is safer to review and clean both layers rather than assuming one field set is enough.
Is metadata cleanup always appropriate?
Only when it aligns with the workflow. Some archival or internal uses may intentionally keep metadata, but external sharing often benefits from minimisation.
Next steps
Continue with related tools, comparisons, and practical guides.