This site lists the support for the SIXEL graphics format across various terminal emulators. The SIXEL format allows the terminal to display bitmap graphics. See https://en.wikipedia.org/wiki/Sixel for more information. SIXEL support for a terminal can be determined by running the lsix command. If SIXEL is not supported, then the message "Error: Your terminal does not report having sixel graphics support." is displayed.
Table of Contents
Alacritty⌗
Status: Unsupported
Open issue: https://github.com/alacritty/alacritty/issues/910
SIXEL support was rejected by the maintainers.
There is a maintained fork with SIXEL support: https://github.com/ayosec/alacritty
Black Box⌗
Status: Needs Patch
Has an experimental “Sixel Support” switch since version 0.13.0, but the switch only works when VTE is built with SIXEL support.
Relies on upstream VTE support: https://gitlab.gnome.org/GNOME/vte/-/issues/253
Bobcat⌗
Status: Supported
ConEmu⌗
Status: Unsupported
Open issue: https://github.com/Maximus5/ConEmu/issues/807
Contour⌗
Status: Supported
Natively supports SIXEL. SIXEL is available in any version.
ctx terminal⌗
Status: Supported
From commit 1c51989b16e onwards.
Darktile⌗
Status: Supported
From commit 978d506 onwards.
DomTerm⌗
Status: Supported
From version 2.0 (September 2019): https://domterm.org/Features.html.
Eat⌗
Status: Supported
From version 0.9 onwards.
Elementary Terminal⌗
Status: Unsupported
Issue closed as out of scope: https://github.com/elementary/terminal/issues/717
Which references VTE upstream: https://gitlab.gnome.org/GNOME/vte/-/issues/253
foot⌗
Status: Supported
From version 1.2.0: https://codeberg.org/dnkl/foot/releases/tag/1.2.0.
Ghostty⌗
Status: Unsupported
See reasoning here: https://github.com/ghostty-org/ghostty/discussions/2496#discussioncomment-11353475
Ghostty instead provides the Kitty graphics protocol: https://sw.kovidgoyal.net/kitty/graphics-protocol/
GNOME Terminal⌗
Status: Unsupported
Open issue: https://gitlab.gnome.org/GNOME/vte/-/issues/253
GNOME Terminal has an enable-sixel profile setting since version 3.38, but it does nothing because VTE removes SIXEL support from every stable release.
guake⌗
Status: Unsupported
Related PR: https://github.com/Guake/guake/pull/2157
Which references VTE upstream: https://gitlab.gnome.org/GNOME/vte/-/issues/253
iTerm2⌗
Status: Supported
From version 3.3.0: https://iterm2.com/downloads.html.
kitty⌗
Status: Unsupported
See reasoning here: https://github.com/kovidgoyal/kitty/issues/2511#issuecomment-609543803
Kitty instead provides a Terminal Graphics Protocol: https://sw.kovidgoyal.net/kitty/graphics-protocol/
konsole⌗
Status: Supported
Support landed in version 22.04: https://bugs.kde.org/show_bug.cgi?id=391781.
LaTerminal⌗
Status: Supported
Supported since September 2022, uses the SwiftTerm engine.
libtsm⌗
Status: Unsupported
Could not find any SIXEL references in libtsm or its forks. DCS sequences are parsed but not rendered.
MacTerm⌗
Status: Supported
Supported since version 20171210: https://www.macterm.net/updates/changelog-2017.html.
mintty⌗
Status: Supported
From version 2.6.0: https://github.com/mintty/mintty/releases/tag/2.6.0.
mlterm⌗
Status: Supported
Fully supported from version 3.1.9: https://github.com/arakiken/mlterm/blob/deb5aad490f/doc/en/ReleaseNote#L830.
MobaXterm⌗
Status: Unsupported
Could not find any SIXEL references in release notes through version 26.4 (June 2026): https://mobaxterm.mobatek.net/download-home-edition.html
mosh⌗
Status: Unsupported
Issue closed as not planned: https://github.com/mobile-shell/mosh/issues/1081
Neovim⌗
Status: Unsupported
Open issue: https://github.com/neovim/neovim/issues/4500
The vim.ui.img API added in version 0.12 implements only the Kitty graphics protocol. SIXEL is available through third-party plugins.
Ptyxis⌗
Status: Unsupported
Related issue: https://gitlab.gnome.org/chergert/ptyxis/-/issues/122
Which references VTE upstream: https://gitlab.gnome.org/GNOME/vte/-/issues/253
PuTTY⌗
Status: Unsupported
Could not find any SIXEL references in source code, mailing list archives, or the change log through version 0.85 (August 2026).
Rio terminal⌗
Status: Supported
From version 0.1.12: https://rioterm.com/changelog#0112.
SIXEL was broken across the 0.4.x series and restored in version 0.4.12.
Rlogin⌗
Status: Supported
Rlogin Windows
sixel-tmux⌗
Status: Supported
sixel-tmux is a tmux fork that intercepts SIXEL sequences and renders them with the best technique available for the terminal.
Note: tmux now has official support for SIXEL.
suckless st⌗
Status: Needs Patch
Unofficial patch to add support: https://gist.github.com/saitoha/70e0fdf22e3e8f63ce937c7f7da71809
st-flexipatch#30 will provide a simple way to use a current st version with SIXEL support.
st-sx is a maintained st fork with SIXEL support built in.
SwiftTerm⌗
Status: Supported
From release 1.0.4: https://github.com/migueldeicaza/SwiftTerm/commit/3f7bed2243b.
SyncTERM⌗
Status: Supported
From release 1.1.
TeraTerm⌗
Status: Unsupported
Mentioned as feature “which may be supported in very far future” in https://teratermproject.github.io/manual/5/en/about/requests.html.
Terminal.app⌗
Status: Unsupported
Could not find any SIXEL references in documentation.
Terminology⌗
Status: Unsupported
However Terminology has extended escapes which allows one to render images.
termux⌗
Status: Unsupported
Open issue: https://github.com/termux/termux-app/issues/142
Related PR: https://github.com/termux/termux-app/pull/2973
There is a fork of termux which supports it: https://github.com/KitsunedFox/termux-monet
Tilix⌗
Status: Unsupported
Related issue: https://github.com/gnunn1/tilix/issues/1631
Which references VTE upstream: https://gitlab.gnome.org/GNOME/vte/-/issues/253
tmux⌗
Status: Supported
From commit dfbc6b1 onwards.
tmux officially supports SIXEL when compiled with ./configure --enable-sixel.
toyterm⌗
Status: Supported
From commit 692ee23 onwards.
ttyd⌗
Status: Supported
From version 1.7.2: https://github.com/tsl0922/ttyd/releases/tag/1.7.2.
Since version 1.7.3 it must be enabled with -t enableSixel=true.
URxvt⌗
Status: Unsupported
There is an old fork (from 2018) that supports SIXEL: https://github.com/saitoha/rxvt-unicode-sixel
Exoterm is a more up-to-date fork with SIXEL support, among other things: https://github.com/tomas/exoterm
U++⌗
Status: Supported
Visual Studio Code⌗
Status: Supported
Must be enabled with "terminal.integrated.enableImages": true.
Uses xterm.js with xterm-addon-image, related PR: https://github.com/microsoft/vscode/pull/182442
From release 1.80: https://code.visualstudio.com/updates/v1_80#_image-support
Warp⌗
Status: Unsupported
Issue closed as not planned: https://github.com/warpdotdev/Warp/issues/4282
Warp provides the iTerm2 and Kitty graphics protocols instead.
wezterm⌗
Status: Supported
From release 20200620-160318-e00b076c: https://github.com/wez/wezterm/releases/tag/20200620-160318-e00b076c.
Windows Console⌗
Status: Unsupported
SIXEL support was merged into conhost, but it only ships in the OpenConsole bundled with Windows Terminal.
The conhost.exe built into Windows has it only in Insider Canary builds so far.
Windows Terminal⌗
Status: Supported
From version 1.22.10352.0: https://github.com/microsoft/terminal/releases/tag/v1.22.10352.0.
xfce-terminal⌗
Status: Needs Patch
Added a SIXEL option in version 1.1.0, but the option only appears when VTE is built with SIXEL support.
Relies on upstream VTE support: https://gitlab.gnome.org/GNOME/vte/-/issues/253
xterm⌗
Status: Supported
Enabled by default since patch #359.
xterm.js⌗
Status: Supported
Requires https://github.com/jerch/xterm-addon-image
yaft⌗
Status: Supported
Framebuffer terminal
Yakuake⌗
Status: Supported
Depends on SIXEL support in konsole.
Zellij⌗
Status: Supported
From release 0.31.0: https://zellij.dev/news/sixel-search-statusbar/