Sublime Text

Overview

Sublime Text is a proprietary, cross-platform text editor for code, markup, and prose, developed by Sublime HQ Pty Ltd (Sydney, Australia). It targets developers who want a native, keyboard-driven editor with excellent performance, multi-cursor editing, and deep customizability—without the weight of Electron IDEs or full JetBrains-style language intelligence out of the box. The current product line is Sublime Text 4; the stable channel as of the May 21, 2025 release notes is Build 4200, with ongoing dev-channel builds after that date.

Unlike VS Code, Sublime Text is not open source. You may download and evaluate the full feature set for free with no enforced time limit; continued use requires a paid license under an honor system (periodic purchase reminders). The editor popularized patterns that many tools later copied—notably the command palette, seamless multiple selections, and Goto Anything fuzzy navigation. Companion product Sublime Merge is a separate Git GUI from the same company, often sold as a bundle.

Through 2025–2026, community and press framing is consistent: Sublime is “done” software that still ships regular point builds (performance, syntax, API, platform fixes) rather than racing AI-agent roadmaps. Long-time users praise instant startup, huge-file handling, and a calm UI; newcomers often bounce when they expect free-forever VS Code marketplaces or built-in Copilot-class AI.

Key features

• Native performance — Not Electron. Fast cold start, low idle RAM relative to VS Code-class apps, and strong behavior on multi-megabyte / multi-million-line files. Multi-cursor editing performance was significantly improved (Build 4200 notes usability beyond 100k selections).
• Multiple selections & column select — Select next occurrence (Ctrl/Cmd+D), skip occurrences, split into lines, and rectangular/column selection for simultaneous edits.
• Goto Anything & command palette — Fuzzy open files, symbols, and lines (Ctrl/Cmd+P); command palette for actions and settings without hunting menus.
• Tab multi-select & split views — Select multiple tabs to view side-by-side; works with sidebar, Goto Anything, definitions, and auto-complete definition links.
• Context-aware auto complete — Completions drawn from patterns across the project (not only the current buffer), with kind icons and definition links; language servers via community LSP packages raise this further.
• Syntax engine — Powerful .sublime-syntax definitions with inheritance, branching, embeds; built-in TypeScript/JSX/TSX (since ST4), plus TOML and Zsh shipped in Build 4200; frequent community-contributed rewrites for SQL, Bash, and others.
• GPU rendering — Optional hardware-accelerated UI compositing (default on macOS; configurable via hardware_acceleration) for fluid UI up to high resolutions.
• Projects & workspaces — .sublime-project / workspace JSON for folders, excludes, per-project settings, build systems, and plugin config (including LSP client settings).
• Build systems — JSON (or Python) build targets; Build 4200 adds optional interactive input ("interactive": true). Integrates with external tools, linters, and project scripts.
• Git awareness (lightweight) — Sidebar git status, incremental/mini-diff, and deep integration path to Sublime Merge for full GUI Git workflows.
• Package Control ecosystem — De-facto package manager for themes, syntaxes, linters, Terminus (terminal), and the LSP client family (LSP-typescript, LSP-pyright, etc.).
• Python plugin API — Dual host history: legacy Python 3.3 packages plus modern 3.8; Build 4200 announces phase-out of 3.3 after ~Q1 2026 and a path to newer Python for plugins. Simple plugins are often single .py files.
• Customization — Settings (user/project), keymaps (platform-specific), snippets with scope selectors, macros, themes/color schemes, distraction-free mode, Vintage (Vim) mode package.
• Platform coverage — Windows (incl. portable), macOS (Apple Silicon universal), Linux x64 and ARM64 (deb/rpm/tar/pkg + official repos). Safe Mode and session/hot-exit controls for reliability.
• CLI (subl) — Open files/folders, wait mode, stdin editing—useful in shell workflows and Git editor config.

Pricing

Sublime Text uses a freemium evaluation model: the download is unrestricted in features and has no enforced trial clock. A license is required for continued legitimate use; unlicensed installs show occasional purchase reminders. Personal licenses are a one-time purchase with a multi-year update window—not a monthly editor subscription.

Plan	Price (USD)	What you get
Evaluation	$0	Full editor; no hard time limit; occasional license nags; not a substitute for a purchased key for ongoing use
Personal license	$99 one-time	Per-user key; all machines/OSes where you are primary user; 3 years of updates; after 3 years, upgrade required for newer builds (existing covered builds remain usable)
Personal + Merge bundle	Higher one-time total (Text+Merge)	Optional cart add-on for Sublime Merge; bundled keys accepted by ST4 and Merge (not older ST3)
Business (annual seats)	$65/seat/year (seats 1–10); $60 (11–25); $55 (26–50); $50 (51+)	Subscription always covers current version; seat count = users; company-named keys
Upgrades	Via store upgrade page	Discounted renewals for update windows; community notes Text+Merge upgrades can approach new-license price—budget as multi-year TCO
Education	Not offered	Sales FAQ: no educational discounts; lab licensing uses lesser of computers or students
Refunds	30 days	Email sales for refund within 30 days of purchase

Licensing nuances: One personal key covers all your machines. Personal keys may be used at work when you are the primary user. Business keys belong to the organization. Site licenses and group buying across companies are not offered. Purchase is direct from the Sublime HQ store (card/PayPal); resellers use the online flow rather than classic POs.

Install: sublimetext.com/download (Windows installer/portable, macOS, Linux packages/repos). Dev builds at /dev for early features.

Limits & gotchas

