JSON в PDF

No. It only rebuilds PDFs from JSON files created by BentoPDF's PDF to JSON tool, which stores the document's full internal structure. A JSON export from an API, a database, or a config file will fail with an error.

Paste or upload the JSON as plain text in Text to PDF, which lays it out as formatted text on pages. JSON to PDF is only for round-tripping documents that started out as PDFs.

The JSON produced by PDF to JSON captures the document's objects, so converting it back reproduces the pages, text, and images of the source. Converting back and comparing is also a quick way to confirm that an export captured everything.

Every conversion downloads as jsons-to-pdf.zip, even for a single file. Inside, each PDF carries the name of its source JSON, so report.json becomes report.pdf.

Yes, as long as the structure stays valid for the CPDF engine. Programmatic changes to the JSON, such as edited metadata or text objects, are rebuilt into the PDF; a malformed edit produces a conversion error.

The conversion depends on the CPDF WebAssembly build. On bentopdf.com it's included, but a self-hosted copy needs the CPDF WASM files configured in WASM settings before this tool will run.

No. The files are read in your browser and rebuilt into PDFs by a Web Worker running the CPDF engine locally, so nothing is transmitted and the page stays responsive during large conversions.