Is it low FPS or network lag?

Low FPS makes movement or rendering visibly uneven. Network delay more often makes actions respond late while the scene may still animate smoothly. A download failure, crash or missing beta entitlement is another problem. Record when the symptom begins, where it happens and whether it worsens over a long session.

Use the same location, approximate camera view and activity for comparisons. Crowded areas and different encounters are not controlled tests. Note your current settings before changing them; screenshots or a short written list make restoration easier.

Step 1: update and restart

Action: let Battle.net finish the current beta update, close the game and restart it. Check the client build.

Observe: compare a fresh session with one of similar length to the session that slowed down. The September 24 notes report a memory-leak fix affecting gradual degradation, as well as Mac display fixes.

Restore: restarting does not require a settings rollback. If the symptom remains, keep the build and timing in your report. Do not repeatedly reinstall the client solely because this reported fix did not resolve your particular issue.

Step 2: compare without addons

Action: disable all addons for a test run, retaining their files and saved settings.

Observe: repeat the same scene. If performance improves consistently, re-enable addons in small groups to narrow the cause. A single busy or quiet moment is not enough to establish a culprit.

Restore: re-enable the original selection if the comparison shows no useful difference. Follow the addon compatibility guide if one project or combination appears responsible.

Step 3: reduce graphics load one setting at a time

Action: record your current resolution/render scale and graphics preset. Lower one available load-related setting, such as render scale or a shadow setting, then repeat the scene. Use only controls exposed by the current client.

Observe: a meaningful improvement can indicate sensitivity to that graphics workload; no improvement means you should restore the setting and test another explanation. There is no hardware-specific optimal preset established in this guide; compare results on your own system.

Restore: return the changed control to its recorded value before the next test. Avoid copying long lists of console commands or disabling security features. Those changes make causality and recovery harder to establish.

Step 4: check hardware and the wider session

Compare your system with the official system requirements. Supported GPU architecture is not a guarantee of a particular frame rate at every resolution. On laptops, check that the machine is powered and using its intended performance mode; on any system, note heavy background activity that overlaps the slowdown.

Use the operating-system or hardware vendor’s normal update path for drivers. Keep each change separate from your graphics and addon tests. Avoid unofficial driver packages. If the problem persists after an official update, continue with the client and addon checks.

Step 5: make a reproducible report

Include platform, CPU/GPU, memory, resolution, client build, addon state, location, session duration and the steps that trigger the symptom. State what changed the result and what did not. Remove private account information from screenshots and logs before sharing them publicly.

If the problem starts only after a specific patch, check known issues and development notes. The official support overview provides escalation paths, but older support instructions should be checked against the current client. A useful report is a better endpoint than endlessly changing settings without a comparison.

If the game does not start at all, see WoW Forever won’t launch. Addons are a common cause of stutter — check addons. Installation steps are on the download page.