How a manuscript makes the round trip

You upload the flattened .tex and its compiled PDF. Every equation is set as native OMML — Word's own math format, editable in place — never as an image. Numbered equations keep visible numbers, including subequations (1a, 1b) and \nonumber; every \eqref and \ref resolves to the number the PDF shows. Citations from a manual thebibliography are restored as [n].

Figures get three chances — the .docx never ships without them:

The from-scratch direction most people need — no original .tex required. A Word manuscript becomes a clean LaTeX project on a built-in single- or double-column article template. OMML equations become real LaTeX math, figures are extracted and captioned, tables are rebuilt for the chosen layout, and Word's unicode habits — Greek letters, the U+2212 minus, ≤ ≈ ° — are made pdflatex-safe.

The PDF is compiled server-side, so you download both the source and a ready document. Templates use only stock TeX Live packages: the delivered .tex compiles anywhere, including Overleaf.

You sent a .docx to a co-author; it came back full of prose edits. The merge is three-way: your original .tex, the base .docx you sent out, and the edited .docx that came back. Paragraphs are paired between base and edited; edits above a similarity threshold are transplanted into the .tex.

It is conservative by design. Macros, \cite, math spans and the preamble are kept byte-for-byte. Anything ambiguous — big rewrites, touched citations, edited math — lands in a .review.md report instead of silently corrupting the source.

Every conversion is an isolated subprocess job with its own directory: uploads in, outputs out, and a merged stdout/stderr log streamed live to the console you watch. Jobs survive restarts honestly — anything caught mid-flight is marked interrupted, never lied about. A hard timeout means a pathological input cannot wedge the service, and a janitor deletes jobs older than 24 hours.

The UI is generated from a converter registry: the API describes each converter's inputs and options, and the page builds the form from that. A new converter appears with zero frontend work.