TeXstudio en 2026: qué envejeció bien y qué no

Open TeXstudio and the tooling makes sense immediately if you grew up on desktop LaTeX. Structure view. Autocomplete. A thousand symbols. Wizards for tables and formulas. PDF side-by-side. SyncTeX. A build system that will run whatever chain you configure. For a long stretch of academic history, that was desktop LaTeX.

Papers got multi-file and multi-tool. People started expecting project shelves, automatic history, citation search, offline grammar that understands source, Typst for fast notes, optional AI that can compile and show a diff. UI patterns moved. TeXstudio is still a studio for TeX—a customizable IDE around a distribution you install—more than a research workspace for everything around the manuscript.

What follows is a critical look. Pros, cons, a comparison table, then how to try your existing tree without throwing TeXstudio away.

The case for staying

Build power. Free-form multi-tool chains, latexmk-style recipes, shell-escape workflows, the long tail of “my university class only works if I run X then Y.” If that is your daily job, TeXstudio’s configurability is still a reason to open it.

Maturity. Years of edge cases on classic desktop LaTeX. Muscle memory. Menus you can find with your eyes closed. Cross-platform and free (GPL-family desktop tradition).

Classic IDE features that still work. Structure, completion, integrated PDF, SyncTeX, reference checks, folding, spelling. For a single-engine LaTeX life with a TeX Live install you already love, the core loop is proven.

If your only complaint is that the icons look dated and the build system already runs your thesis, you do not need a migration story. Close this tab.

The case for criticism

It is a studio, not an AI-era workspace

TeXstudio helps you typeset. It does not treat the project as a modern research desk: optional agent that can edit, compile, read the log, and show approval diffs; MCP for external tools; inline rewrite with accept/reject; literature search wired into the same surface. You can bolt Copilot onto something else, or live without AI. Fine. Calling it a full research workspace in 2026 oversells what the product is.

Oleafly’s AI is optional and inspectable (your key or Ollama; red/green diffs; Git checkpoint first). The workspace is shaped around that loop. TeXstudio is shaped around menus, build profiles, and a TeX tree.

The UI still feels like 2010 desktop

Dialogs. Preferences forests. Assistant panels that solve problems by adding another form. Power users adapt. New students bounce. “Intuitive” is subjective; “dense and dated” is fair next to tools designed in the last few years. Some of that density is the cost of exposing every build knob. Some of it is just age.

A modern research UI can still be keyboard-first (command palette, omnibar, Vim) without a scavenger hunt through nested options to start a paper.

Bring your own multi-gigabyte TeX

TeXstudio assumes TeX Live / MiKTeX (or similar) already exists and stays healthy. That is power and burden. PATH issues, package updates that break a class file, “works on my lab machine” chaos across coauthors.

Oleafly ships Tectonic and Typst in the app; packages cache on first use; Markdown via managed Pandoc when needed. You give up free-form multi-tool recipes for a supervised engine that does not own your weekend. Heavy publisher classes can still trip Tectonic—say that out loud—while most ACM/IEEE/Elsevier-style work is fine.

Project life is thin

Open a file. Compile. Close. Where is the shelf of active papers? Fork a resume variant with full history? Hover a cover and see the last PDF page? Search every project for a phrase? Bookmark the thesis?

TeXstudio is file-and-session oriented. Oleafly’s library is portfolio-oriented: books, covers, engine badges, fork lineage, bookmarks, /docs search, export history. Different job.

History and Git are someone else’s problem

You can use Git next to TeXstudio. You will set it up yourself. Automatic checkpoints after compile and idle edits, staging UI beside the PDF, one-click restore, AI session checkpoints—that is productized in a research workspace, not assumed in a classic IDE.

Multi-engine and research tooling

Typst as a first-class project. Markdown to PDF. Citation Search across arXiv / Semantic Scholar / Crossref / PubMed / OpenAlex. DOI paste into .bib + \cite. Diagram canvas to editable TikZ. Preflight for ATS and accessibility-oriented checks. Context-aware export (DOCX, HTML, PPTX for Beamer, EPUB). These are not “TeXstudio failed”; they sit outside its era and mandate.

