Rank #10 · Weekly · Infra
Hyprland: Independent Dynamic Tiling Wayland Compositor
A fully independent tiling Wayland compositor that stays fast, plugin-friendly, and unapologetically customizable — without sitting on wlroots, kwin, or mutter.
Canonical digest: /daily/hyprland (also on Weekly board).
What it does
Hyprland is a 100% independent, dynamic tiling Wayland compositor that "doesn't sacrifice on its looks." Homepage/wiki: hypr.land. GitHub description matches the README: independent, highly customizable, dynamic tiling.
Highlights from the project README:
- Independent stack — no wlroots, no libweston, no kwin, no mutter.
- Eye-candy + control — gradient borders, blur variants, animations (custom bezier/spring curves), glow, shadows; config reloads on save.
- Window model — tiling / pseudotiling / floating / fullscreen; special workspaces (scratchpads); window groups (tabbed); powerful window/monitor/layer rules; fully dynamic workspaces.
- Layouts — Dwindle, Scrolling, Master, Monocle, custom layouts via Lua, plus plugin layouts; per-workspace layouts.
- Plugins & IPC — built-in plugin manager, powerful plugin support, socket-based IPC, global keybinds passed to chosen apps.
- Input & gaming — native IME and input panels; tearing support for better gaming performance.
- Docs: install / quick start / configure at the Hyprland wiki.
License: BSD-3-Clause. Language: C++.
Who it's for
- Linux desktop users who want a modern Wayland tiling compositor with deep theming and plugin ecosystems.
- Power users migrating from i3/Sway-style workflows who still want animations and visual polish.
- People building desktop environments around Hyprland (bars, lockers, portal stacks) who need stable IPC and a plugin API.
Less ideal if you need a batteries-included GNOME/KDE-style desktop out of the box, or if your hardware/driver stack still struggles with Wayland.
Stars / language / license
40,566 stars · C++ · BSD-3-Clause
Data verified: 2026-11-09 09:19 Asia/Shanghai (GitHub API get_repository + README get_file_contents)
Trending note: +1,465 stars this week (weekly Trending; selection captured 09:10 Asia/Shanghai)
Category tags
Infra · Wayland · compositor · tiling · Linux · desktop · C++ · plugins
How it differs from similar projects
Compared with Sway / wlroots-based compositors. Sway and many others sit on wlroots. Hyprland's pitch is a from-scratch independent compositor with its own plugin and animation story.
Compared with KWin / Mutter. Those ship as part of KDE/GNOME desktop stacks. Hyprland is a standalone compositor you assemble a desktop around.
Compared with niri / other newer tiling Wayland compositors. Different layout philosophies (Hyprland keeps classic dwindle/master-style tiling plus scrolling/monocle/Lua). Choose based on workflow, not star count.
No FPS or battery benchmarks are claimed here. Treat "fast" as project positioning; verify on your hardware.
Hands-on judgment
When Hyprland is a good daily driver. Choose it if you enjoy tiling as a lifestyle and want animations, blur, and a dense plugin/IPC ecosystem without living inside GNOME or KDE. The independent compositor bet matters if you care about Hyprland’s specific layout model (dwindle/master/scrolling/monocle + Lua) and its plugin manager rather than inheriting wlroots defaults. Multi-monitor rules, scratchpads, and per-workspace layouts are where power users feel the upgrade from “Sway with a rice.” Gaming-oriented tearing support is a practical plus for some GPU setups — still verify on your drivers.
When to skip. Skip Hyprland if you need a batteries-included desktop (settings app, enterprise identity, parental controls) — you will assemble portals, bar, launcher, locker, and file manager yourself (or adopt a pre-riced distro spin). Skip if your GPU/legacy apps still misbehave under Wayland and you are not ready to debug. Skip if you want maximum similarity to i3 via Sway’s wlroots compatibility story and do not care about Hyprland’s animation/plugin culture. Skip for locked-down corporate images that only certify GNOME/KDE.
Ops / maintenance cost. Config-as-code is the joy and the chore: live reload is great until a bad bind breaks your session — keep a TTY escape path. Plugins track compositor versions; pin or update deliberately. Screen sharing, fractional scaling, and portal quirks are Wayland-ecosystem issues, not unique to Hyprland, but you own the glue.
Honest boundary. TidyHow has not run FPS, latency, or battery comparisons against Sway, niri, KWin, or Mutter. “Fast” and “eye-candy” are project positioning plus community consensus, not our lab numbers.
Compare vs alternatives
Hyprland vs Sway (wlroots). Sway prioritizes i3 compatibility and wlroots shared infrastructure. Hyprland prioritizes an independent stack, richer animation/theming, and its own plugin story. Pick Sway for i3 muscle memory and wlroots ecosystem proximity; pick Hyprland for the Hyprland layout/UX package. Stability preferences vary by release cadence and your plugin set — measure on your hardware.
Hyprland vs GNOME (Mutter) / KDE (KWin). Full DEs win on integration, accessibility tooling, and corporate familiarity. Hyprland wins on tiling-first workflows and customization depth if you accept DIY desktop assembly. Many users keep a DE install for docking-station days and Hyprland on a personal machine.
Hyprland vs niri (and other newer tilers). niri’s scrolling-strip model is a different spatial philosophy. Hyprland stays closer to classic tiling plus optional scrolling/monocle/Lua layouts. Try both live ISO/VM sessions before migrating dotfiles — workflow fit beats star counts.
Who should not use this
- Users who want GNOME/KDE out of the box with minimal compositor fiddling.
- People stuck on broken Wayland hardware/app stacks who need X11 familiarity more than tiling aesthetics.
- Admins of certified-only desktop fleets (GNOME/KDE only) without an exception process.
- Anyone unwilling to maintain dotfiles, portals, and plugins across upgrades.
- Buyers expecting a vendor support contract for a riceable compositor — this is a community BSD-licensed project.