The Simpsons: Hit & Run in Your Browser: How to Play (2026)

Play Hit & Run in the browser →

The playable version lives on the project's own GitHub Pages site. You do not need a PS2 emulator, an ISO, or a download — hit-and-run-web converts the original game files into a Three.js runtime that runs directly in the tab. This page is an independent guide; we are not affiliated with the project, Radical Entertainment, Fox, or the rights holders, and the game is not hosted here — the button above opens the project's play page in a new tab.

What is the browser version of The Simpsons: Hit & Run?

It is an unofficial Three.js reconstruction of The Simpsons: Hit & Run (the 2003 action game by Radical Entertainment) that runs natively in the browser, with no emulation of the PS2 executable. The project extracted the PA2/Pure3D geometry, textures, skeletons, animations and mission scripts from a PAL PS2 disc image and converted them for a new web runtime; the repository ships the converted browser assets, so a player never touches the extraction tools. (hit-and-run-web README)

It went viral in October 2026 as people realised a full 3D version of the game could be opened from a link instead of a memory card. The project is explicit that it is not yet a 1:1 port: the campaign runs, but the physics, AI and some side systems are reconstructions, and full playthrough testing is ongoing.

How to play The Simpsons: Hit & Run in a browser

1. Open the play page. Go to vheissu.github.io/hit-and-run-web in Chrome, Edge, Firefox or Safari on a desktop. Nothing installs; the first load streams the converted assets, so give it a moment before the menu appears.
2. Press Start, then New Game. That starts the original campaign. Story progression, bonus missions and races run from the converted mission scripts. (README)
3. Set your options once. Options contains the level, vehicle, lighting and rendering settings — the first place to look if the frame rate is poor or the picture looks flat.
4. Learn the four keys that matter. WASD drives and walks, Space is handbrake and jump, E talks and enters vehicles and buildings, Enter retries a failed mission. The full list is below.
5. Play with a keyboard, touch or a gamepad. Touch driving controls and standard gamepad steering and triggers are supported; full gamepad menu navigation is still unfinished, so use the keyboard for menus. (README)

Controls

| Control | Action | | -------------------- | -------------------------------------------------------------- | | W A S D / arrow keys | Drive or move on foot | | Space | Handbrake; jump, then press again near the apex to double jump | | E | Talk, enter buildings, enter or leave your vehicle | | F | Kick on foot | | Enter | Retry a failed mission | | Shift | Run on foot | | C | Change camera | | B | Look behind | | H | Cruise at 50 km/h | | R | Return to the road and repair | | M | Zoom radar | | P | Hide/show HUD | | Escape | Pause / resume | | F3 | Frame timings and diagnostics |

The project documents this layout in its README; F3 is the quickest way to see whether the browser is the thing limiting the frame rate.

What works, and what is still missing

What is in. Seven level variants and five playable characters with original geometry, animations and HUD artwork; 89 scripted missions across seven chapters (49 story missions, the tutorial, four chapter transitions, seven bonus missions, 21 street races and seven wager races) running on 610 stages with original objectives, timers and checkpoints; police pursuit, heat and the 50-coin capture penalty traced from the PS2 executable; 67 character models, 71 vehicle models and 549 dialogue clips. (README)

Saves. Progress is stored locally: the game resumes from your latest mission checkpoint and keeps coins, purchased cars, outfits and completed missions. Because saves are local to the browser, clearing site data or switching browsers starts you over. (README)

What is not there yet. Traffic lights, parked traffic, boarding ordinary traffic vehicles, gags, free prop motion and debris, collectible-card gameplay and full menu parity are listed as unfinished. Mission AI and the UFO sequence use reconstructed behaviour whose timing and difficulty have not been validated against the original game, and the rigid-body solver, collision response and driver control remain reconstructed systems. (README)

Treat it as "the campaign is playable, the details are still being matched" rather than a replacement disc.

Running it locally or offline

If you would rather not depend on the hosted page, the project ships everything needed to run it yourself: clone the repository (the included assets are about 1.09 GB), install Node.js 24 or newer, then run npm ci and npm run dev -- --port 5174 and open the printed local address. A Docker Compose setup is provided for the same result without installing Node.js. (README)

Note the copyright position before you do this: the converted assets keep their original copyrights, the project is unofficial, and the ISO and raw extracted files are deliberately excluded from the repository.

The Simpsons: Hit & Run browser FAQ

Is this the official Simpsons: Hit & Run? No. It is an unofficial fan reconstruction. The repository states it has no affiliation with the original developers or rights holders, and the original assets retain their existing copyrights. (README)

Do I need a PS2 emulator or a disc image to play in the browser? No. The hosted play page ships with converted assets, and the port does not emulate or recompile the PS2 executable. (README)

Is it free? Yes — the play page is a free, open repository project with no account or payment step. There is nothing to buy on the site.

Can I play it on a phone? Touch driving controls exist, but the project treats desktop browsers as the main target and full gamepad and menu navigation is unfinished. A desktop or laptop with hardware acceleration enabled is the safer choice.

Does my progress save between visits? Yes, locally: the game resumes from your latest mission checkpoint with coins, cars, outfits and completed missions intact. Clearing browser site data removes that save. (README)

Why does it run slowly? The page is a full 3D Three.js scene streamed into the tab. The project exposes rendering and lighting options, and F3 shows frame timings so you can tell whether the browser or the scene is the bottleneck; the README does not publish a minimum hardware specification. (README)

More browser games worth a tab

• Lagos Life — the free multiplayer Lagos life sim that went from launch to a million players in three days, playable in the browser with no download.
• Play Hit & Run in the browser — the play page itself, if you skipped the guide.

Sources

• hit-and-run-web repository and README — what the port is, controls, current work, remaining gaps, local and Docker setup
• Play page — the hosted browser build linked from the README
• ScreenRant: Simpsons Hit & Run is currently playable in your browser — press coverage of the October 2026 release
• Hacker News discussion — community reaction and reports from players

---

Last updated 2026-10-20. The project is unofficial and still in development; features and known gaps change between builds, so check the repository for the current state before relying on any detail above.