I went looking for the best VR headset for Linux this month, and the answer moved twice while I was writing it down. On 14 October Valve said the Index is no longer being produced and put the leftover stock on clearance, two days after Pimax announced that its Pimax Play software is getting a Linux client. Neither change helps you much today. What does work is a standalone headset streaming from your PC through WiVRn, or a lighthouse-tracked headset on a kernel that’s been patched for it.
So this is a short list: the Meta Quest 3 and 3S, the Bigscreen Beyond 2e, the Steam Frame, and why I’d hold off on a cheap Index or any current Pimax. I ran WiVRn 26.9, ALVR and Monado in October 2026 on an Arch Linux VM in my lab with no GPU and no headset attached, and every install step, port and error below comes from that box.
Picking a VR headset for Linux in one table
If you only read one section, read this one. Prices are the US listings and vendor prices I could confirm by 28 October 2026, and they move every week before the holidays, so treat them as bands and check the live price before you order.
| Award | Headset | Why it wins on Linux | Approx. price |
|---|---|---|---|
| Best overall | Meta Quest 3 (512GB) | WiVRn, ALVR and Steam Link all support it, pancake lenses, wireless or USB | About $600, check on Amazon |
| Best value | Meta Quest 3S (128GB) | Same chip and Linux support as the Quest 3 for much less | About $350, check on Amazon |
| Best wired headset | Bigscreen Beyond 2e | Micro-OLED at 107 g, runs on Monado and SteamVR with a patched kernel | $1,159 direct, plus base stations and controllers |
| Worth waiting for | Valve Steam Frame | Runs SteamOS itself and streams from Linux SteamVR | $1,059 or $1,299, waitlist only |
Nothing from Pimax is on that table, and the reason is simple: none of its current headsets work on Linux yet. That section is further down, next to the Index.
Testing what I could without a headset
I did not have these headsets on my face for this piece, and I will not pretend otherwise with frame times or comfort scores I never measured. What I could test is the PC side, which is the part that decides whether a headset works on Linux at all. WiVRn, ALVR and Monado run on your desktop, and the headset is only a display and a set of sensors at the other end of them.
My lab box was an Arch Linux VM on kernel 7.2 called box1, close enough to CachyOS that the packages and the AUR behave the same way. On it I did four things:
- Installed WiVRn from Flathub and ran its server
- Pulled the ALVR streamer tarball from GitHub and launched it
- Built Monado from the AUR and started its service with nothing plugged in
- Opened the firewall ports and watched what each one listened on
Everything else is checked against a source rather than my memory. Specs come from Meta’s, Valve’s, Bigscreen’s and Pimax’s own pages, and prices from Amazon and the vendor stores. The support rating for each headset comes from the Linux VR Adventures hardware table, which is where people who own the hardware report what really works. When that table and a vendor disagree, I went with the table.
Comparing the shortlist side by side
The column that matters most is the last one: how the headset reaches a Linux PC. A standalone headset only needs your network and an encoder on your GPU, while a wired PC headset needs the kernel, the compositor and the GPU driver to cooperate on a DRM lease for its display.
| Headset | Per-eye resolution | Refresh | Tracking | How it reaches Linux |
|---|---|---|---|---|
| Meta Quest 3 | 2064 x 2208, pancake | 72/90/120 Hz | Inside-out | WiVRn or ALVR over Wi-Fi or USB, or Steam Link |
| Meta Quest 3S | 1832 x 1920, Fresnel | 72/90/120 Hz | Inside-out | WiVRn or ALVR over Wi-Fi or USB, or Steam Link |
| Bigscreen Beyond 2e | 2560 x 2560 micro-OLED | 75/90 Hz | SteamVR base stations | DisplayPort, Monado or SteamVR, patched kernel |
| Valve Steam Frame | 2160 x 2160 LCD | 72 to 144 Hz | Inside-out | Steam Link from SteamVR over the bundled Wi-Fi 6E adapter |
| Valve Index (clearance) | 1440 x 1600 LCD | Up to 144 Hz | SteamVR base stations | DisplayPort, Monado or SteamVR |
Read the table with your GPU in mind. A wired headset on an AMD card is the best case Linux offers right now, while the same headset on NVIDIA works with more latency, and the GPU section near the end explains why.
1. Meta Quest 3
The Quest 3 is the headset I’d tell most Linux gamers to buy, and it is not because of anything Meta did for Linux. It wins because every open streaming stack supports it: WiVRn, ALVR and Valve’s own Steam Link all list it, and the Linux VR community treats standalone headsets like this one as its best-supported class.
The pancake lenses are the reason to pay more than the 3S, since they stay sharp further from the centre and Meta quotes a 110 by 96 degree field of view. Inside sits a Snapdragon XR2 Gen 2 with 8 GB of RAM, but on Linux that chip mostly decodes the video stream your PC sends it. The headset weighs 515 g, adjusts IPD continuously from 53 to 75 mm, and runs at 72, 90 or 120 Hz.
What changed for Linux in September is the cable. WiVRn 26.9 added a native USB mode on Meta headsets that needs no adb and no developer mode, so a wired session no longer means signing up as a Meta developer. You install the WiVRn client from the Horizon Store, and its version has to match the server on your PC, so update both together.
Is there a catch? You still need a Meta account to set the headset up, and the experience depends on your Wi-Fi as much as your GPU. Here’s who should and shouldn’t buy it:
- Buy it if you want one headset for SteamVR games and standalone apps
- Buy it if your router sits in the room you play in
- Skip it if a Meta account is a dealbreaker
- Look at the Beyond instead for OLED blacks in sim racing
The 512GB model listed at about $600 on Amazon when I checked, and a Batman bundle was a little cheaper. Check the live Quest 3 price on Amazon.
2. Meta Quest 3S
The Quest 3S is the cheapest way into VR on Linux that I’d actually recommend, because it shares the Quest 3’s chip, RAM and Linux support. WiVRn and ALVR don’t care which of the two you own, so the money you save is pure optics and comfort.
Those optics are where it gives ground. The 3S uses Fresnel lenses at 1832 by 1920 per eye with a 96 by 90 degree field of view, and its IPD only moves between three fixed positions. If your eyes fall between two of them, you’ll notice it more than any resolution number. Meta rates the battery at about 2.5 hours, so plan long sessions around a cable or a battery strap.
I’d buy the 128GB model. Storage only holds standalone apps, and a PC VR library lives on your Linux machine anyway, so the 256GB bundle is worth it only if you’ll play a lot without the PC. Skip the 3S if you wear glasses with a wide IPD or plan long sessions in text-heavy apps, where the Quest 3’s lenses earn their price.
It sat at about $350 for 128GB and about $450 for the 256GB Gorilla Tag bundle. Watch for listings marked Renewed, which share the product name. Check the live Quest 3S price on Amazon.
3. Bigscreen Beyond 2e
The Beyond 2e is the wired headset I’d pick for Linux, and it’s the only one on this list that still needs kernel work. It’s rated Gold on the Linux VR hardware table, with both Monado and SteamVR supported, which means it works well once the patches are in, and CachyOS and Bazzite already ship kernels with them.
On paper it’s the opposite of a Quest. It weighs 107 g because it has no battery, no cameras for tracking and no processor to run apps, and it gives you 2560 by 2560 micro-OLED per eye at 75 or 90 Hz across a 116 degree diagonal. The 2e adds eye tracking for $200 over the plain Beyond 2, and its eye cameras need either a firmware workaround or one more kernel patch on Linux.
Those patches are the honest cost. On AMD the community wiki lists a bigscreen-beyond-kernel.patch for kernel 7.3 and newer, a separate one for 7.1 and 7.2, and a display stream compression fix. On NVIDIA you need the open kernel modules from driver 580 on, with a DSC patch. If you run CachyOS, its kernel carries them already, but not the 2e’s eye-tracking camera fix, which still means a custom kernel or a firmware flash through Bigscreen’s Windows utility. The CachyOS kernel manager is where you’d switch to a patched kernel, and uname -r confirms which one you booted.
The box holds only the headset. Tracking uses SteamVR 1.0 or 2.0 base stations and SteamVR controllers, and with the Index discontinued those are getting harder to find new. That decides who it suits:
- Buy it if you already own base stations and Index controllers
- Buy it for sim racing or flight sims on an AMD card
- Skip it if you’d be buying lighthouse gear from scratch
- Skip it if you can’t run a patched kernel
Bigscreen cut the price in September to $959 for the Beyond 2 and $1,159 for the 2e, sold only from its own store with no Amazon listing for the headset. Check the current price on Bigscreen’s store.
4. Valve Steam Frame
The Steam Frame is the headset I’d wait for if you aren’t in a hurry, because it’s the only headset here that runs a desktop Linux distro, SteamOS, as its own operating system. It runs SteamOS on a Snapdragon 8 Gen 3 with 16 GB of RAM, and it streams PC games from SteamVR through a Wi-Fi 6E adapter that ships in the box.
Valve lists 2160 by 2160 LCD panels per eye at 72 to 144 Hz, with 144 Hz marked experimental, and a 21.6 Wh battery. Ars Technica’s review measured it at 440 g with the strap and got about 1.5 hours in performance mode. It costs $1,059 with 256 GB or $1,299 with 1 TB, and the power supply isn’t included.
So why isn’t it the top pick? You can’t buy one today. Valve’s store page only offers a waitlist, and the first units went to people who won the reservation draw in September. Linux streaming also is not finished: the open SteamVR for Linux tracker has a report of Steam Frame stream resets with the Vulkan encoder on both NVIDIA and AMD. Neither WiVRn nor ALVR lists the Frame as a supported headset yet, so Steam Link is the only path I can point you to. If you want to play this Christmas, buy a Quest now.
Deciding whether a discounted Valve Index still makes sense
A Valve Index makes sense in late 2026 only if you already own base stations and controllers and want a spare or replacement headset. On 14 October Valve said the Index is no longer being produced and dropped the remaining stock by 20%, so the headset alone was $399.20 on Steam when I checked, while supplies last. The $999 full kit isn’t offered any more.
That is frustrating, because the Index is the best-supported wired headset Linux has. The community table rates it Platinum, with both Monado and SteamVR supported, and Monado drives it through the same lighthouse driver that covers the Vive and the Beyond. Valve also says existing owners keep SteamVR support, so an Index you already have isn’t going dark.
The trouble is the rest of the kit. A headset without base stations and controllers tracks nothing, and once Valve’s stock runs out you’ll be buying those used. Amazon’s Index listings were used or renewed sellers when I checked, so I haven’t linked one. If you don’t own the lighthouse gear, a Quest 3 does more for less money.
Leaving Pimax and the others off the list
Pimax makes some of the sharpest PC headsets you can buy, and none of its current ones work on Linux. The community table rates the Crystal, Crystal Light, Crystal Super, Dream Air and Dream Air SE as Borked on both Monado and SteamVR, because nobody has reverse engineered their protocols. Only the older 5K and 8K family runs, on a work-in-progress Monado fork with kernel patches.
Pimax’s 12 October announcement doesn’t change that yet. As GamingOnLinux reported, Pimax says Pimax Play is coming to Linux as a dedicated client that’s in development now, with no date, alongside a new Crystal Pro at $1,399 that has no ship date either. I’d treat that as a reason to check back next year, not to spend $1,000 on a Crystal Light today. The others I left out had smaller problems:
- HTC Vive Focus Vision: WiVRn supports it, but the wired bundle runs about $1,450
- Pico 4 Ultra: works with WiVRn, no US retail listing
- PlayStation VR2: Gold through a SteamVR driver, Bronze on Monado
- Vive XR Elite: only third-party Amazon listings
The PSVR2 deserves a second look later. Its Monado driver has 6DoF head tracking and eye tracking but no tracking for the Sense controllers and no passthrough, which rules it out for most games today.
Setting up WiVRn on Arch and CachyOS
WiVRn is not in the official Arch repos; it’s on Flathub and in the AUR as wivrn-server, both at version 26.9 when I checked. I used the Flatpak because it bundles xrizer and OpenComposite, the two layers that let SteamVR games talk to an OpenXR runtime. WiVRn’s README prefers native packages, though: the Flatpak may not support Lighthouse-tracked devices or forwarding the headset’s gamepad and keyboard input, so pick the AUR wivrn-dashboard package if you need either. Fedora packages it in its main repos, so the steps after the install are the same there.
WiVRn finds your headset over mDNS, so it needs Avahi. Install Flatpak and Avahi, then enable the daemon:
sudo pacman -S --needed flatpak avahi
sudo systemctl enable --now avahi-daemonThen add Flathub and install the server, which pulls the KDE runtime with it:
sudo flatpak remote-add --if-not-exists flathub https://dl.flathub.org/repo/flathub.flatpakrepo
sudo flatpak install -y flathub io.github.wivrn.wivrnCheck what landed before you pair anything, because the client you install on the headset has to match this version:
flatpak info io.github.wivrn.wivrnMine reported 26.9, and the last commit message shows the bundled xrizer moving to 0.6:
WiVRn server - Play your PC VR games on a standalone headset
ID: io.github.wivrn.wivrn
Ref: app/io.github.wivrn.wivrn/x86_64/stable
Arch: x86_64
Branch: stable
Version: 26.9
License: GPL-3.0-or-later
Origin: flathub
Collection: org.flathub.Stable
Installation: system
Installed Size: 31.5 MB
Runtime: org.kde.Platform/x86_64/6.10
Sdk: org.kde.Sdk/x86_64/6.10
Commit: 61d58e18b177b19a34f4a0f3063c571bfc7585ef8a3145327a5beb8b5e268332
Parent: a64079b50118e8cd5f97fb9ae7ddbb9e2207d9b1aa1ed4e1b79d9dd86ecab98c
Subject: Update xrizer to 0.6 (489a935f743b)
Date: 2026-10-09 21:45:03 +0000On a desktop you’d normally start the WiVRn dashboard from your app menu. My VM had no display, so I ran the server binary from the Flatpak directly:
flatpak run --command=wivrn-server io.github.wivrn.wivrnMy first attempt failed, because I’d installed Avahi without starting it. The second run, after systemctl enable --now avahi-daemon, printed a pairing PIN and published the service:
Two lines in that output are worth copying somewhere. The PIN is what you type on the headset the first time it connects, and the long PRESSURE_VESSEL_IMPORT_OPENXR_1_RUNTIMES=1 string is the launch option you paste into a Steam game’s properties so it finds WiVRn instead of SteamVR.
Error: “Cannot create avahi client: Daemon not running”
The server exits with code 4 and this message when the avahi package is installed but avahi-daemon isn’t running. Installing the package doesn’t start the service on Arch, so enable it with sudo systemctl enable --now avahi-daemon and run the server again. The headset discovers the PC through that daemon, so a firewall that drops UDP 5353 gives you the same empty server list even with Avahi running.
Open the WiVRn ports
With the server running, it listened on TCP 9757 and nothing else of its own:
ss -tulnpThe *:9757 line is WiVRn, and the 5353 sockets are Avahi:
Netid State Recv-Q Send-Q Local Address:Port Peer Address:PortProcess
udp UNCONN 0 0 0.0.0.0:5353 0.0.0.0:*
udp UNCONN 0 0 0.0.0.0:5353 0.0.0.0:*
udp UNCONN 0 0 0.0.0.0:5355 0.0.0.0:*
udp UNCONN 0 0 127.0.0.54:53 0.0.0.0:*
udp UNCONN 0 0 127.0.0.53%lo:53 0.0.0.0:*
udp UNCONN 0 0 [::]:5353 [::]:*
udp UNCONN 0 0 [::]:5353 [::]:*
udp UNCONN 0 0 [::]:5355 [::]:*
tcp LISTEN 0 4096 127.0.0.53%lo:53 0.0.0.0:*
tcp LISTEN 0 4096 127.0.0.54:53 0.0.0.0:*
tcp LISTEN 0 128 0.0.0.0:22 0.0.0.0:*
tcp LISTEN 0 4096 0.0.0.0:5355 0.0.0.0:*
tcp LISTEN 0 128 [::]:22 [::]:*
tcp LISTEN 0 1 *:9757 *:* users:(("wivrn-server",pid=4874,fd=10))
tcp LISTEN 0 4096 [::]:5355 [::]:* WiVRn’s docs list UDP 9757 as well, even though my server showed only TCP with no headset connected, so allow both along with mDNS. These are the ufw rules I added on box1, where I’d installed and enabled ufw; on a stock Arch install with no firewall you can skip them. If you’re enabling ufw for the first time over SSH, run sudo ufw allow ssh before sudo ufw enable, or you won’t be able to SSH back in:
sudo ufw allow 9757/tcp
sudo ufw allow 9757/udp
sudo ufw allow 5353/udp
sudo ufw statusThe status should list all three rules for IPv4 and IPv6:
Status: active
To Action From
-- ------ ----
9757/tcp ALLOW Anywhere
9757/udp ALLOW Anywhere
5353/udp ALLOW Anywhere
9757/tcp (v6) ALLOW Anywhere (v6)
9757/udp (v6) ALLOW Anywhere (v6)
5353/udp (v6) ALLOW Anywhere (v6) If ufw status says inactive instead, ufw is installed but not enabled, and these rules only take effect after sudo ufw enable. On Arch, also run sudo systemctl enable --now ufw so the rules load again at boot.
Choosing between WiVRn, ALVR, Monado and SteamVR
Which stack you run follows from the headset. A standalone headset streams, so you pick WiVRn or ALVR; a wired headset needs a runtime that drives its display, so you pick Monado or SteamVR. Having run all three on box1 and read their release notes, this is how I’d choose:
- Quest or Pico standalone: WiVRn first
- Standalone, but you live in SteamVR’s menus: ALVR
- Index, Vive or Beyond on AMD: Monado, through Envision
- Anything, if you want Valve’s path: SteamVR, with patience
WiVRn leads because it doesn’t need SteamVR at all. It’s an OpenXR runtime built on Monado, so native OpenXR games talk to it directly and SteamVR titles go through xrizer. Its encoder order is Vulkan video first, then NVENC on NVIDIA or VAAPI on AMD and Intel, then x264 on the CPU, and the 26.9 release says Vulkan encoding should now work well on NVIDIA.
ALVR is older and SteamVR-only. Its latest stable release is still 20.14.1 from July 2025, with 2026 work happening in nightlies, and its own Linux troubleshooting page warns that SteamVR shows a black screen unless you set the vrmonitor.sh %command% launch option. The tarball also showed me what a missing library looks like:
./bin/alvr_dashboard: error while loading shared libraries: libva.so.2: cannot open shared object file: No such file or directoryInstalling libva fixed that one, and the dashboard then stopped because box1 has no Wayland or X display, which on a real desktop you won’t hit. ALVR wants TCP and UDP 9943 and 9944 open, and the tarball ships firewalld and ufw files for exactly those ports under libexec/alvr.
Monado was the one that took real effort. It isn’t in the official repos, and the AUR monado 25.1.0 package won’t build on a clean box as it stands, because pacman can’t resolve five of its dependencies (cnmatrix, librealsense, libsurvive, libuvc and openhmd) that only exist in the AUR themselves.
I got it built by turning those optional drivers off, but that is not something I would ask a gamer to do. Envision exists for this reason: it builds Monado and an OpenVR layer from a profile and runs them for you, and it’s what the Linux VR community points new wired-headset owners to. When I started monado-service with nothing plugged in, it fell back to a simulated HMD and then crashed for lack of a display, which is the expected end on a headless VM.
SteamVR is improving, slowly. Valve’s 2.17 release in September added better wired headset support on Linux that previously needed third-party layers, 2.17.10 fixed two AMD crashes and 2.18 fixed async reprojection failing on AMD GPUs. The community wiki still calls the Linux build buggy, though, and I’d only rely on it where Monado can’t help.
Matching your GPU to the headset
An AMD Radeon on the open RADV driver is the safest card for VR on Linux, and it matters most with a wired headset. The community GPU table rates RDNA cards on RADV as excellent with the strongest reprojection, while NVIDIA cards on the open modules from driver 565 are acceptable, with only partial reprojection and noticeable latency in wired mode. GTX 10-series and older can’t get the DRM lease an Index needs at all.
Streaming is kinder to NVIDIA, because WiVRn and ALVR mostly lean on the video encoder. That’s why a Quest is my default for an NVIDIA owner and a Beyond is a much easier call on Radeon. Before you pick a stack, check these on your own machine:
- RADV, not AMDVLK, as your Vulkan driver on AMD
- Open NVIDIA kernel modules, driver 565 or newer
- KDE Plasma or GNOME 47 or newer for a DRM lease on Wayland
- Your router on 5 GHz or 6 GHz, close to where you play
If you’re still on X11, read up on the Plasma move to Wayland first, because Wayland is where the desktops are putting their DRM lease work now, and GNOME only gained it in version 47. Fedora users can lean on the same Steam setup from our Fedora gaming guide, and a fresh CachyOS install plus its post-install checklist covers the GPU drivers before any of this.
What I still don’t know
A few things I couldn’t settle from a lab without a headset, and I’d rather list them than guess:
- Whether WiVRn will ever run on the Steam Frame
- When Pimax Play for Linux ships, and for which headsets
- Which mainline kernel will make the Beyond patch-free
- How long new Index controllers stay in stock
The Steam Frame question is the one that could reorder this list. A headset that runs Linux itself and streams over its own radio is the obvious Linux pick on paper, and if Valve opens it up to WiVRn or fixes the encoder resets in SteamVR, it moves to the top. Until then I’d buy a Quest 3, put WiVRn on the PC, and spend the difference on a Radeon if the card in your machine is the weak link.
