WoW Forever

WOW FOREVER · BETA ISSUE

WoW Forever Low FPS, Stutter & Memory Leak? Workarounds

WoW Forever low FPS, frame drops and stutter after Blizzard's memory-leak fix: what changed and which current Beta workarounds are still worth trying.

Last checked October 15, 2026
ProblemYour WoW Forever Beta session runs at unexpectedly low FPS, drops over time, or stutters while moving.

Quick answer

Blizzard fixed one gradual-performance memory leak on September 24, but later players still report stutter and FPS drops. First identify the pattern: hitching while moving, FPS declining during a session, or low FPS as soon as you enter the world. Compare the same location and route before changing one setting or relogging; neither Secondary Lighting nor a restart is a universal fix. October 1 temporarily removes Ray Traced Shadows, so an absent option is expected—not evidence of a broken installation or a blanket performance fix.

FixedView evidence

Try this first

  1. Update the Beta client and record its displayed build number. September 24 fixed one memory leak, not every FPS problem.FixedView evidence
  2. Identify your pattern: moving-only hitches, gradual session decline, or low FPS immediately on entering. Record a stationary view and a short repeatable route at unchanged settings.
  3. For gradual decline, repeat that view and route after one character-select relog; if needed, compare a full client restart. Record whether recovery lasts.

If that does not work

  1. For consistently low FPS or movement hitches, test Secondary Lighting → Fair alone, then repeat the same route. Keep it only if the comparison improves your symptom.Community ReportedView evidence
  2. Test a lower Shadow Quality separately. If Target Framerate is enabled, compare with it off rather than changing several options together.Community ReportedView evidence

What not to do

  1. Do not assume all stutter is the memory leak Blizzard fixed.
  2. Do not treat a fog-disabling command as an official performance setting; Blizzard removed an unintended fog option.

What is still unknown

  1. Current stutter, session decline and low starting FPS need not share a cause. A second memory leak, driver fault or vendor-wide issue is not established by these reports.

Current status, version and historical scope

Keep the September 24 memory-leak fix as historical official context. A remaining slowdown is not proof that same defect returned: compare immediate low FPS, movement hitching and session decay separately on the updated client. A removed ray-tracing option or a later-build promise does not prove the remaining rendering issue repaired.

What Blizzard fixed

The September 24 development notes confirm a fix for one memory leak that gradually degraded performance for some players. That specific issue is Fixed; the notes do not say that every low-FPS, stutter or frame-drop report is resolved.

Low FPS immediately

Record FPS immediately after entering the world, then stand still for 30 seconds and repeat a short route. Keep resolution, render scale, camera direction and player density comparable. If both stationary and moving performance start low, test one graphics setting before trying a session-degradation workaround. Earlier Low-versus-Ultra reports are not proof that settings never matter.

FPS still gets worse over time

September 29 testers still describe gradual decline, including NVIDIA systems. Record the same stationary view and route near session start and again when performance falls. Re-enter from character select once and repeat; if that does not help, test a full client restart. Recovery can identify a session-dependent symptom, but does not prove a new memory leak.

Movement stutter and frame drops

September 29 reports include hitches while crossing district boundaries or moving the camera, even when average FPS is acceptable. Compare standing still with repeating the same route twice; note whether the hitch occurs at the same point. One Mac tester reports zone-dependent micro-stutter despite Secondary Lighting on Fair. Do not confuse higher average FPS with the disappearance of hitches.

Secondary Lighting, Shadows and fog

Treat Secondary Lighting → Fair and a lower Shadow Quality as optional community tests, not official fixes. September 25 Radeon reports describe improvement from toggling lighting, while later September 30–October 1 replies report recovery after an update. A September 29 Mac tester says lower settings improved average FPS but not micro-stutter. Retest on your actual build and restore settings that do not help. The September 24 fog-setting removal was not an official performance workaround.

AMD, NVIDIA, Proton and handheld reports

Recent reports span Radeon, NVIDIA, Proton and Mac; some players also report no noticeable problem. Historical handheld results do not verify today's Steam Deck or eGPU setup. Include GPU, operating system, client build and graphics settings in a bug report instead of assuming a vendor-wide cause.

What remains unknown

There is no confirmed universal cause for every remaining performance issue. The confirmed memory-leak fix should not be used to label all post-update stutter or VRAM growth as fixed or as a new leak.

Ray Traced Shadows missing after October 1

Blizzard removed this option while its functionality is repaired and plans to restore it in a future update. Do not search for a hidden toggle or reinstall solely because it is absent. Retest the same stationary scene and movement route after updating; remaining low FPS, gradual decline and stutter still need separate comparisons.

Mouse clicks or camera turning trigger stutter

An October 3 Windows 11 player with an RTX 4080 reports drops on left-click or right-click camera turns in fullscreen at 4K. Disabling addons and lowering mouse polling rate did not help that setup; Windowed mode did. Compare stationary FPS, a left-click, then the same right-click turn. Test Windowed mode as a reversible comparison only, and restore your preferred mode if there is no benefit.

Secondary Lighting may not match its displayed value

October 3 developer evidence identifies swapped raid/non-raid Secondary Lighting settings. Rommax recommends enabling raid settings and matching the values. October 4 players also describe temporary recovery with Fair–Good–Fair or a console command, but no universal or completed fix is established. Use the dedicated guide to compare login and zone-transition symptoms without attributing all stutter to the September memory leak.

