// troubleshooting guide · pulsar
Why Is Pulsar So Slow
- Status
- Workaround available
- platforms:
- Windows, macOS, Linux
- updated:
- November 15, 2026
- reports:
- 3
- Method
- how we research
RUNBOOK · pulsar/slow4 FIXES
// quick answer
Pulsar is an Electron app, so startup and memory are heavier than native editors. Disable unused packages, update to 1.133 and tune large-file settings.
Most likely fix: Update to the latest release
How to fix it
// try these in order, the most common fix is first
FIX 1Update to the latest release
- 01Download Pulsar 1.133.x from pulsar-edit.dev
- 02Install over the old version
- 03The 1.127 large-file highlighting pauses are fixed in 1.133
Did this fix it?FIX 2Disable unused packages
- 01Open Settings > Packages
- 02Disable packages you do not use
- 03Restart and compare startup time
Did this fix it?FIX 3Raise the large-file threshold behavior
- 01Open Settings > Editor
- 02Adjust editor.largeFileThreshold (added in 1.132)
Did this fix it?FIX 4Try safe mode to find the culprit
- 01Run pulsar --safe from a terminal
- 02If it is fast, re-enable packages one by one
Did this fix it?
Symptoms
Slow startup, lag while typing, pauses in large files.
Why it happens
- C-01Many community packages loading at startup
- C-02Syntax-highlighting regression in 1.127 to 1.132 on big files
- C-03Electron memory overhead
// this guide also covers
- pulsar slow
- pulsar editor slow startup
- pulsar high memory
Still not working?
If Pulsar keeps failing, you're not alone. See every Pulsar problem users report or the alternatives people switch to.
Have an app idea? Our small team builds any software: web and mobile apps, games, desktop, AI tools. Price agreed together.
Talk to us
