PDF metadata editor made simpler, in your browser

A PDF may display a clean cover page while its document properties still name an earlier author, an old working title, or the software used to create it. This PDF metadata editor helps you inspect common properties, change chosen fields, or remove the document properties it explicitly supports. The tool reads the resulting file again before offering a download, so you can see what changed and what remains. Processing happens in your browser on your device; the selected PDF is not sent to a document processing API. The website's code and assets still load from its host.

Metadata is not one single field. Many PDFs have a traditional Info dictionary and a separate XML based XMP packet. A reader may show values from either place. This tool displays recognizable values from both side by side, and makes the scope of each action clear. Editing a field changes the Info value. If an older XMP value remains, the output audit shows it. You can optionally remove the document level XMP packet when editing, or choose the supported cleanup action to remove all Info keys and that packet together.

1. Choose one PDF. The file can be up to 30 MB and have 1 to 200 pages. Wait for the properties table to appear. An encrypted, damaged, or unsupported file reports an error instead of an invented result.
2. Compare Info and XMP. Check whether Title, Author, Subject, Keywords, Creator tool, Producer, and the creation and modification times agree across the two columns. A dash means no recognizable value was found in that location.
3. Select only the Info fields to edit. Check each intended field, then enter its replacement. A checked field left empty is removed from Info. An unchecked field keeps its original value. Dates accept a date such as 2026-10-01 or an ISO date and time with a timezone.
4. Decide whether to remove document XMP. If it contains conflicting or unwanted older values, use the separate XMP removal choice. That removes the whole document level XMP packet rather than trying to synchronize individual XML properties. Page level XMP is outside that choice.
5. Create, inspect, and download. The tool reopens its output, compares supported fields with the input, and lists remaining locations. Read that audit before downloading the new PDF. Keep the original until you have reviewed the new file in the PDF reader you use.

The PDF Info dictionary is a collection of document properties. Its familiar keys include Title, Author, Subject, Keywords, Creator, Producer, CreationDate, and ModDate. Some PDFs also include custom Info keys created by a workflow or application. The edit mode changes only the familiar fields you check. The clear mode removes every Info key it finds, including custom keys. The output audit lists removed key names, and it lists recognizable values that still remain after an edit.

XMP is an XML based metadata packet that can store similar information using different property names. For example, a title may appear as an XMP Dublin Core title while a software name may appear as an XMP producer or creator tool. A PDF reader might prefer XMP, Info, or a combination. If you change the Info title but leave a conflicting document XMP title in place, another reader can still show the old title. That is why the inspection table keeps the two sources separate. A recognizable XMP value in this tool is evidence about that packet, not a promise that every XMP namespace or custom property has been interpreted.

The tool checks for a document level XMP packet and reports whether it could decode it. When you request removal, it deletes that packet from the document catalog. A page can have its own XMP packet as well; the tool detects pages with such an entry and names the count, but does not alter them. An XMP packet may also contain properties that this simple table does not parse. If the packet is unreadable, its presence is still reported. Removing it can affect workflows that depend on its metadata, so retain an original copy for comparison.

Choose the clear action when your goal is to remove the ordinary document properties this tool supports. It removes all keys from the Info dictionary and removes the document level XMP packet, then reopens the generated PDF to check those locations. The audit reports the Info key count before and after, whether document XMP remains, each familiar field that changed, and names of Info keys removed. A custom Info key can be removed even though it has no dedicated input box in edit mode.

This cleanup is deliberately limited. It does not scan or erase visible page text, images, attachments, annotation authors, page level metadata, embedded files, scripts, form data, document history, or all possible identifying data in PDF objects. It may report some of those locations when their structures are detectable, including pages with XMP or annotations, attachments, document actions, and a file identifier. A missing indicator is not proof that no other hidden information exists. The output is not certified anonymous, and the tool is not a redaction or forensic sanitization service.

For a document that must meet a specific confidentiality policy, inspect its content and attachments as well as its document properties. Open the downloaded file with an independent PDF reader, review Properties, and check the page content and annotations. If a recipient could recover a name from visible text or an attached source file, clearing Info and document XMP cannot solve that. Follow your organization's approved document sanitization process when sensitive information is involved.

The audit is based on the generated PDF, not just the controls you clicked. The tool reopens the bytes it plans to download and checks the page count, the known Info fields and keys, and document XMP presence. In edit mode it shows changed familiar fields. In clear mode it also shows all removed Info key names. Its “still present” section lists Info key names and recognizable values, recognizable document XMP values, and any detected page XMP, annotations, attachments, document actions, or file identifier. This makes a remaining older title or producer easier to notice.

Reopening does not guarantee that every PDF reader will interpret the file identically. Some readers cache properties or apply their own precedence between Info and XMP. A newly generated PDF can also be rewritten internally, even when its page count and visible content are preserved. For documents with annotations, signatures, or special structures, compare the downloaded result carefully with the source. The tool blocks changes to PDFs with an interactive form dictionary; a certificate based signature can be invalidated by modification, so treat signed documents with particular care.

The input limit is one PDF, 30 MB, and 200 pages. Work is done in a browser worker so a running job can be cancelled and retried. The operation creates a new PDF download and does not overwrite your chosen file. Password protected files are not unlocked here. A corrupted file is rejected. The inspection table displays standard fields and recognizable XMP values; it is not a full XML editor, a version history viewer, or a complete inventory of every embedded stream.

Dates are particularly easy to misunderstand. A PDF can contain a creation time and a modification time in Info, similar XMP dates, and timestamps elsewhere in page content or annotations. Editing one Info date does not synchronize the XMP date. A date only entry is converted to a PDF date by the processing library, so check the displayed output if a precise time or timezone matters. Removing the Info date also does not erase other timestamps in the file. For a public document, review both columns and the output audit rather than relying on one field.

Creator and Producer often identify different stages. Creator can name the application that authored the source, while Producer can name software that generated the PDF. A conversion can leave either name in Info, XMP, or another structure. If you clear Author but a software name remains, that is expected when you changed only one Info field. Choose the additional XMP removal or supported clear action if its documented scope suits your need. Even then, another software marker might exist in a place this tool does not inspect.

Check Author and enter the new value, leaving Title unchecked. The output audit compares both. If the XMP Author remains different, the audit calls out document XMP and its recognizable value; remove the document XMP packet if that old value must go.

Software names commonly live in Creator or Producer, and may be stored in both Info and XMP. Removing one Info Author field does not change those other fields. Inspect both columns and select the specific Info fields or clear mode that match your goal.

No. Page content, comments, attachments, images, page level XMP, file identifiers, and other objects can reveal information. The clear action only verifies the stated Info and document XMP locations. Use a fuller review and an approved sanitization workflow when anonymity is required.

The tool is designed to keep the page count and content while changing supported metadata, and it checks the output page count. It does not intentionally edit visible text. Review a critical PDF in a reader after downloading because rewriting a complex PDF can affect specialized structures.

Encrypted files are not supported. A PDF containing an interactive form dictionary cannot be modified here. Changing any signed PDF can invalidate its certificate signature; preserve the original and use an appropriate signing workflow if a valid signature must remain.