Problem: Fortnite PC stutter + “Preparing Shaders” loading every match (DX12) — after updates, many players can’t get stable performance

Published: 2026-01-02 12:00 (local time)

Quick Summary

• Many Fortnite PC players report heavy stuttering, long “Preparing Shaders” phases, and late spawns after updates—especially when using DirectX 12.
• Symptoms often look like “shader compilation loops”: the game compiles shaders repeatedly instead of settling after the first match.
• Epic acknowledges a DX12 scenario where Fortnite may repeatedly recompile shaders and recommends clearing shader cache.
• There is no single reliable fix; results vary by GPU vendor (NVIDIA/AMD), driver version, and local cache state.
• Workarounds focus on resetting shader caches, stabilizing drivers, and reducing in-game shader churn until Epic/driver updates fully resolve it.

What’s happening

Across multiple community reports over the past year, a recurring Fortnite PC problem has intensified around major updates: the game hangs on “Preparing Shaders,” loads into matches late (sometimes after the Battle Bus route has progressed), and stutters heavily once in-game. Players commonly describe severe frame-time spikes (even if their average FPS looks fine), sudden FPS drops during fights, and “first match after launch” behavior that never improves—because the shader process appears to restart repeatedly.

The issue is most often described on Windows PCs using DirectX 12 (DX12). Some players say switching render mode (DX11 vs DX12) trades one problem for another (less shader hitching but worse overall performance or different stutter patterns). Reports appear across different hardware tiers—from midrange laptops to high-end desktops—suggesting the problem is not limited to “weak PCs,” but rather to how shaders/caches/drivers interact after certain updates.

Epic’s own support documentation describes a specific failure mode: Fortnite can repeatedly recompile DirectX shaders “without stopping,” causing heavy stuttering on DX12, and recommends clearing shader cache as a potential fix. Community threads also show people trying many steps (reinstalls, streamed assets, driver updates) with mixed results—meaning it’s widespread enough to be recognized, but still frustratingly inconsistent.

Likely causes (what research suggests)

• Repeated DX12 shader recompilation or corrupted shader cache. Epic states that sometimes the Fortnite client “repeatedly recompile[s] DirectX shaders,” leading to heavy stuttering, and suggests clearing shader cache to address it.

• Driver-level shader cache corruption or mismatch after driver/season updates. NVIDIA notes that shader cache files can become corrupted and cause crashes, lower performance, or artifacts, and deleting them forces regeneration (which can restore stability).

• “One-time” compilation becoming “every time” compilation. Community reports describe “Preparing Shaders” on every launch and slow/late match loads, implying the cache is not persisting correctly (permissions, corruption, or something repeatedly invalidating it).

• CPU bottleneck during shader build causing frame-time spikes. Some players observe shader compilation saturating CPU threads, creating the perception of “random stutter,” especially right after an update.

Solutions & Workarounds

1) Clear Fortnite-related DX shader caches (Epic’s recommended path)

Who it helps: Windows PC players using Fortnite DX12 with heavy stutter / repeated shader compilation.

Steps:

• Close Fortnite and the Epic Games Launcher.
• Press Windows + R, type %appdata%, press Enter.
• Navigate up to the main AppData folder, then follow Epic’s folder steps for your GPU vendor (NVIDIA or AMD) and delete files inside the DX cache directories.
• Launch Fortnite and play 1 match. Expect the first match to be stuttery while shaders rebuild.

Risks / tradeoffs: First launch/match may stutter more than usual while rebuilding cache; deleting the wrong folders could remove unrelated app caches if you’re careless.

When to stop & contact support: If Fortnite begins crashing immediately after cache deletion, or if stutter remains identical after repeating the procedure once, proceed to other workarounds and then contact Epic Support.

2) Reset NVIDIA shader cache using NVIDIA’s guidance (then rebuild cleanly)

Who it helps: NVIDIA GPU players where stutter appeared after a driver or Fortnite update.

Steps:

• Open NVIDIA Control Panel > Manage 3D settings.
• Set Shader Cache Size to Off, click Apply, then reboot.
• After reboot, delete shader cache files using NVIDIA’s support instructions (manual deletion method).
• Turn Shader Cache back On (or Driver Default), reboot again, then launch Fortnite to rebuild.

Risks / tradeoffs: Temporarily disabling shader cache can reduce performance in some games until re-enabled; rebuilding will cause short-term hitching.

