Before You Send a PDF to a Client: A Metadata Checklist
Use this PDF metadata checklist before sending proposals, invoices, reports, contracts, portfolios, and client documents. Review visible content, annotations, attachments, author fields, creator, producer, keywords, and dates.
Guides are written by the team building Metadata Remover's browser-based metadata inspection and cleaning tools.
Quick answer
Before sending a PDF to a client, review the visible pages first, then check hidden document properties such as title, author, subject, keywords, creator, producer, creation date, and modification date. Remove supported PDF metadata from the final exported copy, not the working draft, and send the cleaned PDF instead of the original.
Metadata risk by file type
| File type | Common metadata | Privacy risk | Cleaner |
|---|---|---|---|
| Document properties | Title, author, subject, keywords, creator, producer, creation date, modification date | Can reveal internal project names, personal accounts, source software, client labels, or revision timing. | PDF metadata remover |
| Visible pages | Names, addresses, account numbers, signatures, screenshots, pricing, client references | Can expose sensitive content even after hidden metadata has been cleaned. | Review and redact manually |
| Annotations and comments | Reviewer comments, sticky notes, markup, highlight notes, author names, timestamps | Can reveal internal feedback, reviewer identities, negotiation notes, or draft context. | Review in a PDF editor |
| Forms and attachments | Filled form values, embedded files, file attachments, scripts, linked documents | Can carry data that is separate from the visible page content and easy to miss before sending. | Review in a PDF editor |
| Signed or encrypted PDFs | Digital signatures, permissions, encryption settings, locked content | Rewriting a signed PDF can invalidate signatures; encrypted PDFs may not be readable in a browser cleaner. | Use the original signing workflow |
Start with the final exported PDF
Run your metadata check on the exact PDF you plan to send. A source document, design file, scanned draft, browser printout, and final exported PDF can all carry different metadata. The last export step often writes the creator, producer, and date fields.
If you clean metadata and then reopen the file in another editor, that editor can add new fields. Finish the document first, export the final PDF, review it, clean supported metadata, then send the cleaned copy.
- Export the final PDF before metadata cleanup.
- Avoid editing the cleaned copy again unless you plan to recheck it.
- Keep the working original private for your records.
- Send the cleaned PDF copy to the client.
Review visible page content first
Metadata cleanup does not change the visible pages. A PDF with clean document properties can still show a client name, private price, account number, address, signature, API key, screenshot, tracked comment pasted into the page, or hidden-looking text that still exists in the document.
For client work, review the PDF the way the recipient will see it. Open the file, scan every page, test links when needed, and confirm that the visible content belongs in the client copy.
- Check names, emails, addresses, phone numbers, account numbers, and signatures.
- Review screenshots for browser tabs, file paths, notifications, URLs, and internal tools.
- Confirm pricing, dates, scope, and client names are meant for this recipient.
- Use proper redaction for sensitive visible text instead of covering it with a shape.
Check annotations, comments, and form fields
PDFs can contain more than page text. Comments, annotations, highlights, sticky notes, form values, attachments, and embedded files may stay inside the PDF even when the document looks polished at first glance.
These layers matter in client delivery. A proposal can carry internal review notes. A contract can keep draft annotations. A form can retain values that are not obvious in a quick preview. Metadata Remover focuses on supported document info fields, so review these layers in a PDF editor before cleaning metadata.
- Open the comments or annotations panel and remove internal notes.
- Check filled form fields and flatten or clear them when appropriate.
- Look for embedded files or attachments.
- Review links, bookmarks, and page labels if the PDF came from a complex workflow.
Inspect PDF document properties
After content review, inspect the PDF document properties. Common fields include title, author, subject, keywords, creator, producer, creation date, and modification date. These fields are separate from the filename and page content.
Client PDFs often leak small workflow details through these properties. The author can be a personal account. The title can be an internal draft name. Keywords can include a client label or matter name. Creator and producer fields can reveal the source app, export tool, or automation library. Date fields can show when the file was created or revised.
- Check title for old draft names, internal titles, or copied browser page titles.
- Check author for personal names, contractor names, and source accounts.
- Check subject and keywords for internal taxonomy, client labels, and private project terms.
- Check creator, producer, and dates for software and timeline details.
Clean supported PDF metadata locally
Use the browser-based PDF metadata remover when you want to clear supported document info fields without uploading the PDF for server-side processing. Metadata Remover inspects common PDF properties locally, shows what it found, removes supported fields, and lets you download a cleaned copy.
This is a good final hygiene step for proposals, statements of work, invoices, research summaries, reports, press files, portfolios, contracts, worksheets, and client-ready PDFs made from Word, PowerPoint, design tools, scanner apps, or browser print workflows.
- Open the PDF metadata remover.
- Select the final PDF from your device.
- Review detected title, author, subject, keywords, creator, producer, and date fields.
- Remove supported metadata in the browser.
- Download the cleaned PDF and send that file to the client.
Handle signed, encrypted, or high-risk PDFs carefully
Some PDFs need a different workflow. A signed PDF may lose signature validity when any tool rewrites the file. An encrypted or damaged PDF may not be readable in a browser. A legal, compliance, investigative, or regulated document may require a formal redaction and document-control process.
In those cases, do not treat a metadata cleaner as the whole workflow. Keep originals private, follow the signing or records process your client expects, and use metadata cleanup only when rewriting the PDF is allowed.
- Do not rewrite a signed PDF unless invalidating the signature is acceptable.
- Use the original document system for encrypted or locked PDFs.
- Preserve evidence originals when legal or investigative handling matters.
- Verify the cleaned output before sending sensitive client documents.
Client PDF checklist
Use this checklist before emailing, uploading, or sharing a PDF with a client, vendor, agency, contractor, buyer, recruiter, partner, or external reviewer.
- Export the final PDF after all edits are finished.
- Review every visible page for private text, screenshots, signatures, and account details.
- Check comments, annotations, form fields, attachments, bookmarks, and links.
- Inspect title, author, subject, keywords, creator, producer, creation date, and modification date.
- Remove supported PDF metadata locally from the final copy.
- Open the cleaned PDF and confirm it still looks right.
- Send the cleaned copy and keep the original private.
Frequently asked questions
What PDF metadata should I remove before sending a PDF to a client?
Review and remove supported document properties such as title, author, subject, keywords, creator, producer, creation date, and modification date when those fields reveal internal names, personal accounts, software, or workflow details.
Can a PDF show a different title than the filename?
Yes. The PDF title is a separate document property. Renaming a PDF does not necessarily change the hidden title field stored inside the file.
Does removing PDF metadata remove comments or annotations?
No. Metadata removal targets supported document info fields. Review comments, annotations, form fields, attachments, bookmarks, links, and visible page content separately in a PDF editor.
Should I clean PDF metadata before or after redaction?
Clean metadata after redaction and final export. If you edit the PDF after cleaning, the editor can add new metadata and you should inspect the file again.
Can cleaning a signed PDF break the signature?
It can. Rewriting a signed PDF can invalidate the signature. Use the original signing workflow when signature validity matters.
Are client PDFs uploaded when using Metadata Remover?
No. Supported PDF inspection and cleanup run locally in your browser. The cleaned PDF copy is generated on your device before you send or upload it anywhere else.