• Proprietary, not FLOSS — Source is closed. You cannot fully audit or fork the core like VS Code/Code-OSS, Zed, or Neovim. Issue tracker and default packages are public on GitHub; the app binary is not.
• Extension graph is smaller — Package Control is mature for syntaxes, themes, and core DX (LSP, Terminus, Git wrappers), but it does not match the VS Code Marketplace’s long tail of niche or vendor-locked tools. Some “must-have” VS Code extensions have no ST equivalent.
• AI is third-party / DIY — No first-party Copilot-class product. Community packages and external tools fill some gaps; AI-first workflows generally fit Cursor, VS Code + Copilot, or JetBrains AI better out of the box.
• Language intelligence is package-assembled — Install LSP + language-specific servers yourself. Quality depends on package maintenance (sublimelsp org and others). Expect more JSON config than VS Code’s one-click language packs.
• Release cadence is calm, not weekly flashy — Point builds land several times a year with deep polish; if you need constant feature churn or marketing releases, ST will feel quiet. That quietness is also why veterans call it “done.”
• Plugin Python migration — Dual 3.3/3.8 hosts have been a long compatibility story. Build 4200 documents phase-out of 3.3 after roughly Q1 2026 and future Python bumps (toward 3.13+), which will force package authors to update and may break abandoned packages. Minimum OS versions will rise with newer Python (e.g., older macOS / Win 7–8.1 drop called out for future builds).
• Update window after 3 years — Personal licenses do not expire for covered builds, but new builds after the window need an upgrade purchase. Upgrades for Text+Merge bundles can feel close to full price—factor TCO before “buy once forever” expectations.
• No education discount / no site license — Students and universities get no special pricing; large lab deals follow seat/computer rules rather than campus-wide site keys.
• Security surface — Treat build systems and packages as code execution. Public issues include CVE-2024-25255 (command injection via New Build System in Sublime Text 4) and historical Mac dylib issues on old ST3 builds. Keep current, review third-party packages, and be careful with untrusted project build configs—same hygiene as any extensible editor.
• Corporate IT friction — Closed source + local plugins can trip security scanners or allowlists that prefer Microsoft-signed VS Code or approved JetBrains channels. Confirm policy before standardizing teams.
• Integrated terminal / remote / containers — Not first-class like VS Code Remote-SSH/Dev Containers. Terminus and SSH-in-terminal workflows work; remote-as-UI architecture is not ST’s design center.

Community sentiment

Sentiment splits cleanly between loyal power users and default-to-VS-Code developers.

On Reddit’s r/SublimeText and Hacker News, recurring praise centers on speed (startup and typing latency), large-file editing, multi-cursor workflows, and a UI that stays out of the way. A January 2025 essay (“Why I still like Sublime Text in 2025”) hit the HN front page with four-figure upvotes; a Sublime developer replied thanking the community—evidence the product is maintained, not abandoned. Users describe ST as finished software: fewer surprises, fewer Electron freezes, fewer AI upsell surfaces.

Complaints are equally consistent: $99 feels high next to free VS Code (especially for students—no edu pricing); upgrade pricing for Text+Merge can approach a new license; Package Control’s long tail and abandoned packages lag VS Code; AI and remote-dev stories are weaker; some teams simply standardize on free tooling to avoid procurement. Migration threads (Rails, web, competitive programming) often keep ST for quick edits or huge logs while moving day-to-day IDE work to VS Code or JetBrains.

Package Control remains the social hub for extensions (trending themes, Terminus, LSP-*). The official forum and Discord handle support; GitHub sublimehq/sublime_text is the public issue tracker for the closed-source app.

Who should use it

• Performance-sensitive editors — People who open multi-MB JSON/logs/SQL dumps and hate editor freezes.
• Multi-cursor power users — Refactors and data wrangling via many carets rather than only structural IDE renames.
• Polyglot / scripting / web / config work — Where LSP + good syntax highlighting + builds cover 90% of needs without a heavy IDE.
• Writers and note-takers who want distraction-free mode and plain-text speed (some users write all prose in ST).
• Developers willing to pay once for a calm proprietary tool and to configure packages deliberately.
• Sublime Merge fans — Same UX philosophy across edit + Git GUI.

Who should skip it: teams that need free-at-scale tooling and Microsoft’s extension/AI ecosystem; developers whose primary value is remote containers, Live Share, or notebooks; buyers who refuse proprietary licenses; AI-agent-first workflows (Cursor/Copilot/Claude Code class).

Alternatives

• Visual Studio Code — Free, largest marketplace, remote/devcontainers, optional Copilot; heavier Electron runtime.
• Zed — Native, collaborative, open-source-leaning speed competitor; younger extension story than ST/VS Code.
• JetBrains IDEs — Deep language intelligence, refactorings, debuggers; higher seat cost and heavier UI.
• Cursor — AI-first fork of the VS Code lineage when agents and chat are the product.
• Warp — Not a full editor replacement, but modern terminal workflows that pair with lightweight editors.
• Neovim / Helix / TextMate — Modal or macOS-native alternatives; different learning curves and plugin models (no Package Control parity).
• Notepad++ — Free Windows-centric editor for lighter needs.

Verdict

Sublime Text remains one of the best “classic” code editors money can buy if you value native speed, multi-cursor editing, and a stable, low-drama product. In 2025–2026 it is not the default for most developers—that title belongs to free VS Code—and it is not an AI IDE. It is a polished proprietary editor with an honest evaluation model, a $99 personal license (3 years of updates), tiered business seats, and a package ecosystem that is excellent for core editing and solid for LSP-driven coding when you invest in setup.

Choose Sublime Text when Electron jank or AI chrome bothers you, large files matter, and you will actually pay for software you use daily. Choose something else when free+AI+remote is non-negotiable or your org standardizes on JetBrains/VS Code. For many veterans, ST is still the calm daily driver—and Build 4200-era work (sidebar options, multi-cursor performance, syntax rewrites, plugin-host modernization) shows the product is maintained, not museum software.