Dragon Ball Z: Budokai 2 Web Online

About Dragon Ball Z: Budokai 2

Dragon Ball Z: Budokai 2 Web Online is a third-party browser build of the 2003 PlayStation 2 fighting game. It runs in a browser tab with nothing to install, and the player link opens the host site.

Budokai 2 was developed by Dimps and published by Atari. It is a 3D fighting game based on Dragon Ball Z, known for its board-game style Dragon World story mode. Browser builds like this one are unofficial and can disappear without notice.

Original release

2003 (PlayStation 2)

Original developer

Dimps

Genre

Fighting

This build

Browser, third-party

Project summary

Dragon Ball Z: Budokai 2 is a browser port: it runs the original game in a web browser tab, with nothing to install. It is listed as a fighting game. Its link was responding when we last checked on November 4, 2026.

Dragon Ball Z: Budokai 2 at a glance

Type

Browser port

Original platform

Browser games

Plays on

Web browser (budokai2onlline.cc)

Link status

Working

Last checked

November 4, 2026

Listed since

October 26, 2026

How to play Dragon Ball Z: Budokai 2

1. Press Play. The game loads in our player, or on the project's own site if it can't run here.
2. Use a desktop browser such as Chrome, Edge or Firefox for the best performance. The first load can take a minute because the game data downloads before it starts.
3. Click inside the game window so it captures your keyboard. Most ports also accept a USB or Bluetooth controller through the browser's Gamepad API.

Tips

• Fighting games need precise input: use a controller connected before you open the player.
• Play on a desktop browser for stable timing.

If Dragon Ball Z: Budokai 2 will not load or runs slowly

1. Refresh the page and wait for the full download bar to finish before pressing anything.
2. Disable ad blockers and privacy extensions for the game's domain—they sometimes block WebAssembly.
3. Enable graphics acceleration and try another browser (Chrome or Edge first).
4. If only you have the problem, clear the site cache or try a private window.