WezTerm is a GPU-accelerated terminal emulator and multiplexer written in Rust, with its official site at wezterm.org and source at wezterm/wezterm on GitHub. It runs on Linux, macOS, Windows, FreeBSD, and NetBSD, multiplexes tabs, panes, and windows locally and over SSH, and is configured through a Lua file with hot reload. The project ships prebuilt automated, release, and nightly builds and is published under the MIT License.[1][2]
Quick verdict
WezTerm is a strong pick for developers who want one GPU-accelerated terminal with built-in multiplexing, Lua configuration, and SSH domains across Linux, macOS, and Windows. Its Lua-file setup and self-supported MIT-licensed model suit hands-on terminal users more than teams needing managed support.[1][2][3]
Capabilities
WezTerm multiplexes tabs, panes, windows, and workspaces and can attach to remote shells over SSH and TLS encrypted channels as well as the local system.[1]
Everything is configured in Lua, and the config file is watched and reloaded while the terminal runs, with an explicit reload path for changes that need it.[1][2]
Text rendering covers ligatures, color emoji, true color, dynamic color schemes, hyperlinks, and a searchable scrollback buffer.[1]
Inline images work through the iTerm2, Kitty, and Sixel graphics protocols, with imgcat support for piping images into the terminal.[1]
Good fit
Developers who live in a terminal and want built-in tabs, panes, and splits without running a separate multiplexer.[1][2]
People who work across Linux, macOS, and Windows and want one terminal with the same Lua configuration on each machine.[1][2]
Users who regularly SSH into remote shells and want persistent-feeling multiplexed sessions over encrypted channels.[1]
Limitations
Configuration is code in Lua rather than a settings screen, so users who want graphical preferences have to learn the config-file workflow.[1]
GPU acceleration and prebuilt binaries cover the mainstream desktop platforms, but FreeBSD, NetBSD, and unusual setups lean on source builds that need more setup effort.[1][2]
There is no managed cloud edition or commercial support agreement documented, so teams that need an SLA have to self-support through the public issue tracker.[1][2]
Community
Community sample is limited to the public GitHub issue tracker venue observed during intake; no individual experience reports were sampled.
1 cited community source. Does not represent broader user sentiment; no Reddit or G2 reports were reviewed, so no user-experience claims are made in this draft.
Development happens in the open at wezterm/wezterm on GitHub, with public release channels, changelogs, and nightly builds that show ongoing 2026 maintenance.[1]
No third-party community sentiment was sampled for this draft assessment, so user-experience claims beyond the documented behavior are left out until attributed reports are reviewed.[1]
Compatibility
Runs on Linux, macOS, Windows 10/11, FreeBSD, and NetBSD, with installs through Homebrew, Winget, Scoop, Chocolatey, Snap, Flatpak/Flathub, an apt repository, AppImage, and source builds.[1]
Documents iTerm2-compatible image protocol support, which keeps image-display workflows portable for people moving from iTerm2 on macOS.[1]
Published under the MIT License with binaries and source available at no charge, so there is no license cost or platform lock to evaluate.[1][2]
Questions worth asking
Which platforms does WezTerm support?
Can WezTerm replace a terminal multiplexer?
Yes. WezTerm multiplexes tabs, panes, and windows, and can attach to remote shells over SSH and TLS encrypted channels in addition to the local system.[1]
Do config changes need a restart?
Yes. WezTerm watches its Lua configuration file and applies changes while it runs, so most edits take effect without restarting, with an explicit reload option for the rest.[1]
Sources and editorial review
Source research. Reviewed on October 13, 2026. Written by Sanjib Sah. AI assisted; reviewed by a human editor.
We have not run or tested this product.
Community sample is limited to the public GitHub issue tracker venue observed during intake; no individual experience reports were sampled. Does not represent broader user sentiment; no Reddit or G2 reports were reviewed, so no user-experience claims are made in this draft.
- WezTerm official homepage
official · Observed October 13, 2026
Homepage presents WezTerm as a powerful cross-platform terminal emulator and multiplexer written in Rust, linking features, docs, the GitHub repo, and release channels.
- WezTerm GitHub repository
official · Observed October 13, 2026
Repo wezterm/wezterm describes a GPU-accelerated cross-platform terminal emulator and multiplexer in Rust, with release channels and a link back to wezterm.org.
- WezTerm features documentation
official · Observed October 13, 2026
Documents five supported platforms, multiplexing, SSH/TLS domains, ligatures, emoji, true color, dynamic schemes, hyperlinks, searchable scrollback, and iTerm2/Kitty/Sixel image display.
- WezTerm license text
official · Observed October 13, 2026
Carries the MIT License naming Wez Furlong as copyright holder with the standard permission grant.
- WezTerm installation instructions
official · Observed October 13, 2026
Offers prebuilt automated builds plus source builds, with Homebrew, Winget, Scoop, Chocolatey, Snap, Flatpak/Flathub, apt, and AppImage installs.
- WezTerm configuration reference
official · Observed October 13, 2026
Documents the Lua config file location, watching and automatic reload, and the window, font, color, key, and mouse option sections.
- WezTerm public issue tracker
community · Observed October 13, 2026
Public issue tracker listed as the community venue; only tracker-level presence observed during this intake, no individual user reports sampled or quoted.
Compared with these products
No explicit proprietary baseline is recorded.