You know that sinking feeling. You spend an hour installing LaTeX, wrestling with `texlive` dependencies, only to realize your document still won’t compile. So you give up. You open Overleaf, paste your code, and the cloud does the rest. It works. It’s easy. But somewhere, deep in your academic soul, you feel like you’ve sold out.
You’re not wrong. Overleaf is convenient, but it’s a betrayal of everything LaTeX was built for. LaTeX was designed to be local, offline, and open-source — a system where you control every aspect of your document, from the packages to the compiler. Overleaf turns that into a web service. Your code lives on their servers. Your compilation happens in their cloud. You’re renting a workflow that should be yours by default.
Enter WASM TeX. It’s a set of LaTeX engines (PdfLaTeX, XeLaTeX, LuaLaTeX) compiled to WebAssembly, running directly in your browser. No server. No installation. No sending your files to a third party. Just open a page, write LaTeX, and compile — locally, in your browser, using your own machine’s CPU. It’s the most LaTeX thing to happen to LaTeX in years.
Let’s be clear about what this means. Overleaf gives you a button that says “Compile” and then waits for a server in some datacenter to process your document. WASM TeX gives you a button that says “Compile” and then your own browser does the work, right there, in milliseconds. Overleaf doesn’t just host your LaTeX — it hosts your freedom.
One comment on the project’s GitHub page nails it: “Overleaf is just an antipode of LaTeX original philosophy.” That’s not a hot take; it’s the truth. The original LaTeX philosophy was about total control, offline access, and no vendor lock-in. Overleaf is a beautiful walled garden. WASM TeX is a wild, open field.
Now, I know what you’re thinking: “But I need the collaboration features of Overleaf.” Fair point. But collaboration doesn’t require a cloud compiler. You can use Git for version control, and compile locally with WASM TeX. The project is still early — it’s not a full editor yet, just the engines. But the vision is there: a browser-based LaTeX experience that respects your autonomy.
You’ve probably wrestled with LaTeX installation at least once. Maybe you’re on a school computer where you can’t install software. Maybe you’re traveling with a Chromebook. WASM TeX solves that without sacrificing the local-first spirit. It’s the best of both worlds: the convenience of a web app with the ethics of open-source, offline software.
This isn’t just about convenience. It’s about principle. The future of LaTeX isn’t in the cloud. It’s in your browser, on your machine, compiling locally. WASM TeX is the first step toward that future. And if you care about the soul of your tools, you should pay attention.
Try it. Fork it. Contribute. Because the next time someone tells you to “just use Overleaf,” you can smile and say: “No thanks. I compile locally. Right here in my browser.”
FAQ
Q: Does WASM TeX work offline?
A: Yes, once the WebAssembly binaries are loaded in your browser cache, you can compile LaTeX documents without an internet connection. The compilation happens entirely on your machine.
Q: Can I use WASM TeX for collaborative editing like Overleaf?
A: Not yet. WASM TeX currently provides only the compiler engines, not a full editor with collaboration features. But you can pair it with Git or any local editor for a collaborative workflow that keeps compilation local.
Q: Is it slower than a native LaTeX installation?
A: WebAssembly performance is close to native. For most documents, compilation speed is comparable to a local LaTeX install. Very large documents may be slightly slower, but the convenience of zero setup often outweighs that.