What Is Krunker.io and How Do You Play It in a Browser?
Updated
Krunker.io is a free browser-based multiplayer first-person shooter — you open the page, join a match, and play with mouse and keyboard, with no download required. It runs on any device with a modern browser, though the page itself recommends the official client or Chrome at 60 FPS if you hit performance problems. This guide covers what you actually do in a match, the controls you need, and how to fix the most common loading and lag issues.
What Krunker actually is
Krunker is an "io game" — a lightweight, instantly playable browser game — built around fast-paced competitive FPS matches. The site describes it as free, multiplayer, and playable without downloading anything, and it says millions of players are already in matches.
Two practical consequences follow from that design:
- Entry cost is near zero. No installer, no account required to start playing (though an account matters if you buy items — see below).
- Performance depends on your browser. Because everything runs in the page, browser extensions, background tabs, and frame rate settings affect how smooth the game feels.
How to start playing
- Open the game page in your browser. The site loads a cookie/terms prompt first — you must accept the Terms & Conditions to use the site, or decline and leave.
- Wait for the match to load. You'll see a match-pending state, then drop into a server with other players.
- Pick your setup. The interface exposes customization (brush/prop tools appear in the HUD) and a competitive mode toggle.
- Play the match. Move and shoot with mouse and keyboard; the HUD tracks your FPS, ping, and match state in real time.
Controls you'll actually use
The in-game HUD lists the key bindings directly, so you don't need to memorize them in advance. The ones that matter most:
| Action | Key |
|---|---|
| Move / aim / shoot | Standard mouse + WASD-style movement |
| First-person view | 1–9 |
| Free cam / objective cam | F / H |
| Nametags | . (force nametags) |
| Minimap | = / - |
| Vote kick | 1 yes, 2 no |
| Forfeit match | Type /ff to vote |
Spectating and competitive modes add their own bindings (player/cam switching, KPD vision, focus), which the HUD shows contextually.
Common problems and how to fix them
The game won't load
The page's own error message is specific about this: if Krunker runs into a problem, disable all of your browser extensions and reload the page. If the issue persists, the site asks you to report it on Reddit or Discord.
That's the first thing to try, and it's worth doing before anything else — extensions are the most common cause of a page that loads but never starts.
Lag or low frame rate
The HUD shows FPS, ping, and network throughput, so you can see whether the problem is your machine or your connection. The game's own guidance: if you see a network lag warning, use the official client or Chrome at 60 FPS.
Practical order of checks:
- Close other tabs and background apps.
- Confirm you're on Chrome (or the official client) rather than a heavier browser.
- Check the ping and packet-rate readouts in the HUD to tell connection lag from rendering lag.
You got kicked or a vote is running
Vote-kick and forfeit prompts appear in the HUD with 1 = yes and 2 = no. Forfeiting a match is done by typing /ff to start the vote.
Accounts, purchases, and one important warning
Krunker includes in-game purchases. The payment screen offers Apple Pay, Google Pay, cash, and crypto as methods.
Read this before you buy: the site states plainly that reversing a payment can result in termination of your Krunker account. If you're considering a chargeback or refund dispute, treat that as a real risk to your account rather than a formality.
The page also shows a purchase-request prompt (accept/decline) for in-game item trades, which is separate from buying from the store.
Is it worth playing in a browser?
Yes, if you want a competitive FPS you can start in seconds without installing anything. The trade-off is that you're dependent on your browser's performance — which is exactly why the game pushes Chrome or the official client when frame rates drop.
If you hit a wall, work through it in this order: disable extensions and reload → switch to Chrome or the official client → check the FPS/ping readouts to isolate the cause.