
Pokémon Diamond (the 2006 DS game) in your browser — with a ROM you supply
This page is about Pokémon Diamond, released for the Nintendo DS in 2006 — the first pair of the fourth generation, not Brilliant Diamond on Switch. It runs in our browser emulator from a ROM you backed up from your own cartridge, but the DS is the first machine on this site with two screens and a touchscreen, so this page spends most of its words on that instead of repeating the plot.
Open the player (upload panel already open)File you need: .nds
What the 2006 game is
Pokémon Diamond and Pearl were released for the Nintendo DS on 28 September 2006 in Japan, 22 April 2007 in North America, 21 June 2007 in Australia, 27 July 2007 in Europe and 14 February 2008 in South Korea. They are the fourth generation, and the first Pokémon games built for the DS rather than the Game Boy line.
The changes that stuck are worth naming: 107 new Pokémon, the physical/special split that made moves behave differently depending on what they hit, and Nintendo Wi-Fi Connection support for trading and battling over the internet using Friend Codes — a service that has since been discontinued, so the online half of this game is gone for everyone, emulated or not.
The touchscreen half still works, and it is the part that survives: the Pokétch is a simulated smartwatch that lives on the bottom screen, hosting a clock, a calculator, a step counter and a map. It is the DS’s second screen used as a tool rather than a second view, which is a distinction most later games dropped.
Two screens and a touchscreen: how this actually works in a browser
On a DS the screens are stacked, top above bottom, with a gap. In a browser emulator that physical gap does not exist, so the core renders both screens into one tall picture: you get the top screen on top and the bottom screen directly below it, on one canvas. Nothing is hidden and nothing needs configuring — but it does mean the picture is roughly twice as tall as it is wide, and on a laptop that is small. Use the emulator’s fullscreen button rather than zooming the page.
The touchscreen is the bottom half of that canvas, and your mouse is the stylus: click or tap inside the lower half and the emulator passes the point through as a touch. Two things follow from this. First, if clicking does nothing, check you are clicking the lower half, not the top screen. Second, a mouse is absolute where a finger is not — for drag gestures, press, move, release, rather than flicking.
What you cannot do is local wireless. DS multiplayer worked over a short-range radio link between consoles; there is no equivalent in a browser tab, so trading with a friend in the same room is not available here. The single-player game is complete and unaffected.
One more layout note, because it catches people on phones: a portrait canvas is the right shape for a DS game, so hold the phone upright rather than turning it sideways — turning it makes each screen smaller, not bigger. And the first load genuinely takes time: the core has to arrive and then the ROM has to be read into memory. If the tab looks frozen for a while on a large file, that is the load, not a crash — but if the tab is using a lot of memory, close other tabs first.
How to run it here, step by step
The ROM is read locally in your browser tab; nothing is uploaded to us.
- Open the player from the link at the bottom of this page — /play/ with the upload panel open.
- Drop in your file. You need a .nds dump of Diamond from your own cartridge — this is the only accepted extension for DS games here.
- Expect a wait: a DS ROM is tens of megabytes, two or three orders of magnitude bigger than a Game Boy ROM, and the DS core itself is a larger download than the 8- and 16-bit ones. The waiting is your own disk being read into browser memory — not a download from us, because there is nothing on our side to download.
- A .zip is fine, by the way. The emulator unzips a ROM archive itself and packs are supported too, so you do not have to extract first. If the archive holds a single ROM it just runs; if it holds several, the player asks you which platform you want, which is a normal step rather than an error.
- Practical advice up front, and it is measured rather than guessed: play this on a computer. We loaded a 64 MB DS ROM in a real browser on both a desktop and a phone, and timed it. Picking the file gives immediate feedback — the loading notice appears, so you are not staring at a blank panel — and then the main thread blocks once for a noticeable pause. After that it runs smoothly. So that pause is the normal load, not a freeze.
- The reason to prefer a desktop is the two-screen layout, not raw speed: a dual-screen picture squeezed onto a phone is small, and you are asked to tap the lower half accurately. Desktops also have the memory headroom for the file plus the core plus your saves.
- The DS core is selected automatically from the .nds extension. First launch fetches it and caches it; subsequent visits are much faster.
- Press Enter (Start), check that the bottom screen responds to a click, then save in-game before doing anything else.
Keyboard and touch mapping
The DS face buttons map onto the same keys as the other handheld platforms, and the mouse becomes the stylus. The microphone button exists in the control scheme but has no default key — nothing in Diamond requires it, so leave it.
| DS button / input | Keyboard or mouse |
|---|---|
| D-Pad | ↑ ↓ ← → |
| A | Z |
| B | X |
| X | A key |
| Y | S |
| L / R | Q / E |
| Start | Enter |
| Select | V |
| Touch screen | mouse click / tap on the lower half |
| Microphone | unbound by default |
Saving, and why DS saves deserve a warning
Diamond saves in-game to the cartridge image, and that write lands in browser storage. A DS save is much larger than a Game Boy save: the game keeps a full party, boxes, the Pokédex, the Pokétch settings and a lot of flags, and the emulator also needs room for the save states you take.
So: take save states sparingly on a low-memory machine, export the in-game save to a file once you have a team you care about, and if the tab starts behaving strangely after a long session, reload and continue from the exported save rather than assuming the game broke. Browser storage is not infinite and it is not backed up for you.
Rough sense of scale: a DS save is measured in hundreds of kilobytes where a Game Boy save is a few kilobytes, and each save state is larger still because it captures the whole emulated machine. Ten states on a Game Boy title is nothing; ten states on a DS title is a real amount of storage. Export the in-game save, keep two or three states, and you will not run into the ceiling.
On the legal side: we provide no file and no link to one. Use a dump of your own cartridge, and check what your own jurisdiction permits. This title is sold through Nintendo’s own services, which is the clean route if you want one.
More in this series
Legal games you can play right here, without providing anything
These are open-source homebrew games hosted by this site. They start in one click — no ROM needed, because their authors released them for redistribution.
FAQ
Is this Diamond or Brilliant Diamond?
Diamond, the 2006 Nintendo DS original. Brilliant Diamond (2021) is a Switch remake and a different ROM.
Which file do I need?
A .nds dump of your own cartridge. It is the only extension accepted for DS games here.
Why does the game look like one tall picture?
The DS has two screens; the emulator renders both into a single canvas, top screen above bottom screen. Fullscreen is the fix for the small size.
Does the touchscreen work?
Yes — the mouse is the stylus. Click in the lower half of the picture. The microphone has no default key and Diamond does not need it.
Can I trade or battle with another player?
No. DS local wireless has no browser equivalent here. The single-player game is complete.

