How to review file metadata and content before sharing
Removing file properties is only one part of a review. Learn what the tools recognize, what may remain in the content, and how to check a copy before sharing.
Metadata is not the same as content
Metadata means properties attached to a file, such as its author, title, creation software, and dates. These details can reveal how a document was made, but they are only one part of the file. Comments, revisions, text, hidden sheets, attachments, and images can hold other information. A link can also carry parameters in its URL without changing the page content.
So “clean metadata” has a specific scope: it removes recognized fields. It does not make a document anonymous or replace a review of the content itself.
What to review in each file type
A PDF can store title, author, subject, keywords, creator application, producer, and dates in its document information fields. The PDF tool here removes recognized fields from that information dictionary and the root XMP packet when present. It does not remove visible text, forms, comments, attachments, or data embedded in images. Rewriting may also invalidate a digital signature, so do not use the output as a signed document.
Word, Excel, and PowerPoint
DOCX, XLSX, and PPTX files can include the author, last editor, company, application, dates, and custom properties. The Office tool cleans fields it recognizes in common package properties. It does not remove comments, tracked changes, sheet or slide content, embedded objects, macros, or every application-specific data location. Signed, protected, and macro-enabled files are not accepted.
Before sharing a spreadsheet, also review hidden sheets, formulas, and cell contents. For a presentation, check notes, comments, and objects outside the visible slide area. If those details need to be removed, use the inspection features in the original application and review the copy again.
Open the Office metadata tool →
Links
A URL may include campaign parameters such as utm_source or known identifiers such as fbclid and gclid. The link cleaner removes only names it recognizes and preserves unknown parameters that may be needed for search, language, filters, or to open the intended page. It does not remove cookies, account-based tracking, or other forms of measurement.
A review workflow that avoids surprises
- Keep the original. Work on a copy and retain the source until you have checked the result.
- Choose the tool for the file type. Check each page’s supported formats and limits before selecting a file.
- Review and clean recognized fields. Results show field types without exposing their values.
- Open the copy in the appropriate application. Check that it opens and the expected content is intact.
- Review what the cleaner does not cover. Look for comments, revisions, hidden sheets, attachments, signatures, and visible details that could identify someone.
- Test important links. Unknown parameters are preserved, but only the destination can confirm that a URL still works.
- Share the reviewed copy. Do not replace or publish the original until you have completed a final check.
Example: a report ready to send
Imagine a PDF whose document properties list the author, while a comment contains an email address. Cleaning may remove the recognized author field, but the comment remains. If the file is digitally signed, the rewritten copy may no longer validate the signature. Handle these separately: clean compatible fields, review comments and content in a PDF reader, and retain the signed original when formal validity matters.
Privacy and limits
Selected files are processed in your browser; they are not sent to our server for cleaning. Required libraries may load from a CDN, and the site may use analytics and advertising depending on your privacy choices. See our privacy policy for details. No cleaner guarantees anonymity, removes every possible data location, or determines how another platform will treat a file.