Pokémon Gold & Silver

About this build

Pokémon Gold and Silver built from the pret/pokegold disassembly with rgbds 1.0.4, byte-identical to the retail cartridges, running in the browser on a WebAssembly Game Boy Color core. You supply your own ROM: it is read with FileReader, kept in the tab's memory and never uploaded, and the page recognises Gold or Silver by its SHA-1. Battery saves persist in this browser.

Built from

The real ROM, built byte-for-byte from the pret/pokegold disassembly, running on the libretro Gambatte core (EmulatorJS 4.2.3, WebAssembly)

Type

Decompilation

Game files

You supply your own Pokémon Gold or Silver ROM (2,097,152 bytes). It is read in the browser and never uploaded. Gold sha1 d8b8a3600a465308c9953dfa04f0081c05bdcb94, Silver sha1 49b163f7e57702bc939d642a18f591de55d92dae — the same ROMs this project's build produces.

Code licence

EmulatorJS is GPL-3.0 and the Gambatte core is GPL-2.0; the pret/pokegold disassembly is unlicensed research. See web/THIRD_PARTY.md.

Assets

No game data is distributed. Everything comes from the ROM you load.

Source

andrewnakas/pokegold-web ↗

What has been tested

Both ROMs build byte-identical to the retail cartridges (sha1 verified against pret's roms.sha1 and against the staged dumps). In the browser: loaded through the page's own file picker, ran at 60 fps, played the opening through to the bedroom in New Bark Town, walked, saved in game, reloaded the page and resumed from the save — the restored save decodes with the game's own SAVE_CHECK_VALUE_1/2 and the player name that was typed, read using the symbol table of the build under test. Nothing past the first house was played; audio was muted throughout.

Last tested 2026-10-05 in Chrome 151 (headless, Linux). Full playthrough: not verified. How games are tested.

Known limitations

• Only the opening was play-tested — up to the bedroom in New Bark Town, an in-game save, a reload and a resume. Nothing after that has been exercised.
• Audio is unverified: every test ran muted.
• Only tested in headless Chrome on Linux. Firefox, Safari, iOS, Android and the on-screen controls are untested.
• Real-time-clock behaviour over days — day/night, the Bug-Catching Contest, the lottery — is untested.
• Link trading and battling are not possible in a single browser tab.

Saves

Save in game the normal way (START → SAVE). The battery save is kept in this browser's storage, per game, and survives a reload. Clearing site data removes it.