OpenCE Brings Halo: Combat Evolved to Your Browser: Setup, Requirements and Multiplayer Limits

What OpenCE is (and isn't)​

OpenCE is not an Xbox emulator and it isn't a streamed video. It is the Halo: Combat Evolved decompilation (Xbox build 01.01.14.2342), ported to Linux, Windows, Android and the web. The project's web documentation says the browser build is the same game and platform layer as the Linux build. It uses the Android build's OpenGL ES renderer, drawing through WebGL 2, and the game is compiled to WebAssembly.

It is also unofficial. The site says it isn't affiliated with Microsoft or Bungie, and calls itself an unofficial fan project.

O'Rourke says this is the second OpenCE-based browser port he has covered. The first one doesn't seem to be active anymore. Other coverage of the wider ecosystem points to several related efforts. Digital Citizen's write-up of a browser build of the decompilation says it ships no game data. The Gamer's early hands-on praised the campaign but had less success with the 128-player mode.

You still need your own copy of the game​

The site hosts no Halo content, and that is the main legal design choice. The maps are copied from your own Xbox disc image into the browser's storage for that site. Nothing is uploaded, and the site serves no game data. O'Rourke notes that you can dump a disc you own, or get the game "from somewhere online". The project's own wording expects you to have your own copy.

Setup, per the project's documentation:

1. Open the site. A panel lists what your browser supports and what is missing.
2. Under Game data, choose a disc image (.iso or .xiso). Alternatively, choose a maps/ folder from an earlier extraction.
3. Wait while the maps copy into browser storage. The documentation estimates about a minute for 2 GB.
4. Choose Play.

O'Rourke says the whole process took only a few minutes. The documentation says every map is validated before it is copied, and it treats the disc image as untrusted input.

Requirements to check before you try​

The documentation is specific about what the browser needs:

• Browser: Chrome, Edge or Firefox on desktop. Safari 17 or later may work.
• Memory: A 64-bit browser that gives the page 2.1 GB. Phones may not, and iPhones are untried.
• Storage: About 3 GB. That is roughly 2 GB for maps and up to about 800 MB for the game's own copies of maps it has played. The disc image stays on your computer.
• Secure context: The site must be served over HTTPS (or localhost). The game's threads need SharedArrayBuffer, which requires a cross-origin isolated page. The site's service worker supplies this, so the page reloads once on your first visit.
• Graphics: Chrome and Edge are named as the fastest. Software rendering without graphics acceleration is warned to be very slow. WebGL 2 lacks some later OpenGL ES features, so supersampling and SMAA are unavailable. FXAA and MSAA are available.

These are the project's claims, not independent benchmarks. If the game stutters, the first thing to check is whether hardware acceleration is enabled in your browser.

Controls and saves​

• Controller: The browser only exposes a gamepad after you press one of its buttons. O'Rourke connected an Xbox Elite Series 2 controller over Bluetooth and says it worked without any configuration. That is one person's setup, not a guarantee.
• Mouse and keyboard: Click the game to capture the mouse, and press Escape to release it. Crouch is mapped to C only, because a page can't keep Ctrl shortcuts like Ctrl+W away from the browser.
• Sound: Audio starts after your first click or key press, because browsers require that.
• Saves: Saves, profiles and config.toml live in site storage. The page asks the browser to keep that data, but a browser short on space can still delete it. Storage is tied to the site's address, so the main site and the GitHub Pages address don't share it.
• Exports: Settings can export saves, profiles and config as a ZIP. That ZIP doesn't include the game's copied maps. It isn't a full backup. You would still re-import maps from the disc.
• Moving saves: O'Rourke says exported saves can move to other OpenCE platforms, such as a gaming PC.

Multiplayer: 128 players versus 16-browser rooms​

The 128-player figure is the headline, and it needs care.

• Capacity: OpenCE supports internet games across browsers and the native Windows, Linux and Android builds. The headline capacity is up to 128 players. A related fork describes multiplayer raised to 128 players and 128 machines.
• Public games: A public game hosted from a browser appears in the in-game server browser alongside native games. Invite links open the site and join the game.
• Rooms: The documentation separately says a browser room holds up to 16 browsers. Everyone who opens the room link is treated as being on one local network. One player hosts a system-link game and the others find it. Anyone with the secret link can join.
• Networking: Browsers connect to each other directly over WebRTC. They find each other through public MQTT brokers over secure WebSockets, with messages sealed. There is no relay. Networks that block WebRTC, such as some company and school networks, can keep a browser out of games and rooms.
• Limits: Browsers have no UDP, so there is no system link with native builds on a local network. Split screen works.

The 128-player mode is not proven to be a 128-browser room. O'Rourke says the game does support up to 128 players in multiplayer and co-op. He also says it wasn't much fun: the port lagged a bit and the matches were too chaotic to follow. He doesn't give his hardware, browser, network or actual player count, so treat that as one anecdote and not a performance finding.

Mods​

The web build can add mods by copying a mod's mod.toml and tags folder into site storage. The game's Mods menu then orders them or turns them off, and the page warns when mods can't be played together. O'Rourke hasn't tested this. He did notice many servers running custom fan-made maps and a Zombies playlist.

Why Windows users should care​

For PC readers, the interesting part is the stack. A 2001 console game is now running on browser features: WebAssembly, WebGL 2, shared memory threads, persistent site storage and WebRTC peer-to-peer networking. It also gives people a way to preserve a game on hardware the original never targeted.

The caveats are real:

• Browser-based doesn't mean zero setup. You still need a compatible disc image, plenty of RAM and storage, and working GPU acceleration.
• The project's legal footing is murky, and The Gamer noted these decompilations exist in a legal grey area. Keeping game data off the server and requiring your own copy is the project's mitigation. Whether it holds up is a legal question, not a technical one.
• Hosting is by volunteers. As the earlier browser port's apparent disappearance shows, sites like this can come and go.

O'Rourke's verdict is that it works well for single-player and for revisiting old maps like Chill Out, Boarding Action, Bloodgulch and Sidewinder. He also reports snappy controls with a slight, tolerable controller delay.

Quick troubleshooting​

• Page says something is missing: Check the panel's list. It tells you what your browser lacks.
• Very slow: Switch to Chrome or Edge and confirm hardware acceleration is on.
• Can't join a game: Try a different network. Corporate and school networks may block WebRTC.
• Saves vanished: Browsers can clear site data under storage pressure. Export saves regularly.