How ANNÁVE PDF Conversion Works (Server-Side Go Engine)

If you have only used ANNÁVE PDF in the browser, it is easy to assume everything happens locally. Preview does — the TypeScript layout pipeline runs in your browser for quick feedback. Export does not — that step POSTs to the ANNÁVE PDF Engine, an open-source Go service that runs normalize through render on the server. When conversion finishes, the file is gone from the server. Uploads are not kept for training or reuse.

Preview and export are different jobs

In the UI you get layout feedback while you are still editing. That layer avoids a round trip on every keystroke.

When you hit export, the app sends the file or text to /convert on the engine. The server returns PDF bytes. Same engine as annave pdf convert and the same one you can self-host from GitHub. The line under the tool — Powered by ANNÁVE PDF Engine · Open source · Files not stored — is literal.

Try it yourself

Upload something from the format grid on the tool — DOCX, Markdown, CSV, and the rest. Or clone the engine repo and run annave pdf convert locally. API details, configuration, and error codes are on docs.annave.tech/pdf-engine.

For where that engine shows up across my products — CV, PasspoPet, and the converter — see ANNÁVE PDF Engine: built for my own products first.

Site privacy for forms and cookies: annave.tech/privacy. Conversion itself is process-and-discard, not store-and-mine.