Fix: Cursor Using Too Much Memory (RAM)
Quick Answer
Close unused tabs, disable extensions you don't use, and add large directories (node_modules, .git, dist, build) to .cursorignore to reduce indexing load.
Quick Fix Summary
| Issue | High memory usage |
| Fastest fix | Close unused editor tabs |
| Use this page if | Cursor using 2GB+ RAM |
Symptoms
- !Cursor using 2GB+ RAM
- !System becomes slow when Cursor is open
- !Cursor crashes on large projects
- !Fan running constantly
Step-by-Step Fix
Close unused editor tabs
Each open tab consumes memory. Close tabs you're not actively using. Use Cmd+K Cmd+W to close all tabs.
Create .cursorignore
Create a .cursorignore file in your project root with: node_modules, .git, dist, build, .next, coverage, *.log. This prevents Cursor from indexing these directories.
Disable heavy extensions
Some extensions (GitLens, Prettier with large configs) consume significant memory. Disable non-essential ones.
Reduce workspace size
If your workspace includes multiple large projects, open only the project you're working on.
Restart Cursor periodically
Memory can leak over long sessions. Restart Cursor every few hours during intensive work.
Frequently Asked Questions
Cursor typically uses 500MB-1GB for medium projects. Over 2GB indicates issues with indexing or extensions.
Slightly more due to AI features and indexing. The difference is usually 200-400MB.
Related
Weekly Signals
Get the next fix, switch, or warning before it hits your build.
Join builders getting the community signals, fix patterns, and tool shifts that matter before they show up everywhere else.
Follow the signals →