Resume Metadata Viewer
Upload your resume and see the document properties embedded inside it — author, company, who last modified it, when it was created — separate from anything actually visible on the page.
-
Hidden Properties
Author, company, last-modified — not visible on the page.
-
Privacy Check
Catch a previous employer's name left behind.
-
No Storage
File is read once, then discarded.
Why this matters
PDF and Word files carry hidden document properties — author, company, who last edited it — separate from anything visible on the page. If a resume started life as a copy of an old template or a previous draft, these fields sometimes still point to someone else. A plain TXT file, or a PDF freshly exported from a clean source, avoids this entirely.
Why this matters
A resume duplicated from a template built for someone else, or repeatedly saved from a copy of an old draft, can carry that other name, a former employer's company field, or a "last modified by" value that isn't you — all sitting in the file's properties, invisible unless someone specifically checks. It's a minor thing most of the time, but on a document you're sending to a stranger evaluating you, it's worth a quick look before you hit send.
What to do about it
If a field here shows something that shouldn't be there — a previous company's name, someone else's name as author — the fix isn't to edit the metadata directly, since most tools don't offer a clean way to. It's to re-export the file from a source that doesn't carry the old properties. Downloading a fresh PDF from this app's own editor, for instance, won't inherit whatever was embedded in an old Word template.
FAQ
What counts as "sensitive" in the results?
Fields that are reliably a person's or company's identity rather than just software info — things like Author, Company, Manager, and "last modified by." Fields like the software used to create the file or a page count aren't flagged as sensitive, since they're not personally identifying.
Can I edit or remove the metadata directly here?
No — this tool only reads and displays what's embedded in the file; it doesn't modify or strip it. If you want it gone, re-export the resume from a clean source, like this app's own editor, rather than the file that's currently carrying it.
Why does my resume have a company name in it that isn't mine?
This usually happens when a resume was built by editing a copy of a template file, or an old draft from a previous job search saved under a work computer's account — document properties get carried over silently across edits unless something explicitly resets them.
Does a plain text (.txt) resume have this kind of metadata?
No — plain text files don't carry document properties the way a PDF or DOCX does. Uploading a .txt file here shows basic stats like line and word count instead.
Should I be worried about metadata for every resume I send out?
Not worried, just aware — most of the time it's harmless, your own name or nothing unusual at all. It's worth a quick check mainly when you're not sure how a file was originally created, like one inherited from a template or an old shared draft.