WoW Forever FPS Drops Fix: Memory Leak & Choppy Frames
By Tier1Settings Updated Published
On this page
Blizzard fixed the WoW Forever beta memory leak on 24 September 2026, so FPS drops on the live game usually come from drivers, a stale Cache folder or a frame-rate cap, and logging out to character select and back in tells you in seconds whether memory is still building up. During the beta, community testing measured committed memory growing ~29 MB/min and dedicated VRAM ~12–15 MB/min, with frame rate falling from around 110 FPS to 40 FPS over 88 minutes. This guide covers what was fixed, the relog test, the fixes that help, and how to tell a client problem from a hardware one. Updated 19 November 2026, after launch.

If performance recovers the moment you relog, the problem is in the client, not your PC.
The 30-second test (and fix)
Log out to character select, then log back in. You don’t need to close the game.
In a measured beta case this single action:
- Dropped VRAM use from 6.24 GB to 4.58 GB
- Restored GPU utilization from 22% to 52%
- Returned frame rate to near its session-start value
If that restores your FPS, memory is building up in the client and you can stop troubleshooting hardware. Blizzard fixed the beta leak on 24 September, so if this still happens to you on the live game, repeat the relog when performance sags and report it to Blizzard with the in-game bug report tool. If the relog changes nothing, skip to the other fixes below.
The measured evidence (beta, fixed 24 September)
Community bug reporting against builds 1.60.1.69893 and 1.60.1.69913 (following the 18 September 2026 patch) documented steady, non-levelling growth:
| Metric | Measured growth |
|---|---|
| Committed system memory | +29 MB/min while playing |
| Dedicated VRAM | +12 to +15 MB/min while playing |
| Handle count | +12/min — even while AFK |
| Frame rate | ~110 → ~40 FPS over 88 minutes |
The AFK handle growth is the telling detail: memory climbs even when you aren’t doing anything, which points at the client rather than at scene complexity or what you’re rendering.
There’s a second symptom worth recognising. As VRAM fills, the engine’s texture defragmenter kicks in and drops render scale from 98% to 75% once video memory hits its budget (reported at used:6.6GB budget:6.6GB). So the game also gets visibly blurrier as the session goes on — that’s the engine trying to cope, not a settings change you made.
Why changing graphics settings doesn’t help
This is the part that confuses people most, and it’s genuinely diagnostic: Low and Ultra produce near-identical frame rates.
Player reports from the beta:
- An RTX 5090 with a Ryzen 9 9950X3D at 25–30 FPS
- “40–50 fps with low settings and 40–50 with ultra settings”
- Multiple users stuck at 20–40 FPS regardless of quality preset
When quality settings make no difference and top-tier hardware performs the same as mid-range, you are not GPU-limited. Turning everything down is wasted effort here. The general principle — and how to confirm it on any game — is covered in why FPS drops after hours of gameplay, which uses this exact WoW data as one of its documented cases.
Other fixes players report working
These produced large, specific gains for players during the beta, and they are the first things to try if your FPS is low on the live game:
- Update your GPU drivers. One player went from 24 FPS to 100+ FPS after a driver update. This is the highest-value first step if you haven’t done it.
- Delete the WoW cache folder and relaunch. Another reported going from 30–40 FPS to 144 FPS after clearing cache and restarting the launcher. Delete the
Cachefolder in your WoW install directory — the game rebuilds it. - Disable the Target Framerate setting. One player reported this “over doubled my FPS.” It’s an easy thing to test and costs nothing.
- Close background applications. Overlays, browsers and capture software compete for the memory the leak is already eating into.
- Cap your frame rate below your refresh rate for steadier pacing once you’re back at a decent baseline.
A note on honesty: some guides claim a Radeon-specific problem with Secondary Lighting. The primary Blizzard forum reports do not show a significant GPU brand difference — both NVIDIA (RTX 3090, RTX 5090) and AMD (RX 9060 XT) cards are affected. Treat brand-specific claims about this beta with caution.
Is it the leak, or something else?
| Symptom | Cause | Fix |
|---|---|---|
| Fine at first, degrades over 15–30 min, recovers on relog | Memory leak | Relog; this guide |
| Bad immediately and constantly, never recovers | Drivers, cache, or Target Framerate | Fixes 1–3 above |
| Stutter only while moving, smooth standing still | Asset streaming / CPU-side hitching | Cache clear, SSD, frame cap |
| Locked at exactly 60 FPS (or your refresh rate) | A frame-rate cap: VSync, an in-game frame limit or a driver-level cap | Turn off VSync and raise or disable the frame limits in Graphics settings and your GPU driver |
| Random micro-stutter in every game | DPC latency / drivers | Fix high DPC latency |
| Hard crash with a VRAM error | VRAM exhausted | Out of video memory fix |
The relog test is the cleanest separator. Failing or thermally throttling hardware does not recover because you returned to character select.
Was the memory leak fixed?
Yes. Blizzard’s WoW Forever Beta Development Notes (official forums, posted by Blizzard staff) list on 24 September 2026: “Fixed a memory leak causing gradual performance degradation for some players.” The notes that followed, up to the 4 November 2026 launch, list no further memory, frame-rate or crash known issues.
| Date | What happened |
|---|---|
| 17–18 Sep 2026 | Beta opens; the leak is documented against builds 1.60.1.69893 and 1.60.1.69913 |
| 24 Sep 2026 | Blizzard’s notes: memory leak causing gradual performance degradation fixed |
| 4 Nov 2026 | WoW Forever launches; no performance known issues listed in Blizzard’s notes |
So the measurements above describe the beta, not the live game. If your session still degrades and recovers on a relog, that is worth a bug report to Blizzard; if it’s slow from the start, the fixes above and the best WoW Forever settings are where to look.
The short version
- The beta memory leak was fixed on 24 September 2026 (Blizzard’s development notes).
- Relog to character select to test whether memory is building up — VRAM 6.24 → 4.58 GB in beta testing.
- Beta leak, measured: ~29 MB/min RAM, ~12–15 MB/min VRAM, 110 → 40 FPS over 88 minutes.
- If Low and Ultra give the same FPS, you aren’t GPU-limited, so lowering settings won’t help.
- Update drivers (24 → 100+ FPS reported), delete the Cache folder, disable Target Framerate.
- Render getting blurry? That’s the texture defragmenter dropping render scale to 75%.
- Stuck at exactly 60 FPS? That’s a cap: VSync or a frame limit.
Related: Best WoW Forever settings for FPS · Why FPS drops after hours of gameplay · Best tools to fix stuttering in games
Frequently asked questions
Why does my FPS drop after 15-30 minutes in WoW Forever?
During the beta it was a client memory leak, which Blizzard's development notes list as fixed on 24 September 2026. Community testing on earlier beta builds measured committed system memory growing about 29 MB per minute and dedicated VRAM about 12–15 MB per minute during play, with frame rate falling from roughly 110 FPS to 40 FPS over an 88-minute session. If you still see that pattern on the live game, log out to character select and back in: if FPS recovers, memory is building up in the client rather than your hardware failing.
How do I fix WoW Forever FPS drops?
The immediate fix is to log out to character select and log back in, which frees the leaked memory without closing the game. In one measured case this dropped VRAM use from 6.24 GB to 4.58 GB and restored GPU utilization from 22% to 52%. Beyond that, update your GPU drivers, delete the WoW cache folder and relaunch, and try disabling the Target Framerate setting — players have reported large gains from each.
Why do Low and Ultra settings give the same FPS in WoW Forever?
Because the bottleneck is not your graphics card. Players report identical frame rates at Low and Ultra, and high-end systems are affected too — one report had an RTX 5090 with a Ryzen 9 9950X3D sitting at 25–30 FPS. When changing graphics quality makes no difference, the limit is elsewhere, which during the beta pointed at the client memory leak (fixed 24 September 2026) and CPU-side overhead rather than GPU load.
Has Blizzard fixed the WoW Forever memory leak?
Yes. Blizzard's WoW Forever Beta Development Notes for 24 September 2026 list: 'Fixed a memory leak causing gradual performance degradation for some players.' The leak had been documented against builds 1.60.1.69893 and 1.60.1.69913 after the 18 September patch. Blizzard's later notes, through the 4 November launch, list no further memory or performance known issues. If your FPS still sinks over a session, the relog test in this guide tells you whether something is still building up.
Is WoW Forever badly optimized or is my PC the problem?
During the beta, most reports were the client: performance was fine at first, degraded over time, then fully recovered on a relog, which failing or overheating hardware does not do. Blizzard fixed that leak on 24 September 2026, and the game launched on 4 November 2026. If you still have low FPS now, work through drivers, the Cache folder and frame-rate caps first, then the relog test.