Linux Window Managers: A Deep Dive Into Tiling and Stacking (i3, Sway, Hyprland)

When new users first explore Linux, they are introduced to Desktop Environments (DEs) like GNOME, KDE Plasma, or Cinnamon. These are fantastic, all-in-one packages that provide a desktop, a panel, a file manager, a settings application, and a window manager. They offer a complete, cohesive, and user-friendly experience.

But as you go deeper into the Linux world, you’ll discover a more modular, powerful, and resource-efficient approach. You’ll hear advanced users and programmers talk about “running i3” or “my Hyprland rice.” They are talking about running a Window Manager (WM) instead of a full desktop environment.

This guide to Linux window managers will explore this exciting concept. We’ll cover the crucial difference between stacking and tiling WMs, dive into the most iconic examples like i3, Sway, and Openbox, and see why new projects like Hyprland are changing the game in 2025.

What is a Window Manager vs. a Desktop Environment?

This is the most fundamental concept to grasp.

• A Desktop Environment (DE) is a suite of applications. It bundles everything you need for a graphical experience. The Window Manager (like KWin in Plasma or Mutter in GNOME) is just one part of the DE.
• A Window Manager (WM) has only one job: it controls the placement, appearance, and movement of windows. That’s it.

When you install only a WM, you get a black screen. You are responsible for adding every other component yourself:

• A panel/status bar (like polybar or waybar)
• An application launcher (like rofi or dmenu)
• A notification daemon (like dunst)
• A wallpaper handler (like nitrogen or swaybg)

The result? An incredibly lightweight, fast, and keyboard-driven system that is 100% customized to your exact workflow, with zero bloat.

The Great Divide: Stacking vs. Tiling Window Managers

Window managers are primarily split into two philosophies of “how” they manage windows.

1. Stacking (or Floating) Window Managers

This is the paradigm you already know from Windows, macOS, and most Linux DEs. Windows are “stacked” on top of each other, like papers on a desk. You, the user, are responsible for manually moving, resizing, and arranging them with your mouse.

The Classic Example: Openbox

OPENBOX is the most famous stacking WM. It’s lightweight, stable, and highly configurable (via XML files). For years, it was the default WM in “lightweight” DEs like LXDE. In 2025, Openbox is in maintenance mode—it’s feature-complete and rock-solid for the X11 display server, but no new development is happening. It remains a fantastic choice for a low-resource, mouse-driven system.

2. Tiling Window Managers

This is where the true power for many advanced users lies. A tiling WM automatically arranges your windows for you. When you open a new window, it automatically resizes to take up a portion of the screen, fitting perfectly alongside other windows without any overlap.

Instead of using a mouse to drag windows, you use keyboard shortcuts to “send” a window to a different workspace, swap its position with another, or resize its “tile.” The goal is maximum screen real-estate and a workflow that never requires you to leave the keyboard.

The Big Three: Tiling WMs You Need to Know in 2025

The world of tiling WMs is vast, but it’s currently dominated by a few key players that follow two different display protocols: the classic X11 and the modern Wayland.

1. i3 (The X11 Standard)

i3 is arguably the most popular tiling window manager of all time. It is a manual tiler, meaning windows are organized in a logical tree. You tell it “split this container vertically,” then “split that new container horizontally.” It’s configured via a simple, human-readable plain text file.

Big News for 2025: For years, the most popular version of i3 was a fork called i3-gaps, which (as the name implies) added configurable gaps between windows. As of I3 VERSION 4.22, the i3-gaps fork has been officially merged into the main i3-wm package. You no longer need to install a separate package; “gaps” are now a core feature of i3.

• Pros: Rock-solid stability, simple text-based config, fantastic documentation, and now includes gaps by default.
• Cons: X11-only, which is considered legacy technology by many distributions.

2. Sway (The Wayland Successor)

Sway is the answer to a simple question: “What if we rebuilt i3 for the modern Wayland display server?” It is designed as a drop-in replacement for i3. It uses the same configuration file, the same keybindings, and the same logic. You can often take your existing ~/.config/i3/config file, copy it to ~/.config/sway/config, and it will work with minor changes.

SWAY leverages Wayland to provide a much smoother, tear-free experience, better HiDPI (4K) monitor support, and simpler graphics stack management.

• Pros: All the benefits of i3 but built for the modern Wayland protocol. Excellent multi-monitor support.
• Cons: Does not (and will not) support proprietary NVIDIA drivers (it only works with the open-source nouveau driver). Development intentionally avoids “eye candy” like animations or blur.

3. bspwm (The Modular Powerhouse)

bspwm (Binary Space Partitioning Window Manager) is another major X11 tiler, but with a unique philosophy. Unlike i3, bspwm itself doesn’t handle any keyboard or mouse input. It’s just the rendering engine.

It is controlled by a separate utility, bspc. To handle keybindings, you use a third, separate program: sxhkd (Simple X HotKey Daemon).

This modularity is its greatest strength. You can write complex scripts to control your windows in any language you want and send commands to the bspc socket. It tiles windows by default as leaves on a “full binary tree,” which is a more automatic (but highly predictable) way of partitioning the screen.

• Pros: Extremely modular and scriptable. Its “binary tree” tiling is very intuitive for many.
• Cons: X11-only. The setup is more complex, as you must configure bspwm, bspc, and sxhkd to get a working desktop.

The New Generation: Wayland Compositors with “Bling”

For a long time, using a tiling WM meant giving up visual effects. The community was split: you either had the “suckless” efficiency of dwm or the “eye candy” of a DE like KDE.

In 2025, that is no longer true. A new wave of Wayland compositors (the Wayland term for a WM) has successfully merged both.

The Prime Example: Hyprland

HYPRLAND has taken the community by storm. It is a dynamic Wayland compositor that provides all the efficiency of a tiling workflow but adds the fluid animations, transparency, rounded corners, and Gaussian blur effects you’d expect from macOS or a heavily-modded KDE.

It is configured with its own robust config file and is developing at an incredible pace. It has proven that a “tiling” desktop doesn’t have to be visually static.

• Pros: All the eye candy (animations, blur, shadows) of a modern DE. Tiling-first workflow. Very active development.
• Cons: Still newer and can be less stable than Sway. Some may find the constant addition of new features to be a distraction.

Why Bother? The Payoff

Building a desktop from a window manager is a right of passage for many Linux users. It’s not for everyone—it requires patience, a love for editing config files, and a willingness to read documentation.

But the reward is a system that is blazing fast, uses minimal RAM (often under 200MB at idle), and is so perfectly tailored to your personal workflow that it feels like an extension of your own mind. It’s the ultimate expression of the Linux philosophy: you built it, so you own it.

For a deeper dive into security on your new minimal system, check out our GUIDE TO GPG ENCRYPTION 

💬  Have you tried a tiling window manager? What’s your favorite combo (e.g., bspwm + polybar)? Share your thoughts and builds in the comments below!