Comment vérifier les métadonnées d’un document
Look at document properties before you look at presentation
A document might look polished on screen while still exposing internal details. Before sending a file outside your team, check the title, author, subject, and creation dates.
These fields often reveal the real story: which software generated the file, whether naming matches the final version, and if older internal details are still attached.
For PDFs, PDF Parser is the quickest starting point. For other office-style files, Document Metadata Viewer gives a broader review before you decide to clean or re-export.
Why PDFs are usually the easiest document format to inspect online
PDFs are a great fit for online inspection because properties like page count and document info are practical to read without heavy processing. This makes them perfect for a quick review before delivery or approval.
Support for other document formats is often lighter. In those cases, basic clues like the file extension and MIME type can still help you confirm what you're dealing with.
The fields that matter in real work
If you're reviewing a proposal or contract, the most valuable checks are the simplest. Does the author field show an internal username? Does the producer field expose a tool chain you didn't expect? Does the page count match what you think is in the document?
These aren't theoretical concerns—they're the exact issues clients or partners notice after a file hits their inbox.
Use the check to decide the next step
Sometimes the answer is easy: the document looks fine, so you send it. Other times, the metadata tells you to create a fresh export or compare versions before sharing. The important part is making that decision while the file is still under your control.
Even a lightweight viewer can catch problems that are invisible in the document content itself.