How to Fix The Most Common Issues on ANY Krunker Client (Freezing, Not Loading, Low FPS, etc.)

ISSUES WITH THE KRUNKER CLIENT? COMMON FIXES (WORKS FOR ALL TYPES OF CLIENTS)

If you are a serious Krunker player, chances are you use a “client”. If you use a client, chances are that you’ve encountered problems with it before. Are you extremely frustrated with your Krunker Client? Then you’ve come to the right place. It doesn’t matter if you use the MTZ Krunker Client, the CClient, the Official Krunker Client or the IDKR Client (which is what I typically use). These fixes should work for all of them.

That’s because these clients are made using something called Electron which helps turn a website into a desktop app. Hopefully this guide will save you a lot of time.

PROBLEM: KRUNKER CLIENT BLACK SCREEN

SOLUTION: DELETE ANYTHING RELATED TO KRUNKER IN “C:\Users\USERNAME\AppData\Roaming” and “C:\Users\USERNAME\AppData\Local”

Sometimes this happens after an update.

These are two folders for local data storage that get populated when playing Krunker. Kind of like a cache, but also for storing config. Delete anything related to “Krunker” or “electron” and “v8”. Don’t worry about deleting something incorrectly - these folders will get repopulated again automatically.

These folders may be different for various clients. One tip is to sort by “date modified” to see which ones you’ve used recently, to narrow things down.

Then, you can reload Krunker to see if it fixes it. Still doesn’t work? Uninstall Krunker or your client completely and repeat steps above. Then, do a fresh install.

DELETE FOLDERS LIKE THESE

DELETE FOLDERS LIKE THESE

PROBLEM: LOW FPS WHEN USING A KRUNKER CLIENT

This often happens after a game or client update. It can also happen anytime your hardware changes, like a gaming monitor or GPU.

SOLUTION: Low FPS could be due to a large number of things. Here are some common reasons and fixes:

  • CHECK KRUNKER SETTINGS: this goes without saying but make sure you have “unlimited FPS” option enabled in Krunker and also set the frame cap to 0 or 1200.

  • CHECK NVIDIA SETTINGS: This should be one of the first things you do. Go to your NVIDIA control panel and add your client into the 3D settings.

    • Make sure that vertical sync = off

    • Ensure it’s set to max refresh rate

    • Try turning G-SYNC off if you are having issues, but typically you can keep G-SYNC on without it impacting FPS

    • Make sure that there is no NVIDIA frame cap

  • CHECK AMD/INTEL SETTINGS: I don’t use AMD/Intel IGPU but do the same thing with the comparable AMD/Intel options as the above, if there are graphics options that can be set on a per-game basis

  • CHECK Chrome Line Switches. These are the commands you can add when you right click on desktop shortcut, hit properties, and add something like “—fullscreen” to the end of the shortcut target.

    • Try deleting ALL of them first if you have them

    • If that doesn’t resolve the issue, try adding:

      • --disable-frame-rate-limit 

      • --disable-gpu-vsync

    • Try launching the game as “maximized” by checking the box in Properties

    • NOTE: You may not need ANY of these. Just try them on/off to see if it helps you. It’s supposed to work without these line switches, but they can fix things occasionally.

  • TURN OFF YOUR SECOND MONITOR. In a perfect world, your old 60hz secondary monitor won’t cause FPS issues on your main screen, but in reality this happens with a TON of games. Turn it off to see if it resolves the issue, and if it does, find a better fix in the future so you can use both at the same time properly.

  • HIT F11 A FEW TIMES - Toggle between fullscreen and windowed to ensure that the issue isn’t related to this. Game performance is usually best in fullscreen mode.

  • DISABLE YOUR CUSTOM CSS - Certain external assets or CSS effects can be incredibly taxing to your CPU and GPU because the game constantly has to recalculate, slowing down the render.

PROBLEM: MULTIPLE INSTANCES OF KRUNKER RUNNING IN THE BACKGROUND

This problem can actually happen with just about any application, but sometimes it is worse with Krunker clients. Do understand that with electron, it can and will run multiple instances of the client - that’s just how it works - it’s like opening up several diff browser tabs. In this case, these “tabs” handle different parts of the game’s processes, allowing the client to take fuller advantage of the CPU and GPU. But sometimes, when you close the game, you may notice these “ghost processes” building up and draining resources.

SOLUTIONS TO GHOST PROCESSES:

  • RESTART YOUR PC - it sounds stupid but remember, these ghost processes are sometimes inevitable. Restarting will ensure everything is fully cleared from memory.

  • UNINSTALL OLD VERSIONS OF YOUR CLIENT - occasionally, past versions of the client can cause issues. These past versions don’t always exist, but you may find them in your control panel. Try to uninstall them.

  • CREATE A TASK KILLER - you can easily make a Windows Batch File to kill the Krunker ghost processes. Learn more about how to do this here https://www.windows-commandline.com/taskkill-kill-process/. Essentially, the batch file would include something like “taskkill /IM Official Krunker Client.exe” (replace “official krunker client” with whatever’s the name of the client you’re using). You just need the wordpad for this.

PROBLEM: CLIENT FREEZES BUT DOESN’T CRASH

The problem above happens on all types of clients, and hopefully gets fixed with future updates, but it’s related to something called the “canvas” freezing. I will update this later, but here are some potential fixes to reduce the problem for now:

CANVAS FREEZE FIXES

  • Disable custom CSS

  • Set a lower frame rate limit

  • Set client “properties” to launch maximized (right click the windows shortcut).

  • Add Chrome line command “—no-sandbox”

  • Limit the number of programs running in the background. Don’t have programs maximized while you play Krunker.

  • Press F11 twice or alt-tab (this is the de-facto temporary fix).

Unfortunately, I don’t have a definitive fix for this quite yet!