How to Fix Apex Legends When It Keeps Compiling Shaders on PC

If Apex Legends keeps compiling shaders on every PC launch, let one full compile finish, then test a second launch before changing anything. If the same long process returns, reset the Windows shader cache once, check the graphics driver’s cache settings, and repair the game files through your launcher. Do not clear shader caches before every session: that forces another rebuild instead of fixing why the cache is not being reused.

A one-time compile after a game update, graphics-driver change, or cache reset is expected. NVIDIA notes that installing a new driver deletes its shader cache, so the first game run afterward can stutter while shaders are rebuilt. The issue to troubleshoot is repeated compilation without another update or reset in between. See NVIDIA’s Shader Cache Size documentation.

1. Let one complete compile finish

Before deleting files, close unnecessary apps and let Apex reach the lobby. Do not force-close the game during compilation. Exit normally, then launch it again. If the second launch skips the lengthy compile or is noticeably faster, stop troubleshooting; the cache is working as intended.

If the same compilation starts again, note whether you recently installed a game patch, changed GPUs, updated the driver, or ran a cleanup tool. That timing can help identify what is invalidating the cache.

2. Clear the DirectX shader cache once

On Windows 11 or Windows 10, open Settings > System > Storage > Temporary files. Select DirectX Shader Cache, review the other selected categories, and choose Remove files. Microsoft’s Windows storage settings guide explains how to reach Temporary files. The exact list can vary by Windows version; if you do not see DirectX Shader Cache, skip this step rather than deleting unfamiliar folders.

Restart Windows and open Apex once to let it rebuild the cache. That first launch may take longer. The important test is what happens on the next launch. Repeating this reset will only make the game rebuild shaders again.

3. Check the GPU driver and shader-cache settings

Install graphics drivers from the GPU manufacturer’s official site. EA’s PC graphics troubleshooting guide recommends updating the graphics driver and describes a clean installation as a way to reduce conflicts between old and new driver components. If you recently updated and the first compile is the only symptom, let the rebuild finish before reinstalling or rolling back anything.

• NVIDIA: Open NVIDIA Control Panel and select Manage 3D settings. Find Shader Cache Size and leave it at the driver default or a suitable non-restrictive limit. NVIDIA says a limit that is too small can cause older cached shaders to be removed. Avoid disabling shader caching.
• AMD Radeon: AMD Software: Adrenalin Edition includes Reset Shader Cache. Use it once if you suspect a damaged cache, then let Apex rebuild it. AMD explains that the cache stores frequently used compiled shaders and that this control deletes the stored cache files in its graphics settings documentation.
• Intel: Use the current driver package for your specific GPU from Intel Download Center. Keep the driver’s cache options at their defaults unless Intel support directs you otherwise.

If the problem began after several driver installations or other graphics issues appeared at the same time, follow the manufacturer’s clean-install instructions instead of layering more driver packages over one another.

4. Repair or verify Apex Legends files

A damaged or incomplete game file can cause launch and graphics problems, so check the installation after the cache and driver steps.

• EA app: Open Library, select the three-dot menu on the Apex Legends tile, and choose Repair. EA lists this process in its EA app game repair guide.
• Steam: Right-click Apex Legends in your Library, open Properties > Installed Files, and select Verify integrity of game files. Steam’s verification instructions explain that Steam checks the installed files and replaces files it finds incorrect.

Let the check finish, restart the launcher, then run Apex twice. The first launch may still compile shaders; the second tells you whether the rebuilt cache is being reused.

Clear the EA app cache only if the launcher is also stuck

The EA app cache is separate from the DirectX and GPU shader caches. Clear it when the EA app itself has download, update, or loading problems—not as the first response to a shader-only loop. In the EA app, open Help > App Recovery > Clear Cache. EA documents the current path in its download and loading troubleshooting guide.

How to tell whether the problem is fixed

Use a simple two-launch check: let Apex finish compiling, close it normally, and open it again without clearing any cache. A successful fix does not have to make the next launch instant, but it should not repeat the same full compilation every time.

If it still recompiles after one cache reset, a driver check, and file repair, stop repeating those steps. Check whether other games also rebuild shaders after each restart, and review whether a disk-cleanup utility is removing graphics caches automatically. If multiple games are affected, the driver or Windows environment may be involved; if only Apex is affected, gather your GPU model, Windows version, driver version, launcher, and when the loop begins before contacting EA. EA’s DxDiag guide explains how to prepare system details for support.

What not to do

• Do not delete shader caches before each play session.
• Do not disable shader caching as a permanent fix.
• Do not use registry cleaners or unofficial cache scripts to remove files.
• Do not assume one compile after a game or driver update means Apex is broken.

The safest fix for Apex Legends continuous shader compilation is to let one rebuild complete, make one deliberate cache reset only if needed, and then verify that the game can reuse the cache on the next launch.