Claim evidence

Blizzard fixed a memory leak causing gradual performance degradation for some players in the September 24 Beta update.Fixed
Players have reported low FPS on capable hardware, sometimes with little difference between Low and Ultra.Beta Verified
Some September 29 players report temporary recovery after relogging or restarting, with inconsistent relog results.Community Reported
Lighting and shadow changes have helped some setups, but current reports include no benefit and later update recovery.Community Reported
Independent post-fix reports describe movement or camera hitches; lower lighting does not eliminate micro-stutter for everyone.Beta Verified
Disabling Target Framerate helped an individual player.Community Reported
Every low-FPS, stutter or frame-drop problem is fixed by the September 24 update.Unverified
Multiple September 29 players still report performance declining during a session after the September 24 fix; the cause is not established.Beta Verified
October 1 temporarily removes Ray Traced Shadows; the update does not claim every performance issue is fixed.Official
Mouse clicks and camera turns caused reproducible stutter for one fullscreen PC setup; Windowed mode helped that player only.Community Reported
Rommax confirms a raid/non-raid Secondary Lighting setting mismatch and suggests matching the values; other FPS causes remain separate.Official
Published scoped fixes and promises of future fixes are different evidence states; remaining reports need their own current-build evidence.Official
How evidence labels work
OfficialConfirmed by Blizzard or an official WoW channel.
Beta VerifiedSupported by multiple independent Beta reports.
Community ReportedReported by players, but not confirmed enough.
UnverifiedNot enough reliable evidence yet.
FixedVerified in the currently checked build.

Sources

WoW Forever Beta Development Notes — September 24Blizzard Official · Official memory-leak, Mac display, class and gamepad changesOpen Blizzard Official source
Beta Client Update — September 22Blizzard Forum · Official Build 69977 notes; no broad FPS fix is announcedOpen Blizzard Forum source
Linux/AMD Forever Beta severe FPS fluctuationsBlizzard Forum · Supports Radeon and Proton fluctuation, Error #109 and Fair reportsOpen Blizzard Forum source
NVIDIA Xid 109 GPU hangs on world loadBlizzard Forum · Supports NVIDIA and Proton degradation and Fair comparisonOpen Blizzard Forum source
Logged in on day 2 and the game is choppyBlizzard Forum · Supports movement stutter, Target Framerate and Secondary Lighting stepsOpen Blizzard Forum source
Reproducible 180 to 30 FPS collapseBlizzard Forum · Independent report of rapid FPS degradation on current Beta hardwareOpen Blizzard Forum source
Performance Issues and FixesBlizzard Forum · Supports multi-system performance degradation while rejecting a confirmed root causeOpen Blizzard Forum source
WoW Forever on Steam DeckReddit · Device-specific handheld performance reportOpen Reddit source
Stuttering & bad frames — September 29 player reportsBlizzard Forum · Post-fix movement hitches, gradual decline and mixed restart outcomes; thread title is not a diagnosisOpen Blizzard Forum source
Mac stuttering appears to be zone-specificBlizzard Forum · September 29 zone-specific stutter and lighting/shadow tests with mixed outcomesOpen Blizzard Forum source
Secondary Lighting memory leak? — later update reportsBlizzard Forum · Radeon setting reports and September 30–October 1 recovery reports; no official root-cause confirmationOpen Blizzard Forum source
Beta Development Notes — October 1, with Warrior amendmentsBlizzard Official · Published October 1 update: level cap, dungeons, XP, class and client changesOpen Blizzard Official source
Mouse clicks and camera turning cause FPS dropsBlizzard Forum · October 3 fullscreen PC reproduction and one player's windowed-mode comparisonOpen Blizzard Forum source
Secondary Lighting resets after zone changesBlizzard Forum · October 3 player report that the displayed setting may differ from the rendered settingOpen Blizzard Forum source
Blizzard developer: raid/non-raid Secondary Lighting mismatchBlizzard Official · October 3 Rommax reply identifies swapped settings and recommends matching raid and non-raid values; no completed fix announcedOpen Blizzard Official source
Official Forever Beta known issues — dated entriesBlizzard Forum · Distinguishes historical next-build promises from resolved entries; not a blanket fix for all crashes or questsOpen Blizzard Forum source
Forever Beta development notes — September 24 to October 8Blizzard Forum · Dated released changes supersede older issue snapshots only for the same named behaviorOpen Blizzard Forum source

If this didn’t solve it

Record your current client build, exact symptom, region and the checks already tried. Use the related problem cluster below to separate a matching issue from a different failure; no community workaround guarantees recovery.

Last checked

Continue from here

What are you seeing?

Related problem cluster: Current WoW Forever issues and detailed troubleshooting

Found something outdated?

Help us keep this guide accurate.

Report an issue

Tell us what needs checking. Your details stay here if sending fails.

Optional details are sent to Formspree only when you choose Send report. See our Privacy Policy.

Email instead

Third-party ads may process IP addresses, device details and advertising identifiers. Your choice applies only to advertising, not existing analytics or optional feedback.

Ads are currently not permitted for this visit. Your advertising choice: unknown.

Reject or withdraw at any time. Withdrawal reloads the page to stop ad execution; it cannot undo information already sent.

Privacy Policy