Roblox is not one game but a platform, and that changes how you should read an FPS drop. The client runs Roblox’s own engine, and every experience you join is a separate set of scripts, meshes and effects written by a different developer. So the first question is always whether the drop happens everywhere or in one specific experience. A frame rate that collapses in every game points at the client: the automatic graphics quality slider fighting your hardware, the wrong rendering API for your GPU, the built-in frame cap, or the Hyperion anti-cheat layer competing for CPU time on older processors. A drop that only happens in one place is almost always the experience itself, and no amount of client tweaking will fix a server-side script that spawns a thousand parts. This guide walks through the client-side causes first because they are the ones you can actually control in 2026, then shows how to prove when the problem is not on your machine.
- Likely Causes
- Fix 1: Switch Graphics Mode to Manual and lower the level
- Fix 2: Raise the frame rate cap
- Fix 3: Force the discrete GPU on laptops
- Fix 4: Change the rendering API
- Fix 5: Clear the Roblox cache and logs
- Fix 6: Disable overlays and background recorders
- Fix 7: Update the GPU driver and set the Windows power plan
- Fix 8: Reinstall the client cleanly
- If Nothing Works
- FAQ
Quick answer: Our top pick in 2026 is the Automatic graphics quality scaling too high — our #1 rated choice. See the full ranked comparison, alternatives and buying advice below.
Likely Causes
| Cause | How to confirm | Fix difficulty |
|---|---|---|
| Automatic graphics quality scaling too high | FPS recovers when Graphics Mode is set to Manual at a lower level | Easy |
| Frame rate cap left at the 60 FPS default | FPS is pinned at exactly 60 in Shift+F5 stats | Easy |
| Wrong rendering API for your hardware | Switching between Direct3D 11 and Vulkan changes FPS noticeably | Moderate |
| Laptop running Roblox on the integrated GPU | Shift+F5 or Task Manager shows the iGPU under load, the discrete GPU idle | Easy |
| Anti-cheat and background CPU contention | CPU usage near 100% on four-core or older systems | Moderate |
| Bloated Roblox cache or logs | Stutters when joining or teleporting between places | Easy |
| Overlays and capture tools | FPS improves with Discord, Game Bar and recording software off | Easy |
| Heavy or poorly optimized experience | Other experiences run fine; Shift+F5 shows high Instances or Draw counts | Not fixable client-side |
Fix 1: Switch Graphics Mode to Manual and lower the level
How to check
Press Escape in any experience, open Settings, and look at Graphics Mode. If it reads Automatic, the client is deciding your quality level on the fly, and it is often optimistic. Press Shift+F5 to display the performance stats overlay and watch the FPS figure as the scene changes.
What to do
Set Graphics Mode to Manual and drag Graphics Quality down to level 4 or 5. Watch Shift+F5. Raise it one notch at a time until FPS starts to fall below your target, then step back one. Level 10 enables full shadow distance, high-quality lighting and long render distance, which many mid-range GPUs cannot hold in dense experiences.
How to undo it
Set Graphics Mode back to Automatic in the same menu.
Fix 2: Raise the frame rate cap
How to check
If Shift+F5 shows FPS locked at exactly 60 while your GPU sits well under full load, the client cap is active rather than a performance problem. On a 144 Hz or 240 Hz monitor this feels like stutter even though nothing is wrong.
What to do
In the Escape menu Settings, find Maximum Frame Rate and set it to match your monitor’s refresh rate or slightly above. Also make sure V-Sync in the same menu is off if you want the cap to be the only limiter. On the Microsoft Store version, the same setting exists but Windows may still enforce the desktop composition rate if the game is not running in exclusive fullscreen.
How to undo it
Set Maximum Frame Rate back to 60.
Fix 3: Force the discrete GPU on laptops
How to check
Open Task Manager, Performance tab, and look at which GPU shows 3D activity while Roblox runs. If GPU 0 (usually Intel or AMD integrated) is busy and GPU 1 (your NVIDIA or AMD discrete card) is idle, Windows has assigned the wrong adapter.
What to do
Open Windows Settings, System, Display, Graphics. Click Browse and add RobloxPlayerBeta.exe from %LOCALAPPDATA%\Roblox\Versions\version-xxxxxxxx (use the newest version folder). Set it to High performance. Repeat after major Roblox updates, because the version folder changes and the rule can lose its target.
How to undo it
Remove the entry from the Graphics settings list or set it back to “Let Windows decide.”
Fix 4: Change the rendering API
How to check
Roblox chooses between Direct3D 11 and Vulkan automatically (Metal on macOS). Shift+F5 does not show the active API, but a large FPS swing when you force one or the other confirms the automatic choice was wrong for your driver.
What to do
The client reads overrides from ClientSettings\ClientAppSettings.json inside the current version folder. Create the ClientSettings folder if it does not exist and add a file containing {"FFlagDebugGraphicsPreferD3D11": "True"} to force Direct3D 11, or {"FFlagDebugGraphicsPreferVulkan": "True"} to force Vulkan. Use only one. Roblox does not officially support these flags, and an update can remove them or reset the folder, so treat this as an experiment rather than a permanent setting.
How to undo it
Delete ClientAppSettings.json and the client returns to automatic selection.
Fix 5: Clear the Roblox cache and logs
How to check
Hitches when loading into a place or teleporting, combined with a %TEMP%\Roblox folder of several gigabytes, indicate cache bloat. Roblox also writes verbose logs to %LOCALAPPDATA%\Roblox\logs, which grow without limit.
What to do
Close Roblox fully. Delete the contents of %TEMP%\Roblox and %LOCALAPPDATA%\Roblox\logs. Do not delete the Versions folder unless you plan to reinstall. Assets will re-download on your next join, so expect one slow load.
How to undo it
Nothing to revert; the cache rebuilds on its own.
Fix 6: Disable overlays and background recorders
How to check
Roblox is CPU-bound in most experiences, so anything else consuming CPU time shows up as lost frames. Discord’s overlay, Xbox Game Bar’s background recording, Medal and browser tabs with video all count.
What to do
Turn off the Discord in-game overlay, disable Xbox Game Bar and its background recording in Windows Settings, Gaming, and close capture software. Close browser tabs playing video. Test with Shift+F5 in the same experience.
How to undo it
Re-enable each item you want to keep.
Fix 7: Update the GPU driver and set the Windows power plan
How to check
An old driver can force Roblox onto a fallback rendering path. Also open Windows Settings, System, Power, and check whether the mode is set to Best power efficiency, which throttles clocks on laptops.
What to do
Install the current driver from NVIDIA, AMD or Intel. Set the Windows power mode to Best performance while gaming, and on laptops plug in. In the NVIDIA Control Panel or AMD Adrenalin, you can add a profile for RobloxPlayerBeta.exe with Power Management set to Prefer maximum performance.
How to undo it
Return the power mode to Balanced and delete the per-application driver profile.
Fix 8: Reinstall the client cleanly
How to check
If the client updates itself repeatedly, fails to launch from the website, or FPS is poor in even the simplest baseplate experience, the installation may be damaged.
What to do
Uninstall Roblox from Windows Settings, Apps. Delete %LOCALAPPDATA%\Roblox entirely. Reinstall from the website (or the Microsoft Store if you prefer that version, but pick one and remove the other; running both installs side by side causes confusion about which client launches).
How to undo it
Reinstallation cannot be reversed, but your account settings are stored server-side, so nothing is lost except local keybinds you can reapply.
If Nothing Works
Prove where the problem lives. Join a near-empty baseplate experience and note the FPS with Shift+F5. Then join the experience that drops, and compare the Instances, Draw and Memory figures on the same overlay. If the baseplate runs perfectly and the problem experience shows very high counts, the drop belongs to the developer, not you, and posting in that experience’s community is the only route. If even the baseplate struggles, check Task Manager for another process using the CPU, test a fresh Windows user profile, and try the other client (web or Store). Roblox’s own logs in %LOCALAPPDATA%\Roblox\logs will show device selection and any graphics fallback warnings near the top of the newest file.
FAQ
Why is Roblox stuck at 60 FPS?
The client caps at 60 by default. Raise Maximum Frame Rate in the in-game Settings menu, and turn off V-Sync if you want the cap to be the only limit.
Does Graphics Quality level 10 matter for competitive play?
Not much. Levels above 6 or 7 mostly extend shadow and render distance. Most players are better served by a stable frame rate at a moderate level.
Is editing ClientAppSettings.json safe?
It does not violate the terms of use on its own, but the flags are undocumented, can change without notice, and Roblox may reset them. Keep it to the two rendering-API flags described above and remove the file if anything behaves strangely.
Why does one experience run badly when everything else is fine?
Each experience is separately coded. Excessive part counts, unoptimized scripts and heavy particle effects are the developer’s responsibility, and lowering your Graphics Quality is the only lever you have.
Ready to decide? Our #1 pick for 2026 is the Automatic graphics quality scaling too high.
Live price & availability on Amazon.