What TeXstudio still does better

Configurable multi-step builds. Long maturity. Familiarity. If Oleafly’s beta label or Tectonic edge cases scare you on a hard deadline, TeXstudio is the conservative open.

What modern looks like on the same plain files

Open the same .tex tree in Oleafly and the difference is integration, not a new file format:

• Project-wide intelligence: definitions, references, rename, live ref/cite checks, structure views, your macros with argument shapes, TexLab/Tinymist when available
• Live KaTeX previews; Harper + Hunspell on prose only
• PDF workspace with stale-tolerant SyncTeX, spreads, detach window
• Real Git from day one; free GitHub sync
• Library fork with full history
• LaTeX + Typst + Markdown
• Optional AI / MCP under your control
• Templates (23 bundled + 99 packs), preflight, multi-format export
• Free forever (AGPL), no account

Downsides to name. Public beta. Supervised compile model (recipes stay in TeXstudio). Live multi-user editing still on the roadmap (Git today). English-focused proofing for now. Try a low-stakes paper before a hard deadline.

A day in each tool

TeXstudio day. Open yesterday’s file. Hope the TeX install still matches. Tweak a build profile because the journal class wants a weird chain. PDF updates. You are productive if you already know the maze.

Oleafly day. Open the shelf. Pick the paper or the forked resume. Type; auto-compile; SyncTeX even while the PDF is catching up. Broken \cite lights up before the log novel. Checkpoint happened while you made coffee. Optional: ask the agent to try a fix, approve the diff, restore if it lies.

One day is classic studio craft. The other is research-desk automation around the same sources. Pick based on the paper in front of you, not on identity.

Snapshot table

	TeXstudio	Oleafly
Age / maturity	Long track record	Public beta
Price / license	Free (open desktop IDE tradition)	Free forever, AGPL
UI era	Classic dense desktop	Modern workspace (palette, library, themes)
TeX install	You provide TeX Live/MiKTeX	Tectonic ships; packages on demand
Build recipes	Free-form multi-tool strength	Supervised per-project engine
Typst / Markdown	Outside core story	First-class engines
Project library / fork	File-centric	Shelf, fork + full Git lineage
Git	External / manual	Built in, auto-checkpoints, free GitHub
Project intelligence	Solid classic IDE	Multi-file index, macros, LS, structure
Math preview / prose lint	Limited / add-ons	KaTeX live; offline grammar on prose
PDF / SyncTeX	Integrated, proven	Full workspace + stale-tolerant map
AI workspace	No (by design era)	Optional agent, approvals, MCP, Ollama
Citations research tools	Manual / external	Search, paste, import, validator
Diagrams	External or packages	TikZ composer + AI figures
Preflight (ATS / a11y)	No	Yes (heuristic)
Export beyond PDF	Limited / external	DOCX, HTML, MD, PPTX, EPUB, source zip
Templates	User-managed	23 + 99 packs + custom / AI
Live multiplayer	Limited / platform-specific stories	Git today; live on roadmap
Best for	Exotic builds, familiarity, conservatism	Integrated research desk, multi-engine, free depth

Moving without a hard cutover

1. Keep TeXstudio installed.
2. Download Oleafly from the releases page.
3. Import the same tree; compile; see if the editor and library save you time.
4. Leave nightmare recipe documents on TeXstudio. Move the ones that only need a reliable engine and a modern desk.

Closing

TeXstudio aged as a TeX studio. It still earns respect on builds and maturity. It never became an AI-era research workspace, and its UI never pretended to.

If you want the classic IDE and you already own TeX Live, stay. If you want a free modern desk—deep editor, real Git, multi-engine, citations, optional AI, portfolio library—on the same plain files, open one paper and decide after a day. The sources do not care which app is focused.