A lot of people learn LaTeX in TeXworks. It ships with TeX Live and MiKTeX on Windows, it’s what many courses hand you on day one, and it does exactly what a first editor should: a source window, a PDF window, and a green button that turns one into the other.
Then you move to a Mac, or your document grows past a single file, and you start looking for what comes next. This is an honest map of the options.
First: you can keep using TeXworks
TeXworks runs on macOS. There are official builds on the project’s GitHub releases page, and it’s available through Homebrew:
brew install --cask texworksIt doesn’t bundle a TeX distribution, so you’ll want MacTeX (or the smaller BasicTeX) installed first. If which xelatex prints a path in Terminal, you’re set.
If TeXworks is working for you, there’s no reason to leave. But if you’re searching for alternatives, something has probably started to pinch.
Where TeXworks starts to pinch
TeXworks was designed to be simple, and its limits are mostly the flip side of that choice.
- Multi-file projects. Once a thesis is split into
main.texand a folder of chapters, the structure sidebar only shows the file you’re looking at. There’s no view of the whole document. - Autocompletion. Completion comes from fixed word lists, not from your project. Typing
\ref{won’t offer the labels you defined in chapter three, and\cite{won’t offer your.bibkeys. - Finding errors. When a build fails, you read the console output and work out which file and line TeX was complaining about.
- Feeling at home on a Mac. TeXworks is a cross-platform Qt application. It works, but it doesn’t always behave like the rest of macOS.
None of these matter for a ten-page paper. All of them matter by chapter six.
The alternatives
TeXShop — the one already on your Mac
If you installed MacTeX, you already have TeXShop in /Applications/TeX. TeXworks was modeled on it, so the two-window workflow will feel familiar, and it’s a native Mac app. It’s free and mature. It’s the closest thing to “TeXworks, but on a Mac” — which also means it shares a similar philosophy of keeping things minimal.
TeXstudio — everything, everywhere
Free, open source, and packed with features: a structure view that follows included files, completion for labels and citations, an error list, a long menu of tools. If you want maximum capability without paying, this is the usual answer. Like TeXworks, it’s a cross-platform Qt app, so on a Mac it trades some polish for breadth.
VS Code with LaTeX Workshop — if you already live in VS Code
A general-purpose editor turned into a capable LaTeX environment by one extension. Strong on configuration, multi-file support, and everything else the VS Code ecosystem brings. The cost is setup: it’s a toolkit you assemble rather than an editor that arrives ready.
Overleaf — if you’d rather not install anything
LaTeX in the browser, with real-time collaboration that nothing local can match. Your documents live on Overleaf’s servers, and some features — longer compile times, full history, more collaborators — sit behind a subscription.
texspark — native, and built for multi-file projects
Full disclosure: we make this one. texspark is a native macOS editor built specifically around the point where TeXworks starts to pinch — a project that outgrew one file. The outline covers the whole \include tree, \ref{ and \cite{ complete from across the project, and ⌘-clicking the PDF opens the sub-file the text came from. It’s paid, with a 14-day free trial and no signup.
Moving your project over
The good news: there’s nothing to convert. Your files are plain .tex, and every editor above reads them as-is. A few habits are worth checking, though.
Magic comments. TeXworks users often put these at the top of each chapter file:
% !TEX root = ../main.tex
% !TEX program = xelatexThe first tells the editor which file to compile when you’re editing a chapter; the second picks the engine. TeXShop, TeXstudio, and LaTeX Workshop all understand a version of these, so they’ll mostly carry over. Overleaf sets the main document and compiler in the project menu instead. texspark uses a build target: double-click the root file’s tab once, and ⌘B compiles it from any chapter. The engine lives in the project’s build command.
SyncTeX. TeXworks passes -synctex=1 in its default tool configurations, which is why clicking between source and PDF just worked. If you set up a custom build command elsewhere, make sure the flag comes along — otherwise jumping between source and PDF will quietly stop working.
Your TeX distribution stays. None of these editors replace MacTeX; they all drive the same xelatex or pdflatex underneath. Switching editors doesn’t change your output.
Picking one
- You liked TeXworks’ simplicity and just want it to feel at home on a Mac → TeXShop
- You want every feature, free → TeXstudio
- You already write code in VS Code → LaTeX Workshop
- You collaborate, or don’t want to install anything → Overleaf
- Your project is many files and you want a native Mac app built for that → texspark
Leave a Reply