Quiver Launcher
One place to find, install, update and play the games and apps people release on GitHub, GitLab and other forges, such as modern ports (source ports and recompilations) and fan projects. Browse the Quiver catalog, press Get, and Quiver downloads it, checks it and installs it. Then it keeps it up to date.
What it does
- A catalog to browse. Search the quiverlauncher.com catalog by console, platform
- Checked downloads, and a 48-hour wait. Quiver records the checksum of each catalog app's release files when
- Your library, your way. Sort and filter by console, make playlists, and share them or follow other people's.
- Made for the couch. TV mode turns Quiver into a full-screen launcher for a controller. It comes on by itself in
- Mods. Browse, install and update mods from Thunderstore and GameBanana for the apps that support them.
- Play it your way. Add any app to Steam or the desktop, and run Windows builds on Linux with Wine or Proton.
- Sign in to sync (optional). Sign in with GitHub or Discord to keep your library and playlists the same on every
- Release hosts, your way. GitHub and GitLab work as before, and so do Gitea/Forgejo (including Codeberg), Bitbucket,
- In your language. English, Português (Brasil), Español (Latinoamérica), Deutsch, Français, Русский, Italiano,
Download
Get the latest version from Releases. Quiver updates itself after that.
Official downloads come only from this repository's Releases page and from Quiver's own updates. A copy from anywhere else isn't made by us.
| Your device | Download | Then |
| --- | --- | --- |
| Windows | QuiverLauncher-win-Portable.zip | Extract it anywhere and run QuiverLauncher.exe. It updates itself from there. |
| macOS | …_universal.dmg | Open it and drag Quiver Launcher into Applications. Works on Intel and Apple silicon. |
| Linux | …_amd64.AppImage or …_x86_64.flatpak | AppImage: mark it executable, then run it. Flatpak: in a terminal, run flatpak install --user --bundle followed by the file. |
| Steam Deck | …_amd64.AppImage or …_x86_64.flatpak | In Desktop Mode, mark the AppImage executable, or install the Flatpak from Konsole as for Linux. Then add Quiver to Steam to start it from Game Mode. |
| Android | …_arm64.apk | Open it on your phone and allow installing from this source when asked. Android 7 or newer. |
Installed the Flatpak with Discover or another software center, and it can't update itself? Run
flatpak install --user --bundle once with the newest release's file. Quiver updates itself from then on.
Coming from Quiver Launcher 3
Your apps come with you, and nothing needs downloading again. On its first start, Quiver Launcher 4 asks where your Quiver Launcher 3 folder is (or finds it by itself), shows what it found and adds your apps to your library, with the tags you gave them, your hidden apps, the pictures you chose and your tag filters (as playlists). For a portable copy, choose the folder you unzipped it to. You can do this later too, in Settings › Library.
Adding them moves nothing: anything already installed stays where Quiver Launcher 3 put it and plays from there. The setup then shows that folder beside Quiver Launcher 4's and asks whether to move the apps across now, or keep them there for now. If you keep them, don't delete your Quiver Launcher 3 folder yet, as that would delete those apps: move them once you've tried Quiver Launcher 4, in Settings › Apps folder, and delete the old folder after.
Quiver Launcher 3 is still available on the v3 branch
and its releases.
Privacy
Quiver sends optional usage data, such as which screens are opened and which apps are installed, to help improve it. When you're signed in, events are linked to your Quiver account; earlier events from the same device may also become linked after sign-in. It doesn't send what you type, your files, paths or your computer's name. You can turn usage data off on first start, in Settings, or through your Quiver account. See what's sent, exactly.
Help
License
Quiver Launcher 4 is source-available under the Business Source License 1.1. You can read, build, modify and test the source code, contribute changes, and use official releases or copies you build yourself from our published source. You can also share source code and modified builds for development and testing.
During the first year after a version is first published, production use is allowed only as described in the Additional Use Grant. Unofficial builds distributed by others do not have production-use permission. One year after each version is first publicly available, that version becomes MIT licensed.
The Quiver name, logo and icons are covered by a separate trade mark policy. Quiver Launcher 3 and earlier remain MIT licensed. Quiver Launcher started as a fork of GithubLauncher by SirDiabo.
Contributing
Want to build Quiver from source or help out? CONTRIBUTING.md explains how to set it up, run the tests and send a pull request.