Typst: LaTeX power, markup simplicity, compiled locally.
GitHub RepoImpressions61
View on GitHub
@githubprojectsPost Author

Typst: LaTeX Power Without the Pain

You know the feeling. You need to write a paper, a technical report, or maybe some docs. LaTeX is the obvious choice for beautiful typesetting, but god, the syntax. And the compilation. And the packages. And the errors. There has to be a better way.

Enter Typst. It's a modern typesetting system that gives you the layout power of LaTeX but with a markup syntax that actually feels clean. And it compiles locally on your machine. No cloud. No waiting.

What It Does

Typst takes a plain text markup file and compiles it into a PDF (or other formats) right on your local machine. You write in a simple, expressive syntax. Think Markdown but with the ability to define proper document structures, equations, tables, figures, and cross-references. It handles all the typographic details: margins, fonts, line breaking, hyphenation, pagination.

Under the hood, it's a Rust-based compiler with its own layout engine. That means it's fast. And because it's local, you're not sending your content to some server to get rendered.

Why It's Cool

  • Syntax that makes sense. Instead of \section{Introduction} you write = Introduction. Instead of \emph{important} it's *important*. Math mode? $x^2$ inline, $x^2$ display. It's intuitive.

  • Real local compilation. You run typst compile file.typ and boom, PDF appears in milliseconds. No waiting for Overleaf to spin up, no CI/CD pipeline for a single document. It's a command line tool, so it fits right into your dev workflow.

  • No package hell. LaTeX packages are a dependency nightmare. Typst has a built-in standard library that covers most needs. Need a specific feature? You write it in Typst's scripting language (it's like a domain-specific language baked into the tool). No hunting for CTAN packages that might not work together.

  • Templating done right. You can define reusable elements, variables, loops, and conditionals. It's like having a build system for your documents. Want to autogenerate a report for each month? Define a template, pass in data, compile. Easy.

  • No voodoo. LaTeX documents often break in mysterious ways because of hidden state (missing packages, old installs, conflicting classes). Typst's compiler is deterministic and gives you clear errors. It's obvious what went wrong.

How to Try It

  1. Install via your package manager or grab the binary from the releases page.

    • macOS: brew install typst
    • Linux: cargo install typst-cli (requires Rust)
  2. Create a .typ file:

= My First Document

Hello, world! This is *Typst*.

Let's do some math: $a^2 + b^2 = c^2$

Here's a list:
- First item
- Second item

= Another Section
This is a new section.
  1. Compile it:
typst compile mydoc.typ

That's it. You get mydoc.pdf in the same folder.

  1. Watch for changes (optional):
typst watch mydoc.typ

This recompiles automatically whenever you save. Instant feedback.

Final Thoughts

Typst isn't trying to kill LaTeX. It's trying to fix the parts of LaTeX that make developers want to pull their hair out. The compilation speed alone is worth the switch for many. For devs who write technical docs, reports, or papers, it's a natural fit: command line, fast iteration, clear syntax, no lock-in.

Is it as mature as LaTeX? No. Some edge cases (like niche math notations or complex floats) still need work. But for 90% of what people use LaTeX for, Typst is already better. And since it's open source, you can contribute.

If you've ever written \documentclass{article} and felt a small piece of your soul die, give Typst a shot. Your future self will thank you.


Follow @githubprojects for more dev tools and open source gems.

Back to Projects
Last updated: June 9, 2026 at 05:49 AM