Dominant format for e-signing
File formats for e-signing in 60 seconds
PDF is the de facto standard for e-signed documents for one reason: it renders identically everywhere and locks content in place. DOCX remains editable after signing, which weakens evidence. This guide explains the technical trade-offs across formats and what they mean for long-term preservation, tamper evidence, and interoperability.
Why format choice is an evidence decision
A signed document is evidence. The format determines whether that evidence survives: whether content can be silently altered, whether signatures stay attached to the right page, and whether the file opens correctly in ten years. Choosing a format is choosing your evidence posture.
Common signing formats
PDF/A archival standard
Typical retention horizon (years)
Formats compared at a glance
The table below ranks the common formats across the dimensions that matter for signed documents.
Identical rendering, content locking, universal support, and a dedicated archival standard (PDF/A, ISO 19005). The default choice for e-signing.
Editable after signing unless explicitly protected. Font and pagination can shift across devices. Acceptable for drafts; weak for final signed records.
Fine for scanned paper, but not editable and poor for text-heavy contracts. Signature placement is visual only, with no structured content.
Useful for consent flows and terms acceptance captured in a browser. Needs careful capture and timestamping to be evidentiary.
Interoperable but rarely used for formal signing. Lacks the ecosystem and archival tooling of PDF.
What PDF/A adds for long-term records
PDF/A is a subset of PDF designed for archival. It embeds fonts, disallows external dependencies, and is self-contained by design.
Self-contained by design
Fonts, color profiles, and metadata are embedded. The file does not depend on external resources that may vanish, so it renders identically decades later.
Conformance levels
PDF/A-1, -2, and -3 differ in features allowed. For signed records, PDF/A-2 or later is common because it supports attachments and transparency.
Signature and archival can coexist
A signed PDF can be saved as PDF/A while preserving the signature. This is the recommended combination for records you must keep for years.
The DOCX signing trap
DOCX is where most signing mistakes happen. Understand the trap before you send a Word file for signature.
Editable after signing
A DOCX remains a zip of XML parts. Without explicit protection, content can be changed after signing without obvious marks, weakening the evidence chain.
Rendering drift
Font fallback and pagination differ across Word versions and devices. A field that aligns in your Word may shift in the recipient's.
When DOCX is acceptable
For internal approvals or drafts, fine. For a final signed record, export to PDF first, then sign. This is the same workflow professionals use everywhere.
Formats for special scenarios
Some scenarios call for formats beyond the usual PDF workflow.
Consent and terms capture
HTML-based consent flows (checkboxes, click-through) capture intent in the browser. Archive a timestamped snapshot or PDF export as the record.
High-volume automated signing
APIs that generate signed outputs often produce PDF plus a structured manifest (JSON/XML) of events. Keep both; the manifest feeds evidence packages.
Regulated industry records
21 CFR Part 11 (life sciences) and similar frameworks expect records that are accurate, protected, and reproducible. PDF/A with embedded signatures fits this bar.
Common questions about file formats for e-signing
No, but it is the safest default. Most platforms accept multiple formats and convert to PDF for signing. The final signed output is typically PDF.
The eSign.AI approach to formats
eSign.AI accepts PDF, DOCX, and image uploads, converts them to a consistent PDF signing experience, and outputs signed PDFs with an independent audit certificate. For teams managing records across formats and languages, the platform keeps the signed record in a format designed to last.
Legal review checklist
Before publishing, verify the following points with legal review.
Standards accuracy
PDF/A (ISO 19005) and related standard references must be accurate at publication time.
Regulatory framing
21 CFR Part 11 expectations should be described as general practice, not as compliance advice for any specific organization.
Format claims
Claims about DOCX editability and PDF rendering should be verifiable with a simple test and dated.







