8. Where to go from here

Before this: You have worked through the previous seven steps.

You can build, lay out, localise, deliver and scale a document. Everything below is a specialisation of what you already know — the content object never changes shape.

Pick the surface that fits your work

• The library — what you have been using. Full control, any runtime.
• pdfnative-cli — 17 commands for shell scripts, CI and Makefiles. Render, sign, encrypt, extract text, fill forms, merge and split, all from JSON on stdin.
• pdfnative-mcp — 24 tools that let an AI assistant (Claude, Cursor, Zed, any stdio MCP client) produce and inspect PDFs on your behalf, with no code.
• pdfnative-react — the same engine driven by JSX components, if your app is already React.

Common next requirements

• PDF/A — archival conformance, validated against veraPDF in CI.
• Accessibility — tagged PDF, structure tree, PDF/UA checks.
• Digital signatures — CMS/PKCS#7, RSA and ECDSA.
• Charts — native vector, no rasterisation.
• Form filling and text extraction — working with PDFs you did not create.
• Merge, split and decrypt — restructuring existing documents.

Try things without installing anything

Nine playgrounds run in your browser: 22 writing systems in one document, native charts, the full toolkit, a CLI command builder, an MCP tool explorer, the React renderer, and 100,000 pages.

All 26 reference guides are one click away. If something in them does not hold up, say so — a claim we cannot defend is a bug.

Tip: Alt + ← / → moves between steps.