Typst vs. LaTeX vs. Extended Markdown: Choosing a Typesetting Stack in 2026

Every team that produces structured documents eventually faces the same question: which authoring stack should we standardize on? In 2026, the honest answer is still "it depends" — but the three realistic options have rarely been so clearly separated. Typst shipped version 0.15 in June 2026, followed by a bugfix release in July, and the momentum behind it keeps building. LaTeX received its annual kernel release at the start of June 2026 and continues to set the pace on standards work, most visibly around accessible mathematical PDFs. And a third path has matured for everything that is less "doctoral thesis" and more "business document": platforms built on Extended Markdown, which render a single source into PDF, DOCX, and ODT.

This article compares the three stacks on the criteria that actually decide projects — output formats, math and diagrams, Word compatibility, automation, collaboration, and accessibility — and closes with a decision table you can apply to your own situation.

What actually changed in 2026

Date	Stack	What happened	Why it matters
June 1, 2026	LaTeX	Annual kernel release 2026-06-01 distributed via CTAN	The foundation TeX Live and MiKTeX users update to during the year
June 15, 2026	Typst	Version 0.15.0: variable fonts, equations in HTML export via MathML, experimental bundle export, multiple bibliographies per document, targeting several PDF standards in one run, spot colors	HTML output and print-production features narrow real gaps to LaTeX
June 16, 2026	LaTeX ecosystem	PDF Association webinar on accessible math in PDF, with LaTeX Project members on the panel	PDF/UA-2 documents with real mathematical content move from theory to practice
July 17, 2026	Typst	Version 0.15.1 with fixes for math alignment and updated default fonts	Early 0.15 adopters get a stable patch level

None of these releases flips the fundamental trade-offs between the stacks overnight. But two of them shift details that matter for specific decisions: Typst's multi-standard PDF targeting makes standards compliance easier in one compile, and the LaTeX accessibility work means long-lived STEM archives can be recompiled as genuinely accessible PDFs.

Three philosophies of document production

LaTeX treats a document as a program: you write source code, run a compiler, and iterate until the output is right. The model is powerful — precise control, a package for almost everything, and decades of templates — but it assumes a compiler-shaped workflow.

Typst keeps the "document as code" idea while redesigning the language, the error messages, and the compile loop around instant feedback. PDF remains the primary output, with HTML export growing in capability — equations are rendered as MathML since version 0.15.

Extended Markdown takes the opposite bet: keep the authoring layer as close to plain Markdown as possible, and move the heavy lifting — layout, templates, tables of contents, exports — into the platform. The point is not maximum typographic control. The point is that a contract, a proposal, or a quarterly report needs to exist as a polished PDF and as an editable Word file and sometimes as a batch of 200 personalized copies — without maintaining three sources.

The comparison at a glance

Criterion	LaTeX	Typst (0.15.x)	Extended Markdown (Autype)
Primary output	PDF (via pdfLaTeX and friends)	PDF, plus HTML export	PDF, DOCX and ODT from one source
Native DOCX	No — external converters required	No — external converters required	Yes, first-class export
Mathematics	The gold standard	Modern math mode, fast compilation	LaTeX-style $$…$$ formulas embedded in Markdown
Diagrams and charts	TikZ and a deep package ecosystem	Growing, younger package ecosystem	17 diagram languages (Mermaid, PlantUML, GraphVIZ, TikZ and more) plus 8 chart types
Editing model	Source code plus compile in TeX editors	Source code plus fast incremental compile	Visual block editor and Markdown mode with live preview
Collaboration	Solved externally (Git or online editors)	Web app with shared projects	Real-time collaboration, comments, Git-style version history
Automation	CLI in CI pipelines	CLI, plus typst eval for scripting	REST API, MCP server, CLI, Make.com and n8n integrations, webhooks, bulk rendering up to 100 documents per job from JSON, CSV or Excel
Accessibility	PDF/UA-2 groundwork for math (2026)	Multiple PDF standards targetable since 0.15	Export profiles for tagged, archival and accessible PDF
Learning curve	Steep	Moderate	Flat — Markdown knowledge transfers directly
Cost model	Free and open source	Free and open source	Free entry tier, usage-based engine, editor plans

