Why is Obsidian using so much CPU or memory on my Mac?
Last reviewed: 19 November 2026.
Obsidian for Mac is built on Electron, so it runs Obsidian Helper processes for its interface and graphics, and every community plugin you enable runs its code inside the app. A plugin doing heavy work, a very large vault being indexed, or big files and embeds on screen are the usual causes of high CPU or memory. Turning plugins off one at a time, or turning on Restricted Mode to disable all of them, shows whether a plugin is responsible.
Which Obsidian processes appear in Activity Monitor?
Obsidian 1.12.7 contains Electron Framework and four helpers. You see the main Obsidian process plus Obsidian Helper (Renderer), which runs the editor, the file explorer and plugins; Obsidian Helper (GPU), which draws the window; Obsidian Helper (Plugin); and a plain Obsidian Helper for utility work. Most CPU and memory show up on the Renderer row.
Each open vault window has its own renderer, so two vaults open at once roughly double the interface's footprint.
Why can plugins make Obsidian slow?
Obsidian's documentation states that community plugins run third-party code on your behalf. Some index your whole vault, render diagrams or maintain live queries over every note, and that work happens in the same renderer as the editor. Community plugins do not update automatically, so an older plugin version can keep a problem you have already seen fixed elsewhere.
How do you find what is slowing Obsidian down?
- Check the Renderer process. In Activity Monitor, filter for
Obsidianand confirm whether Obsidian Helper (Renderer) is the busy row. - Disable community plugins. Open Settings > Community plugins and turn on Restricted Mode (the opposite of Turn on community plugins). If CPU drops, a plugin is the cause.
- Re-enable plugins one at a time. Use each plugin's toggle, which enables or disables it without uninstalling, and watch Activity Monitor after each one.
- Update plugins manually. Because community plugins do not update automatically, check for updates in the Community plugins settings.
- Close extra vault windows. Close vaults you are not using so their renderers exit.
When should Obsidian's resource use concern you?
Brief CPU after opening a large vault, while Obsidian scans and caches its files, is expected. It is not typical for the renderer to stay busy while you are not typing, or for memory to climb steadily with one note open. With all community plugins disabled those symptoms should stop; if they do not, the cause is a specific note (very large files or many embeds) rather than a plugin.
How can Thrum help with Obsidian?
Thrum keeps a live CPU graph in the menu bar. One click shows the eight processes using the most CPU, so you can see when Obsidian is among them and how much it takes. An optional alert tells you when a process stays above a CPU level you choose (50 to 200% of one core) for 1 to 10 minutes. Click Obsidian in the list for its PID, threads and memory, and Quit or Force Quit it after a confirmation.
Thrum is $4.99 once with a 14-day free trial and no account. It requires macOS 26 Tahoe on Apple silicon or Intel.
Questions
Is Obsidian an Electron app?
Yes. The Mac app bundle contains Electron Framework and Obsidian Helper (Renderer), (GPU) and (Plugin) apps.
Does Restricted Mode delete my plugins?
No. It stops community plugins from running. Turning community plugins back on restores them with their settings.
Sources
- Obsidian Help: Community plugins
- Helper apps and frameworks listed in Obsidian 1.12.7 for Mac