A .tex file mixes the sentences you wrote with markup such as \cite{smith2024}, $x_i$ and \begin{equation}. A checker built for plain text marks that markup as misspelled words or broken sentences, so the real mistakes get lost in the noise. The tools below either strip the markup before checking or skip it when they report.
The four options
| Tool | Where you use it | What you need | Cost |
|---|---|---|---|
| LanguageTool with a local server | TeXstudio, as you type | LanguageTool and Java installed on the Mac | Free |
| LTeX+ | VS Code, as you type | The LTeX+ extension, plus LaTeX Workshop for .tex files |
Free |
| TeXtidote | Terminal, one report per run | Java | Free |
| ModernTex Manuscript Checks | ModernTex, when you run the checks | ModernTex on macOS | $19.99 once, after a 7-day trial |
I read each tool's own documentation on November 12, 2026. I did not run the three free tools on a paper for this page, and I do not rank them by accuracy.
LanguageTool with a local server in TeXstudio
LanguageTool is the grammar engine behind the next three options. It can run as a small server on your own Mac, and TeXstudio knows how to talk to it. TeXstudio's manual says the grammar checker needs a separate install of LanguageTool and Java. Once LanguageTool is running, it serves at http://localhost:8081/ and TeXstudio connects to it when TeXstudio starts. Paragraphs you type go to that local server, not to the internet.
- Install Java and LanguageTool. LanguageTool's server page gives a Homebrew route for macOS, though the LanguageTool team does not support it:
brew install languagetool, thenbrew services start languagetoolto run the server in the background. If it says Java cannot be found, install Java 8 or later first. - Or start it by hand from the unzipped LanguageTool folder:
java -cp languagetool-server.jar org.languagetool.server.HTTPServer --config server.properties --port 8081. If you have no settings to add, create an emptyserver.propertiesfile first. - Check that it answers:
curl -d "language=en-US" -d "text=a simple test" http://localhost:8081/v2/checkshould return a short JSON reply. - Start TeXstudio. To have TeXstudio start LanguageTool for you, enter the path to the LanguageTool jar on the grammar page of TeXstudio's settings, and the path to Java if it is not on the default path.
Limits: you look after Java and the server yourself, and the checking happens only inside TeXstudio. LanguageTool says its AI-based rules are only available in the cloud, so a local server does not have them. The long-running TeX Stack Exchange question on LanguageTool in TeXstudio collects the problems people hit with this setup.
LTeX+ in VS Code
LTeX+ is a VS Code extension that runs LanguageTool against LaTeX, Markdown and other markup. Its README says it comes with everything included, with no need to install Java or LanguageTool, and that offline checking does not upload anything. On first use it downloads its language server if it cannot find one, and the project documents an offline installation as well. VS Code does not know LaTeX on its own, so install LaTeX Workshop next to it.
- Install LaTeX Workshop and LTeX+ from the VS Code extensions view.
- Open a
.texfile. Possible errors are underlined in the editor.
The latest releases on GitHub were vscode-ltex-plus 15.7.1 and ltex-ls-plus 18.7.0, both from June 13, 2026. LTeX+ describes itself as the successor to the original LTeX extension, whose GitHub repositories are now archived. If you search for ltex vscode not working, check first which of the two you have installed: the archived one gets no fixes.
Limits: it lives inside VS Code, and the first run needs a download unless you install offline.
TeXtidote on the command line
TeXtidote reads your .tex file, removes the markup, passes the clean text to the LanguageTool library and maps each finding back to the right line of your source. It is a Java program. brew install textidote installs it with Java and gives you a textidote command; if you download the jar from GitHub instead, type java -jar textidote.jar where the steps say textidote.
- Run it with a language and an HTML report:
textidote --check en --output html paper.tex > report.html. - Open
report.htmlin a browser to see your source with the findings marked. - Add
--dict words.txtwith one word per line for names and terms it should accept.
Limits: there is no live highlighting while you type. You run it, read the report and go back to your editor.
ModernTex Manuscript Checks
ModernTex runs a spelling and grammar pass in Manuscript Checks. It uses the spelling and grammar checker built into macOS, and the text stays on your Mac. Spelling skips commands, citation keys, labels and maths. Grammar is on by default and can be turned off with Check Grammar in Manuscript Checks in Settings. I make ModernTex.
Limits: it is Apple's checker, not LanguageTool, so it is less thorough on style. Grammar findings come back for whole sentences, so a sentence dense with markup can still draw an odd finding. If that gets noisy, switch grammar off and keep the spelling check.
If you write in Overleaf
Overleaf's own help lists Writefull language suggestions, described as grammar and fluency edits for academic writing, among the AI features you switch on in Overleaf. Your project already lives on Overleaf's servers, so the choice there is about which features you enable, not about uploading. To check grammar on your Mac instead, download the project as a ZIP and use one of the tools above.
Last checked
November 12, 2026. Commands, requirements and versions were read from these pages on that day. Versions change, so check the source before you rely on a detail.
- LanguageTool: HTTP server (server command, Homebrew service, test URL).
- TeXstudio: configuration manual (configuring the grammar checker).
- LTeX+: vscode-ltex-plus and ltex-ls-plus on GitHub (README, releases) and the documentation.
- TeXtidote: README (options and report format) and the Homebrew formula (version 0.9).
- TeX Stack Exchange: LanguageTool in TeXstudio.
- Overleaf: Writefull integration.
If something here is out of date or wrong, write to ben@purplelink.llc and I will fix it.