Adobe LiveCycle Designer appears on both legitimate first-generation output and downstream re-save flows — context (the other tool on the same document) is what flips the signal.
Back to all statisticsForensic verdictBased on this tool’s share of the HTPBE? corpus.
Corpus profile
Adobe LiveCycle Designer is one of the PDF-handling tools surfaced in the HTPBE? corpus. Adobe LiveCycle Designer appears predominantly as the original Creator (92% of its occurrences) — i.e. on documents that started life inside Adobe LiveCycle Designer rather than passing through it as a downstream re-saver.
In the HTPBE? corpus the contextual signal we look for is a producer/creator mismatch: when Adobe LiveCycle Designer appears as the latest Producer on a document whose Creator was an institutional source (e.g. Adobe PDF Library, Microsoft Word, a banking back-end), the document was rebuilt or re-saved after its original creation. That mismatch is the marker — never the tool itself.
On documents where Adobe LiveCycle Designer acts as Creator, 64% carry modification markers; on documents where it acts as Producer, 100% do. These are observed rates inside the HTPBE? corpus and should be read as base-rates, not as accusations against Adobe LiveCycle Designer or its users.
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 LiveCycle Designer in the wild. All are merged into the same canonical profile.
Why variants matter
The same tool publishes itself under 2 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 LiveCycle Designer writes when acting as Producer, and the other tools that appear in the same documents.
Most output is PDF 1.7 (100% of files where Adobe LiveCycle Designer is the Producer).
Related profiles
Other tools that frequently share metadata with Adobe LiveCycle Designer in the same documents. Each card links to its own forensic profile.
Long tail
Smaller cuts of the Adobe LiveCycle Designer corpus — useful context, but treat each row as a single data point rather than a strong signal.
Of files carry at least one digital signature
Of files have attachments inside
Create your account — API key on signup, free test environment on every plan.
From $15/mo. No sales call. Cancel any time.