Someone made Doom run on Sega Genesis, and the hardware is probably crying

Doom has been ported to almost everything, from serious workstations to devices that look as if they should be displaying a shopping list rather than a demon invasion. Yet a Doom port running on the Sega Mega Drive, also known as the Genesis, still has a special kind of madness to it. This is not a simple case of loading an old shooter onto old hardware and calling it retro magic. This is Doom squeezed into a machine with 64 KB of main RAM, a Motorola 68000 CPU, strict video limits and a graphics system that was never designed for texture-mapped corridors full of angry monsters. In other words, exactly the sort of technical challenge that makes programmers smile, swear and possibly reconsider their life choices before lunch.

A real Doom port, not a Mega Drive costume

What makes this project interesting is that it is not merely a Doom-themed demo. It is a working port based on Doom64KB, a reduced Doom implementation designed for systems with only 64 KB of RAM while allowing larger ROM storage. That distinction matters. The Mega Drive has enough cartridge space to hold a lot of data, but its main memory is brutally small by PC standards. The trick is not just fitting Doom onto a cartridge. The trick is making Doom think, draw, load and play inside a RAM budget that modern web browsers would spend opening a cookie banner.

The result is recognisably Doom. The title screen appears, the game can load its data, the 3D renderer draws walls, floors, ceilings and sprites, the HUD is there, menus work, automap text appears, the joypad handles input and sound is present. It is clearly not a commercial Mega Drive release from 1994 that id Software somehow forgot in a drawer. It is rough, limited and visibly compromised. But that is also why it is fascinating.

Why 64 KB makes this so difficult

Doom was never a lightweight game in the console sense. The original PC version expected a different class of machine, with more flexible memory and a graphics model better suited to pushing pixels around. The Mega Drive, meanwhile, is a tile-based console. It is excellent at fast 2D action, scrolling backgrounds and sprites, but Doom asks for something different: columns of perspective-correct walls, shaded surfaces, changing palettes and lots of tiny updates that do not naturally fit the hardware.

This port works around that by using the video display processor in an unusual way. A plane is treated like a chunky framebuffer at 38 by 28 cells, where each cell is an 8 by 8 solid-colour tile. Doom’s original column drawing is mapped into this coarser grid, then the tilemap is pushed over with DMA. It is clever, practical and, yes, visually chunky enough to make every pixel feel as if it has been eating protein powder.

The look: Doom through a Mega Drive keyhole

The visuals are the first thing players will notice. This is Doom, but it is Doom seen through a very narrow technical window. The game’s 256-colour palette has to be reduced to the Mega Drive’s much smaller practical colour set. Four palettes of 16 colours are available, with reserved entries for black and text colours, leaving a modest selection for the 3D view itself. The result is a recognisable but heavily reduced version of Doom’s world.

That does not mean it looks bad. It looks like a machine doing something it was absolutely not invited to do, which is more interesting than polished perfection. Walls, floors and sprites come through, but colour banding, coarse resolution and visual compromises are all part of the package. Nobody should expect PlayStation Doom here. This is more like the Mega Drive putting on a marine helmet and insisting it is fine, even though the helmet is clearly three sizes too big.

Sound, controls and the little victories

The port also includes music and effects, using the Mega Drive’s sound capabilities rather than pretending the console is a PC. Music is handled through converted data suitable for the Yamaha FM sound hardware, while effects use PCM through the available audio system. That is a major part of why the port feels like a real console experiment rather than a silent tech preview.

Controls are mapped to the joypad, and essential interface elements such as the HUD, menu and automap text are working. These may sound like ordinary features, but on a port this constrained, ordinary features are hard-won. Every bit of functionality competes with memory, performance and toolchain issues. Even basic text display requires thought, because the system is not drawing in the same way a PC does.

Far from perfect, and better for being honest

This is not a finished, full-fat Doom experience. The supported map list is tiny, limited to E1M1 and E1M8 as part of the Doom64KB base. Some effects are still missing, including screen wipe and fuzzy invisibility rendering. The frame presentation is necessarily coarse, the colour conversion is a compromise and the overall experience is more proof of possibility than replacement for a normal Doom port.

That honesty is important. Retro projects often get buried under hype, as if every technical demo has to be described as impossible, unbelievable or mind-blowing. This one does not need that treatment. The achievement is already clear. It runs Doom-style gameplay on stock Mega Drive-class constraints with 64 KB of main RAM. That is difficult enough without pretending the result has no rough edges. In fact, the rough edges are the evidence of the battle.

The hidden work behind the cartridge

The hardest parts are not always the most visible. Porting Doom to a 68000-based console means dealing with byte order, alignment, memory layout, stripped-down libraries, custom build steps and hardware-specific I/O. The WAD data has to be repacked for proper alignment, palettes have to be generated, sound data must be prepared and parts of the code need careful shims to avoid clashes between toolchains and headers.

This is the sort of work that rarely fits into a flashy screenshot. A player sees a wall texture. A developer sees hours of debugging because one lump of data was not aligned and the 68000 responded with the digital equivalent of throwing a chair. The Mega Drive is friendly when you play Sonic. It is less friendly when you ask it to become a tiny Doom PC.

Why this Mega Drive Doom port matters

The value of this port is not that it delivers the definitive way to play Doom. It obviously does not. The value is that it shows how flexible old code can be when handled with patience, restraint and a willingness to break the problem into small, ugly, solvable pieces. It also reminds us that hardware limits are not just barriers. They are design prompts.

For retro developers, this is a compact lesson in adaptation. Use ROM where possible. Save RAM wherever it hurts. Replace assumptions about pixels with what the machine can actually draw. Accept that perfect is not the target. Working is the target, and working well enough to make people grin is a bonus.

A beautiful technical headache

Doom on the Sega Mega Drive in 64 KB of RAM is not smooth, not complete and not pretending otherwise. It is a deeply technical port with visible compromises, missing effects, limited maps and a lot of clever engineering under the surface. It must have been very hard to achieve, because almost every part of Doom pushes against what the console naturally wants to do.

And yet it runs. It boots, draws, plays, makes noise and gives the Mega Drive one more impossible-looking trophy for its shelf. Somewhere, a demon has been reduced to a handful of chunky tiles and a tiny palette, and honestly, it probably had it coming.