Repository navigation
FAQ
Short answers, based on the project README and policy documents. Each answer links to a fuller source where one exists.
No. OpenBox has no account system. Optional integrations, such as RetroAchievements, EmuMovies, and IGDB, have their own accounts and credentials.
No. OpenBox does not distribute games, ROMs, BIOS files, firmware, or DRM circumvention tools. You supply the files. OpenBox catalogs, launches, and tracks them.
In library.json in the data folder. The Installation page lists the folder for each system. Media, backups, themes, and logs live in the same folder. Deleting library.json resets the library, and media files stay.
Yes. Set OPENBOX_DATA_DIR before OpenBox starts.
Yes, through a mounted folder. Turn on library catalog sync in Settings, preview the incoming changes, and apply the reviewed plan. Paths, launch commands, credentials, media, and play statistics stay local.
No. The project includes no telemetry. The diagnostic report is redacted and stays on your machine until you share it. Network requests come from features you use, such as metadata and media lookups.
No. The server binds to loopback (127.0.0.1). Treat any URL that contains the token as a password. Anyone who has the token controls the instance.
Yes. OpenBox runs on Windows 10 and 11 (x86_64) from the signed portable install. Linux-only features are not available there. These include AppImage and Flatpak packaging, gamescope and Game Mode, XDG desktop entries, and Flathub-aware emulator management.
Yes, on macOS 11 or newer, Apple Silicon and Intel, since version 1.19.0. The app bundle is not notarized, so the first launch needs Open Anyway in System Settings. Linux-only features are hidden. Seven bundled emulator definitions have no verified macOS build, so they are reported as not installed.
Yes. Linux AppImages are published for x86_64 and aarch64. Physical aarch64 hardware has not been verified. The Flatpak bundle is x86_64 only.
Linux has a Game Mode option: python3 web_app.py --game-mode, or openbox --web --game-mode. The project has a gamescope test harness. SUPPORT.md lists the physical maintainer pass as unavailable.
Yes. Plugins are Python packages. On Linux with bubblewrap, a plugin runs in a sandbox with no network and no home folder. Without bubblewrap, OpenBox runs a plugin only after you trust that exact package. macOS has no bubblewrap, so enabled plugins are skipped there unless you trust the exact package.
No. OpenBox Game Launcher is an independent project. It is not affiliated with LaunchBox, Unbroken Software, LLC, or the Openbox window manager project. LaunchBox and Big Box are trademarks of Unbroken Software, LLC.
The GNU Affero General Public License v3.0 (AGPL-3.0). Contributions are licensed under the same license.
Yes. The local REST API accepts the X-OpenBox-Token header. The token and port files exist only while the web interface runs. This example prints the number of games on Linux:
TOKEN=$(cat ~/.local/share/openbox-game-launcher/server.token)
PORT=$(cat ~/.local/share/openbox-game-launcher/server.port)
curl -H "X-OpenBox-Token: $TOKEN" http://127.0.0.1:$PORT/api/library | jq '.games | length'The REST API reference lists every endpoint.
Use Reporting issues. Security problems go to a private advisory, never a public issue.
OpenBox Game Launcher is open source under the GNU Affero General Public License v3.0.
It is an independent project, not affiliated with LaunchBox, Unbroken Software, LLC, or the Openbox window manager.
Issues ·
Discussions ·
Security policy ·
Buy me a coffee
Start
Help
Community
Contribute
Project