Hyprland

On this page 7

Hyprland is a dynamic tiling Wayland compositor for the Linux desktop that arranges windows automatically in non-overlapping tiles while adding smooth animations, rounded corners, blur and other visual effects. It combines the roles of display server, window manager and compositor in one program, which is how every Wayland session works.

Hyprland belongs to the same family as Sway and i3, but it trades their minimalism for eye candy and extensive runtime configurability. It is written in C++, configured through a plain text file that reloads instantly, and controlled at runtime through the hyprctl command and IPC sockets.

How Hyprland manages windows on Wayland

Under Wayland, the compositor is the display server: it receives client buffers, composites them into frames and sends them to the screen through the kernel’s DRM and KMS interfaces. Hyprland implements this role and also decides where each window goes, how input is routed and how workspaces behave.

Early versions were built on the wlroots library, which Sway also uses. Over 2024, the project replaced wlroots with its own Aquamarine backend and related libraries, giving the developers direct control over rendering, input and output handling.

Windows are placed by a layout engine. Hyprland ships two built-in layouts, and the user can switch between them per workspace or globally.

LayoutPlacement ruleBest suited for
DwindleEach new window splits the focused area in a binary treeGeneral use with many windows
MasterOne main window plus a stack of secondary windowsCoding or writing with references
Floating windowsFree position set by rules or the mouseDialogs, pickers and media players
Plugin layoutsScrolling or grid placement from extensionsWide monitors and special workflows
Built-in Hyprland layouts

Configuration, rules and runtime control

Hyprland is configured through a single text file, usually ~/.config/hypr/hyprland.conf, that can source other files. Changes are applied as soon as the file is saved, without restarting the session, which makes experimentation fast but also lets a typo break keybindings immediately.

The configuration covers monitors, input devices, keybindings, animations and window rules that match windows by class or title. The table below lists the most important configuration areas.

Keyword or sectionControlsExample purpose
monitorResolution, refresh rate, position, scaleRun a laptop panel at 1.25 scale
bindKeyboard and mouse shortcutsOpen a terminal with Super and Enter
windowrulePer-application behaviorFloat a calculator, pin a video window
animationsCurves and speeds of transitionsShorten workspace slide animations
decorationRounding, blur, shadows, opacityReduce blur to save GPU time
exec-oncePrograms started with the sessionLaunch a bar and a notification daemon
Main configuration areas

At runtime, the hyprctl utility queries and changes the compositor state, for example listing clients or setting a keyword temporarily. Scripts can also subscribe to an event socket to react when windows open, workspaces change or monitors connect.

Hyprland compared with other Linux desktops

Hyprland is a compositor, not a full desktop environment. GNOME and KDE Plasma ship panels, settings applications, file managers and session services, whereas Hyprland users assemble those parts themselves from separate projects.

OptionTypeDisplay protocolMain trade-off
HyprlandDynamic tiling compositorWaylandRich effects, more maintenance
SwayTiling compositorWaylandStable and i3 compatible, few effects
i3Tiling window managerX11Mature and light, no native Wayland
GNOMEFull desktop environmentWayland or X11Integrated, limited tiling
KDE PlasmaFull desktop environmentWayland or X11Feature-rich, basic tiling only
Hyprland and related Linux desktop options

Applications that only speak X11 run through XWayland, which Hyprland starts on demand. Most programs work well this way, although X11 clients may appear blurry when fractional scaling is active unless the user disables XWayland scaling.

Building a working Hyprland session

A usable Hyprland session needs several companion components, because the compositor deliberately leaves them out. The project maintains its own utilities, such as hyprpaper, hyprlock and hypridle, and many users combine them with community tools.

NeedCommon choicePurpose
Status barWaybarWorkspaces, clock, battery, tray
Application launcherWofi, Rofi or FuzzelStart programs from the keyboard
WallpaperhyprpaperSet backgrounds per monitor
Screen lock and idlehyprlock and hypridleLock and dim after inactivity
Screen sharingxdg-desktop-portal-hyprlandShare screens in browsers and calls
NotificationsMako or DunstShow desktop notifications
Typical companion components

Most users start Hyprland from a display manager such as SDDM or GDM, or from a TTY login. The xdg-desktop-portal-hyprland package matters more than beginners expect: without it, screen sharing in video calls and some file dialogs fail.

Limitations and common problems

Hyprland develops quickly and with frequent breaking changes, so configuration keywords can be renamed between releases. Users on rolling distributions such as Arch Linux get new features early but should read release notes before upgrading.

  • NVIDIA graphics: support improved greatly with recent proprietary drivers and explicit synchronization, but older driver versions can still cause flicker.
  • Higher GPU load: blur, shadows and animations cost power, so laptop users often reduce or disable them on battery.
  • No graphical settings: almost everything is edited as text, which suits experienced users but slows newcomers.
  • Plugin breakage: plugins compile against specific Hyprland versions and may stop loading after an update.

In simple terms

Hyprland is the part of a Linux computer that draws windows on the screen and decides where they go. Instead of letting windows pile on top of each other, it arranges them side by side automatically, like tiles on a wall, and adds smooth motion when they move.

It is aimed at people who like to customize their computer through a text file and use the keyboard more than the mouse. The reward is a fast, attractive and personal desktop; the cost is time spent setting it up.

A practical example

A backend developer working on a laptop with a 27-inch external monitor installs Hyprland on Arch Linux. The laptop panel runs at 1.5 scale and 60 Hz, while the external monitor runs at 1.0 scale and 144 Hz, both defined in two monitor lines of the configuration file.

The developer uses the master layout on the external screen, keeping the code editor as the large main window and two terminals in the stack, and binds Super with number keys to ten workspaces. A window rule floats the password manager and centers it, and Waybar shows workspaces and battery level.

On battery, a short script run through hyprctl disables blur and shortens animations. The result is a keyboard-driven workspace where switching between editor, logs and browser takes one keystroke, with roughly an hour of extra battery life compared with full effects.