Linux Support
Linux is a first-class support target across the HyperSpin ecosystem. The current alpha is for x64 PCs and Steam Deck.
Alpha targets: Bazzite, Steam Deck running SteamOS Desktop Mode, and Ubuntu Desktop. Full desktop and device testing is still in progress. Compatibility is not yet confirmed on every target. Expect bugs.
This guide defines setup requirements and platform differences. The release requirements define acceptance. A listed build target does not establish a tested release.
Start here
We recommend Bazzite for a quick start. Use your preferred Linux distribution with matching runtime requirements. Follow Ubuntu, Bazzite, and SteamOS Setup for distribution-specific steps.
- Read Install and Maintain.
- Review Games, Controls, and Displays for your desktop and hardware.
- Check the release description for tested distributions, architectures, package formats, and desktop sessions.
- Complete one game launch, pause, resume, and exit before importing your full library.
For a cabinet opening directly into the frontend, follow Fullscreen and Cabinet Startup. Dedicated graphical startup provides a kiosk-style session. Headless operation means running without a local display.
System requirements
| Requirement | What you need |
|---|---|
| Operating system | Bazzite, SteamOS Desktop Mode on Steam Deck, or Ubuntu Desktop as alpha targets; compatibility testing is ongoing |
| Processor | x64 for this alpha, including Steam Deck. Match every app, native helper, and plugin. arm64 build targets do not establish arm64 alpha support. |
| Desktop | A working graphical session. Record X11 or Wayland and the desktop version. Gaming Mode requires separate testing. |
| Graphics | A working GPU driver and accelerated rendering for HyperSpin and HyperTheme. Test your display resolution and theme workload. |
| Storage | A writable HyperSpin folder, space for media and extraction, and an executable filesystem for apps and plugins |
| Accounts and network | Your HyperSpin account and internet access for sign-in, downloads, publishing, and connected services |
| Games | Linux emulator builds or a configured compatibility runtime for each selected platform |
| Controls and sound | Devices recognized by Linux, user access to required devices, and a working audio output |
Release owners must publish minimum distribution, runtime, GPU, RAM, and storage requirements from testing. These docs do not assign unmeasured minimums or claim every Linux distribution is supported.
Ecosystem coverage
| Component | Linux scope | Release evidence required |
|---|---|---|
| HyperHQ | Setup, library management, imports, media, accounts, profiles, settings, updates, backups, and game lifecycle | Installed package and full setup-to-game workflow |
| HyperSpin | Wheel navigation, themes, search, favorites, profiles, video, game launch, and return to the frontend | Packaged rendering, controls, playback, and recovery |
| HyperOverlay | Loading, extraction progress, pause menu, manuals, saves, disc changes, and restart where the platform supports each action | Real game processes, input focus, and audio restoration |
| HyperMarquee | Game artwork and video on a separate display | Display selection, scaling, reconnect, and fullscreen behavior |
| HyperTheme and ThemeBuilder | Browser editing, uploads, PSD import, fonts, audio, preview, export, and publishing | Linux browser and GPU checks plus playback in HyperSpin |
| Plugins and HyperspinCore Essentials | Platform-specific executables, shared APIs, native helpers, installation, and repair | Linux runtime packages and end-to-end plugin communication |
| HyperLED and cabinet integrations | Supported USB and network hardware, profiles, game events, and device recovery | Per-device Linux testing. HyperLED's development status does not establish release availability. |
| HyperCapture | Server-side theme recording, page audio, encoding, upload, and project attachment | Target Linux GPU server and full queued recording flow |
| HyperAuth, HyperAI API, HyperList, and connected services | Browser sign-in, callbacks, catalogs, ratings, metadata, media, and account access from Linux clients | Live client-to-service checks with the release versions |
| HyperSpin Docs and plugin templates | Linux setup steps, runnable examples, and portable links | Documentation build and Linux execution of published examples |
Apply the same requirements to additional ecosystem plugins and services before advertising Linux support. Server hosting requirements are separate from desktop requirements. A Linux user does not need to host the APIs or HyperCapture.
Platform differences
| Windows workflow | Linux workflow |
|---|---|
| Windows installer and Start menu | Linux setup and desktop application menu |
| Drive letters and Windows paths | Absolute Linux paths with exact filename case |
| Windows startup entries | XDG desktop login entries. Steam Gaming Mode has a separate launch flow. |
.exe and .dll emulator files | Native executable and Linux libraries, or an explicitly configured Wine/Proton launch |
| Windows global input and window controls | Desktop-dependent shortcuts, focus, and compositor permissions |
| Windows taskbar controls | Desktop panel settings |
| LEDBlinky and Windows batch wrappers | Unavailable Windows integrations, or separately tested Linux alternatives |
Existing Windows examples apply to Windows. Use the linked Linux steps for paths, installation, startup, controls, and recovery.
Implementation references
The local source review on September 15, 2026 covered HyperHQ's docs/LINUX_DISTRIBUTION.md, HyperHQ's docs/FULLSCREEN_STARTUP.md, HyperSpin's docs/linux-distribution.md, HyperOverlay and HyperMarquee package targets, HyperspinCore Essentials runtime documentation, HyperLED project metadata, and HyperCapture acceptance procedures. These establish implementation scope. They do not certify a published package or physical Linux system.