What does your PDF say about you? Find out before you share it.

Drop PDFs below — get every hidden field listed: author, XMP, embedded files, comments, hidden layers and old revisions, each with what it reveals and how to remove it, plus a verdict per file. Inspected entirely on your device.

  • Your file data never leaves the device
  • Batch up to 20 PDFs + reports
  • Per-item risk verdict + removal fix
  • Password-protected PDFs refused

Add your PDF files

Drag & drop PDF files here

or browse your files · you can also paste from clipboard (Ctrl+V)

Inspected in your browser with pdf.js — every metadata store is read on your device: document properties, XMP, embedded files, annotations, layers and revision history. Nothing is uploaded.

    No files yet. Everything stays on this device. Reports download instantly.

    Privacy you can verify, not just trust

    Most online metadata checkers upload your documents to their servers first — and several charge for the detailed report. This one can't: pdf.js opens your PDF and its metadata stores are read entirely in your browser. Your file data never leaves the device — the only third-party requests are the site's own analytics, which count page views — and it uploads nothing, ever. There is no file fetched after load for the inspection itself. Don't take our word for it:

    New cross-origin requests during use: 0
    1. Press F12 to open developer tools, then the Network tab.
    2. Inspect any PDF above. Watch: apart from the site's analytics, nothing new is requested — no uploads, and no file data ever leaves your device.
    3. Extra credit: disconnect your internet after this page loads — inspection still works.

    How to check a PDF for hidden metadata without uploading it

    A PDF is a container, not just a page. Beyond the visible text and images it stores structured data most people never see: who wrote it, with what software, when it was created and changed, what was edited along the way, files tucked inside it that never appear on any page, comments left by reviewers, and layers that are switched off. That data travels with the file to whoever you send it to — a client, a publisher, a court, the public — and the usual advice is to run ExifTool on the command line or dig through Acrobat's Properties, Attachments and Sanitize dialogs, none of which gives you a verdict, a batch check, or a report you can send to the person who made the file.

    This tool does exactly that, where the file already is: on your own device. When you drop a PDF here, your browser:

    1. Checks the file is really a PDF — by its %PDF magic bytes, not its name — and that pdf.js can open it, so a corrupt or truncated file is refused with a clear message instead of producing a wrong report. A JPEG renamed to .pdf is refused the same way, and a PDF renamed to .txt still inspects.
    2. Reads every metadata store the file carries — the document information dictionary, the XMP stream parsed field by field (including edit history and document IDs), embedded files and attachments, annotation metadata, optional-content layers, incremental-update revision history, and JavaScript or automatic actions — including metadata stored in compressed object streams, which most modern producers use. Embedded images are counted, because photos in a PDF often keep their own EXIF data.
    3. Gives each file a verdict — Clean, Review before sharing, or Exposed — with every finding labelled by what it reveals and how to remove it, so you know what to fix and where. A downloadable text report per file (or one combined report for the batch) carries the same detail to whoever needs it.

    What makes this inspector different

    The pages that top the results for this search mostly check a single file on a server, charge for the detailed report, or need an account — and the one dedicated client-side rival we found shows only creator information and dates for a PDF, with no XMP parse, no embedded files, no annotations, no revision history, no verdict and no downloadable report. This page is the only fully client-side dedicated PDF hidden-metadata inspector we found that combines a batch of 20 PDFs with a per-item risk verdict and removal fix, a full XMP parse with edit history, embedded-file and annotation listings, hidden-layer and revision detection, and a free downloadable report for every file — with no daily limits, no account and no watermark — plus a live network-request counter so you can verify the privacy claim yourself. It runs entirely in your browser — there is no server to upload to.

    When is inspecting the right choice — and when is it the wrong one?

    Inspecting is right whenever a PDF leaves your hands: a manuscript for a publisher, a contract or proposal for a client, a report for a journalist or a court, a CV, a book for KDP or IngramSpark, or anything posted publicly. It is the wrong choice for a file you only ever open yourself, where the metadata never leaves your machine — and for a file whose metadata you actually want to keep, such as an archived document where the author and dates are part of the record. If the destination accepts the source document, fix the metadata there instead of patching the PDF.

    Honest limitations

    Metadata, not full forensics

    This tool reads metadata — it is not a forensic engine. It cannot recover text deleted in an earlier revision, only tell you revisions exist.

    Embedded image EXIF is not read

    Photos inside a PDF often keep their own EXIF data — camera model, GPS, timestamps. This tool counts the images and says so; it does not open the image bytes.

    No guarantee of cleanliness

    A producer can hide data in ways no inspector can enumerate. A Clean verdict means nothing this tool can see was found — not that nothing is there.

    Some metadata is invisible

    Metadata inside encrypted streams, or stored by an application in a private structure this tool does not read, will not be listed.

    No password-protected PDFs

    Password-protected PDFs are refused, and this tool never asks for a password. Remove the password in a desktop PDF tool first, then inspect the unlocked copy.

    Scanned PDFs still carry metadata

    A scanned PDF has no fonts or text, but it still carries document properties, XMP and the scanner's software trail — and its embedded page images may carry EXIF. Check it the same way.

    Frequently asked questions

    Do my PDFs upload anywhere?

    No. Your PDFs are opened and their metadata is read entirely in your browser with pdf.js — your file data never leaves the device, and the only third-party requests are the site's own analytics, which count page views. You can verify it yourself with the network-request counter in the privacy section below the inspector.

    What hidden metadata can a PDF contain?

    More than the pages show. A PDF carries a document information dictionary (title, author, subject, keywords, the application that made it, the software that produced it, creation and modification dates), an XMP metadata stream that duplicates those fields and adds edit history and unique document IDs, embedded files and attachments that never appear on a page, comments and annotation metadata, hidden layers, incremental-update revision history from earlier saves, and sometimes JavaScript or automatic actions. Embedded photos can also carry their own EXIF data.

    How do I check a PDF for hidden metadata before sharing it?

    Drop the PDF on this page and read the verdict: every finding is listed with what it reveals and how to remove it. Clean means nothing identifying or hidden was found; Review before sharing means author, software or date trails were found; Exposed means hidden content travels with the file — embedded files, comment text, old revisions or scripts. In Adobe Acrobat, the same information is spread across File, then Properties, then Description and Additional Metadata, plus the Attachments panel and the Sanitize Document tool.

    What is the difference between document properties and XMP metadata?

    They are two metadata systems in one file. Document properties are the older dictionary (Title, Author, Subject, Keywords, Creator, Producer, dates) that most applications write. XMP is a newer XML stream embedded in the PDF that duplicates those fields and adds more — edit history, document IDs, and application-specific data. Clearing properties in a dialog often clears only the first and leaves the XMP behind, which is why this tool reads both and reports them separately.

    How do I remove hidden metadata from a PDF?

    Re-export the PDF from the source application with metadata turned off, or run a metadata scrubber — for example, ExifTool with exiftool -all:all= file.pdf removes document properties and XMP. That does not remove embedded file attachments or annotation content, so delete those in a PDF editor first. In Acrobat, Tools, then Redact, then Sanitize Document is the most thorough built-in route. After cleaning, drop the new file here and check the verdict flips to Clean.

    Can this tool see text I deleted from an earlier version?

    It can tell you that earlier versions are still inside the file, but it cannot recover the deleted text itself. PDFs saved with incremental updates append each save instead of rewriting the file, so previous versions of the content can linger. If this tool reports revision history, re-save with Save As (which rewrites the whole file) or print to a fresh PDF, then check the new file here.

    Can I inspect several PDFs at once?

    Yes. Drop up to 20 PDFs at a time, up to 25 MB each, and inspect them all in one go. Every file gets its own verdict and findings table, the summary strip totals the batch, and Download all reports collects every file's report into one text file (or a ZIP). There is no daily limit, no account and no watermark — a 200-page cap per PDF applies because very page-heavy PDFs are memory-bound in the browser.

    Can I inspect a password-protected PDF?

    No. Password-protected PDFs are refused with a clear message, and this tool never asks for a password. Remove the password in a desktop PDF tool first, then inspect the unlocked copy here.

    What does this tool NOT check?

    It reads metadata; it is not a full preflight or forensic engine. It cannot recover text deleted in an earlier revision (it can only tell you revisions exist), cannot read EXIF inside embedded images (it counts the images and tells you to check them separately), and cannot guarantee a file is clean — a producer can hide data in ways no inspector can enumerate. It never opens embedded image bytes or font programs. For a full forensic check, use ExifTool or a dedicated validator.