IT Consulting
Illustration of a magnifying glass scanning a PDF document's metadata for AI-tool fingerprints

PDF AI Provenance Scanner

Checks a PDF's Info dictionary and XMP metadata for known AI writing-tool and AI-PDF-generator fingerprints (ChatGPT, Claude, Notion AI, ChatPDF, and others). Uploaded files are kept in an internal log for abuse monitoring, not shown or used for anything else. A signal found is a hint, not proof; no signal found doesn't confirm the document is human-written either — details below.

Drag & drop a PDF here, or

ℹ️ What does this check, and what are the limits?

AI-Tool Metadata Fingerprints

Many AI writing assistants and AI-specific PDF generators leave their name in a PDF's own metadata — either because the exporting tool stamps it there by default, or because the document was exported directly from that service.

  • Info dictionary: the classic Producer, Creator, Author, Subject, Title, and Keywords fields every PDF can carry.
  • XMP metadata: the newer, XML-based metadata stream — Dublin Core fields (dc:creator, dc:description, dc:subject), the PDF namespace's Producer/Keywords, the XMP namespace's CreatorTool, and any custom properties a tool chose to add.
  • Not exhaustive, and not proof: new AI tools appear constantly, and any of this metadata can be edited, stripped, or forged in seconds with any PDF editor — a match is a real signal, but a miss proves nothing either way.

What this doesn't do

  • No C2PA check: unlike images (see the AI Image Scanner), there's no real-world C2PA Content Credentials support for PDFs to check — no cryptographically-verifiable signal exists for this file type today, only self-declared metadata.
  • No writing-style analysis: this doesn't read or judge the document's actual text for "AI-sounding" prose. That's a fundamentally different, far less reliable kind of tool; this one only looks at metadata fields.
What this can and can't tell you: every field this checks is metadata that the authoring tool chose to write, and anyone can strip or forge with any PDF editor in seconds. So: a signal found is a real hint worth a closer look, not proof; no signal found is not proof the document is human-written, only that no known fingerprint survived in this copy.
💡 Show API usage examples (cURL)

Scan a PDF and get JSON findings

curl -sS -X POST https://devops.majbase.com/pdf-ai-scanner/api \
    -F "file=@document.pdf"