Pokebonk Not Loading? Browser & Save Fixes
Fix a black screen, missing 3D scene, stutter or missing run result in Pokebonk, with settings to check and the details worth including in a bug report.
Quick answer
Check WebGL and hardware acceleration first, then lower graphics and disable battery saver. If a run result is missing, note the version, mode, region and time before contacting the game's Discord.
Most Pokebonk problems are browser problems. The game is a WebGL build served from a single site, so a black screen, a missing 3D scene or sudden stutter usually points at graphics settings, a blocked script or a device that is thermal-throttling.
Checked against Beta v0.7.3 menus and release notes through v0.6.4.
Symptom → first check
| Symptom | First thing to try |
|---|---|
| Black screen, no menu | Enable hardware acceleration and WebGL, then reload |
| Menu loads, 3D scene stays empty | Lower graphics quality; disable battery saver |
| Heavy stutter after a few minutes | Check thermals and battery saver; close other GPU-heavy tabs |
| Controls feel delayed | Switch aim mode; check frame rate before blaming input |
| Run result missing | Note version, mode, region and time, then report |
| Guest progress vanished | Check whether site data or the browser profile was cleared |
| No sound in Safari after tab switching | Update Safari and reload; audio recovery was reported in v0.6.4 |
| Map shows nothing useful | Expected since v0.6.0: only explored areas are revealed |
Graphics settings that matter
Open Settings → Graphics and look for:
- Quality preset — lower it first. This is the single biggest lever on weak hardware.
- Battery saver — caps rendering at 30 FPS and lowers resolution. Good for a laptop on battery, bad if you are trying to dodge precisely.
- Hide my attacks / own-attack opacity — reduces visual noise. If you cannot see telegraphs, turn your own effects down instead of turning theirs up.
- Camera distance — a wider camera shows more of the wave but makes small hazards harder to read.
WebGL and browser checks
- Open a WebGL test page in the same browser. If it fails, the problem is the browser or driver, not Pokebonk.
- Update the browser and, on desktop, the graphics driver.
- Disable extensions that block scripts or canvas on the game's domain.
- Try a private window with extensions disabled. If the game works there, re-enable extensions one at a time.
Missing run results
The release history describes several fixes in this area:
- v0.5.7 — earned results recorded after a closed or reloaded browser or a lost connection.
- v0.6.3 — recovered run results that had been incorrectly rejected; stricter validation of edited currency and zones cleared without damage.
- v0.6.4 — fewer legitimate runs incorrectly sent for review, particularly on poor connections.
None of these guarantees that a specific lost run can be restored. If a result is missing:
- Do not clear site data.
- Record the version, mode, region, elapsed time and what you saw on screen.
- Report it through the game's own Discord or in-game report flow.
This wiki cannot access accounts, saves or leaderboards. We can only explain what the release notes say.
Guest progress
Guest progress lives in browser storage. Clearing site data, switching browsers or using a different device will lose it. If you care about the history, create an account.
The v0.6.1 notes describe a Guest-progress fix around Exit and signing back in. If you hit a case that still looks wrong, capture the sequence before reporting it.
Mobile
- Play in landscape.
- Close background apps before a long run.
- Battery saver helps heat but costs frame rate.
- If the screen flickers with battery saver on, update to a build after the v0.6.0 fix and retest.
What to include in a bug report
A useful report saves everyone time:
- game version (under the logo)
- browser and operating system
- desktop or phone model
- mode, region, difficulty and approximate run time
- what you expected and what happened
- a screenshot or short clip
- whether you had just updated
Do not include your password. The game's staff do not need it.
Sources and scope
Settings names and release-note summaries come from the game's public menus and version history. We have not reproduced every bug, tested physical iOS devices, or measured frame rates across hardware. This page is a triage checklist, not a repair service.