10 LaTeX Equation Mistakes That Break When You Convert to Word (and How to Avoid Them)
Equation conversion problems aren't random — the same handful of patterns cause almost all of them. If you know what to look for, you can fix these in your LaTeX source in seconds, before they turn into a broken equation in your Word document.
- Custom macros without a fallback.
\newcommand{\R}{\mathbb{R}}is fine within LaTeX, but a converter needs the macro definition present to expand it — if you only define macros in a separate style file that isn't included, the symbol won't resolve. - Unclosed math delimiters. A stray unmatched
$or\[without its closing\]will cause everything after it to be misinterpreted as math (or vice versa) for the rest of the document. - Nested
aligninsideequation. These environments aren't meant to nest; usealignon its own for multi-line equations instead of wrapping it insideequation. - Non-standard packages for symbols. Some specialized packages define symbols that have no direct equivalent in Word's native equation format — these usually convert but can shift to the nearest visual equivalent rather than an exact match.
- Manual line breaks inside inline math. Inline
$...$math isn't meant to span multiple lines with manual breaks — use a display environment instead if the expression needs to break. - Using
\labelwithout a matching\refor\eqrefanywhere. Not a hard error, but it usually signals a cross-reference that's supposed to exist elsewhere and doesn't — worth double-checking rather than assuming it's intentional. - Tables inside equation environments. Occasionally used as a layout hack for multi-column derivations — this rarely survives conversion cleanly. A proper
arrayoralignedenvironment converts far more reliably. - Font-switching commands mixed into math mode. Commands like
\textbfused inside math mode instead of\mathbfcan produce inconsistent formatting once converted. - Overloaded operator redefinitions. Redefining common operators (like
\sumor\int) to behave differently than their standard meaning will convert using the standard symbol, not your redefinition — since the converter has no way to know about a purely visual redefinition. - Copy-pasted Unicode math symbols instead of LaTeX commands. A pasted "≤" character behaves differently from
\leqduring conversion and can produce inconsistent spacing or font mismatches in the output.
The fastest way to catch these
Most of these are easy to miss by eye in a long document. Running your text through Stemdoc's preflight check before converting won't catch every item on this list — some are inherent limits of translating between two different math typesetting systems — but it will catch the structural issues (unresolved cross-references, missing definitions) before they show up as broken math in your final Word file.
When in doubt, convert a test section first before running your entire document through, so you can spot-check the equation-heavy parts before committing to the full conversion.