VideoGameEsoterica Breaks Down Decomp, Recomp, and Port Differences

If you've spent any time in N64 or PS2 preservation circles lately, you've almost certainly used "port," "recomp," and "decomp" in the same sentence — possibly interchangeably. Video Game Esoterica, the 65,900-subscriber YouTube channel built around conversational deep-dives into retro gaming technology, has made it its mission to untangle exactly that confusion. The channel's recent video, "Decomp vs Recomp vs Port! So What Is the Difference?", lays out the distinctions between decompilation, static recompilation, PC ports, and hybrid emulation backends with the kind of clarity that the scene has genuinely needed.

The timing is sharp. As the host points out, "We have had so many N64 decomps, N64 recomps and N64 PC ports and PS2 recomps on the way! Plus Xbox 360 recomps as well!" The wave is real, and it is accelerating. The N64 decomp and recomp scene has exploded in the past year, and with projects now spanning multiple platforms, the vocabulary around these efforts matters more than ever.

What a Decompilation Actually Is

Decompilation, the "decomp" half of the conversation, is the painstaking process of reverse-engineering a game's compiled binary back into human-readable source code. After two years of painstaking work, for example, Banjo-Kazooie was fully decompiled from Assembly to the more modifiable and readable C code. The end result of a full decomp is essentially the original game's source, reconstructed, which opens the door to modifications, bug fixes, and — crucially — building native PC ports that compile and run without the original hardware or an emulator in the loop.

The important nuance is that a decomp alone does not equal a port. Decompiling code is a whole different ballpark from actually translating that code to work on different platforms like PC. While the core game loop functions don't really need to be tweaked, stuff like the graphics and sound APIs have to be modified, as well as making menus and accepting new input types. A completed decomp gives developers the raw material. What they build with it determines which category a given project falls into.

What a Static Recompilation Is (and Why It's Different)

Static recompilation is the other major path to a PC port, and it is the one generating the most excitement in the scene right now. As the Video Game Esoterica host explains, a static recomp "is one of two different ways to get these classic retro games having PC ports." Critically, he adds: "even though we use the word port all the time, technically it isn't a source port."

Unlike N64 ports of the past, static recompilation bypasses the need for decompiled source code when making a port, allowing ports to be made without source code. Instead of reconstructing the original code line by line, a static recompilation tool reads the game's compiled machine code and translates it directly into native executable code for a target platform. The N64: Recompiled tool, created by developer Mr-Wiseguy, automates much of the work required to create native ports of N64 games via static recompilation.

The practical payoff is substantial. Banjo: Recompiled, for instance, is essentially a full remaster of the original game, improving frame rates and adding widescreen support for modern displays. It also enables the use of a second analog stick to control the camera, providing a much more modern control scheme than the C buttons on the N64 controller. The host of Video Game Esoterica described MrWiseGuy's Banjo-Kazooie static recomp as "absolutely incredible!" — and the community reception broadly agrees.

Banjo: Recompiled makes use of the N64: Recompiled project to statically recompile the beloved 1998 title into a native PC port, with the project spearheaded by Mr-Wiseguy, creator of N64Recomp and Zelda64Recomp. The distinction between this approach and a decomp-based port is subtle but real: the reverse engineering work done by the decompilation team was invaluable for providing some of the enhancements featured in the project, and the project uses headers and some functions from the decompilation project in order to make modifications to the game — but the underlying architecture is fundamentally different from building a port directly out of reconstructed source code.

The Hybrid Approach: Recomp Plus Emulation in the Background

The scene doesn't stop at two clean categories. The Video Game Esoterica host identifies a third approach: hybrid static recomps, which he describes as projects "where it's recompilating some things and then using emulation in the background." This is where the terminology gets genuinely tricky, and where the channel's explainer earns its keep.

A helpful real-world illustration of this hybrid approach comes from an older precedent in the community. The Zelda: A Link to the Past "port" is in fact a glorified SNES emulator, because while the CPU code has indeed been ported, that code is trying to drive the SPC700 (sound chip) and the SNES PPU, and both functions have been literally brought in from a SNES emulator. The host flags this kind of arrangement as potentially "a little bit problematic" precisely because the emulated components are only as good as the emulator backing them. He references Zenia by name as an example, noting that "because that is incomplete emulation, you're obvious going to end up in a situation where it could be a little bit problematic."

The takeaway: calling something a "PC port" when part of the runtime is still running through an emulation layer is technically accurate only up to a point. The user experience, compatibility, and accuracy all hinge on how complete that emulation component actually is.

Why the Labels Matter for Preservation

Understanding which approach produced a given project isn't academic pedantry — it shapes what you can expect from the result. Modding a recomp is like modding an average PC game versus modding an open source PC game. You can still do a lot if the modding support is there, but the full source code is how you get the truly INSANE stuff.

A decomp-based port generally provides deeper access to the game's internals, enabling more radical modifications. A static recomp, even a polished one, operates at a different layer. Previously, making a native port required painstakingly reverse-engineering a game's code line by line, then creating a renderer to run that code on modern hardware. Static recompilations still require tweaking and polishing, but the N64: Recompiled tool also includes a built-in renderer to speed things up even further. Both approaches represent genuine preservation work — they are just different tools for different situations, and conflating them leads to misaligned expectations.

The Video Game Esoterica host is candid about his audience for this explainer: "Because if you have a technically minded brain, you probably already know the difference. And the video really isn't quote unquote for you." His stated goal is pedagogical in the truest sense: "My entire goal as a college professor of film and television and with this channel is to be able to conversationally explain deep topics without making you zone out, without making you get lost along the way."

What the Next Decade Looks Like

The host's long view is optimistic and specific. "It's going to be basically completely different in 5 to 10 years. The technology and tooling is going to change." He notes that a PS2 recomp tool is currently in development and "showing some promise" — a significant development given that PS2 recompilation lags meaningfully behind the N64 ecosystem in maturity. His prediction: "by the time this video is 10 years old, we probably have hundreds of games playable on PC."

While ports of both N64 Zelda games, Star Fox 64, Super Mario 64, and Mario Kart 64 already exist, accurate N64 software emulation remains challenging, and the trident controller doesn't translate well to modern Bluetooth controllers — which is precisely why native ports built through these methods matter. The groundwork being laid now, across N64, PS2, and Xbox 360 projects, is infrastructure that future developers and preservationists will build on directly. The terminology is the map. Getting it right means knowing exactly where the scene is heading.