PDF Metadata Editor

PDF Metadata Editor — View and Modify PDF Properties

Every PDF you have ever created, downloaded, or received in an email carries a hidden layer of information called metadata. It is not visible on the page itself — you will not see it when you print the document — but it travels with the file everywhere it goes. This metadata records the document's title, the name of whoever created it, the software that was used to produce it, when it was first generated, when it was last modified, and a variety of other properties that most people never think about. That anonymity is fine until it is not. You have probably received a PDF at some point where the title bar reads "FINAL_v3_real_final_COPY.pdf" or where the author field shows someone else's name because the file was built from their template. That is metadata causing a small but real professionalism problem, and this tool exists to fix it.

Our metadata editor lets you view and modify the most important PDF document properties directly in your browser. Nothing gets uploaded. The file stays on your device, the changes happen locally, and you download the modified version. For anyone handling sensitive, confidential, or client-facing documents, that local-only processing model is not just convenient — it is essential.

What Exactly Lives Inside PDF Metadata?

PDF metadata is structured information stored in a dedicated section of the file, separate from the visible page content. Think of it as the label on a manila folder — it tells you what is inside without being part of the contents themselves. The PDF specification defines a standard metadata dictionary with specific fields, and it also allows for extended metadata through the XMP (Extensible Metadata Platform) standard. The fields you will encounter and work with most frequently are these.

Title is the human-readable name of the document as displayed by PDF readers in their title bar or tab. If this field is empty, most readers fall back to displaying the filename instead — which is why you often see raw filenames like "scan_029384.pdf" at the top of documents that clearly deserve better. A well-filled title field immediately elevates how a document appears in professional settings. Author records the person or organization credited as the creator. Many PDF-producing applications auto-fill this from the current user profile, which means it might say "John's Laptop" or "TEMPLATE_USER" if nobody bothered to configure it. Subject is a short description of the document's content — useful for categorization but frequently left blank. Keywords are searchable tags that document management systems and search engines use to index and retrieve files. Think of them as hashtags for your PDFs. Creator and Producer are read-only fields that record the software chain that produced the file — "Microsoft Word" or "Adobe InDesign" for the creator, and the specific PDF generation library for the producer. Creation Date and Modification Date are timestamps set automatically by the software. These cannot be manually changed through standard editing, which preserves an accurate history of when the document was born and when it was last touched.

XMP Metadata and Dublin Core: The Deeper Layers

While the standard document information dictionary covers the basics, modern PDFs increasingly use XMP metadata for richer, more structured information. XMP is an XML-based standard developed by Adobe that can store the same fields as the standard dictionary — title, author, subject — plus much more: color management profiles, copyright status, usage rights, geolocation data, and custom application-specific properties. XMP data lives in a dedicated metadata stream inside the PDF, and it can be quite extensive on files produced by professional design and prepress tools.

Dublin Core is a metadata standard that XMP often follows. It defines a set of fifteen core elements — title, creator, subject, description, publisher, contributor, date, type, format, identifier, source, language, relation, coverage, and rights — that provide a consistent framework for describing documents across different systems. If you work in an environment that uses Dublin Core-compliant metadata (academic repositories, government document systems, library archives), keeping your PDF's metadata aligned with those elements ensures your files are discoverable and properly cataloged. Our tool edits the standard document information dictionary fields, which map directly to several Dublin Core elements. For full XMP editing — including custom properties and nested XML structures — you would need a more specialized tool that can parse and modify the XML stream directly.

Creator vs. Producer: Why the Distinction Matters

This confuses almost everyone at first, so it is worth clarifying. The Creator field records the application that originally authored the document — the word processor, spreadsheet program, or design tool where someone first typed content. The Producer field records the software that actually generated the PDF file, which is often a different program. For example, if you write a letter in Google Docs and export it to PDF, the Creator might say "Google Docs" while the Producer says "Adobe PDF Library" or whatever backend library Google uses for PDF export.

