Partner Shop
Enjoy our articles? Add us as a preferred source on Google:
This C64 port brings Hyrule, dungeons, saves, music, and classic adventure magic to Commodore hardware.
A Familiar Adventure Finds New Hardware
There’s something wonderfully strange about seeing Link step into Hyrule on a computer that was never meant to host him. Yet this ambitious C64 port is already far beyond a simple technical demo, with most of the familiar adventure functioning on real Commodore hardware.
A developer working under the name Goldfinger is adapting The Legend of Zelda for Commodore 64, using annotated assembly code prepared by Aldo Nunez as a foundation. That technical starting point matters. The project isn’t merely recreating the game’s appearance from scratch; it is using carefully documented low-level code to bring the original adventure’s systems across to a very different machine.
The current build runs from an EasyFlash 3 cartridge and automatically detects whether the system is using PAL or NTSC video. That might sound like a small convenience, but it removes one of the classic headaches of retro hardware projects: making sure the game behaves correctly across regional display standards.
More importantly, the build already contains the broad shape of the complete adventure:
- The full overworld of Hyrule
- Underground dungeons
- Enemies and combat
- The item screen
- The opening sequence
- Music and sound effects
- Character creation
- Progress saving directly to the cartridge
That is an impressive checklist for any homebrew conversion. It also means this isn’t just a character wandering around a single test room while someone proudly points at a working sword swing. The adventure structure is present, and the cartridge can remember your progress.
A Real Commodore Has Already Handled the Quest
The next question is obvious: does it actually play, or does it merely exist in screenshots and development notes?
Goldfinger brought an early version to a gathering for retro-computer enthusiasts, where one participant completed the game from beginning to end on a genuine Commodore 128. The run reportedly finished without crashes, which is the kind of practical test that carries more weight than a polished menu or a confident progress update.
The build still has some rough patches. Certain boss rooms suffer from slowdowns, and those moments are a reminder that the Commodore 64 has to work much harder here than the Nintendo Entertainment System did. Even so, optimization has brought the overall speed close to the NES version.
That comparison is crucial. A port can contain every enemy, room, and item while still feeling sluggish enough to lose the original game’s rhythm. Zelda depends on quick movement, clean reactions, and the satisfying snap of a sword strike. A few badly timed pauses would change the experience considerably.
At first, I expected the Commodore version to feel like a fascinating but compromised curiosity: recognizable, playable, and slightly sticky under the fingers. That impression has softened after hearing that the full game has already been completed without crashes. It still needs refinement, especially in boss rooms, but it sounds much closer to a proper conversion than a museum-piece experiment.
The developer believes further optimization could remove those slowdowns altogether. That remains uncertain, naturally. Old hardware projects have a habit of revealing one stubborn problem just when another appears to be solved. Still, the comparison with the Commodore 64 version of Super Mario Bros. is telling: that conversion never managed to eliminate its own performance drops, while this Zelda project may yet do so.
The Cartridge Is Doing More Than Holding the Game
The technical target is almost as interesting as the game itself. Goldfinger is trying to fit the project into 128 KB, matching the memory size of the original NES release.
The current build has edged slightly beyond that limit, so the team is still working on compression, code efficiency, and graphical refinement. That memory goal gives the project a satisfying old-school discipline. Modern development often assumes that space is plentiful; classic console and computer games were built around the opposite idea. Every animation frame, sound effect, and room layout had to justify its existence.
There is also a practical benefit to the cartridge format. Saving progress directly to the cartridge means players don’t have to treat the game as a one-sitting challenge. Zelda has always invited wandering, experimentation, and the occasional reckless dive into a dungeon before collecting enough equipment. Being able to stop and return later makes the conversion feel much more like a complete adventure.
Some bugs still need to be found through continued testing, and the graphics remain under development. That isn’t a criticism of the project so much as a reality check: a playable build and a finished release are very different creatures. The former can surprise you with what it achieves; the latter has to survive people trying every suspicious wall, bush, staircase, and corner.
One detail deserves a raised eyebrow, too. According to the developer, no neural-network tools were used during development. Whether that changes the final experience is debatable, but it does underline the hands-on, code-first nature of the work. This is being shaped through low-level programming and testing rather than automated shortcuts.
Nintendo May Be the Bigger Obstacle
The strangest part of the project may be what happens after the technical work is complete. The main obstacle might not be memory, speed, graphics, or compatibility. It could be the legal reality of releasing a fan-made version of a Nintendo property.
Goldfinger would like to publish the source code so other developers could improve the port and reuse its engine. That would be valuable for the wider Commodore scene, particularly because the project is tackling difficult problems involving memory, timing, storage, and compatibility. Open code could turn one impressive conversion into a useful foundation for future work.
There is understandable hesitation, however. Nintendo is known for protecting its intellectual property, and releasing both a playable conversion and its underlying engine could attract more attention than keeping the project within a small retro-computing circle.
That tension gives the project an unusual shape. The build appears to be ready enough for serious play, but its public future is less certain. I’m not entirely sure whether it will emerge as a broadly distributed release, remain available through specialist retro-computing channels, or change form before that happens. The technical side feels increasingly concrete; the release strategy feels much less settled.
A Disk Drive Version Would Complete the Circle
If the project does reach players, Goldfinger plans to add loading from the 1541 disk drive at a later stage.
That would be a fitting addition. The original game debuted in Japan on the Famicom Disk System, so a disk-based Commodore version would echo an important part of its early history. It also suits the personality of the C64. The cartridge build offers convenience and speed, while the disk version would bring back the ritual of loading an adventure from removable media—the whirring drive, the patient wait, and the sense that something substantial is slowly arriving.
Neither format is automatically better. A cartridge is practical and sturdy, especially for a game with saving. A disk version would feel historically appropriate and perhaps more authentic to the period’s home-computer atmosphere. The best outcome would be having both options available.
For now, the existing build already demonstrates the important part: Hyrule can function on Commodore hardware. The world is there, the dungeons are there, the soundtrack and effects are in place, and someone has completed the full quest on a real machine. That is a long way from an early proof of concept.
Where to Find the Current Build
The current version can be located through its CSDb release page, while development discussion is available through the Lemon64 forum. The build should be approached as a work in progress rather than a perfectly finalized commercial-style release.
That distinction matters because the remaining issues are visible: boss-room slowdowns, unfinished graphical touches, bugs still waiting to be discovered, and the unresolved question of how openly the code can be shared. Even with those caveats, the project has crossed the line from “interesting idea” to “playable adventure.”
And that’s the magic of these conversions. They make familiar games feel slightly unfamiliar again. The map is known, the enemies are expected, and the item screen has been memorized by generations of players—but place the whole thing inside a Commodore 64, and suddenly every room carries a little extra tension.
Conclusion
This C64 port of The Legend of Zelda is already a remarkably complete piece of retro engineering. It brings the full Hyrule adventure, saving, audio, dungeons, and combat to Commodore hardware while aiming for the tight memory limits of the NES original. The remaining slowdowns and release concerns are real, but they don’t erase what has already been achieved. Would you try the quest on a Commodore 64 or Commodore 128 if the finished build becomes widely available?
FAQ
- What is this C64 port of The Legend of Zelda?
It is a Commodore 64 conversion of the original Zelda adventure, including Hyrule, dungeons, enemies, music, sound effects, saving, and the item screen. - What hardware does the current build use?
The build runs from an EasyFlash 3 cartridge and has also been completed on a real Commodore 128. - Does the port support both PAL and NTSC systems?
Yes. The current build detects whether it is running on PAL or NTSC hardware. - Are there performance problems in the game?
Some boss rooms still experience slowdowns, although the overall speed has reportedly been optimized to roughly match the NES version. - Will the game support 1541 disk loading?
That is a planned addition. The developer intends to add loading from the Commodore 1541 disk drive in the future.
Want more stories about unusual hardware conversions, homebrew experiments, and forgotten corners of gaming history? Subscribe to the newsletter for new articles delivered directly to your inbox.
