ODT is OpenDocument text, the native format of LibreOffice Writer. JSON is a data tree of objects, lists, numbers and strings. pandoc sits between the two, and this page says exactly what happens to an ODT file on the way to becoming a JSON one.
What runs when an ODT file becomes JSON
pandoc in two passes, on a machine we rent and watch. Your ODT file is uploaded once, pandoc runs once, the JSON comes back, and neither file is kept. ODT to JSON is one of the 3649 pairs that engine was probed on with a real file, which is why it has a page here and why the pairs the probe could not prove do not.
What survives from the ODT into the JSON
Lists from the ODT file, nesting included, plus code blocks, block quotes and links, all re-expressed in JSON.
Images: pandoc extracts them out of the ODT file into a working directory and re-embeds them in the JSON, so nothing ends up pointing at a file that no longer exists.
What ODT to JSON costs you
Page layout. ODT carries some and JSON carries none, so margins, page breaks, headers and footers have nowhere to land and are simply not written.
Tables. The JSON writer cannot carry one, and the probe caught this the hard way: a CSV file, which is nothing but a table, came back as a well formed and completely empty JSON with a zero return code. The engine now refuses that case outright rather than handing you the emptiness.
Where ODT and JSON files come from
ODT. LibreOffice Writer writes it natively. Like ODS it is ISO/IEC 26300, and it turns up wherever a public body or a policy asked for an open format rather than a vendor one.
If a model is going to read the JSON
Structure is what survives from the ODT file, and structure is what a model needs. ODT in, JSON out, with the heading tree intact instead of flattened into one long paragraph.
ODT to JSON, measured rather than promised
Running ODT to JSON against the real engine with a real file, pandoc wrote 1,761 bytes of JSON in 0.1 seconds, machine otherwise idle. That is one ODT file on one day and not an average, which is why the number is given together with the file that produced it.
The ODT to JSON verdict was reached by a pandoc round trip, meaning the output was read back by pandoc and had to still contain a witness word planted in the source, which proves the content travelled and not merely the container. Which check was used matters, because they do not all prove the same thing, and a status code of 200 proves nothing whatsoever about whether the JSON file has anything inside it.
The same ODT file, sent somewhere else
Other outputs the probe measured out of an ODT file, so the cost of choosing JSON can be read against something. Sizes do not compare across engines, because each family was probed with its own ODT witness file.
ODT to PDF: 11,917 bytes in 1.1 seconds, verified by a format signature.
ODT to MD: 277 bytes in 0.1 seconds, verified by a pandoc round trip.
ODT to DOCX: 5,514 bytes in 1.1 seconds, verified by a format signature.
ODT to EPUB: 5,063 bytes in 0.1 seconds, verified by a pandoc round trip.
ODT to TXT: 264 bytes in 0.1 seconds, verified by reading the text back.
ODT to HTML: 4,043 bytes in 0.1 seconds, verified by a pandoc round trip.
Other ways into JSON, and what they measured
Among the published routes into JSON, ODT is the second largest output of the 8 measured. The witness files differ, so this ranks the probe run and not your document.
RTF to JSON: 1,743 bytes in 0.1 seconds.
TXT to JSON: 1,343 bytes in under a tenth of a second.
CSV to JSON: 110 bytes in under a tenth of a second.
YAML to JSON: 110 bytes in under a tenth of a second.
DOCX to JSON: 1,722 bytes in 0.1 seconds.
What we will not pretend about ODT to JSON
An ODT file over 25 MB is refused before the upload finishes rather than after it, so you do not wait for a rejection.
An ODT to JSON run that passes 60 seconds is killed, and the pandoc process is killed with it. A run left behind would sit on one of the machine's two cores until somebody noticed.
32 of the 935 pairs probed in the family that serves ODT to JSON failed, and this pair is not one of them. They fail for reasons worth knowing: a writer that cannot carry what the document is made of, or output the engine could not read back. They are counted here rather than hidden, because a pair that fails quietly is worse than one that fails loudly.
pandoc never writes the JSON through a TeX engine here, and it never writes PDF at all: the eleven engines it would need are not on this machine and a TeX distribution weighs several gigabytes. Anyone who wants a PDF out of an ODT file goes through LibreOffice or calibre, both of which genuinely can.
One ODT file at a time, chosen in the browser. There is nothing else to set up and nothing else on offer.
ODT to JSON: what people ask
What actually converts my ODT file to JSON?
pandoc does it, in two passes, on a machine we rent and watch. Not a browser trick and not somebody else service: the ODT file is uploaded once, pandoc runs once, the JSON comes back, and neither file is kept afterwards.
How long does ODT to JSON take?
On the file the probe used, pandoc took 0.1 seconds and wrote 1,761 bytes of JSON. That is one real measurement on one real ODT file, not an average and not a promise about yours: a larger ODT takes longer, and past 60 seconds the run is stopped.
What do I lose going from ODT to JSON?
The one to know about first: Page layout. ODT carries some and JSON carries none, so margins, page breaks, headers and footers have nowhere to land and are simply not written.
Are the tables in my ODT file still tables in the JSON?
No, and that is a property of JSON rather than a defect of this path. JSON cannot hold a table, so an ODT file built around one is the wrong candidate for this pair.
Is ODT to JSON free?
There is a free allowance every month, and one ODT to JSON conversion costs half a credit against it. When the allowance runs out the tool says so and stops, rather than quietly handing you a worse JSON.