Wuthering Waves Best Graphics Settings 2026 (Low-End PC to RTX 4060)

TL;DR: On a mid-range GPU like the RTX 4060, run Wuthering Waves at 1440p with DLSS Quality, Shadow Quality Medium, Volumetric Fog Off and the frame cap at 60 (or 120 if your monitor supports it) — you keep the art direction intact and hold a stable 60+ fps. On low-end hardware (GTX 1650, Vega 8 iGPU, older laptops), the three settings that buy back the most frames are Volumetric Fog, Scene Detail and Shadow Quality; drop those first and leave Anti-Aliasing alone until last, because Wuthering Waves' anime-style rendering shimmers badly without it.

This guide covers the PC version as of Version 3.7 (October 2026). Wuthering Waves runs on Unreal Engine 4, and most of its performance cost comes from a small number of heavy settings rather than an even spread — which is good news, because it means you can cut 30–40% of GPU load by turning off three or four things, while the image barely changes.

The settings that actually matter (ranked by frames-per-cost)

Not all settings are equal. Community testing across the 2.x and 3.x patches consistently shows the same hierarchy, so follow this order when tuning:

Impact figures are approximations from community benchmarks; exact gains vary by GPU, driver version and scene.

Recommended presets by hardware tier

The pattern in every tier is the same: upscaler first, fog and shadows second, everything else last. Wuthering Waves' stylized art hides upscaling artifacts far better than it hides shadow pop-in, so prioritize accordingly.

Upscaling: DLSS vs FSR vs native

• NVIDIA RTX cards: DLSS Quality (67% render scale) is nearly free image quality at 1440p. In fast camera pans during Echo encounters, DLSS holds outlines better than FSR.
• AMD / older GTX cards: FSR Balanced or Performance. WuWa's implementation is solid, but expect slightly more shimmer on fine hair highlights during Sonatta Cistern echo fights.
• Never combine a heavy render-scale reduction with Low anti-aliasing — that combination is what produces the "crawling edges" screenshots players complain about on forums.

If you see shimmer at 1080p, the fix is not raising anti-aliasing (expensive) — it's moving the resolution up one notch and letting the upscaler do the work.

Frame rate: cap it, don't chase it

Wuthering Waves' combat is timing-sensitive — dodge windows and parry prompts are generous, but camera-heavy echo animations expose stutter more than raw fps. Two practical rules:

• Cap at a rate you can hold 95% of the time. A locked 60 beats an uncapped 45–90 rollercoaster in feel, even though average fps is lower.
• 120 fps is worth it only if your whole chain supports it — 120 Hz monitor, GPU headroom, and no vertical sync penalty. Otherwise the cap adds input smoothing issues for no gain.

Also enable NVIDIA Reflex / low latency mode in the driver panel if available; it trims input lag more noticeably in this game than in slower-paced gacha competitors.

Fixing stutter and shader hitches

The classic WuWa complaint — "fine in the overworld, freezes when I cast an ult" — is usually shader compilation, not settings. Checklist in order of likelihood:

1. Let the first session run. After a driver or game update, play 10–15 minutes in a busy area (Jinzhou docks) before judging performance; hitching fades as shaders cache.
2. Move the game to an SSD if it isn't already — texture streaming from a hard drive causes open-world pop-in that reads as "lag".
3. Cap background apps. Browser hardware acceleration and launcher overlays (including screenshot tools) are the most common silent frame stealers.
4. Full-screen mode, not borderless windowed, on multi-monitor setups — borderless costs a few percent when a second monitor is playing video.

Laptop-specific advice

• Force the discrete GPU in Windows Graphics Settings — WuWa sometimes launches on the iGPU by default on Optimus laptops, and that single misroute costs more frames than any in-game setting.
• Power mode: Best Performance while plugged in; on battery, cap fps at 30–40 to keep thermals and battery drain sane.
• Undervolted/thermally limited laptops benefit more from a lower frame cap than from lower settings — sustained clocks beat momentary peaks.

Settings that are safe to max

If you have headroom after the big three, these add the most visual value per frame spent: Bloom (WuWa's signature light bloom on Resonance Skills), Effects Quality (combat readability), and Texture Quality (VRAM-dependent, cheap on 8 GB+ cards). Maxing textures while lowering shadows is the best-looking budget configuration — the reverse looks worse and costs more.

Re-tuning after driver and version updates

Two events should trigger a five-minute settings review, because they change the performance picture under your feet:

• GPU driver updates. Major driver branches occasionally shuffle relative setting costs (shader compilers change). After a big driver jump, run one combat-heavy session before deciding your settings are still optimal — and re-enable Volumetric Fog once to see if it's cheaper than you remember. Sometimes it is.
• Game version updates. New regions ship with different scene complexity. When a patch lands, players commonly report fps shifts even with untouched settings — a new map's lighting model can cost 5–10% on identical hardware. The fix is not panic-lowering everything; check the per-region behavior first (the overworld hub is the right benchmark, not the login screen).

A practical habit: keep a note (or screenshot) of your settings after each tuning pass. When performance shifts, you're comparing against a known baseline instead of memory — and you can revert in two minutes instead of re-deriving everything.

Mobile players: the two settings that matter

Phone and tablet users get a shorter settings menu, and the calculus is different — thermal throttling dominates. Two moves cover most of it: set the frame rate to 30 fps unless your device is flagship-class (then 60 with a cooler), and drop effects quality before resolution, since big spell VFX is what spikes phone SoCs. If your device supports it, a small cooling clip changes sustained performance more than any menu option. Pull odds and combat math are identical on mobile — see the pity guide — so a lower visual tier costs you nothing but eye candy.

Use this with our tools

• Planning pulls while you wait for shaders to compile? Pull Calculator shows your exact pity odds before you spend Astrite.
• Finished your build and farming Echoes? Score them in seconds with the Echo Scorer.
• More performance-adjacent reads: Beginner Guide and Energy Regen Breakpoints.

FAQ

Does Wuthering Waves support DLSS and FSR in 2026?

Yes — DLSS on NVIDIA RTX cards and FSR on AMD/older GPUs are available in the display settings on PC. Use DLSS Quality at 1440p or FSR Balanced at 1080p as starting points.

Why does my fps drop in cities but not in the open world?

Dense areas (Jinzhou, Rinascita hubs) combine more shadow casters, reflection surfaces and NPC scene detail. That's why Scene Detail and Shadows are the first cuts — they're exactly what cities load heavily.

Is 120 fps worth it in Wuthering Waves?

Only on a 120 Hz+ display with consistent GPU headroom. The game supports high frame rates, but an unstable uncapped framerate feels worse than a solid 60. Test 120 for a few combat encounters before committing.

Does graphics settings affect the gacha or gameplay?

No — purely presentation. Pull odds (0.8% base, 80 hard pity) and combat math are identical on every device; see our pity system guide.

What's the single best setting to lower on a low-end PC?

Volumetric Fog. It's the most expensive setting for the least visible payoff in combat, and turning it off often returns double-digit percentages of GPU headroom.