Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/ClassicUO/classicuo-web/llms.txt

Use this file to discover all available pages before exploring further.

Before spending time troubleshooting in-game problems, it’s worth confirming that your browser and graphics hardware are actually capable of running the ClassicUO Web Client. This page lists the supported browsers and provides a set of quick test links that check WebGL, WebAssembly, and overall browser speed — all of which the Web Client depends on.

Browser Support

Not all browsers are equal when it comes to WebAssembly performance and storage quota. Use the table below to choose the right browser before you start.
BrowserStatusNotes
Chrome✅ RecommendedBest overall compatibility and WebGL performance
Chrome (installed as app)✅ RecommendedStandalone window, no tab bar, persistent storage, fewer hotkey conflicts
Microsoft Edge✅ SupportedSame Chromium engine as Chrome; often grants a larger storage quota and is a great choice for a dedicated game browser
Brave❌ Not supportedAggressive fingerprinting and storage restrictions break the Web Client
Firefox❌ Not supportedWebAssembly threading model differs; not compatible at this time
Safari❌ Not supportedMissing WebAssembly features required by the client
Incognito / Private mode❌ IncompatibleStorage is severely limited (often under 100 MB); game files cannot be downloaded
Microsoft Edge is built on the same Chromium engine as Chrome, so all chrome://flags tips in the performance guide have equivalents at edge://flags. Edge is an excellent choice if you want a dedicated browser for the game.

Is WebGL Working?

The Web Client renders entirely through WebGL 2. Use these two pages to confirm your browser can run WebGL and that it is using your real GPU rather than a slow software fallback.
1

Check for WebGL 2 support

Open the following URL in your browser:
get.webgl.org/webgl2
If you see a spinning, colourful cube, WebGL 2 is working correctly. If the page shows an error or a blank canvas, your browser does not have WebGL 2 enabled — revisit the performance troubleshooting guide to enable hardware acceleration.
2

Check which GPU is being used

Open the WebGL report page:
webglreport.com/?v=2
Find the Unmasked Renderer field. It should show the name of your real graphics card (e.g. NVIDIA GeForce RTX 3060, AMD Radeon RX 6700, Intel Iris Xe).
If the Unmasked Renderer shows any of the following values, your browser is using slow software rendering instead of your GPU. Performance will be unacceptably poor — follow the performance guide to fix it before playing.
  • Google SwiftShader
  • llvmpipe
  • Apple Software Renderer

GPU Benchmark Tests

These tests measure how quickly your GPU can process graphics workloads in the browser. They are optional but useful if you want a baseline before and after applying performance fixes.

WebGPU Stress Test

Pushes your GPU hard to surface thermal and driver issues under load. Good for checking stability.

GPU Benchmark with FPS Graphs

Runs a rendered benchmark and plots live FPS graphs so you can compare performance across settings.

Is WebAssembly Working?

The ClassicUO Web Client is compiled to WebAssembly. If WebAssembly is disabled or broken in your browser, the client will not load at all. Run this quick check:
wasm.joway.io
The page gives a simple yes/no result. If it says WebAssembly is not supported, check that your browser is up to date and that no enterprise policy or extension is blocking it.

Overall Browser Speed

Speedometer measures how quickly your browser can execute JavaScript and update the DOM — a good proxy for general responsiveness.
browserbench.org/Speedometer3.1/
A score above 20 is generally comfortable for the Web Client. Lower scores may indicate that the browser is throttled, running in a VM, or that the machine itself is under heavy load.
Once all tests pass, head to the Quick Start guide to get in game, or continue to the performance troubleshooting page if you want to fine-tune your setup first.

Build docs developers (and LLMs) love