WebStorm Indexing Takes Forever

How to fix it

Try these in order — the most common fix is first.

1. 1. Exclude generated folders

   Copy steps
   1. Open the Project tool window (Alt+1)
   2. Right-click the folder and choose Mark Directory As | Excluded
   3. Excluded folders are not indexed, so completion and navigation do not work inside them
   Did this fix it? Yes No

2. 2. Pause indexing

   Copy steps
   1. Click the progress in the status bar to open the Processes dialog
   2. The main analysis can be paused and resumed but not canceled; file scanning cannot be paused
   Did this fix it? Yes No

3. 3. Let it finish first

   1. You cannot speed up a running analysis; wait for it to complete, then simplify the project to make the next one faster
   Did this fix it? Yes No

Symptoms

The status bar shows indexing or scanning for a long time and the IDE feels slow after builds or branch switches.

Why it happens

• Very large project
• Many files generated by a build or package install
• Large external file changes
• Generated folders (dist, build, caches) are not excluded

This guide also covers

• webstorm indexing slow
• webstorm indexing node_modules
• webstorm stuck indexing

The same problem in other apps

All slow, laggy or resource-hungry guides →

• VS Code High CPU Usage (VS Code)
• IntelliJ IDEA High Memory Usage (JetBrains IntelliJ)
• Sublime Text Slow or Glitchy Display: Indexing and GPU Settings (Sublime Text)
• Why Is Neovim So Slow? (Startup Lag and Large Files) (Neovim)
• Cursor Slow, High CPU or Memory Usage (Cursor)

Other WebStorm errors

• WebStorm Node.js Interpreter Not Configured
• WebStorm ESLint Not Working
• WebStorm Prettier Not Working
• WebStorm TypeScript Language Service Errors and Slowness
• WebStorm High Memory Usage: Increase Heap Size
• WebStorm Debugger Not Attaching or Breakpoints Not Hit
• WebStorm License Activation and Login Problems