DOCX is Word in the OOXML format, with headings, tables and named styles. JATS is the XML every journal publisher and PubMed archives articles in. pandoc sits between the two, and this page says exactly what happens to a DOCX file on the way to becoming a JATS one.
What runs when a DOCX file becomes JATS
pandoc in two passes, on a machine we rent and watch. Your DOCX file is uploaded once, pandoc runs once, the JATS comes back, and neither file is kept. DOCX to JATS 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 DOCX into the JATS
The heading hierarchy. pandoc parses the DOCX file into its own document tree and writes that tree out as JATS, so a level two heading is still a level two heading and not merely bold text.
Tables, rebuilt in JATS syntax rather than screenshotted. That is the difference between a table a machine can read and a picture of one, and it is the whole reason to send a DOCX file through pandoc rather than through a printer.
Lists from the DOCX file, nesting included, plus code blocks, block quotes and links, all re-expressed in JATS.
Images: pandoc extracts them out of the DOCX file into a working directory and re-embeds them in the JATS, so nothing ends up pointing at a file that no longer exists.
What DOCX to JATS costs you
The presentation layer. pandoc does not translate the DOCX file into JATS, it rebuilds it from its own document tree, so custom styles, page setup, headers and footers do not cross over. The structure does, and that is what the tree is made of.
Where DOCX and JATS files come from
DOCX. Word writes it, and so does Google Docs on export. It is ISO/IEC 29500, a zip of XML, which is what lets a program read the document without opening Word.
JATS. Journal Article Tag Suite, a NISO standard and the format PubMed Central, Crossref and most publishers store articles in. If a paper is going into a journal pipeline rather than onto a web page, this is the shape it has to arrive in.
If a model is going to read the JATS
Structure is what survives from the DOCX file, and structure is what a model needs. DOCX in, JATS out, with the heading tree intact instead of flattened into one long paragraph.
DOCX to JATS, measured rather than promised
Running DOCX to JATS against the real engine with a real file, pandoc wrote 1,116 bytes of JATS in 0.1 seconds, machine otherwise idle. That is one DOCX file on one day and not an average, which is why the number is given together with the file that produced it.
The DOCX to JATS verdict was reached by finding a marker unique to the format, and the witness word with it, meaning the output carries a marker no other format writes, and the witness word planted in the source is still in it. Nothing can read these targets back, so both were required: the word alone would prove the text travelled, the marker alone that the shape is right. 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 JATS file has anything inside it.
The same DOCX file, sent somewhere else
Other outputs the probe measured out of a DOCX file, so the cost of choosing JATS can be read against something. Sizes do not compare across engines, because each family was probed with its own DOCX witness file.
DOCX to PDF: 11,917 bytes in 1.2 seconds, verified by a format signature.
DOCX to MD: 266 bytes in 0.1 seconds, verified by a pandoc round trip.
DOCX to EPUB: 5,040 bytes in 0.1 seconds, verified by a pandoc round trip.
DOCX to TXT: 264 bytes in 0.1 seconds, verified by reading the text back.
DOCX to HTML: 4,018 bytes in 0.1 seconds, verified by a pandoc round trip.
DOCX to RTF: 4,205 bytes in 1.1 seconds, verified by reading the internal type and finding a witness word.
What we will not pretend about DOCX to JATS
A DOCX file over 25 MB is refused before the upload finishes rather than after it, so you do not wait for a rejection.
A DOCX to JATS 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 DOCX to JATS 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 JATS 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 a DOCX file goes through LibreOffice or calibre, both of which genuinely can.
One DOCX file at a time, chosen in the browser. There is nothing else to set up and nothing else on offer.
DOCX to JATS: what people ask
What actually converts my DOCX file to JATS?
pandoc does it, in two passes, on a machine we rent and watch. Not a browser trick and not somebody else service: the DOCX file is uploaded once, pandoc runs once, the JATS comes back, and neither file is kept afterwards.
How long does DOCX to JATS take?
On the file the probe used, pandoc took 0.1 seconds and wrote 1,116 bytes of JATS. That is one real measurement on one real DOCX file, not an average and not a promise about yours: a larger DOCX takes longer, and past 60 seconds the run is stopped.
What do I lose going from DOCX to JATS?
The one to know about first: The presentation layer. pandoc does not translate the DOCX file into JATS, it rebuilds it from its own document tree, so custom styles, page setup, headers and footers do not cross over. The structure does, and that is what the tree is made of.
Are the tables in my DOCX file still tables in the JATS?
Yes. pandoc reads the DOCX tables into its own document tree and writes them back out in JATS syntax, so what you get is a table a machine can parse rather than a picture of one.
Is DOCX to JATS free?
There is a free allowance every month, and one DOCX to JATS 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 JATS.