I measured what Electron apps really cost a 16GB Mac. Some are worth it. Some are a very expensive way to send one request.
My Mac has 16GB of RAM. Most days it feels fine, until it doesn't. A few weeks ago I opened Activity Monitor to see what was eating the memory, and half the list was apps I barely thought about.
So I stopped guessing and measured. Same Mac (M4, 16GB), same afternoon, apps just sitting open doing nothing.
The result that annoyed me most was Postman.
The test: one request, two tools
I opened Postman and left it alone for 45 seconds. No collection loaded, no request sent. Then I added up every process it started.
Postman 12.17.2, idle: 517 MB across 6 processes.
Then I sent a request with curl and asked macOS how much memory it needed at its peak:
/usr/bin/time -l curl -s -o /dev/null https://api.github.com/zen 2>&1 | grep "maximum resident"
curl, peak: about 7 MB. It finished in 0.6 seconds and was gone.
That's roughly 70 times more memory for a tool that was sitting there waiting for me. And the request was the same: one GET, one 200.
I'm not saying Postman is bad. It has collections, environments and a nice UI for teams. If you use those, keep it. But for "does this endpoint return 200?", I had been opening a 517 MB app to do what one line in the terminal does.
Why one app becomes six processes
Postman is an Electron app. So are Cursor, Claude, Wispr Flow and a lot of other things on my Mac. I checked: six apps in my /Applications folder ship with their own copy of Electron inside.
Electron bundles a full Chromium browser with every app. That's why the Postman list looked like this:
- one main process
- one GPU process
- one network process
- one renderer holding the actual interface (273 MB of the 517)
- a crash reporter
- an updater
It's basically a small browser, per app, that opens just to show one window. You'd never keep six Chrome windows open to read six notes. But that's what a few Electron apps do for you quietly.
The numbers on my Mac
Here is what I measured, live, on that same machine:
- Postman: 517 MB idle across 6 processes. The app is 337 MB on disk, plus 397 MB of app data.
- Cursor: 1.4 GB across 15 processes. The app is 971 MB on disk, plus 3.8 GB of app data.
Claude (626 MB) and Wispr Flow (610 MB) are two more Electron apps; both were closed when I measured, so I only have their size on disk.
Cursor was in use while I measured, so that number is a working editor, not an idle one. I'm including it because 15 processes is the point: an editor like that is doing real work, and I'm happy to pay for it.
I'd rather admit one more thing. Not everything native is tiny either. Telegram, which is a native Mac app, sat at 258 MB for me. So "native always wins" isn't the lesson here.
The rule I use now: is the app the work, or a wrapper around the work?
This is the one idea from the whole experiment.
Keep an Electron app when it's the place where you spend hours. Your editor. Your design tool. The thing you live in. A big memory cost is fair when the app is doing the heavy lifting all day.
Replace it when it's a window around a small task. Sending one request. Checking one thing. Running a command. For those, the app is costing memory the whole time just to be there when you want 2 seconds of work.
Ask it like this: if this app disappeared, would I lose a workflow or just a button? Postman, for me, was a button.
How to check your own Mac in two minutes
You don't need to trust my numbers. Here's how to get yours:
- Open Activity Monitor, click the Memory column to sort.
- Look for apps with many processes under one name (Electron shows up as "Helper", "Helper (GPU)", "Helper (Renderer)").
- To total one app from the terminal:
ps -axo rss=,command= | grep -F "/Applications/Postman.app" | grep -v grep | awk '{s+=$1} END{printf "%d MB\n", s/1024}'
- To find out which of your apps are Electron at all:
for a in /Applications/*.app; do [ -d "$a/Contents/Frameworks/Electron Framework.framework" ] && echo "$a"; done
On mine that printed six apps. I'd guessed two.
Then ask the question above for each one. I moved my quick API checks to curl, and kept the heavy-use apps exactly where they were. The Mac isn't magically faster, but when I'm on battery I'm no longer paying 500 MB for a window I opened by habit.
Which one should you do?
-
If you test APIs a few times a week: use
curland keep a small notes file of your usual requests. - If your team shares Postman collections: keep Postman, but quit it when you're done, because it doesn't need to live in the background.
- If you have 8GB of RAM: this matters more than it does for me. Every idle Electron app is a bigger slice.
- If you have 32GB or more: you can mostly ignore all of this. Memory is cheap when you have plenty of it.
But honestly, don't trust a stranger's numbers, including mine. Spend two minutes with Activity Monitor and see what's really sitting in your RAM.
Quick answers
Why do Electron apps use so much RAM?
Each one ships its own copy of Chromium, so a single app starts several processes: main, GPU, network and renderers.
Is Postman an Electron app?
Yes. On my Mac it started 6 processes and used 517 MB while idle.
How do I see which Mac apps are Electron?
Check for an Electron Framework.framework folder inside the app's Contents/Frameworks. The command above does it for every app in /Applications.
Is curl a real Postman alternative?
For one-off requests, yes. For shared collections, saved environments and team workflows, no.
If you liked this, I write about Mac apps and tools I actually test. Follow me here, or find me on X: @priyanshudotsol.
Top comments (0)