Postman Slow and High Memory or CPU Usage

How to fix it

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

1. 1. Clear cache

   1. Force close Postman, relaunch, Help > Clear Cache and Reload
   Did this fix it? Yes No

2. 2. Lighten the runner

   1. In Collection Runner deselect 'Persist responses for a session' and select 'Turn off logs during run'
   Did this fix it? Yes No

3. 3. Split large collections

   1. Break one huge collection into smaller ones and close unused tabs
   Did this fix it? Yes No

4. 4. Toggle hardware acceleration

   1. macOS: Postman > Disable Hardware Acceleration. Windows/Linux: Help > Disable Hardware Acceleration, then restart (may change CPU use)
   Did this fix it? Yes No

5. 5. Send logs to support

   1. View > Developer > View Logs in Finder/Explorer, and attach to a support request
   Did this fix it? Yes No

6. 6. Try a lighter client

   1. Bruno, Insomnia, Hoppscotch or Thunder Client use less memory for simple workflows
   Did this fix it? Yes No

Symptoms

Slow startup, laggy typing, freezing with large collections, and high RAM or CPU in Task Manager or Activity Monitor.

Why it happens

• Electron app baseline memory use
• Very large collections or many open tabs
• Collection Runner persisting responses in memory
• Stale cache after updates
• Hardware acceleration issues

This guide also covers

• why is postman so slow
• postman high cpu usage
• postman using too much memory
• postman not responding

Other Postman errors

• Postman Could Not Get Response Error
• Postman Error: connect ECONNREFUSED
• Postman SSL Error: Self Signed Certificate
• Postman CORS Error in Web App
• Postman Scratch Pad Removed: Login Required to Save
• Postman Collection Runner Limit: You've Exhausted All Available Runs
• Postman Collections Not Syncing
• Postman Lost My Collections