Reducing LaTeX justification ugliness with the microtype package

The problem: rivers, hyphenation and overfull boxes

When you compile a justified paragraph in LaTeX, you may notice uneven spaces that form visual "rivers" down the page, frequent hyphenation, or warnings like Overfull \\hbox in the log. These issues stem from the line‑breaking algorithm’s limited flexibility when the text is forced to fit a fixed column width.

Why microtype helps

The microtype package adds two subtle typographic adjustments that are built into pdfTeX‑based engines:

• Character protrusion – allows punctuation marks and certain glyphs to hang slightly into the margin, making the right edge appear more even.
• Font expansion – varies glyph widths by a tiny amount (typically 1‑2 %) to give the line‑breaker more wiggle room without visible distortion.

Together they reduce the need for hyphenation and lower the chance of overfull lines, often eliminating the warnings you see in the log.

Worked example: comparing a document with and without microtype

1. Create a minimal test file named test.tex with the following content (replace \lipsum[1-3] with any paragraph-heavy text you have):

   \documentclass{article}
   \usepackage{lipsum}% for dummy text
   \begin{document}
   \lipsum[1-3]
   \end{document}
   

2. Compile twice, first without microtype:

   pdflatex -interaction=nonstopmode test.tex
   

   Check the log (test.log) for lines containing Overfull \\hbox and note the count.

3. Add the package after any font loading (here none is needed) and recompile:

   \documentclass{article}
   \usepackage{lipsum}
   \usepackage{microtype}% <-- added line
   \begin{document}
   \lipsum[1-3]
   \end{document}
   

   Run the same command again and compare the log.

4. Visually inspect the PDF: zoom to the right margin of a justified line. With microtype enabled, hyphens and punctuation (e.g., commas, periods) will appear to extend slightly past the edge, while without it they sit flush.

You should see fewer (or zero) overfull box warnings and a more uniform right edge. The exact numbers vary by document, but the visual difference is usually noticeable even without typographic training.

Trade‑offs and limitations

• Engine support – pdfLaTeX and LuaLaTeX implement both protrusion and expansion fully. XeLaTeX supports protrusion but historically lacks font expansion; check the log for a line like microtype mode: 2 (protrusion only) if you use XeLaTeX.
• Font awareness – microtype ships preset configurations for common fonts (Computer Modern, Latin Modern, Times‑like via newtx). If you use an obscure font, the package falls back to generic settings, which still work but may be less optimal.
• PDF size and compile time – enabling expansion creates a few extra font variants, increasing the output file size by a negligible amount (typically under 1 %) and adding a barely perceptible compile‑time overhead.
• Not a cure‑all** – narrow columns, long URLs, or manually forced line breaks can still produce overfull boxes; microtype reduces frequency but does not eliminate them.

Actionable closing

For most LaTeX workflows, adding a single line \usepackage{microtype} after your font setup yields a noticeable typographic improvement with virtually no risk. Try the comparison above on your own project; if the log shows fewer warnings and the margin looks smoother, keep the package enabled. If you are on XeLaTeX and need font expansion, consider switching to LuaLaTeX or pdfLaTeX, or consult the microtype documentation for engine‑specific tweaks.