Adobe InDesign reads as a downstream re-saver — it surfaces disproportionately on documents whose original Creator was a different, often institutional, application.
Back to all statisticsForensic verdictBased on this tool’s share of the HTPBE? corpus.
Corpus profile
Adobe InDesign is a layout / publishing application. Its PDF export rebuilds the document through Adobe PDF Library.
InDesign-as-Creator paired with Adobe PDF Library Producer is the legitimate Adobe-stack baseline. Contextual signal: when InDesign appears as Creator on a document whose existing structure (institutional template, server-rendered layout) suggests it did not originate in a layout app.
Role in the workflow
Every PDF carries a Creator (the application that produced the original document) and a Producer (the engine that wrote the PDF). The same tool can appear in either slot, with very different modification profiles.
Name fingerprints
Different version strings and spellings observed for Adobe InDesign in the wild. All are merged into the same canonical profile.
Why variants matter
The same tool publishes itself under 8 different metadata strings — version bumps, locale tags, build IDs. We canonicalize them so the corpus reflects one identity, not noise.
Distributions
The PDF versions Adobe InDesign writes when acting as Producer, and the other tools that appear in the same documents.
Related profiles
Other tools that frequently share metadata with Adobe InDesign in the same documents. Each card links to its own forensic profile.
Long tail
Smaller cuts of the Adobe InDesign corpus — useful context, but treat each row as a single data point rather than a strong signal.
Of files contain JavaScript code
Create your account — check PDFs on the web or with an API key, both ready on signup.
From $15/mo. No sales call. Cancel any time.