davatorium/rofi: A Window Switcher, Launcher and dmenu Replacement
Rofi: A window switcher, application launcher and dmenu replacement
At a glance
- What is it?
- Rofi is a C-based popup selector for X11 and Wayland that covers window switching, application launching and dmenu-style input. It is powerful, theme-driven and not a UI toolkit, and its Wayland backend still has gaps.
- Who is it for?
- Adopt rofi if you run an EWMH-compatible X11 window manager or a wlr-family Wayland compositor and you want one binary for launching, switching and piping script output. Do not adopt it if you need a library, a UI toolkit, or full window-mode support on KWin, and do not expect the dmenu compatibility to be the whole product.
- Can I use it commercially?
- Check first. The repository uses a licence we do not classify automatically, so read its LICENSE file before any commercial use.
- Is it still maintained?
- Yes. The repository last received commits 1 day ago.
- What is it written in?
- Mainly C, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- davatorium/rofi16,542 ★ · +139
| Repository | 2026-09-21 | 2026-11-15 |
|---|---|---|
| davatorium/rofi | 16.4k | 16.5k |
139 Stars in the last 55 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
What rofi replaces, and for whom
Rofi presents a textual list of options in a popup and lets you pick one or more. The README describes three jobs: running an application, selecting a window, or selecting from options provided by an external script. That single interaction model is why the project has outlived its origin. It began as a clone of simpleswitcher, written by Sean Pringle, and the README credits him with most of the credit for the foundation. It was renamed because it lost the simple property.
The audience is narrow on purpose. Rofi is for people who already run a keyboard-driven desktop and want one selector they can point at different data sources. The built-in modes cover run (applications from $PATH), drun (XDG desktop files), window (EWMH-compatible window managers), ssh, filebrowser, keys, script and combi. The README is explicit about what it is not: not a UI toolkit, not a library for other applications, and not an application that supports every possible use case. That last point matters. The project positions itself as generic enough for everybody, with specific behaviour added through scripts or plugins.
How the mode and matching pipeline works
Every mode is a source of rows. The run mode reads $PATH, drun reads desktop files and tries to follow the XDG standard, window mode asks an EWMH-compatible window manager for its window list, ssh connects to a remote host via ssh, filebrowser walks the filesystem. Combi merges several of these into one list, which is the clearest sign that modes are interchangeable inputs rather than separate programs.
Filtering is the part users feel most. The README lists tokenized filtering (type any word in any order), case-insensitive or SmartCase matching, and support for fuzzy, regex, prefix and glob matching. Optional sorting includes Levenshtein distance or fzf-like ordering, and history-based ordering can put the last 25 choices on top. Rendering is Cairo drawing with Pango font rendering, with UTF-8 collating, international keyboard support and RTL language support. Configuration and theming are separate concerns: CONFIG.md and the themes/ directory exist alongside the manpages, and the README points at the locally installed manpages as the more up-to-date source. That is a real caveat. The README itself says other sections and links might be out of date.
Installing rofi and a first dmenu-style use
The README's installation section points at INSTALL.md and the locally installed manpages. Distribution packages are the normal route on Linux and BSD, which the README says rofi is known to work on. The build system is Meson. Wayland support is enabled by default along with X11/xcb, and the README gives these two options for building with one backend disabled:
# Wayland only:
meson setup build-wayland -Dxcb=disabled
# Or X11 only, in a separate build directory:
meson setup build-x11 -Dwayland=disabledAt least one backend should be enabled, so disabling both is not a supported configuration. Once installed, the dmenu replacement path is the simplest real use: rofi reads candidates from standard input and writes the selection to standard output, which is what makes it usable inside shell pipelines and window manager scripts. The Examples/ directory contains scripts such as i3_switch_workspaces.sh and i3_empty_workspace.sh that glue rofi into an i3 configuration. If you are on Wayland and want to force the X11 path instead, the README documents the -x11 flag:
rofi -x11 -show drunThat flag only works if the xcb backend was enabled at build time, so check your package before relying on it.
Wayland works, but not identically
The README states that Wayland support has been official since 2025, after lbonn added it in a fork and maintained it for years. Rofi should select the xcb or wayland backend automatically based on the environment it runs in. The catch is that the README lists features that are difficult or impossible to replicate in Wayland mode: the -normal-window flag, -monitor -n for fine-grained monitor selection, fake transparency, and window mode on KWin, which implements different protocols than the wlr family. Offset parameters work only partially, with x-offset and y-offset applying from screen edges rather than absolutely.
DPI handling is the more interesting design consequence. On Wayland the output is only known after the first surface is shown, so sizing rofi windows in absolute millimetres is difficult. The README calls this a problem unique to rofi because the actual DPI is unknown beforehand. The documented workaround is to pass DPI through configuration: if the dpi option is 0 and only one monitor is connected, rofi uses that monitor's DPI, and with multiple monitors you can specify a monitor name to inherit its DPI. That is a workaround, not a fix, and it is the kind of detail worth reading before you file a bug.
Where rofi is the wrong tool
The README's own list is the best starting point. Rofi is not a UI toolkit and not a library, so if you wanted to embed a fuzzy selector inside your own application, this is not that project. It is also not just a dmenu replacement; the README says dmenu functionality is a nice extra rather than the main purpose. Teams that adopt rofi purely for dmenu compatibility are using the smaller half of the tool and inheriting the larger dependency surface.
The second limitation is window management coverage. Window mode depends on EWMH compatibility, with workarounds documented for i3 and bspwm, and on Wayland it targets the wlr family. KWin is called out as not working for window mode because it implements different protocols. If your compositor is outside those groups, window switching is the feature you lose first.
Third, the documentation is versioned for a reason. The README opens by asking you to match documentation and scripts to the version of rofi in use, and links branches for 2.0.0 back through 1.7.0. If you copy a theme or script from the next branch onto a 1.7.x package, the mismatch is yours to debug.
Rofi against dmenu, and against a desktop launcher
The honest comparison is with dmenu, because rofi is a drop-in replacement for it. Both read a list and return a selection. Dmenu stays close to that single job. Rofi adds tokenized filtering, fuzzy, regex, prefix and glob matching, optional Levenshtein or fzf-like sorting, history ordering, UTF-8 and RTL handling, Cairo and Pango rendering, and a theming system. The cost is a larger program with more configuration surface, and a Wayland backend whose feature set differs from the X11 one.
The other comparison is with whatever launcher your desktop already ships. A GNOME or KDE launcher is integrated with that desktop's search providers and settings. Rofi is not integrated with anything by default; it reads $PATH, desktop files, EWMH window lists and the filesystem, and everything else is a script. That is the trade: less integration out of the box, more control over what appears in the list.
Maintenance, licence and upgrade cost
The repository is not archived, and the last push was on 2026-10-31. The most recent release is 2.0.0, published on 2025-09-01, after a 2.0.0-beta1 on 2025-08-16, with 1.7.9.1 before that on 2025-06-02. The default branch is next, which is also the branch the README links for the next version. Practically, that means the branch you read on GitHub is not necessarily what your distribution packaged.
The licence is recorded as NOASSERTION in the repository metadata, and the repository contains a COPYING file. This is not legal advice: read COPYING and the package metadata your distribution ships before you redistribute rofi or bundle it into an image.
Upgrade cost is dominated by two things. The 2.0.0 line is a major version, and the README's version-matching warning exists precisely because configuration and scripts drift between releases. Second, Wayland support became official in 2025, so older packages may be built without it. Check which backend your build enables before you plan around Wayland behaviour.
Editorial conclusion
Adopt rofi if you run an EWMH-compatible X11 window manager or a wlr-family Wayland compositor and you want one binary for launching, switching and piping script output. Do not adopt it if you need a library, a UI toolkit, or full window-mode support on KWin, and do not expect the dmenu compatibility to be the whole product. Before installing, check whether your distribution ships 2.0.0 or an older 1.7.x package, and confirm whether that build has the xcb or wayland backend enabled, because the two are not feature-identical.
Frequently asked questions
What is rofi in Linux?
Rofi is a window switcher, application launcher and dmenu replacement that shows a textual list of options where one or more can be selected. It is written in C, runs on Linux and BSD, and its built-in modes include run, drun, window, ssh, filebrowser, keys, script and combi.
What are the key differences between rofi and dmenu?
Rofi is a drop-in dmenu replacement with added improvements, but the README says the dmenu functionality is a nice extra rather than rofi's main purpose. Beyond selection, rofi adds tokenized, fuzzy, regex, prefix and glob matching, optional Levenshtein or fzf-like sorting, history ordering, and Cairo and Pango rendering.
Where can I find the rofi configuration file?
The repository contains CONFIG.md, a config/ directory and a themes/ directory, and the README points to the locally installed manpages as the more up-to-date source for configuration details. The README also warns that other sections and links might be out of date.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/davatorium-rofi)Star history chart for your README
[](https://hysenlabs.com/projects/davatorium-rofi)Was this useful?