In practice, the Producer field is more useful for technical forensics — it can reveal exactly which PDF generation engine was used, which matters for compatibility testing and troubleshooting. The Creator field is more relevant for understanding provenance: who or what made this document. Both fields are read-only in our tool because they represent factual history about the document's creation. Altering them would be misleading, much like changing a photograph's EXIF data to hide which camera took it.

Privacy and Metadata: The Information You Might Be Accidentally Sharing

This is the aspect that catches people off guard most often. When you share a PDF, you may be sharing significantly more than the visible content. The author field can reveal who created the document even if you carefully removed their name from the text. The creator software field might disclose that you used a specific proprietary application. The producer field could inadvertently expose that an internal document was converted from a source file on a workstation named "CFO_WORKSTATION_3." The modification date history can reveal how many times a contract was revised and exactly when each revision occurred — potentially valuable information in a negotiation context.

Before publishing PDFs to the internet, submitting them to public repositories, or sharing them outside your organization, review the metadata carefully. Set the author to something generic or remove it entirely. Clear the title if it reveals internal project codenames or draft statuses. Adjust keywords to reflect what you actually want associated with the document publicly. This process — commonly called metadata scrubbing — is standard practice in legal document production, financial reporting, and any context where documents move between organizations. The European Union's GDPR and similar regulations have made metadata awareness even more important, since hidden personal information in metadata can constitute a data protection issue.

Custom Fields and Extended Properties

Beyond the standard dictionary fields, PDFs can carry custom metadata through XMP extensions and application-specific data pockets. Some organizations use these custom fields to embed project codes, document classifications, workflow statuses, or integration identifiers that their internal systems read programmatically. For example, a legal firm might tag each PDF with a case number in a custom metadata field, allowing their document management system to auto-file incoming documents without manual sorting.

While our tool focuses on the standard editable fields — title, author, subject, keywords — understanding that custom metadata exists helps you ask the right questions when working with PDFs in enterprise environments. If someone tells you "the metadata is wrong" and the standard fields look fine, the issue might be in an XMP custom property or an application-specific metadata stream that requires a more specialized editor to access and modify.

Metadata Best Practices for Common Workflows

Freelancers and agencies: Set the author to your company name and the title to the project title before delivering final PDFs to clients. It is a small touch that looks professional and helps clients organize their files. Avoid leaving template metadata — "Acme Corp" from a previous client's template shows up on your deliverable, which is embarrassing at best and a confidentiality breach at worst. Academic researchers: Add relevant keywords to research paper PDFs to make them discoverable in reference managers like Zotero, Mendeley, and EndNote, which read metadata to auto-populate citation fields. A paper tagged with the right keywords gets found; a paper with no keywords stays buried. Legal professionals: Strip or update metadata on discovery documents before production to avoid disclosing privileged information about document creation, revision history, or authorship. Courts have sanctioned parties for metadata leaks, so this is not theoretical risk — it is practical necessity. IT and records management: Establish metadata conventions early in any document migration project. Define a consistent title format, a standard author value for your organization, and a controlled vocabulary for keywords. Files tagged correctly from the start are findable for years; files with blank or inconsistent metadata become digital lost-and-found items within months.

How Metadata Affects Searchability and Indexing

Search engines like Google read PDF metadata when indexing documents for their search results. A clear, descriptive title and well-chosen keywords directly influence how high your PDF appears in relevant searches. A PDF titled "Q3 2025 Financial Summary" with appropriate keywords will surface for relevant queries; the same document with a blank title and no keywords will be buried pages deep in results, if it appears at all. Document management systems, corporate intranets, and cloud storage platforms all use metadata similarly — the title shows in file browsers, the author field enables "documents by" filtering, and keywords power the search index. Investing thirty seconds to set proper metadata before saving or sharing a PDF pays dividends in findability for the life of the document.

Frequently Asked Questions