Read the table with one caveat: the rows are not equally weighted for every team. A legal department cares mostly about the DOCX row; a physics institute cares mostly about math and accessibility; a SaaS backend team cares mostly about automation.

Where LaTeX still wins

If your output is a dissertation, a book, or a paper destined for a journal that dictates a LaTeX class, the decision is already made. Forty years of packages mean that whatever exotic requirement appears — a publisher's title page, a specific citation style, microtypography — someone has solved it before.

The 2026 accessibility work adds a new argument: existing LaTeX archives with heavy math can now be recompiled as PDFs that comply with PDF/UA-2, the first version of the standard that handles mathematical content properly. We covered what that means for document pipelines in our article on accessible PDFs at scale.

Where Typst wins

Typst is the strongest choice when you are starting a new, PDF-first technical document today and value fast feedback loops. Version 0.15 removed several practical excuses to stay away: variable fonts for brand-consistent typography, HTML export that finally carries equations as MathML, multiple bibliographies in one document, and the ability to target several PDF standards in a single compile instead of one per run.

The honest caveats: the package ecosystem is years behind LaTeX, the API still evolves between minor versions, and there is no native Word export. If your reviewer insists on tracked changes in a DOCX, you will end up in a converter again — the same friction that plagues pure Markdown-to-Word conversion pipelines.

Where Extended Markdown wins

Extended Markdown platforms such as Autype are built for business documents — proposals, contracts, reports, invoices — where the requirements look different: mixed authoring teams, brand templates, approval steps, and multiple output formats from one source.

Four capabilities decide most projects here:

1. One source, three outputs. The same document renders to PDF, DOCX and ODT, so the client gets an editable Word file while the archive keeps the PDF.
2. Visual and text editing on the same document. Developers stay in Markdown mode; operations teams use the visual block editor. Nobody converts anything.
3. Data-driven bulk output. Template variables like {{client_name}} plus bulk rendering from JSON, CSV or Excel turn one template into hundreds of personalized documents in a single job — the classic reporting and invoicing use case, at up to 100 documents per job.
4. Agent-friendly interfaces. A REST API, an MCP server, a CLI and integrations for Make.com and n8n mean an AI agent can assemble the finished document, not just draft its text. The document engine exposes exactly this side of the platform.

A quarterly report illustrates the difference. In Extended Markdown, the skeleton is close to the final document:

# Quarterly report {{client_name}}

:::chart{...}:::

Revenue recognition followed the schedule in table 1.

The same report in LaTeX starts with a document class, a TikZ/pgfplots setup and a bibliography configuration; in Typst it starts with a template function and a chart package. Both approaches are legitimate — they simply optimize for authoring control and reproducibility rather than for "finished by Friday."

Choosing your stack: a decision table

Your situation	Recommended stack
Doctoral thesis or journal with a prescribed template	LaTeX
New in-house technical documentation, PDF-first, team likes modern tooling	Typst
Client-facing proposals and contracts that must look right as PDF and DOCX	Extended Markdown
Hundreds of personalized documents per month from CSV or Excel data	Extended Markdown
Long-lived STEM archive that must become PDF/UA-2 compliant	LaTeX pipeline today
An AI agent that should deliver finished files, not text drafts	Extended Markdown with MCP or CLI

Cost rarely decides between the stacks: LaTeX and Typst are free and open source, and Extended Markdown platforms start free with usage-based engine pricing — Autype's plans are typical of the category. What decides is the shape of your documents and the shape of your team.

Conclusion

"Typst or LaTeX?" is the wrong question for most organizations. The right question is: how much typographic control do we actually need, and who has to edit the result? Maximum control with an established ecosystem points to LaTeX. A modern, fast, PDF-first workflow for technical writing points to Typst. Mixed teams producing business documents that must survive as Word files and scale from data point to Extended Markdown. In 2026, all three are mature enough that the choice is about fit — not about risk.

Sources

• Typst releases, version 0.15.0 (June 15, 2026) and 0.15.1 (July 17, 2026): https://github.com/typst/typst/releases (retrieved October 6, 2026)
• LaTeX Project news, kernel release 2026-06-01 and accessible-math announcements: https://www.latex-project.org/news/ (retrieved October 6, 2026)
• Autype feature overview: https://autype.com/llm.txt (retrieved September 21, 2026)