Edit standard Document Info
The PDF metadata editor changes title, author, subject, keywords, creator, producer, creation date, and modification date in the traditional Document Info dictionary.
Private PDF utility
Use this free online PDF metadata editor with no sign-up to review and change standard PDF properties. Your file stays on your device, and the saved copy is verified before download.
PDF EditorPDF Metadata Editor
One PDF · 25 MB max
Clear scope
The PDF metadata editor updates the standard Document Info dictionary used by common PDF readers. Existing XMP stays untouched, so the tool does not silently rewrite a separate metadata source.
The PDF metadata editor changes title, author, subject, keywords, creator, producer, creation date, and modification date in the traditional Document Info dictionary.
Existing document and page XMP packets stay intact. The interface reports their presence so you can choose the remover when your task requires supported XMP cleanup.
After saving, the browser reparses the output and compares every requested Document Info value. Download appears only after the supported result passes verification.
Three steps
The free online PDF metadata editor follows a visible three-step workflow with no sign-up. It keeps the original file on your device and creates a separate verified copy for download.
Choose one PDF up to 25 MB. The PDF metadata editor reads its supported fields inside this browser tab.
Change title, author, subject, keywords, creator, producer, creation date, or modification date.
Save the copy, let the PDF metadata editor verify every requested field, then download the result.
Practical uses
Use the editor when descriptive PDF properties are useful but inaccurate, outdated, or incomplete. Each example below stays within the supported Document Info boundary.
Give a report, ebook, portfolio, résumé, proposal, or public download an accurate title, author, subject, and keywords before release. The PDF metadata editor can correct those supported fields without changing the visible page design.
Files exported by different applications can carry inconsistent creator, producer, and date values. Use a deliberate naming policy, update the fields that matter, and verify the new copy before it enters an archive or shared library.
An older project name, draft subject, former author label, or irrelevant keyword can remain after visible content is revised. Inspect first, change only the supported values you understand, and retain meaningful metadata when it serves readers.
Detailed guide
Open a topic when you need more detail about Document Info, XMP, privacy, verification, or the right tool for the job. The notes below describe the exact PDF metadata editor boundary. If you need a supported cleanup instead of a field change, read how to remove metadata from PDF. To look up the eight standard keys, open PDF metadata fields. To see why Document Info and XMP can disagree, read PDF metadata vs XMP.
Document Info stores descriptive properties separately from visible pages: title, author, subject, keywords, creator, producer, and creation and modification dates. This PDF metadata editor reads those eight fields into a form and writes your changes into a new copy. Blank fields stay blank; the tool does not infer an author or title from page content.
Title, author, subject, and keywords help identify a document. Creator usually names the originating application; producer names the software that generated the PDF. Applications may rewrite dates during export. These descriptive values do not prove authorship, ownership, publication time, legal status, or who last changed the file.
The PDF metadata editor does not change visible text, images, page order, OCR, permissions, or annotations. It creates a separate output after checking the requested Document Info changes; your source file is not edited or renamed in place.
A PDF may contain Document Info, XML-based XMP, both, or neither. Their values can conflict, and a reader or publishing system may prefer one source. Updating Document Info therefore does not update every metadata value in the file.
This PDF metadata editor preserves existing XMP and reports detectable document or page XMP separately. It does not expose individual XMP properties for editing. An old author or title can remain in XMP even after you correct the corresponding Document Info field.
Use the remover to clear the complete Info dictionary and detectable document/page XMP references, or the viewer for a read-only report. Detailed XMP editing, archival profiles, embedded assets, and custom objects require specialist software and verification against your workflow requirements.
Open a copy of the exact PDF you intend to publish. In the PDF metadata editor, keep useful fields, correct inaccuracies, and clear values only when your publishing policy requires it. A later export can replace your edits. Metadata presence alone does not indicate a privacy problem.
Write a descriptive title, use the intended author attribution, and avoid private project labels in keywords. Creator, producer, and dates may support troubleshooting or records management. Confirm legally or archivally significant values with the document owner before changing them.
After saving, the tool reparses the output and checks each requested Document Info value. Download it, inspect its pages and properties in your usual reader, and keep the original until your review passes. Recheck after later printing, merging, conversion, signing, or uploading, which can introduce new metadata.
The PDF metadata editor needs no account and processes files in browser memory without uploading them. This does not replace device security: downloaded copies may still be indexed, backed up, synchronized, or shared by your operating system, browser, cloud folder, or other software.
Encrypted or password-protected PDFs fail fast because the editor has no decryption feature. Use an authorized decryption workflow first and follow the document owner’s policy. When a signature field is detected, the tool allows supported read-only inspection and disables writing. Rewriting a signed PDF can invalidate the signature or change its verification status, even when the visible content appears unchanged.
The browser accepts one PDF up to 25 MB, with no folder batches or saved history. Successfully replacing the file or closing the tab clears the current work. Complex, regulated, or legally sensitive documents may require an approved desktop workflow and audit trail.
Choose the PDF metadata editor when supported Document Info values should remain useful but need correction. Typical tasks include replacing an inaccurate title, updating an author label, revising a subject, removing stale keywords, or normalizing creator, producer, and date fields. The editor keeps existing XMP and creates a verified output, making it suitable for precise changes within a known boundary.
Choose the viewer when you need a read-only report. It shows the supported Document Info fields, page count, Info entry count, detectable document and page XMP presence, and signature-field status without creating a rewritten file. Inspection is often the best first step because it helps you see whether any supported value actually needs attention and whether a signed-file boundary applies.
The remover clears complete Document Info and detectable document/page XMP, then verifies their absence. None of these tools guarantees forensic sanitization: attachments, annotations, visible content, OCR, custom objects, historical revision data, and external records need separate review.
Know the limits
The PDF metadata editor changes standard Document Info fields and preserves existing XMP. It does not edit visible page content, OCR text, attachments, annotations, permissions, arbitrary custom objects, every historical revision artifact, or records stored by another service.
Saving produces a new PDF byte structure, so file size and internal ordering may change. The tool verifies requested Document Info values; it cannot guarantee identical rendering in every PDF reader or certify compliance with a specialized archival, legal, or publishing standard.
One PDF up to 25 MB is supported. Encrypted PDFs fail fast. A file with a detected signature field stays read-only because any rewrite can affect signature validity or verification status.
FAQ
These answers cover the PDF metadata editor fields, local processing, XMP boundary, verification, and the choice between editing, viewing, and removal.
Yes. This free PDF metadata editor works online for one PDF up to 25 MB with no sign-up. It reads, changes, saves, and verifies the supported metadata in your browser before it offers the new file for download.
You can change title, author, subject, keywords, creator, producer, creation date, and modification date in the standard PDF Document Info dictionary. The tool also shows the supported values before you edit them.
No PDF upload endpoint is used. Reading, editing, saving, output verification, and download preparation happen in browser memory on your device. Closing the tab or replacing the file clears the current tool state.
No. The PDF metadata editor preserves existing XMP packets and changes only standard Document Info. Use the remover when your goal is to clear Document Info plus detectable document-level and page-level XMP streams.
Encrypted PDFs are rejected because this browser tool has no decryption workflow. A PDF with a signature field can be inspected, while editing and removal stay disabled because rewriting the file can invalidate its signature state.
The PDF metadata editor does not intentionally change visible page content. Saving creates a new PDF byte structure, so file size and internal ordering can change even when the pages look the same. Always review the downloaded copy in your normal PDF reader.
Yes. Leave a supported Document Info field empty, save the result, and the editor will verify that requested value in the output. For a broader supported cleanup that also removes detectable XMP references, use the dedicated remover.
Edit when a useful title, author, subject, keyword, creator, producer, or date needs correction. Remove when your policy calls for clearing the complete Document Info dictionary and detectable document or page XMP. Use the read-only viewer when you only need a report.
Related tools
Use one page for one task. Inspect supported properties with the read-only viewer, or clear supported metadata structures with the remover.
Check Document Info, page count, detectable XMP presence, and signature-field status without creating an output file.
Clear the complete Document Info dictionary and detectable document or page XMP, then verify the saved copy before download.
Choose one PDF, make only the supported changes you need, and download a verified copy. No upload or sign-up is required, and your source file stays on your device.
Edit PDF metadata