KDE Tiling Extension: Does It Make KDE a WM?

No, a tiling extension does not turn KDE Plasma into a full tiling window manager, but it adds true tiling behavior that can replace most of what a standalone tiling WM does. You still run Plasma’s own window manager (KWin) underneath; the extension simply adds automatic, keyboard-driven tiling layouts on top of it. This article explains what the extension actually does, how it differs from a real tiling WM, and whether it is worth switching to.

What the Extension Actually Does

The most popular KDE tiling extension is Krohnkite, a KWin script that automatically tiles windows as you open them. It uses a set of predefined layouts (e.g., spiral, grid, rows, columns) and lets you switch between them with keyboard shortcuts. Unlike Plasma’s built-in tiling (which only supports a few manual snap zones), Krohnkite continuously reflows all windows as you open, close, or resize them.

It does not replace KWin. KWin remains the window manager; the script merely injects tiling logic into it. This means you keep all of Plasma’s features—desktop widgets, panel, activities, and system settings—while gaining tiling behavior. You are not running a separate WM like i3 or Sway; you are running Plasma with a tiling script.

How It Works: KWin Scripting

KWin has a built-in scripting API that lets you write JavaScript code to manipulate windows. Krohnkite uses this API to listen to window events (open, close, move) and then apply a tiling layout. The script defines a master area (the primary window) and a stack area (the rest). You can cycle through layouts, swap the master window, and resize tiles with shortcuts.

Because it is a script, it runs inside KWin’s process. This means it is fast and stable, but it also means it is limited to what the API allows. For example, you cannot create floating windows that stay above tiles in a complex way (though you can exclude specific windows from tiling). The script is open source and can be installed from the KDE Store or GitHub.

How to Install and Set It Up

Installation is straightforward:

• Download the Krohnkite script from the KDE Store (or GitHub) and save it as a .kwinscript file.
• Open System Settings → Window Management → KWin Scripts.
• Click “Importâ€� and select the file.
• Enable the script and log out and back in (or restart KWin via the command line).

After that, you can configure shortcuts in System Settings → Shortcuts → KWin. Common shortcuts include cycling layouts, toggling tiling on/off, and moving the master window. You can also set per-application rules to exclude certain windows (e.g., keep a dialog floating).

If you prefer a more modern approach, there is also the “Tiling Assistant� built into Plasma 5.25+ which adds manual tiling shortcuts, but it does not auto-tile. For automatic tiling, Krohnkite remains the primary option.

Common Problems and Limitations

Users often report a few issues:

• Some applications (especially games or fullscreen video) may not behave well with auto-tiling; you need to exclude them manually.
• Multi-screen setups can be tricky; the script tiles per-screen, but switching layouts across screens may be inconsistent.
• Wayland support is partial. Krohnkite works on X11 fully, but on Wayland, some features (like certain window state changes) may not work due to API limitations.
• Updating Plasma may break the script if the API changes; you need to wait for the script to be updated.

If you encounter issues, the first step is to check if the script is compatible with your Plasma version. The GitHub repository usually indicates which versions are supported.

How It Compares to a Real Tiling WM

Standalone tiling WMs like i3, Sway, or dwm are minimal and fast. They manage windows entirely with tiling logic, often without a desktop environment. They are highly configurable via text files and are extremely resource-light. However, they lack integrated desktop features—you need to add a bar, a compositor, and a launcher yourself.

KWin with Krohnkite gives you a middle ground. You get tiling, but you also get Plasma’s full desktop. The trade-off is that you are not as minimal or as fast as a bare WM, and the tiling logic is not as flexible (e.g., i3 allows arbitrary splits; Krohnkite uses predefined layouts). For most users, the convenience of having a full desktop outweighs the lack of extreme customizability.

Should You Use It?

If you are a developer or power user who wants tiling without losing Plasma’s features, yes. If you are a minimalist who wants a lean WM, you might prefer i3 or Sway. If you are a beginner, you can start with the built-in Tiling Assistant (manual tiling) and later try Krohnkite for automatic tiling.

Consider your workflow: if you constantly open many windows and need them automatically arranged, Krohnkite is a huge productivity boost. If you only occasionally snap windows, the built-in features may suffice. Also, if you use Wayland, test carefully—some features may be missing.

Frequently Asked Questions

Does Krohnkite work on Wayland? Partially. It works, but some features like certain window state changes may not be available due to Wayland’s security restrictions. For full functionality, use X11.

Will it slow down my system? No, it is a lightweight script that runs in KWin’s process. It has negligible performance impact.

Can I exclude specific windows from tiling? Yes, you can set window rules in System Settings to make certain windows float or not tile.

Is it still maintained? Yes, Krohnkite is actively maintained on GitHub, though updates may lag behind Plasma releases.

Can I use it with other desktop environments? No, it is specifically for KDE Plasma because it relies on KWin’s scripting API.

What is the difference between this and Plasma’s built-in tiling? Plasma’s built-in tiling is manual—you snap windows to edges. Krohnkite automatically tiles all windows as you open them, with dynamic layouts.

Related

• Compare US vs Overseas Manufacturing Costs
• Supermarket Acquisitions: Shopper Impact
• Set Up Visual Studio for Python: Step-by-Step