PDF Metadata Editor

Two places a PDF stores its properties

A PDF can describe itself twice. The document information dictionary, usually called the Info dictionary, holds short text entries such as /Title, /Author and /Producer. The XMP packet is an XML stream attached to the document catalog that repeats most of those values under names such as dc:title and pdf:Producer, and can also carry custom schemas, rights statements and document IDs. Viewers do not agree on which copy to display, so a file whose two copies disagree can show one title in one program and a different title in another.

This editor does not patch the existing file. It builds a new one: FPDI imports every page as-is, and TCPDF writes a fresh Info dictionary and a fresh XMP packet from the values you submit. In the output both copies match. Anything else the old XMP held, including custom entries, is not carried over.

Fields in the rebuilt file and where each value comes from

Before and after on a sample file

The sample below was edited the way the form sends it: Title and Author changed, Subject emptied, Keywords and Creator left at their pre-filled values. Everything in the right-hand column was read back from the downloaded file.

Measured properties of the sample before and after one save

Clearing a value versus changing it

An empty field is not sent at all, and TCPDF writes no entry for it. Most viewers show a missing entry as blank, and the metadata checker reports it as absent. There is no way to keep an original value while clearing the form field: the new file contains only what you submit.

The Producer and both dates cannot be set here. If you need every text property emptied, the metadata remover is the closer fit, although Ghostscript then records its own name as the producer.

Error messages when saving

• Files with compressed object streams, a PDF 1.5 feature used by default Ghostscript 10 output and by pdf-lib, which writes the downloads of the PDFCheck editor, highlighter and form filler, used to fail with "This PDF document probably uses a compression technique which is not supported by the free parser shipped with FPDI." The editor now rewrites such a file with a classic cross-reference table first, using qpdf or Ghostscript, and then edits it.
• "This PDF is password-protected." or "This PDF has permission restrictions set by its owner." The message appears as soon as you choose the file, and nothing is pre-filled, because an encrypted file's values cannot be read without the password and a rebuilt copy would drop the protection. Remove the protection with the password tool, using the file's password, then edit.
• "Daily limit reached." Each successful save uses one check, 100 a day on the free plan. Reading the current values when you choose a file does not use a check.
• A size error means the file is over 50 MB on the free plan or 100 MB on Pro and AI.

What the rebuild keeps unchanged

The uploaded copy is deleted as soon as the save finishes. The edited file can be downloaded only from the browser session that created it and is removed by the hourly cleanup once it is more than 24 hours old. A troubleshooting log keeps the file name, its size and the property values before and after the edit.

• Page appearance, including mixed page sizes and orientations.
• All text drawn on the pages, including text hidden under a white box. Changing properties is not redaction.
• Embedded image data. A JPEG in the sample still carried its EXIF author tag after the save.
• Nothing outside page content: bookmarks, links, comments, attachments, form fields, page labels and the tag tree used by screen readers are not copied.
• Nothing is added to the pages. TCPDF's default hidden "Powered by TCPDF" text and link on the last page is switched off.