Why play.hypersomnia.io Is Stuck on "Downloading... 0%"

Updated

The "Downloading... 0% 0 MB" screen is the game's asset loader, not the game itself. If it stays at 0% with 0 MB, your browser has not received any game files yet, so the problem is almost always network-side: a blocked request, a proxy or firewall, an extension, or a browser that can't run the Web build. Work through the checks below in order — the first two resolve most cases.

What the loader is actually doing

Hypersomnia is a free, open-source competitive 2D shooter that runs in the browser. Before you see a menu, the page fetches the game's asset bundle and reports progress as a percentage and a size in MB. A frozen "0% 0 MB" means the first request never completed, so nothing has been counted yet. That distinguishes it from a loader that climbs slowly — slow is a bandwidth issue, zero is a connection or blocking issue.

Quick checks, in order

  1. Hard refresh. Reload with Ctrl+Shift+R (Windows/Linux) or Cmd+Shift+R (macOS) to bypass a cached, incomplete response.
  2. Try a private/incognito window. If it loads there, an extension is interfering — commonly ad blockers, privacy shields, or script blockers. Disable them for this site and reload.
  3. Check your network path. Corporate networks, school filters, VPNs, and some DNS-level blockers can drop the asset requests. Switch to a different network (for example, a mobile hotspot) and reload.
  4. Confirm the browser can run it. Use a current version of Chrome, Firefox, or Edge with hardware acceleration enabled. Very old browsers or strict "JavaScript disabled" settings will stall the loader.
  5. Look at the browser's developer tools. Open DevTools (F12) → Network tab, reload, and check whether requests are failing (red status) or pending forever. A failed request confirms blocking rather than a game bug.

If it still won't load

  • Wait and retry later. The loader depends on the host serving assets; a temporary outage on the site's side looks exactly like a local block. Retrying after a few minutes is a reasonable next step.
  • Check free disk and memory pressure. A browser tab with very little free memory can fail to buffer large assets. Close other heavy tabs and reload.
  • Try another device on the same network. If a second device also stalls at 0%, the cause is the network or the host, not your machine.

What this screen does not tell you

The page evidence shows only the loader state, so there is no basis to claim a specific failure reason, a required login, or a paid tier. Treat "0% 0 MB" as "no data received yet" and test the network path first; that is the check most likely to change the outcome.