iTerm2 vs Terminal.app
iTerm2 vs Terminal.app: independent split panes, triggers and a Python API versus the macOS bundled terminal with AppleScript and window groups.
Updated
short verdict
Pick iTerm2 if you work in the shell all day on a Mac and want independent split panes, triggers, shell integration, a Python scripting API or native windows for a separate terminal multiplexer's sessions. Pick Terminal.app if you only need tabs, profiles and AppleScript, want nothing to install, and are fine with a closed-source app. Both are macOS-only.
Both tools are macOS terminal emulators, so the choice is about scope rather than platform. Terminal.app ships with the OS and covers tabs, profiles, window groups and AppleScript. iTerm2 is a GPL-2.0 replacement written in Objective-C that adds independent panes, regex triggers, shell integration, inline images and a Python API.
this page is for
- Mac users deciding whether to leave the bundled terminal
- Developers who run many shells, SSH sessions or remote hosts at once
- Users who want a terminal with no install and no extra configuration
The better pick when you want independent panes, automation and per-host behavior and can install a third-party app.
best for
- All-day shell users on macOS
- Remote work over SSH with per-host profiles
- Scripting the terminal in Python
strengths
- Tabs split into any number of independent panes; inactive panes are dimmed
- Triggers fire regex-matched actions: highlight, run a command, notify or call a Python script
- Profiles switch by hostname, username, directory or running command, such as a red production background
- Sessions run in long-lived server processes, so shells survive an app crash or upgrade
weaknesses
- macOS only, with no Linux or Windows build
- Most configuration lives in the Settings window, not a text file, apart from JSON profile export and Dynamic Profiles
- Ligatures are rendered through CoreText, which the font documentation calls significantly slower
The better pick when you want the terminal already on your Mac and only need tabs, profiles and AppleScript.
best for
- Occasional command-line use
- Machines where you cannot or prefer not to install apps
- Simple AppleScript or defaults-based automation
strengths
- Ships with macOS, so there is nothing to install
- Profiles and window groups export as .terminal property list files
- Window groups save a window and tab arrangement, optionally reopened on launch
- Terminal 2.15 in macOS Tahoe 26 added 24-bit color, Powerline font support and new themes
weaknesses
- Command-D splits show the same session twice, so you cannot run two shells side by side in one window
- No inline image protocol such as Sixel or the kitty graphics protocol
- True color arrived only with macOS 26, and there is no documented text config file
Key differences
- Scope: iTerm2 is a third-party replacement; Terminal.app is the terminal bundled with macOS.
- Splits: iTerm2 panes run separate shells; Terminal.app's Command-D split mirrors one session.
- License: iTerm2 is GPL-2.0 and written in Objective-C; Terminal.app is proprietary and closed source.
- Scripting: iTerm2 has a Python scripting API; Terminal.app is scripted with AppleScript and defaults.
- Config format: iTerm2 exports JSON profiles and reads Dynamic Profiles; Terminal.app uses .terminal plist files.
- Images: iTerm2 shows inline images through imgcat; Terminal.app has no inline image protocol.
Choose iTerm2 when
- You want panes that each run their own shell, with dimmed inactive panes.
- You connect to many hosts and want profiles to switch by hostname or running command.
- You want a system-wide hotkey window or Instant Replay to scrub back through earlier screen states.
- You want to attach a separate terminal multiplexer's sessions as native windows and tabs.
Choose Terminal.app when
- You need only tabs, profiles and window groups and want zero setup.
- You prefer AppleScript or defaults over a Python API for scripting.
- You want a terminal that is always present on any Mac you sit down at.
When not to use these
- You need the same terminal on Linux or Windows, since neither tool has a build for them.
- You need the kitty graphics protocol, which neither tool supports.
FAQ
- Which is faster, iTerm2 or Terminal.app?
- Neither project publishes benchmarks. iTerm2 has a GPU renderer that can be turned off on battery power, and its docs warn that ligatures render through CoreText, which is significantly slower. Terminal.app documents no rendering performance figures.
- Can I use iTerm2 and Terminal.app on the same Mac?
- Yes in practice: both are macOS apps, and iTerm2 is described as a replacement for Terminal.app, not a modification of it. Neither project documents any conflict between them.
- Which is easier to configure?
- Both use a Settings window. Terminal.app has four panes: General, Profiles, Window Groups and Encodings. iTerm2 has far more options, and it also supports JSON profile export and Dynamic Profiles that reload when the file changes.
- Does Terminal.app support true color?
- Only on macOS Tahoe 26, where Terminal 2.15 added 24-bit color. iTerm2's documentation does not state a color-depth limit.