LibreQuake: free game data that needs an engine of its own
A free and open source Quake remake with art under the BSD license
At a glance
- What is it?
- LibreQuake is a free content remake of Quake that ships assets rather than an executable, so it has to be paired with a source port such as FTEQW or vkQuake. The repository holds the data, the compatibility work and the build scripts, and the licence file uses custom terms that the GitHub licence picker cannot classify.
- Who is it for?
- LibreQuake suits players and modders who want to play the classic Quake catalogue on hardware or platforms where the id Software data files cannot be obtained, and who are willing to assemble an engine alongside it. It is not a game you can launch on its own, and the project says so plainly.
- Can I use it commercially?
- Check first. The repository uses a licence we do not classify automatically, so read its LICENSE file before any commercial use.
- Is it still maintained?
- Yes. The repository last received commits 12 days ago.
- What is it written in?
- Mainly QuakeC, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on October 25, 2026, and from our analysis. They are not legal advice.
Editorial analysis
LibreQuake is data, not a game
The most important sentence in the README is the one that explains what the project is not. LibreQuake "by itself is just the raw material for a game" and "must be paired with a compatible engine to be played." Any evaluation that starts by asking whether the project runs is starting in the wrong place.
The reason a free remake of Quake needs a companion engine comes from how the original shipped. The Quake engine source code was released as free software, but the game still needed one of the proprietary data files from id Software. LibreQuake's aim is to create a free alternative to those data files, and combined with the GPL-licensed Quake source code the result is described as a completely free game.
The practical audience is specific: people who want to play the two-decade back catalogue of Quake levels and fan modifications, listed in the README with a link to quaddicted.com, without depending on non-free software to do it. That catalogue is the reason to care. LibreQuake does not try to be a new game; it tries to be the missing half of an existing one.
How the id1 directory is laid out
The engine looks for a directory called `id1/`, and inside that directory sit two archives, `pak0.pak` and `pak1.pak`. Those two files carry all of the game data with a single exception, the soundtrack.
This structure is what makes compatibility with old source ports possible at all. Because the data lives in the same archive layout and the same directory name that the Quake engine expects, an engine can read LibreQuake in place of the original id Software data, and the thousands of community maps and mods written for the classic game can load without conversion. A reimplementation with its own asset format would break that link and defeat the purpose of the project.
The repository layout reflects the separation between assets and tooling. There is an `lq1/` directory holding the game data itself, a `qcsrc/` directory for QuakeC source, `texture-wads/` for textures, `bin/` for binaries, plus `build.py`, `build_components.json` and `build_releases.json` describing how releases are assembled. The `docs/` folder holds documentation including a deathmatch setup guide.
Installing LibreQuake with a source port
There is no installer and no package manager entry, because the project deliberately produces assets rather than a runnable program. The README's own procedure is short. Download an engine first, then place the downloaded `id1` folder, or `lq1`, in the same directory as the engine executable, and run that executable.
The README names FTEQW as the engine particularly recommended by the LibreQuake project, pointing to the downloads page at fte.triptohell.info, and says it offers good support for singleplayer, multiplayer and the majority of mods created for both Quake and LibreQuake. Three alternatives are named as good options: vkQuake, QuakeSpasmSpiked and Ironwail, each linked to its own download page. The README also points to the Quake Wiki engine list for further options.
The order matters. The engine executable and the data folder must sit in the same directory, and the data folder keeps the name `id1` or `lq1` depending on which form you downloaded. Nothing else needs configuring for singleplayer play, and the README points to docs/deathmatch-setup-guide.txt for anyone who wants to set up a LAN deathmatch game.
Two practical warnings. The soundtrack is not part of the two pak archives, so an install without music is expected rather than a broken copy. And because the engine is a separate download that LibreQuake does not control, a problem with the game running is more likely an engine or mod issue than a LibreQuake one.
What the compatibility work actually buys you
The pitch in the README is that LibreQuake aims to be compatible with the back catalogue of Quake levels and mods, and that most of them can then be played without non-free software. That claim is about the old content, not about new content.
In practice this means the existing ecosystem of community maps becomes usable again on a platform where the original id Software data cannot be shipped. The Quake Wiki is cited as the reference for engines, and the README itself positions LibreQuake as raw material for a game rather than a finished one, which is an honest framing that sets expectations correctly.
The screenshots in the repository are organised as texture examples and weapon examples, which points at the core of the effort. Rebuilding a Quake-compatible asset set is not about inventing new art but about reproducing the look and feel that mods were written against, so that a fan map from 1998 renders the way its author intended. The project also accepts community submissions and asks contributors to provide a name and email when submitting resources, so the asset set is partly crowd sourced.
Where LibreQuake is the wrong choice
The first limitation is the one the README states itself: this is not a game you can double-click. Anyone who wants a single installer or a Steam style library entry will find the assembly step more work than it is worth, and the engine still has to be sourced and configured separately.
The second is scope. There is no singleplayer campaign of its own in the usual sense, no settings menu, no controller layout, no modern graphics options beyond what the chosen engine provides. Those belong to the source port. If the port you choose does not support a mod well, LibreQuake will not paper over it, and the README is candid about that by naming FTEQW as the engine with the best mod support rather than claiming universal compatibility.
The third is the licence, which is the practical surprise for anyone planning to redistribute or build on it. The repository records the licence as a custom one that GitHub cannot classify, and the README points to a `COPYING` file for the terms. The project describes its goal in free software terms: use, copy, modify and study without restriction, with the condition that the licence stays intact. That is a description, not the licence text, and the details have to be read in the file itself.
The fourth is the release cadence. The listed releases are all betas: v0.09-beta from 2025-11-05, 0.08-beta from 2024-11-09 and 0.07-beta from 2024-08-16. A beta tag is a reasonable signal for an asset set, but it also means version numbers do not promise a stable API in the way a released library would.
Other free engines compared to running the data on its own
The comparison here is not against other free games but against the two ways a player normally gets Quake running. The first is the original commercial release, with id Software's own data files, which LibreQuake exists to replace. The second is an engine plus a community data pack that is not Quake compatible at all, and which therefore cannot run the classic maps and mods.
Between LibreQuake and the original data there is a licensing difference, and that is the whole axis of comparison. The original data files are proprietary and cannot be redistributed. LibreQuake's data can be, provided the terms in COPYING are respected. For a household that simply wants to play, that difference means nothing. For a server operator, a Linux distribution, a handheld port, or anyone shipping a package, it is the entire reason the project exists.
The engines named in the README also differ from each other in ways that matter to a LibreQuake user. FTEQW is highlighted for mod and multiplayer support, vkQuake is a Vulkan renderer path, and QuakeSpasmSpiked and Ironwail are given as further options. Choosing between them is a matter of which features a given mod needs, and the Quake Wiki is the reference for that comparison. What none of them change is the fact that the data comes from LibreQuake and the executable comes from elsewhere.
Contributing, versioning and maintenance
The repository is not archived and the last push was on 2026-10-16, so work on the data and the build scripts is continuing. The most recent tagged release, v0.09-beta, dates from 2025-11-05, which puts the tip ahead of the newest published build.
The contribution path is deliberately low friction. The README says you can clone the repository and commit directly, but calls that a technical task and notes that leaving it to the maintainers is the normal mode of operation. Pull requests are welcome, and GitHub's direct pull requests are described as the simplest route, but not the only one. The project follows the commit message style common to distributed version control systems, the Linux style, and links to the well known How to Write a Git Commit Message guide for the details. There is a CODEOWNERS file, a CONTRIBUTING.md and a .flake8 configuration at the root, and the Python build script and its two JSON descriptors show how releases are put together.
Asset contributions come with an etiquette rather than a technical hurdle. The README asks submitters to provide a name and email so credit can be given, and states that all contributors, including the reader, deserve credit. That is a reasonable expectation for a project whose output is a redistribution-friendly asset pack.
Editorial conclusion
LibreQuake suits players and modders who want to play the classic Quake catalogue on hardware or platforms where the id Software data files cannot be obtained, and who are willing to assemble an engine alongside it. It is not a game you can launch on its own, and the project says so plainly. Before adopting it, read the LICENSE file, which uses custom terms GitHub cannot classify, and confirm that the engine you plan to use is one of the ports the README names, because compatibility with older mods is where the value of this data lies.
Frequently asked questions
How do I play LibreQuake?
LibreQuake is only the game data, so you also need an engine. Download a source port such as FTEQW, vkQuake, QuakeSpasmSpiked or Ironwail, then place the downloaded id1 or lq1 folder in the same directory as the engine executable and run that executable.
What files does LibreQuake provide?
The engine expects a directory called id1/ containing two archives, pak0.pak and pak1.pak, which hold all of the game data except the soundtrack. The repository also has an lq1/ directory holding the data itself.
Can I use LibreQuake with Quake mods and community maps?
That is the stated aim of the project. LibreQuake aims to be compatible with the back catalogue of Quake levels and mods so most can be played without non-free software, and FTEQW is named as the engine with the best support for singleplayer, multiplayer and most mods.
What licence does LibreQuake use?
The licence is a custom one that GitHub cannot classify, and the terms live in the COPYING file. The README describes the intent in free software terms: you may use, copy, modify and study the work, including redistributing it, as long as you keep the licence intact.
Does LibreQuake come with its own engine?
No. The README states that LibreQuake by itself is just the raw material for a game and must be paired with a compatible engine to be played, which is why the install step begins with downloading a source port.
How do I set up a LAN deathmatch game with LibreQuake?
The README points to docs/deathmatch-setup-guide.txt in the repository for the details of setting up a LAN deathmatch game.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/lavenderdotpet-librequake)Was this useful?