Other editors

Editors for LaTeX are not limited to purpose-built tools. There are TeX front-ends long favored on Windows — WinEdt and WinShell — and there is the other path: taking a general-purpose editor you already use and adding a plugin or an external-command setup to drive LaTeX. This page surveys those options, on the shared understanding that none of them typesets anything itself: each is a place to write, then hand off to a TeX engine.

One thing up front: every option below is an editor, not a TeX system. The actual typesetting is done by a distribution you install separately — TeX Live, MiKTeX, or MacTeX — and the editor merely invokes it to produce a PDF. So “which editor” and “which engine” are separate questions, and the latter must be settled first.

WinEdt — the veteran Windows front-end

WinEdt is a Windows-only Unicode text editor that has been going since 1993 and was for years the default TeX front-end on the platform. It works as a plain editor, but its real strength is that it is built to integrate seamlessly with TeX Live and MiKTeX: a single toolbar button runs pdflatex, platex, and friends, alongside completion, spell-checking, project management, and regex search-and-replace.

The catch is licensing. WinEdt is shareware: after a 31-day trial you pay a registration fee to keep using it (with separate educational and business rates). With so many free, open-source options now available, paying for an editor may give you pause — but development is active, and as of 2026 the 11.x series is still being updated for Windows 11 and 10.

WinShell — a free Windows IDE

WinShell occupies much the same niche as WinEdt, but it is free. This Windows LaTeX IDE bundles a text editor, syntax highlighting, project management, spell-checking, a table wizard, BibTeX integration, and Unicode support, and it invokes your engine from the toolbar to typeset. It is freeware distributed as a binary (the source is not public), but it too has been maintained through 2026, making it a solid no-cost alternative to the paid WinEdt.

Neither WinEdt nor WinShell ships a typesetting engine. The procedure is the same for both: install MiKTeX or TeX Live first, then point the editor’s settings at where those commands live.

Driving LaTeX from a general-purpose editor

A general-purpose editor that is not TeX-specific can still write LaTeX comfortably, as long as you can arrange two things: syntax highlighting and a way to invoke the build. Broadly there are two approaches. The “rich” path leans on a plugin that also handles completion, PDF preview, and forward/inverse search; the “plain” path simply calls a build such as latexmk from the editor’s external-command feature. The latter is quick to set up, but jumping to error locations and syncing with the PDF are left for you to wire up.

JetBrains IDEs (IntelliJ IDEA and the rest) become a full LaTeX environment once you add the TeXiFy IDEA plugin. It brings syntax highlighting; completion of labels, commands, environments, and file names; an embedded PDF viewer; and BibTeX (.bib) support — letting you carry IntelliJ’s ergonomics straight into LaTeX. For anyone who already lives in JetBrains tools for programming, it is the natural choice (IntelliJ IDEA has a free Community edition).

Notepad++ is a lightweight editor widely used on Windows. Thanks to the underlying Scintilla library it does syntax-highlight TeX files, though by default it does not color math environments (you can fill that gap with a user-defined language). The usual way to build is the NppExec plugin: bind a command to a key such as F6 to run your engine, show the output in a console, and optionally colorize error lines.

In Japan there is also a durable tradition of using a home-grown, Japanese-savvy editor as the base. EmEditor is a Windows editor that stays nimble even on huge files and has shipped TeX (LaTeX) syntax-coloring settings from early on (there is a free edition and a paid Professional one). Sakura Editor (サクラエディタ) is a free, popular domestic editor; the community has long shared build automations that call platex from its macro facility (e.g. ExecCommand) and then open a DVI viewer. Both suit the pattern of “type the Japanese manuscript in an editor you know well, and farm out only the build.”

For the historical record, there is also Atom. GitHub’s editor had LaTeX packages too, but development ended (the project was archived) on December 15, 2022. Technically it handed the baton to its descendant Electron and to VS Code. If you are starting today, do not pick Atom — choose its spiritual successor, VS Code, instead.

At a glance

A summary of what each editor is and how it handles LaTeX. As the “how it does LaTeX” column shows, every one of them produces a PDF by calling out to a separately installed engine.

How to choose

On Windows and want a TeX-specific feel right away? The free WinShell, or the polished (if paid) WinEdt. Want to reuse your everyday dev setup? JetBrains users reach for TeXiFy IDEA; if you would rather keep it light in Notepad++, use NppExec. Prefer to type a Japanese manuscript in a familiar editor? Wire an external command into EmEditor or Sakura Editor.

That said, absent a strong attachment, a safe starting point is VS Code (LaTeX Workshop) — free, full-featured, cross-platform, and actively developed — or the purpose-built TeXstudio. Both have their own pages here, well worth a look alongside this one.