Alacritty is the fastest terminal emulator in existence. Using the GPU for rendering enables optimizations that simply aren't possible without it. Alacritty currently supports macOS, Linux, BSD, and Windows.
Alacritty is a terminal emulator with a strong focus on simplicity and performance. With such a strong focus on performance, included features are carefully considered and you can always expect Alacritty to be blazingly fast. By making sane choices for defaults, Alacritty requires no additional setup. However, it does allow configuration of many aspects of the terminal.
The software is considered to be at a beta level of readiness -- there are a few missing features and bugs to be fixed, but it is already used by many as a daily driver.
Precompiled binaries are available from the GitHub releases page.
- Announcing Alacritty, a GPU-Accelerated Terminal Emulator January 6, 2017
- A short talk about Alacritty at the Rust Meetup January 2017 (starts at 57:00)
- Alacritty Lands Scrollback, Publishes Benchmarks September 17, 2018
- Version 0.3.0 Release Announcement April 07, 2019
Some operating systems already provide binaries for Alacritty, for everyone else the instructions to build Alacritty from source can be found here.
Pop!_OS / Ubuntu
If you're not running Pop!_OS, you'll have to add a third party repository first:add-apt-repository ppa:mmstick76/alacritty
apt install alacritty
pacman -S alacritty
zypper in alacritty
pkg install alacritty
nix-env -iA nixos.alacritty
eopkg install alacritty
Unofficial builds of stable tags can be found in Fedora Copr: pschyska/alacritty.
dnf copr enable pschyska/alacritty dnf install alacritty
If you want to help test pre-releases, you can additionally enable pschyska/alacritty-testing.
brew cask install alacritty
choco install alacritty
scoop bucket add extras scoop install alacritty
Prebuilt binaries for Linux, macOS, and Windows can be downloaded from the GitHub releases page.
To work properly on Windows, Alacritty requires winpty to emulate UNIX's PTY API. The agent is a single binary (
winpty-agent.exe) which must be in the same directory as the Alacritty executable and is available through the GitHub releases page.
On Windows, Alacritty also requires Microsoft's VC++ redistributable to work properly.
Although it's possible the default configuration would work on your system, you'll probably end up wanting to customize it anyhow. There is a default
alacritty.yml at the Git repository root. Alacritty looks for the configuration file at the following paths:
If none of these paths are found then
$XDG_CONFIG_HOME/alacritty/alacritty.yml is created once Alacritty is first run. On most systems this often defaults to
Many configuration options will take effect immediately upon saving changes to the config file. For more information about the config file structure, refer to the default config file.
On Windows the config file is located at:
A full guideline about contributing to Alacritty can be found in the
Issues (known, unknown, feature requests, etc.)
If you run into a problem with Alacritty, please file an issue. If you've got a feature request, feel free to ask about it. Please just keep in mind Alacritty is focused on simplicity and performance, and not all features are in line with that goal.
Before opening a new issue, please check if it has already been reported. There's a chance someone else has already reported it, and you can subscribe to that issue to keep up on the latest developments.
Is it really the fastest terminal emulator?
In the terminals we've benchmarked, Alacritty is either faster or way faster than the others. If you've found a case where this isn't true, please report a bug.
Why isn't feature X implemented?
Alacritty has many great features, but not every feature from every other terminal. This could be for a number of reasons, but sometimes it's just not a good fit for Alacritty. This means you won't find things like tabs or splits (which are best left to a window manager or terminal multiplexer) nor niceties like a GUI config editor.
macOS + tmux + vim is slow! I thought this was supposed to be fast!
This appears to be an issue outside of terminal emulators; either macOS has an IPC performance issue, or either tmux or vim (or both) have a bug. This same issue can be seen in
Terminal.app. I've found that if tmux is running on another machine which is connected to Alacritty via SSH, this issue disappears. Actual throughput and rendering performance are still better in Alacritty.
My arrow keys don't work.
It sounds like you deleted some key bindings from your config file. Please reference the default config file to restore them.
Alacritty discussion can be found in
#alacritty on freenode.
Wayland is used by default on systems that support it. Using XWayland may circumvent Wayland specific issues and can be enabled through:
env WINIT_UNIX_BACKEND=x11 alacritty
Alacritty is released under the Apache License, Version 2.0.