When to stop & contact support: If performance degrades across many games after this (not just Fortnite), roll back to a known-good driver or contact NVIDIA support.

3) Clean-install GPU drivers (DDU approach) if the problem began right after a driver update

Who it helps: Players whose stutter started immediately after changing GPU drivers and persists even after cache clears.

Steps:

• Download the latest stable GPU driver from your vendor.
• Use a clean uninstall method (many users reference DDU workflows), reboot, then install the driver fresh.
• Launch Fortnite and allow one full match for shader rebuild.

Risks / tradeoffs: If done incorrectly, you can lose display settings or install the wrong driver branch; expect shader rebuild stutter initially.

When to stop & contact support: If you experience system instability (BSODs, black screens) after clean install, stop and contact your GPU vendor support.

4) Temporarily switch rendering mode (DX12 <-> DX11) to reduce “shader hitching loops”

Who it helps: Players stuck in repeated DX12 shader prep or extreme stutter immediately after updates.

Steps:

• In Fortnite video settings, switch rendering mode from DirectX 12 to DirectX 11 (or vice versa).
• Restart Fortnite (required).
• Test one full match; compare frame-time consistency (feel) rather than average FPS.

Risks / tradeoffs: DX11 may reduce performance/features (depending on your setup), while DX12 may reintroduce shader stutter.

When to stop & contact support: If either mode hard-crashes on launch or you can’t reach the lobby consistently, contact Epic Support with logs.

5) Reduce shader churn: cap FPS and lower the biggest “spike generators” for one session

Who it helps: Players who can play but get constant hitching during combat or fast camera movement post-update.

Steps:

• Set a conservative FPS cap (e.g., 60/90/120 depending on your monitor) to smooth frame pacing during rebuild periods.
• Lower settings that commonly increase shader/streaming pressure (shadows, effects, view distance) for 1–2 matches.
• After performance stabilizes (if it does), raise settings gradually.

Risks / tradeoffs: Visual downgrade; may not fix root cause—this is stabilization, not a cure.

When to stop & contact support: If stutter is identical even at low settings and capped FPS, the issue is likely cache/driver/update-related—move on to cache/driver workarounds and then support.

6) Verify game files and avoid repeated reinstalls unless nothing else works

Who it helps: Players who suspect partial/corrupt content after an update.

Steps:

• Use Epic Games Launcher’s Verify option for Fortnite.
• Reboot, then test.
• If verifying doesn’t help, only then consider reinstalling (as a last resort).

Risks / tradeoffs: Verification/reinstall costs time and bandwidth; reinstall does not guarantee fixing a driver/cache loop.

When to stop & contact support: If verifying and caches/driver steps don’t help, gather logs and contact Epic Support—your case may depend on a bug fix rather than local changes.

Prevention (so it doesn’t come back)

• After major Fortnite updates, plan for 1–2 “warm-up” matches where shader compilation may hitch; don’t judge stability from the first 2 minutes.
• Avoid stacking multiple major changes at once (new driver + new Windows updates + new Fortnite season) if you need reliability; change one variable at a time.
• Keep adequate free SSD space; shader caches and streamed assets need room to behave normally.
• If you find a stable driver version, note it. When updating drivers later, keep the installer for rollback.

FAQ

• Q: Why does it say “Preparing Shaders” every time?
  A: Research and user reports suggest the shader cache may not be persisting properly (corruption, repeated invalidation, or a DX12 loop). Epic specifically acknowledges repeated DX shader recompilation can happen in Fortnite.

• Q: Will deleting shader caches make things worse?
  A: Temporarily, yes—your first match can be choppy while shaders rebuild. If the cache was corrupted or stuck in a loop, rebuilding can improve stability.

• Q: Is this only an AMD issue?
  A: No. Community reports include AMD and NVIDIA. The “shape” of the issue may differ by driver branch and Fortnite version, but both vendors appear affected in practice.

• Q: Should I switch to DX11 permanently?
  A: If DX11 is stable for you, it’s a valid workaround. The tradeoff is potentially lower performance or missing DX12-specific benefits, depending on your setup.

• Q: I cleared cache and it still stutters. What next?
  A: Try a clean GPU driver install, test the alternate rendering mode, and verify files. If none help, it may require an Epic-side patch or a driver fix—contact support with logs.

• Q: Does reinstalling Fortnite fix it?
  A: Sometimes, but many reports suggest reinstalls aren’t consistently reliable because the root cause can be driver/cache behavior rather than missing game files.

Sources & References