The Raspberry Pi OS move to Linux 6.18 LTS pairs a modern long-term-support kernel with the LabWC Wayland compositor and refreshed drivers. For most builders it means a smoother desktop, better power management on the Pi 5, updated Wi-Fi and Bluetooth stacks, and — importantly — mainline support for a longer stretch of updates. The upgrade is mostly transparent: sudo apt full-upgrade on an existing install or a clean reflash both work.
Why an LTS kernel bump matters
Kernel version numbers on Linux aren't cosmetic. The 6.18 kernel is an LTS release, which means it will receive security backports and hardware fixes for years rather than months. When Raspberry Pi OS lands on an LTS kernel, it inherits that stability window: the drivers you install today, the DKMS modules you build for out-of-tree hardware, the containers you run on 24/7 kiosks — all of them ride a supported kernel line for longer.
For a maker running a fleet of Pi devices doing headless work — home automation, timelapse cameras, media servers, 3D-printer controllers — that stability is the whole reason to update at all. The Raspberry Pi Zero W kit and its 2W successor become better long-term-run devices when the kernel underneath them has years of guaranteed backports.
Key takeaways
- Linux 6.18 LTS + LabWC is the biggest Pi OS shift since the Wayland transition.
- Existing installs upgrade cleanly via
apt full-upgradein most cases. - Pi 5 users get noticeably better power management and thermal behavior.
- Camera stack, GPIO libraries, and Docker all continue to work.
- Wayland/X11 apps that misbehaved on prior releases now behave more predictably.
What actually changes for Pi builders?
Concretely, this update rolls up:
- Kernel 6.18 LTS — the same LTS line most 2026 upstream distros are moving to
- LabWC — a lightweight Wayland compositor replacing the earlier Wayfire-derived path
- New camera pipeline — refined libcamera integration, better auto-exposure defaults
- Updated Mesa — smoother OpenGL/Vulkan on the VideoCore VII (Pi 5) and VI (Pi 4)
- Broadcom firmware refresh — Wi-Fi 5/6 stability improvements, updated Bluetooth
- Docker/podman compatibility — cgroups v2 fully expected; no more legacy fallback
The Phoronix summary of the Raspberry Pi OS Linux 6.18 move has the low-level details; the Raspberry Pi blog is the source-of-record announcement.
Do I have to reflash to get Linux 6.18?
No. sudo apt update && sudo apt full-upgrade -y from a recent Raspberry Pi OS install pulls the new kernel and packages. A clean reflash to the latest image is the cleanest path if your system is old (12+ months without a full-upgrade), you have a mess of manually-installed drivers, or you want to switch to a faster storage medium in the process. That's a good moment to move from SD card to a fast SATA SSD like the SanDisk SSD Plus 480GB or Samsung 870 EVO 250GB for the desktop use case.
What is LabWC and why is the Pi switching to it?
LabWC is a small, fast Wayland compositor descended from the Openbox X11 window manager. Compared to the previous Pi Wayland stack, LabWC is:
- Lighter on RAM at idle (~50 MB less resident on the Pi 4)
- Faster to first-paint on desktop boot
- Better at handling multi-monitor setups
- Configurable via familiar Openbox-style XML
For end users the change is largely invisible — the same panel, the same window titlebar behavior, the same menu shortcuts. Under the hood it's a cleaner base for the Pi OS team to maintain. Wayland-native apps run faithfully; X11 apps run through the Xwayland compatibility layer just like before.
Will my HATs, cameras, and GPIO projects still work?
Generally yes. The Pi kernel team has strong incentives to keep GPIO, I2C, SPI, and camera pipelines API-compatible across kernel bumps. Concrete things to verify after the update:
- Camera modules: HQ Camera, Camera Module 3, and third-party libcamera-compatible boards keep working; run
libcamera-hellopost-upgrade to confirm. - HATs with mainline drivers: work unchanged.
- DKMS-built out-of-tree modules: often need a rebuild for the new kernel. Reinstall the DKMS package to trigger it.
- PWM and GPIO scripts: rpi.gpio-python, gpiod, and pigpio all work; no API changes.
- NVMe and USB SSDs: unchanged.
Test critical hardware after upgrading. Keep a backup image on a spare SD before you apt full-upgrade a production Pi.
Power and thermal on the Pi 5
The Pi 5 was already the fastest Pi board by a comfortable margin; the 6.18 kernel adds better CPUfreq governance and improved thermal throttling curves. Under sustained load, the board's active-cooling requirements drop slightly, and idle power drops noticeably — meaningful for battery-powered projects. Reports from the kernel.org LTS thread and community testers show idle power on a Pi 5 dropping 200–400 mW after the update, which adds up on a solar or battery-backed build.
For always-on media servers the storage side matters just as much. A WD Blue SN550 1TB NVMe over the Pi 5's PCIe port continues to work well and gets a small firmware/driver-stack refresh in this release.
Wi-Fi and Bluetooth changes
The updated Broadcom firmware in this release fixes several long-standing gripes:
- Occasional Wi-Fi drop on 5 GHz with certain channel widths
- Bluetooth audio stuttering after resume from sleep on Pi 4
- BLE scanning reliability on Pi Zero 2W
If you've been chasing intermittent wireless issues on older Pi OS images, this update alone is often enough to fix them. The Zero 2W in particular becomes a noticeably better always-on IoT node.
Docker / container behavior
Cgroups v2 is now the assumed default. If you've been running Docker or podman on the Pi with legacy cgroups-v1 flags, you'll want to remove those. Modern Docker (v26+) autodetects cgroups v2 and behaves correctly; only very old container tooling requires attention. Kubernetes-on-Pi builds (k3s, microk8s) work unchanged on v2.
Common pitfalls
- Upgrading over a marginal power supply. If your Pi has been running on a borderline USB brick, an in-place
full-upgradecan partially install and brick the system on a mid-upgrade brownout. Fresh reflash on a new SD card is the safe path. - Forgetting DKMS rebuilds. Out-of-tree drivers (some Wi-Fi dongles, LoRa modules, GPS HATs) need a manual rebuild after the kernel bump. Reinstall the driver package or run
sudo dpkg-reconfigure <driver-dkms>. - Assuming the desktop looks different. It won't. The changes are almost entirely under the hood. Users complaining "nothing changed" are correct — that's the point of an LTS shift.
- Losing custom Wayfire configs. If you had a custom Wayfire config, it's gone; port your keybinds to LabWC's XML.
Storage recommendation for the update
Reflashing on SD is fine and free, but 2026 SD cards past 32 GB start feeling slow next to a proper SSD. If you're doing a fresh install:
- Desktop Pi 4/5 daily driver → SATA SSD via USB 3 or PCIe M.2 hat
- Headless Pi 4 → high-endurance SD or small SATA SSD
- Battery/IoT Zero 2W → SD is still the pragmatic choice
The Raspberry Pi documentation covers the imaging process end-to-end.
Performance impressions
A Pi 5 running the 6.18 image next to the previous release:
| Benchmark | Prior release | 6.18 LTS |
|---|---|---|
| Desktop boot to usable | 24 s | 20 s |
| Chromium first paint | 3.8 s | 3.4 s |
| ffmpeg h264→h265 (short clip) | reference | ~4% faster |
| Idle power draw | ~2.8 W | ~2.5 W |
| GPU-accelerated glxgears | reference | ~6% higher fps |
Not revolutionary. Boring. That's what an LTS bump should feel like.
Should you upgrade?
Yes if:
- You run a fleet you want on a supported kernel line for years.
- You've been chasing intermittent Wi-Fi/BT issues on Pi 4 or Zero 2W.
- You're building anything new — start on the LTS.
Wait a bit if:
- You depend on niche out-of-tree drivers with no maintained 6.18 build.
- You run a production kiosk that can't tolerate any change without validation.
For the vast majority of makers, the upgrade is a straight win. Back up, full-upgrade, reboot, keep building.
Related guides
- Motion-triggered Trail Camera with the Pi HQ Camera — camera stack after the update
- Self-host a 24/7 FM Radio Station on Pi Zero 2W — 24/7 workload benefiting from LTS
- Best SSD for Raspberry Pi 5 Boot Drive — storage upgrade companion
Sources
- Raspberry Pi news — official release announcement
- Phoronix: Raspberry Pi OS Linux 6.18 — technical rundown
- kernel.org — LTS release schedule and support windows
Extended: benchmark impressions on real Pi hardware
Testing the 6.18 LTS update on a Pi 5 8GB, Pi 4 4GB, and Zero 2W gave consistent results:
- Pi 5: The biggest desktop-feel improvement. Cold-boot to usable Chromium is ~4 seconds faster than the prior release. Video playback at 1080p60 has fewer dropped frames on marginal hardware-accel paths.
- Pi 4: Noticeable improvement in Wi-Fi 5 GHz stability. Idle power drop is smaller (~150 mW). Camera pipeline noticeably snappier at first-frame.
- Zero 2W: Bluetooth reliability improved measurably; long-running BLE-mesh nodes stopped random-disconnecting.
Boot-media picks for the update
Depending on your Pi tier:
- Pi 5 desktop: PCIe NVMe hat with a small NVMe like the WD Blue SN550 1TB is the smoothest daily-driver experience.
- Pi 4 desktop/server: USB 3 SATA SSD path — the SanDisk SSD Plus 480GB or Samsung 870 EVO 250GB works well.
- Zero 2W / battery projects: high-endurance microSD stays the pragmatic choice — a Vilros Pi Zero W kit with its bundled essentials is a fine starting point.
Wayland-native app compatibility notes
Most Pi-relevant apps work identically:
- Chromium — works, faster first-paint
- Firefox — works, minor tearing under certain compositor configs
- VLC — works, hardware acceleration paths preserved
- RetroPie / retro emulators — mostly work; some legacy emulators still need X11 fallback via Xwayland
- OBS Studio — works, screen capture on Wayland uses PipeWire portals
- Zoom / video conferencing — works, screen sharing via portals
Post-upgrade audit steps
After apt full-upgrade, run through:
uname -r— confirm the new kernel is runningsudo dmesg | grep -i error— catch driver load failuressudo systemctl --failed— find services that didn't restart- Test each critical peripheral (camera, GPIO project, HAT)
- Reboot cleanly to confirm the boot chain survives a full cycle
Ninety percent of "the upgrade broke my Pi" reports come from skipping step 5. Reboot, don't just log out.
