Open-source project
TrenchBroom/TrenchBroom avatar
TrenchBroom/TrenchBroom

The downloads link and the changelog link are different repositories

Cross-Platform Level Editor

2,908 stars388 forksC++GPL-3.0

At a glance

What is it?
trenchbroom is a cross-platform level editor for Quake-engine games, with brush and entity tools, unlimited undo and a versioned release train. Its README is short on instructions and long on credits, and the two places it sends you for binaries and for changes are not the same repository.
Who is it for?
trenchbroom fits you if you are making maps for Quake, Quake 2, Hexen 2 or Daikatana and want a single application for brush and entity work across platforms, and it does not fit if you need Quake 3 patches or brush primitives or anything outside the Quake family without writing a game configuration yourself. Before you commit to it, check two things the page leaves open.
Can I use it commercially?
Yes, with conditions. GPL-3.0 is a copyleft licence: if you distribute software that includes it, you must release that software's source code under the same licence. Running it internally without distributing it does not trigger that obligation.
Is it still maintained?
Yes. The repository received new commits within the last day.
What is it written in?
Mainly C++, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • TrenchBroom/TrenchBroom2,908 ★ · +61
Star history
Repository2026-10-042026-11-15
TrenchBroom/TrenchBroom2.8k2.9k

61 Stars in the last 42 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

Downloads and the changelog sit in two different repositories

The releases section says binary builds are available from a releases link, and that link resolves to github.com/kduske/TrenchBroom/releases. The changes section at the bottom of the same file points its releases link at github.com/TrenchBroom/TrenchBroom/releases. Those are two different repository paths under two different account names, and only the second matches where this file lives. For a reader arriving at the page it is a small thing, but it means the download you get and the notes you read can come from two places that are not obviously the same project, which is worth knowing before you file a bug against a build. The release train itself is calendar versioned. The recent tags are v2026.2, preceded by v2026.2-RC1 and v2026.2-RC2, so a final release here is preceded by at least two published candidates rather than a single pre-release.

The version scheme is a calendar and the manual link is not versioned

Two of the three dated entries in the release history are candidates: a first candidate in late July, a second in early August, and the final in the second half of August, all carrying the same 2026.2 name with an RC suffix. That is a predictable enough scheme to plan around. The documentation link is less predictable. The manual is addressed at trenchbroom.github.io/manual/latest, and the word latest is the only version reference in the URL, so the text you read may describe options that do not exist in the build you installed. The two other entry points split the difference in different ways: the website is given as a path on kristianduske.com, a personal domain, while the repository itself lives under the TrenchBroom organisation. So the project has three namespaces for the same software, and none of the three is versioned in a way you can pin.

There is no setup section, only a link to the manual

Count what the page gives you about getting the tool running. The releases section, one sentence, tells you binary builds exist. The compiling section, one sentence, tells you to read BUILD.md. There is no first launch, no configuration directory, no instructions for pointing the editor at a game's directory, no mention of where entity definitions live, and no sample configuration. Everything a new user needs beyond acquiring a binary is expected to come from the linked manual, which is a separate site with a moving version. The same is true of the editor's own concepts: FGD and DEF entity definition files, mod support and custom game configurations are named as features, but the page never shows one. The tree at the repository root has no manual directory either, alongside app, lib, cmake, docker and www, so the manual's source is not part of what you clone.

Quake 3 carries its own gap in the same line

The supported games list is six entries and one of them is a partial. Quake appears with two file format variants named in parentheses, Standard and Valve 220. Quake 2 follows. Quake 3 is listed as partial, with no patches or brush primitives yet, which is the only place on the page where a specific missing capability is named next to a game. Hexen 2 and Daikatana follow, then Generic, described as being for custom engines. Two extension paths are named. Custom entity definition files are supported through FGD and DEF files, and more games can be supported with custom game configurations. Neither is accompanied by an example or a link, so the difference between the Generic entry and a custom game configuration is something you would have to work out from the manual before you could rely on it.

Undo, backups and point files are the three safety nets

