Remove PDF Metadata

Inspect and remove PDF metadata without uploading the file

A PDF can carry information that is not obvious on the page: an author name, document title, editing application, creation date, modification date, custom business properties, an XMP packet or an internal document identifier. Those details can be useful inside a workflow and undesirable when the document is shared outside it.

DraftFort scans those metadata locations locally and shows the values it can find before changing anything. You decide whether to create a cleaned copy. The source PDF, detected properties and result stay in temporary browser memory; they are not sent to DraftFort for processing.

This tool has a precise boundary: it removes common document metadata. It does not promise anonymous, forensic or redacted output.

How to remove metadata from a PDF

1. Add one PDF. Choose a file up to 100 MB. The browser opens it locally.
2. Review the scan. Check the named document properties and structural signals such as XMP, document IDs and application-private data.
3. Choose whether to clear annotation identity. This optional setting removes author and date fields from ordinary comments and annotations. It leaves comment text and form fields intact.
4. Create the cleaned copy. DraftFort removes the selected metadata and saves a separate file ending in -metadata-removed.pdf.
5. Check the verification result. The downloaded bytes are scanned again before the tool reports success.
6. Inspect the complete document. Open the result, search for sensitive text, review attachments and form values, and keep the original until the recipient’s workflow has been tested.

The verification covers the categories this tool is designed to remove. It is not a certificate that the document contains no identifying information.

What the metadata remover clears

PDF producers can store similar information in several places. DraftFort checks and removes these categories:

Some PDF viewers create default properties when they save a document again. That later viewer behaviour is outside DraftFort’s cleaned download, so inspect the copy you actually plan to distribute.

What it deliberately does not remove

Metadata removal is not complete anonymization. Visible content is not removed. The following can still contain personal or confidential information:

• text and images displayed on a page;
• OCR text hidden behind a scanned page;
• comments, sticky-note text and drawing content;
• form field names and entered form values;
• bookmarks, links, layers, JavaScript and accessibility structures;
• embedded files and every name, description, date or byte inside them;
• image-level metadata embedded inside page images;
• fonts, application-specific objects or other forensic traces; and
• the downloaded filename and filesystem timestamps outside the PDF itself.

Do not use a metadata cleaner as a substitute for redaction. Proper redaction must remove the underlying sensitive text or image data, not merely cover it or delete document properties.

Why annotation identity is optional

Comments often contain both useful review content and identity fields. Removing all annotations would erase the review itself. DraftFort therefore preserves annotations by default and offers a separate option that clears common author, subject and date fields from non-form annotations.

That option does not remove the comment text. It also skips widget annotations so interactive form names and values are not silently destroyed. If comment content is sensitive, remove or rewrite it in a suitable PDF editor before sharing the file.

PDF metadata, visible content and redaction are different

These three tasks solve different risks:

Cropping is not redaction because content outside the CropBox can remain in the file. A white rectangle placed over text is not redaction either because the underlying object may remain selectable or recoverable.

Digital signatures and archival PDFs need special care

A cryptographic PDF signature validates particular bytes in a particular revision. Metadata removal rewrites the document, so the signature can become invalid even when a visible signature image is still present. Keep the signed source unchanged whenever signature verification matters.

PDF/A archival profiles also require particular metadata relationships. Removing XMP or application data may break conformance. If the document is part of an archive, regulated process or records schedule, use the organisation’s approved workflow and validate the result with a dedicated PDF/A checker.

Password-protected, damaged and unusual PDFs

This tool does not guess or bypass passwords. If you know a password you are authorised to use, first create an unlocked copy with Unlock PDF, then scan that copy.

PDF is a flexible format and some files contain damaged references, unusual encryption, rights-management systems or producer-specific structures. DraftFort reports an error rather than claiming success when it cannot safely load or verify the output.

Private by design

Metadata can be more sensitive than the visible page, so it does not need to leave your device merely to be inspected or removed. DraftFort performs the scan, rewrite and verification inside the browser and downloads the result directly. There is no account, watermark, processing queue or document upload.

The practical limit is your device’s memory. A complex 100 MB PDF can require several temporary copies while it is parsed and saved. Close memory-heavy tabs or use a computer if a phone cannot complete the operation.