Adobe Photoshop 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 Photoshop’s PDF export is raster-first and rebuilds the document around an embedded image stack. Legitimate for photo books, posters, and rasterized artwork.
Photoshop-as-Producer on a document whose Creator was a text-based institutional source is structurally inconsistent (raster-rebuild of a text document) — that producer/creator mismatch, especially with vectors-flattened-to-image evidence, is a contextual signal.
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 Photoshop in the wild. All are merged into the same canonical profile.
Why variants matter
The same tool publishes itself under 14 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 Photoshop writes when acting as Producer, and the other tools that appear in the same documents.
Most output is PDF 1.4 (73% of files where Adobe Photoshop is the Producer).
Adobe Photoshop sits upstream in 68% of cases — read this row as “what kinds of documents end up routed through Adobe Photoshop.”
Related profiles
Other tools that frequently share metadata with Adobe Photoshop in the same documents. Each card links to its own forensic profile.
Long tail
Smaller cuts of the Adobe Photoshop corpus — useful context, but treat each row as a single data point rather than a strong signal.
Create your account — API key on signup, free test environment on every plan.
From $15/mo. No sales call. Cancel any time.