Edit Metadata

One PDF opens in the editor shell with page one visible and the current common metadata loaded into the side panel. Use this metadata editor online to change PDF metadata online without installing a desktop application. The eight fields are Title, Author, Subject, Keywords, Created with, Producer, Created on, and Modified on. The preview helps confirm that the values belong to the intended document before anything is changed.

The title is a document property and can differ from the filename. Created with maps to the PDF creator field, while Producer records the application or library that wrote the PDF. Keywords remain a comma-separated string in the classic document information store; an existing XMP packet receives a matching keyword value and subject list.

Only fields that differ from the loaded values are sent to the save path. Unchanged fields are omitted rather than deliberately rewritten. The reset control restores the loaded values before saving. Clearing a changed text field writes an empty value, but an empty date control does not erase an existing date individually.

A PDF can carry common properties in two document-level stores. The older Info dictionary uses flat PDF strings. XMP stores XML and can include many additional namespaces and fields. Applications do not always choose the same source, which explains why an old title can appear in one reader after another program changed only the other store.

Edit mode writes the selected common properties to the Info dictionary. When the source already has a readable XMP packet, the tool patches the matching title, author, subject, keywords, creator tool, producer, and date elements there too. Unrelated XMP properties, namespaces, rights data, history, and PDF/A identification are left in the packet. A file without XMP does not receive a newly invented packet.

This alignment covers the fields owned by the tool. It is not a promise that operating-system indexes, cloud previews, or catalog software will refresh immediately. If a viewer still shows an earlier value, close and reopen the downloaded copy and confirm that the application is reading the new file.

Select Save changes after reviewing the edited fields. A source named catalogue.pdf downloads as catalogue-metadata.pdf. The result panel reports Metadata saved, shows the output name and size, and offers another download plus follow-on tools such as Compress PDF, Protect PDF, Sign PDF, and Merge PDF.

Open the result in the reader used by the recipient. Check document properties, page count, visible content, links, forms, annotations, bookmarks, attachments, and accessibility features when they matter. Any save changes file bytes, so an existing digital signature can become invalid. Metadata work should normally happen before final signing.

Add two or more PDFs to open batch mode. The fields begin empty because the files can hold different values. Enter an author, subject, keyword list, application name, producer, or date only when that value should be written to every file. Empty fields are left alone in each source, which prevents an untouched property from being blanked accidentally.

Batch mode suits bulk edit metadata work such as assigning one author to a report set or adding a shared subject to exported records. The same entered values are applied sequentially. The workable batch size depends on document complexity, browser memory, and available device resources.

Completed files appear in individual rows with download buttons. Download all as ZIP creates frisqoo_metadata.zip, while each PDF keeps its base name and gains the -metadata.pdf suffix.

Use removal mode to remove PDF metadata from the two document-level stores this tool manages. Remove all metadata clears every entry in the classic Info dictionary and deletes the catalog’s document-level XMP packet. In single-file mode it disables the form because removal replaces field editing. In batch mode it performs the same document-level removal for every selected PDF.

The option is broader than clearing the eight visible boxes because custom entries in the Info dictionary are removed too. Its scope is still narrower than a forensic sanitizer. Text or names printed on pages remain visible. Information can also exist in annotations, attachments, embedded files, image data, form values, comments, layers, scripts, or other PDF objects outside these two stores.

Use Redact PDF when visible page content must be removed. Review attachments and annotations separately when disclosure requirements cover them. A cleaned metadata panel should never be treated as proof that every possible hidden object has been removed.

Edit mode patches supported elements in an existing XMP packet and leaves unrelated XML in place. That design avoids replacing conformance identification or history merely to change a title. Even so, saving rewrites the PDF, and archival workflows should validate the result with their required PDF/A checker rather than relying on a page claim.

Removal mode deletes the XMP packet, including PDF/A identification stored there, so the result should not be presented as retaining the source conformance claim. Digital signatures are also byte-sensitive. Keep the signed source, edit metadata before signing, and re-sign only after the final output has been reviewed.

To change a PDF metadata title, edit the Title box and save a new copy. To change a PDF metadata creation date, use the Created on control. The created and modified controls use the local time shown by the browser. A selected date becomes a JavaScript date for the Info dictionary. When XMP exists, the corresponding value is written in ISO 8601 form; an existing XMP MetadataDate is updated alongside the chosen modification date.

Text values are saved as entered. Keywords keep their comma-separated wording in the Info dictionary, while the XMP subject list is built by splitting the string at commas and trimming each item. If exact capitalization, commas, or dates are important to a records system, compare the downloaded properties with the intended values before filing the PDF.

If an open password blocks the source, the shared PDF gate can request a password before the metadata tool receives the file. Enter a password you are authorized to use. The local working copy is decrypted so its values and first page can be read.

The saved -metadata.pdf copy is not automatically protected with the source password. Use Protect PDF after reviewing the properties when the output still needs an open password. An unknown password cannot be bypassed by editing metadata.

A current mobile browser can run the tool when it supports the required PDF and download features and has enough memory. The single-file form appears in the compact editor panel, while a batch keeps its shared form on the page. Date input appearance and the final download location follow the browser and operating system.

Large or complex PDFs may be more practical on a desktop. Keep the tab active while files are processed, use a modest batch, and verify the downloaded filenames. The browser may place results in Downloads, Files, or another location chosen in its settings.

• Edit fields when the title, author, subject, keywords, application names, or dates are wrong.
• Use batch mode when several PDFs need the same selected values.
• Use Remove all metadata when the Info dictionary and document XMP packet should be cleared.
• Use Protect PDF after review when the new copy needs an open password.
• Do not use metadata removal to conceal words, images, form values, comments, or attachments.
• Do not expect an existing digital signature to remain valid after saving.