Your next visit
to Los Santos.

In Chrome, open chrome://settings/system. Turn on Use graphics acceleration when available, then choose Relaunch. In Edge, open Settings → System and performance and enable the equivalent setting, then restart Edge. Reopen this page and run the checks again.

This fixes one cause of unavailable WebGPU, not every loading freeze. If it still stops, collect the first red console error and check chrome://gpu or edge://gpu. Do not disable antivirus or use unsafe GPU flags.

These change actual engine settings. FPS values are caps, not promised frame rates. Compare presets in the same scene after shaders finish loading.

The light profiles lower scene complexity and disable shadows. Uncapped mode can increase heat and power use; return to 30 or 60 for normal play. More reserved RAM does not automatically increase FPS.

The light profile normally uses 2 logical cores to reduce memory use. If your device has memory to spare, compare 4 cores in the same scene and watch the FPS counter (press =). Four cores may improve simulation speed or increase memory use and stuttering.

Standard controller mapping is included in this browser game and the updated local launcher. The separate enhanced launcher also adds the experimental cheat panel and development-map launcher.

1. Connect an Xbox-compatible or PlayStation controller by USB, or pair it in your computer's Bluetooth settings. Put the controller into pairing mode using its manufacturer's instructions.
2. Open the game in Chrome or Edge and press a controller button so the browser can detect it.
3. Click the game to capture the mouse. Left stick moves; right stick looks. View + Menu switches on-foot/driving mappings, or click the controller status button. In the enhanced launcher, use the F7 panel.

This maps a standard gamepad to keyboard/mouse input; it is not native analog vehicle support. Disconnect other controllers when troubleshooting. In the enhanced launcher, F7 opens controller/cheat controls; F8 hides the extra controls together.

This guide works on mobile, but the game needs WebGPU, 64-bit WebAssembly memory, shared memory and substantial RAM. A responsive page cannot supply missing browser capabilities. Experimental touch controls appear on touch-first devices; use ?touch=1 to force them or ?touch=0 to disable them. Hold the arrows to move/drive and drag the camera area to look. Buttons provide aim/fire, vehicle entry, jump/handbrake and basic menus. These map to keyboard/mouse input; aircraft and every menu are not covered. Multi-touch input logic is tested, but phone gameplay is not yet verified. A phone that opens this page is not necessarily able to run the game.

Mac support is experimental. Use a current Chrome or Edge build, run the checks here, and use a keyboard and mouse or the enhanced launcher with a controller. Safari and mobile browsers are not certified by this project.

Shared-world multiplayer and GTA Online are not implemented in this browser snapshot. Sharing this address opens separate single-player games; it does not join a friend's world.

Real multiplayer needs engine access to entities, player input and world state, plus an authoritative server and synchronization. FiveM's native client cannot be dropped into this WebAssembly build. Follow the multiplayer feature request for progress and technical discussion.

Free disk space stores the download; RAM and GPU memory run the game. A loading timer alone does not prove that memory is exhausted. An error such as memory access out of bounds can also be an engine bug, so buying more RAM is not a confirmed fix.

If loading stops at 24% or another percentage, note the last loading message, check that all 14 archives finished installing, and collect the first red browser-console error and any failed Network request. Try the lower-memory option above. Include your actual RAM, GPU, browser version, and Story/Sandbox choice in the report.

Close the game tab and try the lower-memory link above. Compare Story and Sandbox modes. If the world stays black, open browser developer tools (F12 on Windows; ⌥⌘I on Mac), capture the first WebGPU / shader errors, and attach them with these diagnostics to issue #2. A working menu does not prove that world shaders or all game files loaded.

Close every game tab, stop the local server with Ctrl+C if you use one, and launch again. Update the browser and graphics driver (macOS updates supply Mac drivers). Check chrome://gpu or edge://gpu for hardware acceleration and Problems Detected. Close GPU-heavy apps. Post the first error and diagnostics to issue #1.