||6 days ago|
|.github||7 months ago|
|cmake||1 month ago|
|common||1 year ago|
|contrib||5 months ago|
|doc||6 days ago|
|include||6 days ago|
|lib||2 weeks ago|
|src||6 days ago|
|tests||3 months ago|
|.clang-format||7 months ago|
|.clang-tidy||8 months ago|
|.editorconfig||5 years ago|
|.gitignore||12 months ago|
|.gitmodules||3 years ago|
|.valgrind-suppressions||6 years ago|
|CHANGELOG.md||3 weeks ago|
|CMakeLists.txt||2 months ago|
|CONTRIBUTING.md||6 months ago|
|LICENSE||6 years ago|
|README.md||3 months ago|
|SUPPORT.md||7 months ago|
|build.sh||12 months ago|
|version.txt||5 months ago|
A fast and easy-to-use tool for creating status bars.
Polybar aims to help users build beautiful and highly customizable status bars for their desktop environment, without the need of having a black belt in shell scripting.
Table of Contents
- Getting Help
- Getting started
The main purpose of Polybar is to help users create awesome status bars. It has built-in functionality to display information about the most commonly used services. Some of the services included so far:
- Systray icons
- Window title
- Playback controls and status display for MPD using libmpdclient
- ALSA and PulseAudio volume controls
- Workspace and desktop panel for bspwm and i3
- Workspace module for EWMH compliant window managers
- Keyboard layout and indicator status
- CPU and memory load indicator
- Battery display
- Network connection details
- Backlight level
- Date and time label
- Time-based shell script execution
- Command output tailing
- User-defined menu tree
- Inter-process messaging
- And more...
If you find yourself stuck, have a look at our Support page for resources where you can find help.
Read our contributing guidelines for how to get started with contributing to polybar.
Polybar is already available in the package manager for many repositories. We list some of the more prominent ones here. Also click the image on the right to see a more complete list of available polybar packages.
If you are using Debian (bullseye/11/stable) or later, you can install polybar
sudo apt install polybar. Newer releases of polybar are sometimes provided in the backports
repository for stable users, you need to enable backports and then install using
sudo apt -t bullseye-backports install polybar.
If you are using Ubuntu 20.10 (Groovy Gorilla) or later, you can install polybar
sudo apt install polybar.
If you are using Arch Linux, you can install
polybar to get the
latest stable release using
sudo pacman -S polybar. The latest unstable
changes are also available in the
polybar-git package in the
If you are using Manjaro, you can install polybar to get the latest stable release using
sudo pacman -S polybar.
If you are using Void Linux, you can install polybar using
xbps-install -S polybar.
If you are using NixOS, polybar is available in both the stable and unstable channels and can be installed with the command
nix-env -iA nixos.polybar.
If you are using Slackware, polybar is available from the SlackBuilds repository.
If you are using Source Mage GNU/Linux, polybar spell is available in test grimoire and can be installed via
If you are using openSUSE Leap or openSUSE Tumbleweed, polybar is available from the
and can be installed via
zypper install polybar.
The package is available for openSUSE Leap 15.3 and above.
If you are using FreeBSD, polybar can be installed using
pkg install polybar. Make sure you are using the
latest package branch.
If you are using Gentoo, both release and git-master versions are available in the main repository.
If you are using Fedora, you can install polybar using
sudo dnf install polybar.
If you can't find your distro here, you will have to build from source.
Want to get in touch?
- Visit our Discussion page
- Join our Gitter room at
- We have our own subreddit at
- Chat with us in the
#polybarIRC channel on the
- Patrick Ziegler @patrick96
- Michael Carlberg @jaagr
Logo Design by
Polybar accepts donations through open collective.
Become a backer and support polybar!
Polybar is licensed under the MIT license. See LICENSE for more information.
Release archives and tags are signed by a maintainer using GPG. Currently
everything is signed by Patrick Ziegler