The general feature block is where the editor's actual priorities show. Editing works in 3D and in up to three 2D views at once, over a renderer described as high performance with support for huge maps. The recovery affordances are three: unlimited undo and redo, macro-like command repetition, and automatic backups. Alongside them sit point file support, which is the engine-side mechanism for taking vertex positions back out of a map, and .obj file export, which is the interchange path to other 3D tools. Texture work gets its own pair, a UV view and what the page calls precise texture lock for all brush editing operations, plus multiple material collections. One feature is named after a Quake habit rather than a generic concept: an issue browser with automatic quick fixes, which is the compiler error list a Quake modder already expects to see.

Three clang configs, three CI scripts and a signing directory

The root of the repository carries the tooling that a large C++ desktop project accumulates. Three separate clang configuration files sit side by side, a format config, a tidy config and a clangd config, each tool doing a different job. Three continuous integration scripts exist as OS-specific files, CI-linux.sh, CI-macos.sh and CI-windows.bat, matching the cross-platform claim rather than a single matrix definition. There is a coverage document, a docker directory, an AGENTS.md, and a .signpath directory, which is the configuration for signing Windows binaries. The credits list at the bottom of the page names the same stack in prose: Qt for the toolkit, FreeType and FreeImage for text and images, TinyXML and miniz for parsing and compression, Assimp for the 3D models the editor displays, Catch2 for tests, CMake for the build and Pandoc for the documentation, plus a Source Sans Pro font and two community contributed icons.

Free and cross platform is one bullet in a feature list

There is no licence section and no pricing section. The economics are covered by a single bullet in the general feature list that reads free and cross platform, and the licensing fact sits in the repository metadata instead, GPL-3.0, with a LICENSE.txt file at the root. Nothing on the page mentions a trademark, a CLA, or any restriction beyond the licence, and the contributing section is a one-line pointer to a CONTRIBUTING.md. The credits section is by some distance the longest part of the file, naming nine libraries and tools, a typeface and two individual artists, which is a reasonable signal of where the maintenance attention goes. The community links above the features are similarly prominent, a trailer, a tutorial playlist, a Discord, a Mastodon and a Bluesky account, none of which is versioned against the build you are reading about.

Editorial conclusion

trenchbroom fits you if you are making maps for Quake, Quake 2, Hexen 2 or Daikatana and want a single application for brush and entity work across platforms, and it does not fit if you need Quake 3 patches or brush primitives or anything outside the Quake family without writing a game configuration yourself. Before you commit to it, check two things the page leaves open. First, the manual link points at a latest path rather than a version, so pair it with the release number you install. Second, the binaries and the changelog are advertised through two different repositories, so confirm you are downloading from the one you think you are when a build behaves unexpectedly.

Frequently asked questions

What is a TrenchBroom?

A modern cross-platform level editor for Quake-engine based games, listed as free and cross platform. It edits in 3D and in up to three 2D views, offers brush editing with vertex manipulation, clipping, scaling and CSG operations, and entity editing with FGD and DEF definitions. The repository is published under GPL-3.0.

Which games are supported by TrenchBroom?

Quake in both the Standard and the Valve 220 file formats, Quake 2, Quake 3 which is marked partial with no patches or brush primitives yet, Hexen 2, Daikatana, and a Generic entry intended for custom engines. The page adds that more games can be supported with custom game configurations.

how to install trenchbroom

The page gives no installer steps. It says binary builds are available from its releases link, and that compiling should follow the instructions in BUILD.md. Worth knowing before you click: that downloads link resolves to the kduske/TrenchBroom repository, while the changes link at the bottom of the page points at TrenchBroom/TrenchBroom, so the binaries and the release notes are advertised through two different repository paths.

Official sources

  1. Issues
  2. License: GPL-3.0
  3. README
  4. Releases
  5. TrenchBroom/TrenchBroom on GitHub
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.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/trenchbroom-trenchbroom.svg)](https://hysenlabs.com/projects/trenchbroom-trenchbroom)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/trenchbroom-trenchbroom.svg)](https://hysenlabs.com/projects/trenchbroom-trenchbroom)

Was this useful?