Ad Space — Top Banner

Low FPS / Stuttering

Blizzard Diablo 4

Severity: Moderate

What Does This Error Mean?

Diablo 4 stuttering and low FPS on PC is most often caused by shader pre-compilation not having completed, VRAM being exceeded by texture settings, or the CPU being a bottleneck in dense scenes. Allow the game to finish shader compilation on first launch, lower texture quality one step, and cap the frame rate to a stable target rather than running uncapped.

Affected Models

  • Diablo IV — PC (Battle.net)

Common Causes

  • Shader compilation is incomplete — stuttering is severe until shaders are pre-compiled
  • Texture quality setting exceeds available VRAM
  • CPU is bottlenecked in town or during large group play
  • DLSS or FSR upscaling is not enabled on a mid-range GPU

How to Fix It

  1. On first launch or after a major patch, Diablo 4 compiles shaders in the background. Stutter during this phase is normal. Let the game run for 15–20 minutes before judging performance.

    Shader compilation progress is visible in the bottom-right corner of the main menu. Do not skip to gameplay until it shows 100% — stuttering during this phase is unavoidable.

  2. Lower the Texture Quality setting by one step (Ultra to High, or High to Medium). If your GPU has 8 GB VRAM or less, Ultra textures cause VRAM overflow and severe stuttering.

  3. Enable DLSS (NVIDIA), FSR (AMD), or XeSS (Intel) in the Graphics settings. Set Quality or Balanced mode. Upscaling significantly improves frame rates on mid-range GPUs with minimal visual loss.

  4. Cap the frame rate to a value your GPU can sustain consistently (e.g. 60 or 120 fps). An uncapped frame rate causes the GPU to fluctuate, producing perceived stutter even when average fps is high.

    Use the in-game frame rate cap rather than V-Sync to avoid input lag.

Frequently Asked Questions

My PC exceeds the recommended specs but Diablo 4 still stutters — why?

Diablo 4 has a known shader compilation stutter that occurs even on high-end systems, particularly in the open world when entering new areas for the first time. This is an engine-level issue that Blizzard has partially addressed in patches. Keeping the game updated and allowing full shader pre-compilation before playing are the best workarounds.