Updated Oct 13, 2026 · 2 more we checked and added
Two separate projects run Duke Nukem 3D in a browser tab, both built on EDuke32, the long-running community version of the Build engine compiled to WebAssembly.
Both bundle the free shareware episode, so you can start right away in 6 to 12 MB. webduke also loads your own full game data and hosts invite-link games, while the GitHub Pages build adds peer-to-peer co-op and deathmatch.
Shareware episode, single-player and invite-link multiplayer (beta)
Controls
Mouse look · WASD or arrows move · Ctrl or Space fire and jump · Esc release the mouse
Host
gawen.me
Download
~12 MB (measured Oct 13, 2026)
Phone
Phone: limited
webduke runs the EDuke32 engine compiled to WebAssembly, with the shareware episode bundled (about 12 MB). You can load your own DUKE3D.GRP for the full game and host invite-link multiplayer games, which are in beta. A diagnostics option sends technical traces to the game server; the page says no personal data or gameplay content is collected. On phones it asks you to rotate to landscape.
Opens a third-party site. Skip anything that asks you to install a launcher or extension.
EDuke32 WASM (Duke Nukem 3D)
Status
Free demoLink up on Oct 13, 2026
Mode
Shareware episode, single-player plus peer-to-peer co-op and deathmatch
Host
digitalcybersoft.github.io
Download
~6 MB (measured Oct 13, 2026)
Phone
Phone: limited
A second EDuke32 WebAssembly build, hosted on GitHub Pages. It loads the shareware 1.3D episode in about 6 MB and opens with the 3D Realms intro. Co-op and deathmatch run peer to peer over WebRTC, with no game server in between.
Opens a third-party site. Skip anything that asks you to install a launcher or extension.
Two ways to play Duke Nukem 3D in browser
You can play Duke Nukem 3D in browser through two independent projects, webduke and EDuke32 WASM. Both run EDuke32 compiled to WebAssembly, both bundle the free shareware episode, and neither asks you to install anything. Where they differ is size, multiplayer and what else they let you do.
webduke: about 12 MB in our test, most of it the shareware DUKE3D.GRP data file. It opens with a DOS-style boot screen, lets you load your own DUKE3D.GRP to play the full game, and offers invite-link multiplayer, which is still in beta.
EDuke32 WASM: about 6 MB, hosted on GitHub Pages. It loads shareware version 1.3D, plays the 3D Realms intro and supports co-op and deathmatch that run peer to peer over WebRTC.
About Duke Nukem 3D (1996)
Duke Nukem 3D was developed by 3D Realms and released in 1996. It ran on the Build engine, written by Ken Silverman, which was known for detailed, interactive levels: light switches, mirrors, working toilets and buildings you could walk into. The shareware episode, L.A. Meltdown, sends Duke through a ruined Los Angeles overrun by aliens, and its one-liners became as famous as its levels.
Many people played that shareware episode first, because it was given away on disks and magazine CDs. It is the same episode both browser builds include today.
What EDuke32 is
3D Realms released the game's source code under the GPL in 2003 (the Build engine had its own source licence). The game data, including the levels, art and sound in the full DUKE3D.GRP, stayed commercial. Community programmers then built source ports on that code. EDuke32 is one of them, maintained for many years with modern features and support for current systems.
That split is why the browser builds work the way they do. The engine is open source and can be compiled to WebAssembly by anyone. The shareware data could be shared freely. The full game data still belongs to the rights holders, which is why webduke asks for your own DUKE3D.GRP rather than shipping it.
Controls in webduke
webduke lists its default controls on the page; besides the Esc key covered in the tips, they are below. We did not find a published list for the EDuke32 WASM build, so check its menus once the game loads.
Mouse: look around.
WASD or the arrow keys: move.
Ctrl or Space: fire and jump.
Multiplayer and privacy
The two builds handle multiplayer differently. webduke creates an invite link that you send to friends; this mode is still marked beta, so expect rough edges. EDuke32 WASM connects players directly to each other over WebRTC, so there is no game server in between.
webduke also has a diagnostics option that sends technical traces back to its game server. The page says no personal data or gameplay content is collected. If you would rather not send anything, leave that option alone.
Phones and tablets
Neither build is a phone game. On a phone, webduke asks you to rotate the screen to landscape, and EDuke32 WASM showed its download progress, but we could not confirm comfortable touch play in either. Duke Nukem 3D was designed for a keyboard and mouse, and that is still the best way to play it.
Which Duke Nukem 3D in browser build should you pick?
Just want to play the shareware episode quickly: EDuke32 WASM, which is the smaller download.
Own the full game: webduke, the only one of the two that takes your own data.
Playing with friends: either one. webduke uses an invite link (beta); EDuke32 WASM uses peer-to-peer co-op or deathmatch.
For other shooters from the same years, see Doom in browser, which includes an online multiplayer build, and Wolfenstein 3D in browser, the id Software game that came before Doom.
Tips before you play
Click into the game to capture the mouse, and press Esc to release it.
Own the full game? Load your DUKE3D.GRP in webduke to play every episode.
For multiplayer, send friends the invite or room link instead of a screenshot of your screen name.
FAQ
Is Duke Nukem 3D in browser free?
The shareware episode is free. The full game needs a DUKE3D.GRP file from a copy you own.
Can I play Duke Nukem 3D online in the browser?
Yes. webduke has invite-link multiplayer in beta, and the EDuke32 WASM build supports peer-to-peer co-op and deathmatch.
Where do I get DUKE3D.GRP for the full game?
It is in the install folder of a copy of Duke Nukem 3D you own. Do not download it from file-sharing sites.
Is webduke the same as EDuke32 WASM?
No. They are separate projects built on the same EDuke32 engine, with different sizes and multiplayer methods.
