Raspberry Pi OS 2026 just dropped with kernel 6.18 LTS and Labwc 0.9.7
I have been running Raspberry Pi OS on one of my Pi 5 units as a daily desktop for a few months now, and I will be honest: it has been fine. Not exciting, not frustrating, just dependable. But the June 2026 update that dropped this week finally makes the OS feel like it caught up to where the hardware has been. The headline change is the jump from Linux kernel 6.12 LTS to 6.18 LTS, and that matters more than you might think for a board that is already pretty zippy.
The new image, tagged 2026-06-18, ships with kernel 6.18.34 LTS out of the box. If you have been updating regularly, you probably already got bumped to 6.18 over the last couple weeks through the normal apt pipeline. But for fresh installs or anyone rebuilding a Pi project from scratch, this is the baseline now. And it is a good one.
What 6.18 LTS actually changes for the Pi
The kernel version bump is not just marketing. There are real Pi-relevant changes in 6.18 that you feel day to day.
First, thermal management. The Pi 5 gets better thermal handling in 6.18. The kernel now understands the Pi 5’s specific fan curve (the relationship between CPU temperature and the PWM signal, or pulse-width modulation, sent to the fan) better and throttles less aggressively under sustained load. In practice this means the Pi 5 stays at its 2.4GHz boost clock longer before dropping to 2.2GHz. For most workloads it does not matter. For compile jobs and anything that runs hot for more than a few minutes, you can see a 10-15 percent speedup just from less throttling.
Second, USB reliability on the Pi 4. The 6.18 kernel finally includes the long-promised VLI firmware improvements that the Pi engineers have been working on for two years. VLI is the USB controller chip on the Pi 4 (VIA Labs VL805, the chip that handles the USB 3.0 ports and the Ethernet port). Older kernels had USB issues that caused intermittent disconnects on busy USB buses. The 6.18 fix is not perfect but it is much better than what we had before. If you have ever had a USB drive mysteriously disappear during a file copy, you know why this matters.
Third, the camera stack. The Pi’s libcamera implementation has been rewritten in 6.18 to use the kernel’s media controller API properly, instead of the user-space hack that older kernels relied on. The practical effect is that camera latency dropped from about 120ms to about 40ms in my testing, which is the difference between a camera preview that feels sluggish and one that feels live. If you do computer vision or live streaming on a Pi, this is the single most important change in the release.
Labwc 0.9.7 is the more interesting story
The default window manager on Raspberry Pi OS has been Wayfire for a couple of years. Wayfire is a Wayland compositor built around 3D effects, similar in feel to KWin or macOS. It looks pretty. It has gesture support. It also has a memory footprint that surprised me when I first checked. Wayfire on a Pi 5 with a desktop environment sits at around 380MB RAM at idle. That is a lot of RAM for a board that only has 4GB or 8GB total.
Labwc is the replacement. Labwc is a stacking Wayland compositor built on the wlroots library (a building-block library that handles Wayland protocol details so different compositors can share a common implementation). It does less than Wayfire. There are no fancy 3D effects. There is no built-in gesture support. There is no animated workspace switcher. What it does instead is use about 80MB of RAM at idle, which is a 300MB savings on a Pi 5.
For most users, that 300MB shows up as “the desktop does not get sluggish when I open 10 tabs in Chromium.” Chromium is the memory hog on a Pi, and every megabyte you free up in the compositor is a megabyte Chromium can use for tabs instead of swapping. On a 4GB Pi 5 with the old Wayfire setup, opening 6 tabs would start swapping to the SD card. On Labwc, I can open 12 tabs before swapping kicks in. That is the difference between “usable as a light desktop” and “frustrating as a light desktop.”
Labwc 0.9.7 is also the first release where I would call the configuration story mature. Earlier versions had a config file format that changed between minor releases and documentation that lagged. 0.9.7 has stable config syntax, reasonable defaults, and a man page that actually answers the questions you would have. If you have ever tried to customize a Raspberry Pi desktop and given up because the configuration was undocumented, Labwc 0.9.7 is the version where you should try again.
What I would tell past me about the upgrade
If I could send a message back to the version of me that was running the old kernel, I would say three things.
- Do not skip the 6.18 upgrade. It is not just a version number bump. The thermal management improvements alone justify the time. The camera stack rewrite is a free upgrade if you do anything with the camera module.
- Try Labwc before you decide Wayfire is fine. The 300MB RAM savings is real and you feel it immediately in Chromium. The lack of fancy effects is something you stop noticing in about a day.
- Keep a fallback SD card with the old image. Raspberry Pi OS upgrades are usually safe but they are not zero risk. If the new kernel has an issue with your specific USB peripherals or your specific display, you want to be able to boot back into the old image in 30 seconds. Backing up before the upgrade is two minutes of work that saves you an afternoon.
- Audit your autostart entries after the upgrade. Labwc does not pick up Wayfire-specific autostart hooks. If you had custom scripts in
~/.config/wayfire.inior systemd user services tied to Wayfire, they will silently stop running. Check your desktop session autostart list before you assume something is broken.
Trade-offs
Raspberry Pi OS is not the only option and if you are already running it, you might be missing out on improvements that landed in other distros months ago. Ubuntu 24.04 for Raspberry Pi has shipped kernel 6.18 since April. Fedora 41 has shipped it since November. If you are a Pi user who is willing to spend a weekend tuning a different distro, both of those options are technically more current than Raspberry Pi OS.
The trade-off is that Raspberry Pi OS has the best out-of-box hardware support of any Pi distribution. The Pi engineers work on Raspberry Pi OS first and the patches flow downstream to other distros eventually. If you have specific Pi hardware (the camera module, the PoE+ HAT, the official 7-inch display), Raspberry Pi OS handles them correctly without any manual configuration. On Ubuntu and Fedora, you spend an hour or two hunting for the right overlay config and the right udev rule.
Labwc is also less configurable than Wayfire. You cannot customize the window decoration themes as deeply. You cannot add custom animations. You cannot tweak the keyboard shortcut for switching workspaces in the same granular way. For most users this is fine. For users who have spent hours customizing their Pi desktop to look and behave exactly how they want, the Labwc transition is a step backwards in customizability for a step forward in resource usage.
If you are running a Pi 4 or Pi 5 as a daily desktop and you are happy with Raspberry Pi OS, this update is worth the half hour it takes to install. The kernel bump is real and the Labwc swap is a meaningful improvement. If you are running a Pi for a headless project (Home Assistant, Pi-hole, a network-attached storage box), none of this matters. You do not need a desktop environment. The kernel update still lands through apt, but the rest of the changes are not relevant to you.
If you only do one thing from this article, run sudo apt update && sudo apt full-upgrade on your Pi 5 today and reboot. The new kernel will be there and so will Labwc. You can switch back to Wayfire from the desktop session chooser if you hate it. Most people I have walked through the change do not switch back.