Q3Edit Brings Quake III Map Editing to the Browser
20 Jul 2026
A new Show HN project called Q3Edit is putting a classic level-design workflow into a place most modders never expected: the browser tab.
Q3Edit is a browser-based editor for Quake III maps that allows users to edit, compile, and play maps entirely online. It supports opening, editing, and saving real .map files—including brushes, patches, entities, and terrain—without requiring any local software installation.
What's under the hood
According to the report, Q3Edit is built with TypeScript and WebGL2, and it leans on id Software's original q3map compiler, ported to WebAssembly, to handle BSP map compilation directly in the browser. The interface follows a Radiant-style four-view layout, a nod to the classic level-editing tools long familiar to Quake III mappers.
Feature-wise, Q3Edit supports brushes, patches, CSG operations, and terrain editing—core building blocks of Quake III level design. Once a map is compiled, it can be launched with one click in browser-native ioquake3, collapsing the traditional edit-compile-test loop into a single tab.
Why this matters technically
The most interesting signal here isn't the game itself—it's the porting pattern. Using WebAssembly to run a compiled tool like q3map inside a browser suggests a broader technical playbook: legacy, performance-sensitive software that once required local installation can potentially be moved to the browser with modern web tooling. Q3Edit could also serve as a technical showcase for what WebAssembly and WebGL2 are capable of when applied to older, native game-engine tooling.
Risks and open questions
The report flags several risks worth watching. Browser-based BSP compilation via WebAssembly may hit performance limits on complex maps, and reliance on browser-native ioquake3 could constrain compatibility across devices or browsers. There's also the more fundamental question of market size: as a tool built for a legacy game engine, Q3Edit's potential user base may simply be small.
Notably, the report has no information on who built Q3Edit, when it launched, its pricing or licensing model, performance benchmarks, device compatibility, community feedback, or a future roadmap. These gaps make it hard to assess momentum or long-term viability at this stage.
Why founders should care
For founders in devtools or creative tooling, Q3Edit is a useful case study rather than a market to chase directly. It's likely—though not confirmed—that porting compiled legacy tools to WebAssembly is a viable technical strategy for other classic software beyond gaming, given that Q3Edit demonstrates the pattern works well enough to ship a working demo. It's also plausible that building niche developer tools around established, passionate-but-small communities (like retro gaming and modding) can be a legitimate go-to-market wedge, even if the total addressable market stays modest. Finally, the one-click compile-and-play workflow hints at a more general truth: reducing friction between creation and testing tends to resonate with technical users, a principle that could apply well beyond game map editors.
Founders building browser-based tools for legacy or niche technical workflows may want to watch how Q3Edit's compatibility and performance issues get resolved—or don't—as an early signal for where WebAssembly-based porting hits real-world limits.