Roadmap
The direction of travel.
Where NextPDF is heading — what's in progress, what we're exploring, and what's planned. This is direction, not a dated promise.
Actively being built on the in-development line.
Long-term signing, end to end
B-LT / B-LTA (DSS + document timestamps) driven through the same high-level seam as B-B and B-T.
Vertical writing modes to Stable
vertical-lr promoted to a default, with OpenType vert / vrt2 GSUB binding.
Public-API freeze for the next major
The Inspector, RFC 5280 PKI path-validation, and RAG vector-index contracts frozen as a stable API.
Canonical conic gradients
Conic gradients rendered as a Type-4 Gouraud mesh via the /sh operator.
Research and prototypes — promising, not yet committed.
Post-quantum signing
Maturing the ML-DSA (FIPS 204) and SLH-DSA (FIPS 205) signer providers from interface to production.
C2PA content credentials
Provenance manifests for documents, building on the experimental C2PA work.
Accessibility autofix
Deeper heuristics for the tagged-PDF auto-fixer, beyond the current fixers.
Broader runtime coverage
More framework and edge-runtime targets for the engine and Connect.
On the list, sequencing to be decided.
Self-serve licence issuance
Instant, automated licence-key issuance and entitlement provisioning after a Merchant-of-Record checkout — today a licence is set up by request.
Expanded e-invoicing validation
Wider validator coverage across the EN 16931 / Factur-X / ZUGFeRD profiles.
More migration adapters
Compatibility surfaces beyond the current set, prioritised by what teams are migrating from.
This roadmap shows direction, not commitments or dates. Priorities move with what teams actually need, and nothing here is a promise to ship a particular feature on a particular timeline. The moment something ships, it leaves this page and appears on thechangelog. Want to influence what we build next?Tell us what you need.