PDF Metadata Editor & Remover

A PDF metadata editor reads document properties stored inside a PDF and lets you change fields such as title, author, subject, keywords, creator, producer, language and dates.

It can edit or clear the standard title, author, subject, keywords, creator, producer, language, creation date and modification date fields supported by the document.

Privacy Clean removes the supported standard properties, dates, language, custom Info entries and the document-level XMP metadata packet. Some PDFs can contain other private information outside those locations, so the result is not a forensic anonymity guarantee.

The title is a document property that some PDF readers display in their title bar, properties panel, search results or document library. It is separate from visible text on the first page.

Author metadata identifies the person or organization associated with creating the document. Clearing it does not remove visible author names printed on PDF pages.

Creator usually describes the original application or workflow that made the source document, while producer often identifies the software that generated the PDF representation.

Keywords are descriptive search terms stored as a document property. This tool accepts comma, semicolon or line-separated keywords and writes a normalized keyword list.

Yes. Enter a language tag such as en, en-US, fr or ar. Clearing the field removes the document-level language entry when possible.

Yes. Use the date and time controls to set either date, use the current time for modification, or clear a date to remove that property.

XMP is a separate metadata packet that can duplicate or extend document properties. The removal option deletes the document-level XMP metadata reference when present.

Custom properties are nonstandard entries stored in the PDF document information dictionary. The tool lists readable custom keys and can remove those entries together.

No. Metadata removal does not erase text, images, headers, annotations or names visibly printed on PDF pages.

No. Comments, sticky notes, highlights and other annotations are page content structures rather than the document properties handled by this tool.

No. Embedded attachments are not removed. Use a dedicated attachment-removal workflow when a PDF contains attached files.

Not necessarily. Metadata embedded inside individual images is different from PDF document metadata and is not inspected or rewritten by this page.

No. Layers, form fields, actions, scripts and other interactive structures are outside the metadata scope of this tool.

Yes, modifying and resaving a signed PDF can invalidate or alter signature validation because the document bytes change. Do not edit signed PDFs unless that consequence is acceptable.

No. Encrypted or password-protected PDFs are rejected. Unlock the document with authorization before editing its metadata.

The tool modifies the existing document rather than rebuilding pages. It is designed to preserve page content and document structures, although any PDF rewrite should be reviewed before important distribution.

Saving rewrites the PDF object structure. Compression and object-stream choices can make the result smaller or larger even when page appearance is unchanged.

Compatibility save avoids compressed object streams. The file can be larger, but some older PDF tools may read that structure more reliably.

Yes. Clear only that field and leave the other prefilled values unchanged. The generated PDF will preserve or rewrite the remaining supported properties.

Yes. Restore Original repopulates the detected metadata and resets removal options before you create the output.

It clears supported standard text properties, language and dates, disables title-bar display, and selects removal of custom Info entries and the document-level XMP packet.

No. Trailer file identifiers are preserved because they can be used by PDF workflows and are not the same as user-facing title or author metadata.

Yes. After generating the result, download a JSON report or plain-text report containing the before-and-after properties and selected actions. The report does not contain page text or images.

No page-specific upload endpoint receives the PDF. The source bytes, edits, verification and generated file remain in the current browser session.

No. The browser downloads pinned processing code, but the page does not send your PDF bytes or metadata values to that delivery service.

No page-specific permanent storage is used. Source and output files remain in browser memory until reset, replacement, navigation or page closure.

Yes. The interface is responsive and touch-friendly. Large or structurally complex PDFs may exceed the available memory on lower-end phones.

Current Chrome, Edge, Firefox and Safari versions are expected to support the required file, PDF and download features. Content blockers may prevent the processing component from loading.

The page applies a 100 MB input limit to reduce browser crashes. Available memory and document complexity can create a lower practical limit, especially on mobile devices.

Some browsers or privacy settings do not display PDFs inside an embedded preview. Metadata editing and downloading can still work even when inline preview is unavailable.

A reader may display XMP metadata, cached values or a filename instead of the standard document information field. Review the XMP detection status and the verified output summary.

No. It removes supported document-level properties but does not inspect visible content, image metadata, attachments, comments, hidden layers, signatures or every possible proprietary structure. Review sensitive files with an appropriate privacy workflow.

No page-specific account, browser extension or desktop installation is required. A current browser with JavaScript enabled is sufficient.

Use Reset to release the current PDF, output preview, metadata report and temporary browser URLs, then choose another document.