WoW Forever Best Graphics Settings for FPS: Presets, Caps and Fixes

WoW Forever runs on the modern client, so its graphics menu is the long one from current World of Warcraft. A few settings eat most of the frame time, and lowering them barely changes the look of the new zones. This guide gives the best WoW Forever graphics settings as starting values for three kinds of PC, the order in which to lower things, sensible frame caps, laptop advice and what players have found about the stubborn 60 FPS lock. Checked on 8 November 2026 for WoW Forever 1.60.1. Change one setting at a time and test in the same busy spot.

Short answer

• Start from your native resolution, Render Scale 100% and the preset your PC handles, then lower Secondary Lighting and Compute Effects before anything else.
• Use CMAA2 anti-aliasing; multisampling at 8x costs far more than it gives back.
• Set Max Foreground FPS to your monitor refresh rate or a little below, and Max Background FPS to around 30.
• Keep Texture Resolution high if your card has the video memory; it costs little frame rate.
• Stay on DirectX 12 and switch to DirectX 11 only for crashes, flicker or the 60 FPS lock.
• If FPS is low even on minimum settings, test with all addons off.

What to lower first

Work down this list and stop once your frame rate holds in a crowd.

1. Secondary Lighting: the heaviest single option. Drop it to Good, or Fair on a weak card.
2. Compute Effects: one step down from the top is usually enough. Players report that the lowest step strips fog and light shafts, which hurts the look more than it helps.
3. Render Scale: 90% is hard to tell apart from 100% at 1440p; 80% saves more but softens the image. Go below that only as a last resort.
4. Shadow Quality: Good is a fair middle ground.
5. Ground Clutter and View Distance: trim these on older processors.
6. SSAO, Depth Effects and Bloom: small savings; turn them down to taste.

Leave Projected Textures on; it draws area spells on the ground, which you need to see. Blizzard's beta development notes of 1 October removed the Ray Traced Shadows option and say it will return in a future update; if it reappears, test it on its own.

Starting values per PC tier

These are starting points rather than benchmarks; adjust them up or down after a test in a busy area.

Setting	Low-end or older laptop	Mid-range (1080p to 1440p)	High-end (1440p and up)
Render Scale	85–90%	100%	100%
Anti-aliasing	CMAA2	CMAA2	CMAA2, or CMAA2 with 2x
Shadow Quality	Fair	Good	High or Ultra
Secondary Lighting	Fair or Good	Good	High
Compute Effects	Good	High	High
View Distance	6–7	8	9–10
Texture Resolution	High if video memory allows	High	High
Max Foreground FPS	60	Refresh rate or slightly below	Refresh rate or slightly below

Max Background FPS applies when the game is not the focused window. Somewhere between 8 and 30 keeps your card cool while you tab out. Leave Target FPS off unless your frame rate collapses in crowds.

Do not leave the foreground cap unlimited; a steady 120 feels smoother than a rate jumping between 90 and 200. For more distance and grass tweaks through console variables, see console commands and camera distance.

Laptops and integrated graphics

1. Plug the laptop in and pick a performance power mode; on battery many laptops cut their graphics clock.
2. In the Windows graphics settings, assign the game executable to the dedicated graphics card if you have one.
3. Start from the low-end column above, keep textures high if memory allows, and skip extra grass density commands.
4. Cap foreground FPS at 60 to limit heat.

Blizzard has published a hardware floor: the graphics chip must be AMD GCN 1, NVIDIA Maxwell, Intel Skylake or newer. Blizzard adds that some chips which pass this floor, such as Intel HD Graphics 530, are still well below the minimum requirements, and players on Intel HD 520 and 530 report loading screens that hang. The full minimum specification is on the Battle.net shop page; many third-party spec tables are unsourced.

The 60 FPS lock, DirectX 11 and DirectX 12

During the beta, players on NVIDIA cards found the client capping itself at exactly 60 FPS. The game folder's Logs\gx.log showed a thermal state change and the line "Imposing FPS cap of 60 FPS", even at low temperatures. Similar reports returned on the launch build from 5 November, with no official fix at the time of writing. What players report:

1. Open _forever_\Logs\gx.log in a text editor and search for "FPS cap". If the line is there, the client applied the cap itself.
2. Turn off G-SYNC or any driver-level frame cap in the NVIDIA app; this fixed it for at least one launch-week player.
3. Turn off in-game V-Sync; another player found that was the whole cause.
4. Turn off NVIDIA Smooth Motion; results are mixed. A full game restart lifted the cap for some RTX 4090 owners, but only until it came back.
5. Switch the graphics API to DirectX 11 in the advanced graphics options and restart; this helped some players and did nothing for others.

DirectX 12 remains the better default; use DirectX 11 for crashes, flickering or this lock.

Common problems

Problem	What helps
Stutter in cities while FPS looks fine	Lower Secondary Lighting, then View Distance and Ground Clutter; check whether layering has put you in a crowded copy of the zone
FPS stuck at exactly 60	Check gx.log, turn off G-SYNC, V-Sync and Smooth Motion, then try DirectX 11
Low FPS even on the lowest preset	Disable all addons, test, then enable them one at a time
Screen flickers on DirectX 12	Switch to DirectX 11 and update the graphics driver
Loading screen hangs on an older laptop	Check the chip against Blizzard's GPU floor and the Battle.net minimum spec; see login and loading errors

Tips

• Test every change in the same crowded place at the same time of day, otherwise layer population skews the result.
• If you see stutter, compare Windowed (Fullscreen) with exclusive Fullscreen.
• Skip "FPS booster" addons; they mostly change the same options you can set yourself.
• Update the graphics driver before chasing settings.
• Back up WTF\Config.wtf before experimenting so you can return to a known state.
• On a laptop, clean fans can be worth more frames than any single slider.

ForeverBot and this setup

ForeverBot needs no special graphics settings. A steady frame cap makes the route arrow and turn hints smoother, and keeping the UI scale where you set it during ForeverBot first-run setup avoids windows moving between sessions. Be clear about the rules: any automation breaks Blizzard's terms, and Blizzard bans accounts for it. More options are collected under settings guides.

FAQ

What are the best graphics settings for WoW Forever on a mid-range PC?

Native resolution, Render Scale 100%, CMAA2, Shadows Good, Secondary Lighting Good, Compute Effects one step below maximum, SSAO Good and View Distance around 8, with foreground FPS capped at your refresh rate. If crowded zones still stutter, lower Secondary Lighting first and Render Scale to 90% second.

Why is my WoW Forever FPS stuck at 60?

Check V-Sync on a 60 Hz monitor and the foreground cap first. If neither explains it, look for "Imposing FPS cap of 60 FPS" in Logs\gx.log, which points to the client's own thermal cap reported since the beta. Players have cleared it by disabling G-SYNC, V-Sync or Smooth Motion, or by trying DirectX 11, with mixed results.

Should I use DirectX 11 or DirectX 12 in WoW Forever?

DirectX 12 for most players, since it is the default the client is tuned for. Move to DirectX 11 only for crashes, flickering or the 60 FPS lock, and test whether it actually helps. Switching needs a restart; try DirectX 12 again after each patch.

Can WoW Forever run on integrated graphics?

Sometimes, but it is below what Blizzard aims for. The chip must meet the published floor of AMD GCN 1, NVIDIA Maxwell or Intel Skylake, and Blizzard calls chips like Intel HD 530 well below the minimum. Use the low-end values, a 60 FPS cap and mains power, and expect slow loading screens.