Why this matters
The Creator field can read like 'TeXLaTeX 3.14159265-2.6 (University of X template 2024)' — a direct fingerprint of your institution.
Even generic creators like 'Microsoft Word for Office 365' can be cross-referenced with the Producer field to identify the specific Office license holder.
Reviewers with PDF forensics experience (and there are more than you'd think) can read the Creator field in seconds.
What the scanner detects
- Creator field (your PDF generation software + version)
- Producer field (the underlying PDF library)
- Custom XMP metadata often added by institutional templates
- Document identifiers some academic publishers embed
- Trapped and GTS_PDFXVersion fields used in publishing workflows
Ready to scan your PDF?
Drop your file into the scanner. Results in 5 seconds. Nothing leaves your browser.
Open the scannerHow it works
Click "Scan your PDF now" above. The scanner opens in your browser tab — no download, no install.
Drop in your PDF. The file is parsed entirely in your browser using JavaScript. No upload, no server, no logs.
Review your 0–100 risk score, the list of findings, and the AI-generated redaction recommendations. Then take action.
Frequently asked questions
How do I remove the Creator field from my PDF?
Drop your PDF into the scanner above. It reads the info dictionary locally, sets the Creator field to empty, and also strips the Producer, Author, and other identifying fields. The cleaned PDF downloads immediately.
What does the PDF Creator field reveal?
It shows the software that generated the PDF — e.g., 'LaTeX with hyperref package', 'Microsoft Word for Office 365', 'Pages'. Combined with the Producer field and any custom XMP metadata, this can fingerprint your institution's template, your specific software version, or your workflow.
Will removing the Creator field affect my PDF's content?
No. The Creator field is descriptive metadata only. Removing it doesn't affect page layout, fonts, images, hyperlinks, or any visible content. Your PDF opens and renders identically.
Is browser-based stripping safe for unpublished research?
Yes — and it's the only safe option. Server-based metadata removers upload your full paper (including any unpublished content) to their server before stripping. Browser-based tools like PrivacyScanPDF process locally in your tab — no upload, no disclosure of unpublished research.
Related privacy scans
Remove Author Name From an Academic PDF (Double-Blind Review)
Double-blind peer review requires that your PDF contain no identifying information — not just in the visible text, but in the file's metadata. The Author field, Creator software, file path, and timestamps can all de-anonymize you. This tool strips every identifying field locally in your browser, so your submission is truly anonymous.
Strip Metadata From Legal Contract PDFs
Legal PDFs routinely leak identifying metadata: the drafting attorney's name (Author field), the firm's Word version (Creator field), editing timestamps that can contradict a contract's stated execution date, and tracked-change history in some cases. Strip all of it locally before emailing — no upload to a third-party server means no breach of attorney-client privilege.
Remove Editing History From a Corporate PDF Before Emailing
When you export a corporate document to PDF, the file silently carries your editing history: the author's name (often their email from the corporate Office account), the editing software and version, creation and modification timestamps, and sometimes the original file path including the corporate network share name. Strip all of it before the PDF leaves your network.
Clean Personal Data From a PDF Resume (Anonymous Job Application)
Anonymous job applications require removing more than just visible name and contact info. Your PDF resume's metadata can reveal your real name (Author field), your email (often auto-populated), your editing software, and your timezone. This tool strips all of it — locally in your browser, no upload — so your resume is truly anonymous.
Your PDF never leaves your device
Every operation runs as JavaScript in your browser tab. No upload endpoint exists. Verify it yourself in DevTools (F12 → Network).