Inline AI editing and proofreading
Live nowIn-editor AI requests can generate, rewrite, and proofread selected LaTeX content.
Read the docsComparison
LaTeX in the Browser vs a Local TeX Toolchain
A local setup — TeX Live or MiKTeX plus a desktop editor such as TeXstudio — is free, offline, and fully under your control. The trade is setup and maintenance time, harder collaboration, and no built-in help when a compile fails. This page lays out that trade honestly.
The local-setup side describes widely known properties of TeX Live, MiKTeX, and desktop editors rather than any single vendor’s claims.
Best fit if you need
- Writing to start now, without installing and maintaining a TeX distribution
- Real-time collaboration and comments without emailing project archives
- AI help when the compiler output is cryptic
- The same project reachable from any machine, with ZIP and GitHub portability
Trust & Status
What the browser workflow actually includes
Every feature below is documented in the product; roadmap items stay labeled as roadmap. Your local toolchain is not being talked down — it simply sits on the other side of a real trade-off.
Comments in the editor
Live nowTeams can add, reply to, edit, and delete line-linked comments inside a project.
Read the docsVersion history and snapshots
Live nowProjects expose version history, labeled milestones, and snapshot restore flows.
Read the docsGitHub import, export, and sync
Live nowUsers can connect GitHub, import repositories, export projects, and run push/pull sync.
Read the docsZIP-based project migration
Live nowProjects can be moved into the editor through standard file upload flows and ZIP-based migration.
Read the docsTrust & Privacy
The details that matter before switching
Moving from a fully local setup raises fair questions about data, portability, and control. These pages answer them.
AI & your data
How AI features handle your documents, including where the training-data boundary sits.
Moving your projects
ZIP and GitHub transfer paths that work today — your local project folder imports as-is.
Security & compliance
EU-oriented hosting, consent-based analytics, and the answers your institution will ask for.
Fit
Choose based on where your time goes
Both approaches compile the same LaTeX. The question is whether your time should go into maintaining an environment or only into the document.
Choose LaTeX Cloud Studio if
The better fit when writing, collaboration, and portability matter more than owning the toolchain.
- You lose time to installs, package updates, or "works on my machine" differences between co-authors
- You collaborate — comments, shared projects, and version history beat emailing ZIPs
- You want AI help decoding compile errors instead of searching forums for them
- You switch machines and want the project — not a synced folder — to be the source of truth
A local setup can still be the better fit if
Local toolchains remain excellent, and for some workflows they are clearly the right call.
- You regularly write without an internet connection
- You need custom engines, exotic packages, or build scripts beyond a standard TeX Live distribution
- You work solo and your institution or workflow forbids cloud tools for the material
- You want zero recurring cost and full control over every part of the stack
Comparison table
Where the two workflows differ in practice
The local column describes a typical TeX Live/MiKTeX plus desktop-editor setup, honestly — including the points where it wins.
| Feature | LaTeX Cloud Studio | Local setup |
|---|---|---|
| Setup and maintenance | ||
| Time to first compile | Open the browser and compile — packages are available without local installation. | Install a multi-gigabyte distribution, configure an editor, and resolve packages first; fully offline afterwards. |
| Keeping it working | The environment is maintained centrally; every collaborator compiles against the same toolchain. | Updates, package conflicts, and per-machine differences are yours to manage — with full control in return. |
| Collaboration | ||
| Working together | Shared projects, comments, and version history are part of the product. | Typically Git plus discipline, or emailing archives — workable for experienced solo users, hard for mixed teams. |
| Reviewing changes | Line-anchored comments and named versions inside the editor; track-changes review remains roadmap. | Diff tools and latexdiff work well but require every participant to run the same tooling. |
| Help and portability | ||
| When the compile fails | AI-assisted error explanation and proposed fixes inside the project. | Raw log output plus your own experience — powerful for experts, a wall for newcomers. |
| Project portability | ZIP import/export and GitHub sync are documented current workflows — including the way back out. | Files are plain and local by definition — maximum portability, minus the shared environment. |
A hybrid is common and reasonable: GitHub as the source of truth, local toolchain for offline work, the browser editor for collaboration — the GitHub sync workflow exists precisely for that.
Why switch
What usually triggers the move from local to browser
Few people leave a working local setup for fun. These are the moments that actually cause the switch.
A co-author joins
The first shared deadline turns environment differences and emailed archives from an annoyance into a real cost.
A new machine or reinstall
Rebuilding a TeX environment is exactly the moment people question whether they should be maintaining one at all.
An error that eats an evening
One cryptic compile failure before a deadline is often what makes in-editor AI error help concrete rather than abstract.
Transition path
Your local project imports as-is
A local LaTeX project is already in the perfect format for migration — it is just files.
01
Zip the project folder
Main file, chapters, figures, bibliography — the folder you already have is the import format.
02
Upload and compile
Import the ZIP, compile, and check the usual suspects: main file, bibliography, and image paths.
03
Keep Git if you use it
If the project lives in a repository, connect GitHub instead and keep your local clone for offline work.
FAQ
Common questions from local-setup users
Do I have to give up my local setup?
No. With GitHub sync as the source of truth you can keep compiling locally when offline and use the browser editor for collaboration — the two coexist well.
Are my packages available in the cloud?
The cloud environment compiles against a full TeX Live distribution, so standard packages are available without installation. Genuinely custom engines or private packages remain a reason to keep a local toolchain in the loop.
Can I get my projects back out?
Yes. ZIP export and GitHub sync are documented current workflows — the project stays plain LaTeX files throughout, with no proprietary format.
Is a browser editor slower than compiling locally?
Compile time depends on the document in both cases. The honest difference is not raw speed but where your time goes: local setups cost maintenance time, the browser workflow costs a network dependency.
Test it with the project you already have
Zip a real project, import it, and compile. If it does not earn its place in your workflow, export and walk away — the files stay yours either way.