Sublime Merge
Git client
Install with Homebrew
brew install --cask sublime-mergeQuick Take: Sublime Merge
August 2026 Sublime Merge (Build 2125) is still among the fastest Git GUIs on Mac: $99 personal / $75 business seat, Apple Silicon native, with LFS locking. Pick it when performance and Sublime Text habits matter. Pick Fork when you want a friendlier native UI for less money.
Best For
- •Sublime Text users wanting a matching Git client
- •Developers working in large repositories who feel GUI lag elsewhere
- •Individuals who prefer one-time licences over Git SaaS seats
What is Sublime Merge? Complete guide for Mac developers in 2026
Sublime Merge is Sublime HQ's cross-platform Git client, built with the same performance focus as Sublime Text. In August 2026 the stable Mac build is 2125 (14 April 2026), adding Git LFS lock/unlock among other fixes, after Build 2121's major load/blame performance work and SHA-256 repository support (December 2025). It remains actively maintained with native Apple Silicon binaries and an unlimited free evaluation that occasionally prompts for a licence. Pricing structure is unchanged: a Personal licence is $99 USD one-time with 3 years of updates (then an optional paid upgrade; licences do not expire for covered builds). Business licences are $75 per user per year. Checkout offers a bundle with Sublime Text. There is no Mac App Store edition. Mac developers who want keyboard-driven, syntax-highlighted diffs still shortlist Merge beside Fork, GitHub Desktop, Sourcetree, and GitKraken. Merge wins on speed and Sublime Text integration; Fork often wins pure GUI friendliness; Sourcetree wins free plus Mercurial. Day to day, Merge feels like Sublime Text applied to Git history: dense UI, keyboard shortcuts everywhere, and diffs that stay readable in large repositories. Build 2121 (December 2025 era) already cut repository load and blame time and added SHA-256 repository support; Build 2125 on 14 April 2026 is the release most binary-heavy teams care about because LFS lock and unlock finally live in the client. The free evaluation is full-featured with no hard time bomb, but a purchase is still required for continued licensed use. One personal key covers all of a user's machines and OSes. If you already bought Sublime Text, checkout still offers a Text+Merge bundle; the products stay separate apps with a shared design language rather than a single merged binary.
Background: Why Sublime Merge stays fast
Merge's speed comes from deliberate architecture choices that favor responsiveness over web-stack convenience. In August 2026 on Mac, confirm the current download build, Apple Silicon support on macOS Tahoe 26.x, and the live pricing page before you renew seats. After each point release, compare release notes with forum reports, especially when macOS privacy prompts change. Install from official DMGs or Homebrew Casks, keep a rollback path, and try Fork or GitHub Desktop on the same weekly workflow before you move licences or team billing. The custom UI toolkit and native Git wrapping are why Merge still shows up in 2026 shortlists even as Electron Git clients add flashier graphs. If your pain is lag on blame and multi-thousand-line diffs, that architecture is the product. If your pain is onboarding juniors who want big buttons and guided flows, Fork or GitHub Desktop may frustrate them less on week one.
Key Features
Line-by-Line and Hunk Staging
Stage individual lines or hunks instead of whole files. Click the gutter beside a line, or drag to select a range, then commit only what belongs together. The diff view color-codes staged vs unstaged changes so debug leftovers and half-finished edits are harder to ship by accident. Developers who care about atomic history often cite this control as the reason they pay for Merge. Staging is visual: color-coded markers show what will land in the next commit versus what stays in the working tree. That matters when a single file mixes a real fix with temporary logging, or when you touched three features before you had time to commit any of them.
Side-by-Side Diffs with Syntax Highlighting
Merge uses the same highlighting engine as Sublime Text across 40+ languages. Side-by-side diffs mark character-level adds and deletes inside a line. Drag hunk boundaries to show more or less context. Strings and keywords keep their colors under your theme, which makes review faster than monochrome patch output. Context expansion is interactive rather than a fixed three lines of patch context. Reviewers who bounce between languages all day get the same highlighting they already trust in Sublime Text, including custom syntaxes loaded from their editor install when available.
Fast Commit Search
Search is effectively instant as you type across commit messages, authors, paths, and file contents. Operators include author:, path:, file:, and contents:, plus boolean logic (and, or, not) and time filters (before:, after:). Finding a six-month-old commit that introduced a specific call becomes a query, not a scroll marathon. Combined queries such as author plus path plus after: date turn archaeology into a filter instead of a scroll. Teams that rotate between monorepos and micro-repos feel the difference immediately when the alternative GUI freezes on blame.
Built-in Merge Conflict Resolution
Conflicts open in a three-way view: base, incoming, and yours. Conflicting blocks are marked; you accept one side or edit the result by hand. Non-conflicting sections merge automatically so attention stays on real conflicts. Resolve, mark files done, and finish the merge without leaving the app or pasting conflict markers into another editor. Anxiety drops because you see base, ours, and theirs without decoding conflict markers by hand. When a release branch is messy, finishing the merge inside one tool beats hopping between terminal, editor, and a separate merge utility.
Commit Editing and History Rewriting
Edit unpushed commit messages, squash commits, or drop them from a visual graph that shows branches and merge points. The edit_commit flow is aimed at fixing typos or author fields before a push. The goal is a readable history on shared remotes without memorizing interactive rebase flags. Keep this for unpushed work. Once commits are public, the same visual tools still help you inspect history, but rewriting shared history remains a team policy decision rather than a Merge feature flag.
Git LFS and Submodule Support
LFS-tracked files show special icons, and you can lock or unlock LFS assets from the UI (lock/unlock landed in Build 2125). Submodules appear in the location bar with status; context menus cover initialize, update, and sync. Double-click opens a submodule in a new tab so multi-repo projects stay navigable. Design and game teams that coordinate PSD, audio, or other binary assets finally get lock/unlock without leaving the client after Build 2125. Submodule tabs keep multi-repo layouts usable when a product repo nests libraries.
Command Palette and Custom Commands
⌘+Shift+P opens a searchable Command Palette for Git operations, matching Sublime Text habits. Shortcuts are customizable. Custom Commands wrap shell scripts (tests, builds, deploys) so they appear in the UI and can bind to keys, turning Merge into a Git-centered control surface for your own tooling. If your team already memorized Sublime Text muscle memory, the palette and key-binding model transfer. Custom Commands are how people bolt on lint, test, or deploy scripts without writing a separate Git GUI plugin.
Git LFS Locking (Build 2125)
Build 2125 (April 2026) adds LFS lock and unlock in the client, which helps game and design teams coordinate binary assets. Together with Build 2121's repository load and blame gains, Merge stays competitive on large repos running on Apple Silicon Macs.
Who Should Use Sublime Merge?
1The Fastidious Git Purist
A senior developer who treats history as documentation stages only the relevant lines from each file so every commit is one logical change. Before push, they squash WIP commits and rewrite messages to conventional-commit style. The cleaned history makes git bisect and later archaeology easier for anyone who inherits the repo.
2The Code Reviewer
A tech lead checks out a teammate's branch and uses search to find commits that touch specific files, then reads side-by-side syntax-highlighted diffs. Blame shows who last touched each line and when. If something looks wrong, they comment in the team's review tool and cherry-pick individual commits to test in isolation.
3The Release Manager
A release manager merges main into a release branch with dozens of conflicting files. The three-way merge tool walks each conflict, shows both sides, and pre-merges clean sections. They verify with the built-in diff view and finish the merge without command-line conflict markers.
How to Install Sublime Merge on Mac
Sublime Merge installs via Homebrew for easy updates, or as a direct download from the official site. The current stable version (Build 2125) requires macOS 10.14 or later and runs natively on Apple Silicon as well as Intel.
Install via Homebrew
Open Terminal and run: brew install --cask sublime-merge. Homebrew places the latest stable build in Applications and handles later upgrades through brew upgrade.
Launch and Initial Setup
Launch Sublime Merge from Applications or Spotlight. The first window shows an empty repository list. Choose Open Repository for an existing Git project, or Clone Repository to fetch a remote.
Configure Git Identity
Merge reads identity from ~/.gitconfig. Confirm user.name and user.email are correct; those values appear on every commit. Verify under Preferences > Edit Settings if a commit shows the wrong author.
Pro Tips
- • From the Command Palette (Cmd+Shift+P), run Open in Terminal to drop a shell at the repository root when you need raw Git or project scripts.
- • Install the smerge CLI helper (symlink or PATH entry) so you can open repositories from the terminal without hunting through Finder.
- • Set open_in_editor so files opened from diffs land in Sublime Text, VS Code, or whichever editor you actually write code in.
Configuration Tips
Customize Your Color Scheme
Merge accepts the same color schemes as Sublime Text. Drop .tmTheme files into ~/Library/Application Support/Sublime Merge/Packages/User/ and pick a theme from the Command Palette (Select Theme). A familiar palette reduces eye strain in long review sessions.
Set Up Auto-Fetch
Add "auto_fetch": true in user preferences so remote refs stay current. Tighten or loosen the fetch interval for busy shared repos versus solo work.
Configure Custom Commands for Your Workflow
Register Custom Commands for test suites, builds, or staging deploys. They show up in the Command Palette and can take keyboard shortcuts so Git and automation live in one place.
Alternatives to Sublime Merge
August 2026 Git GUI buyers comparing Merge usually also install Fork, GitHub Desktop, Sourcetree, and GitKraken. Price, Mercurial needs, and how much hand-holding you want usually decide the shortlist more than raw feature checklists.
Fork
Friendlier native GUI around $49.99. Choose Fork for approachability and a softer learning curve; choose Merge for Sublime-like speed, density, and line-level staging.
GitHub Desktop
Free and simple, especially for GitHub-centric teams. Merge is far stronger for advanced history surgery, blame-heavy archaeology, and large-repo performance.
Sourcetree
Free Atlassian client with Mercurial support. Often slower on big trees; better when Bitbucket or Jira depth matters more than keystroke speed.
GitKraken
Flashy freemium graph with broad integrations. Merge feels lighter on the machine and is one-time for individuals instead of a SaaS seat.
Pricing
August 2026 (sublimehq.com/store/merge): Personal licence $99 USD once, includes 3 years of updates; after that continue using the last covered build forever or buy an upgrade for another 3 years. Business licences $75 per user per year (subscription). Optional bundle with Sublime Text at checkout. Free evaluation with full features and no enforced time limit; purchase required for continued licensed use. One personal key covers all of a user's machines and OSes.
Pros
- ✓Exceptional speed for diffs, blame, and large-repo load in the Build 2121/2125 era.
- ✓Native Apple Silicon builds with first-class macOS integration.
- ✓Personal $99 licence with 3 years of updates, no forced subscription for individuals.
- ✓Syntax-highlighted diffs matching Sublime Text's engine across 40+ languages.
- ✓Build 2125 LFS lock/unlock plus earlier SHA-256 repository support from Build 2121.
- ✓Unlimited free evaluation so you can prove the workflow before paying.
- ✓Command Palette and keyboard-first staging of lines and hunks.
- ✓Same company support surface as Sublime Text, including forum.sublimetext.com.
Cons
- ✗Git only; no Mercurial.
- ✗UI is denser and less hand-holding than Fork or GitHub Desktop.
- ✗Business pricing is a yearly subscription, unlike personal one-time keys.
- ✗After 3 years, new builds need a paid upgrade even though old builds keep working.
- ✗Smaller social and plugin ecosystem than VS Code Git extensions.
Community & Support
Sublime Merge shares community infrastructure with Sublime Text. The official forum at forum.sublimetext.com has Merge-specific sections with experienced users and responsive staff. Sublime HQ publishes feature docs, and the team ships fixes quickly: Build 2125 (April 2026) addressed multiple crashes and added LFS lock support from user reports. There is no dedicated Discord or Reddit only for Merge; the broader Sublime Text community treats it as part of the same toolkit. Support is email-based with detailed replies. Documentation covers staging, search operators, custom commands, and LFS workflows. When something breaks after a macOS update, the forum is usually faster than waiting on a generic ticket queue. People who already live in Sublime Text rarely need a separate onboarding course; the muscle memory transfers, and the remaining learning is Git workflow taste rather than UI chrome.
Frequently Asked Questions about Sublime Merge
About the Author
Expert Tips for Sublime Merge
Licence-upgrade threads on the Sublime forum still confuse newcomers: you are not rented software. You keep the last covered build forever; you only pay again for newer builds after the three-year update window.
For binary-heavy repos, Build 2125's LFS locking is the first Merge release in 2026 many teams force as an update, especially when designers and engineers share asset-heavy repositories.
Related Technologies & Concepts
Related Topics
Git Clients for macOS
Git clients for macOS, including Merge and common rivals.
Developer Productivity Tools
Developer productivity tools that shorten review and commit loops.
Native macOS Applications
Native macOS applications for software teams.
Sources & References
Fact-CheckedLast verified: Aug 9, 2026
Key Verified Facts
- Personal Sublime Merge licences cost $99 with 3 years of updates; business seats are $75/user/year.[cite-1, cite-2]
- Stable Build 2125 released 14 April 2026 with LFS lock/unlock support.[cite-3]
- Personal licences do not expire for builds inside the update window.[cite-2]
- Build 2121 improved repository loading/blame performance and added SHA-256 repository support.[cite-3]
- 1Buy Sublime Merge
Accessed Aug 9, 2026
"Personal $99 with 3 years updates; business $75/user/year; Text bundle option."
- 2Sublime Sales FAQ
Accessed Aug 9, 2026
"Explains non-expiring personal licences and update-window rules; no Mac App Store."
- 3Sublime Merge Download / Changelog
Accessed Aug 9, 2026
"Build 2125 (14 Apr 2026) LFS lock/unlock; prior 2121 performance and SHA-256 notes."
- 4Sublime Merge product site
Accessed Aug 9, 2026
"Product overview for cross-platform Git client by Sublime HQ."
- 5Best Git Clients 2026
Accessed Aug 9, 2026
"2026 GUI landscape context where Merge/Fork-class native clients compete."
- 6Sublime forum licence upgrade discussion
Accessed Aug 9, 2026
"Official clarification that licences cover three years of updates without expiring older builds."
Research queries: Sublime Merge Build 2125 pricing; Sublime Merge LFS lock 2026; Sublime Merge vs Fork