The Nintendo Entertainment System, Game Boy and Mega Drive stopped being current hardware decades ago, but developers never stopped making games for them. In 2026 the scene is easier to enter, easier to discover and more ambitious than ever. New releases arrive as downloadable ROMs, browser demos and fully boxed cartridges that sit beside games from the original era.
This is not simply nostalgia with a new label. Modern homebrew developers work within the real limits of old processors, graphics modes, memory maps and sound chips. Demake creators go one step further, asking how a newer idea would have been redesigned for an earlier machine.
Homebrew, demake, port or retro-style?
These terms often overlap, but they describe different projects:
- Homebrew is independently developed software made for hardware outside its original commercial lifecycle. It may be an original game, utility, demo or experiment.
- A demake reinterprets a newer game or genre as if it had been created for older hardware. A good demake changes structure and mechanics, not only the pixel size.
- A port adapts an existing game to another platform while trying to preserve its identity.
- A retro-style game may look and sound old but run only on a modern PC or console. Pixel art alone does not make something NES or Game Boy software.
The crucial test is the target. If a ROM can run on the original machine, through a compatible flash cartridge or a newly manufactured cartridge, the developer is solving authentic hardware problems.
Why the scene is growing now
Development tools are more approachable
Earlier hobbyists needed assembly knowledge, home-made cables and fragmented documentation. Those routes still exist, but visual tools and mature software development kits now provide a gentler starting point.
GB Studio offers drag-and-drop development for Game Boy games, with visual scripting for beginners and access to engine code for advanced users. It can export a ROM for emulators, web pages or original hardware. NESmaker provides genre modules and tools for graphics, music, levels and dialogue, while still allowing experienced developers to work deeper in its codebase.
For the Mega Drive and Genesis, SGDK provides a C-based development kit, libraries, tools and documentation. Developers can concentrate on game logic without building every low-level routine from the beginning.
Testing is faster
Modern emulators provide debugging, memory inspection and rapid builds. FPGA systems and flash cartridges make it easier to test on hardware throughout development. A developer can iterate on a laptop, run the same build on a real console and identify timing or display behaviour that an emulator did not expose.
Distribution no longer requires a conventional publisher
A creator can release a ROM directly, provide a browser version, fund a cartridge run or work with a small physical publisher. The homebrew and retro section on itch.io currently contains hundreds of projects across Game Boy, NES, Mega Drive, Commodore and other platforms.
Players understand hardware limitations differently
Modern audiences have decades of design history to draw from. A new Game Boy developer knows about quality-of-life features, accessibility, clearer tutorials and fairer checkpoint design that were not always priorities in the 1990s. The result can feel historically authentic without reproducing every old frustration.
What old hardware changes about game design
Restrictions are not just technical trivia. They shape the game.
- Limited colours force artists to make silhouettes and contrast readable.
- Small tile sets reward reuse, animation and clever combinations.
- Tight memory encourages compact levels, data compression and disciplined scope.
- Sprite limits affect enemy counts, flicker and boss design.
- Simple sound channels turn composition into careful allocation of melody, bass, percussion and effects.
- Original controllers keep interfaces focused because there may be only a directional pad and two main buttons.
A demake succeeds when these constraints influence the mechanics. Shrinking a screenshot is easy; redesigning a modern inventory, camera or combat system for two buttons is the interesting part.
Where new old-console games come from
Game Boy and Game Boy Color
The Game Boy scene benefits enormously from GB Studio, strong emulator support and accessible flash hardware. Developers create puzzle games, adventures, horror stories and role-playing games, often with a browser build that lets players try the game before buying a ROM or cartridge.
NES and Famicom
The NES remains demanding but well documented. NESmaker provides a visual route, while experienced programmers use C or assembly toolchains. Games such as new puzzle titles and platformers demonstrate how much variety remains possible within the console’s familiar tile and sprite limits.
Mega Drive and Genesis
The 16-bit Sega hardware offers colourful visuals, distinctive FM sound and enough performance for ambitious action games. SGDK has made it a popular target for programmers comfortable with C. Physical releases can feel remarkably close to late-era commercial cartridges while using contemporary workflows behind the scenes.
Commodore, Amiga and other computers
Retro computers never had a clean dividing line between commercial development and bedroom coding. Modern releases continue that tradition through disk images, tapes, downloads and boxed editions. The scene includes arcade conversions, adventures, strategy games and technical demonstrations that push familiar machines in unexpected directions.
Demakes are design criticism you can play
A thoughtful demake reveals which parts of a game are essential. Remove the cinematic camera, huge map and dozens of buttons and what remains? Perhaps it is the rhythm of combat, one traversal mechanic or the relationship between risk and reward.
This makes demakes more than novelty screenshots. They are a form of analysis. Their creators choose which modern conventions to discard, which to translate and which older techniques can communicate the same idea more clearly.
They can also introduce players to a platform. Someone attracted by a familiar concept may learn why the Game Boy’s palette, the NES controller or the Mega Drive sound chip produces such distinctive design choices.
From a ROM file to a real cartridge
A downloadable ROM is often the first release because it is affordable and easy to update. Physical production adds several more stages:
- Test the final build on multiple revisions of original hardware.
- Choose a compatible cartridge board, memory and save arrangement.
- Design labels, manuals, inserts and region-appropriate packaging.
- Arrange programming, assembly and quality control.
- Plan updates for any bugs found after manufacturing.
Small print runs are expensive, so pre-orders and crowdfunding are common. Buyers should check who is manufacturing the cartridges, whether the ROM will also be available, how updates will be handled and whether the project has demonstrated working hardware builds.
How to play homebrew responsibly
- Download games from the developer or authorised publisher.
- Read the licence before sharing a ROM or modifying a project.
- Do not confuse an original homebrew release with an unauthorised commercial-game ROM.
- Where a demake uses somebody else’s characters or trademarks, understand that its legal position may differ from a wholly original game.
- Back up saves and original downloads, including manuals and version notes.
- If buying a cartridge, keep the creator’s packaging and documentation with it.
Supporting a developer with a direct purchase or donation helps fund testing, music, artwork and future physical runs. Free does not mean valueless.
How to discover worthwhile releases
Start with platform-specific communities rather than general retro lists. Look for development logs, public demos and evidence of testing on original hardware. Useful places include:
- itch.io’s homebrew and retro listings
- GB Studio’s community and documentation links
- SGDK and its linked Mega Drive development community
- Platform game jams, where small finished projects often appear before larger releases
- Retro-development channels that show code, tools and real-hardware testing rather than only final trailers
A useful GB Studio starting point
This introductory tutorial shows the kind of visual workflow that has brought many new creators into Game Boy development.
Try making something in one weekend
The best introduction is a tiny finished project. Keep the first goal deliberately small:
- Choose one platform and one tool.
- Create one room or screen with a clear objective.
- Use one player action beyond movement.
- Add one sound effect and a short music loop.
- Export a playable build and test it away from the editor.
- Ask one other person to play without instructions.
A one-room puzzle teaches more about the complete development cycle than an unfinished plan for a 40-hour role-playing game.
What collectors should look for
New physical games should be treated as modern products for vintage machines, not automatically as artefacts from the original era. Confirm the release year, publisher and cartridge-board quality. Check whether the item is an authorised original game, a licensed port or an unofficial fan project.
Good documentation adds real value. A manual, version number, developer note and accessible digital backup make the release easier to understand and preserve. Artificial scarcity is less interesting than a game that can still be played and studied.
The Retromart verdict
Homebrew is one of the healthiest parts of retro gaming because it turns old systems from static collectibles back into living platforms. The strongest projects respect the hardware without being trapped by old habits. They use modern knowledge to create something that could only exist on that machine.
For players, the scene offers new reasons to reconnect original consoles. For developers, it provides a focused way to learn game design. And for collectors, a thoughtfully produced new cartridge can tell the next chapter of a console’s story rather than merely imitate its past.