Guides

16 GB vs 24 GB MacBook Air: measure it, do not guess

You cannot add memory later, so the question deserves better than a spec sheet. Your current Mac already knows the answer.

Last updated September 11, 2026 · by the RAMKeeper team

Every thread about this ends the same way: someone says 16 GB is plenty, someone else says they regretted not paying for more, and neither of them is describing your workload. The useful part is that this is not an opinion question. The Mac you are typing on right now is already keeping the three numbers that answer it.

This page is the procedure. It takes about a week of ordinary use and nothing needs installing. The same three readings, written up without the buying decision attached, are in how much RAM do I need.

Why the decision is worth measuring

On Apple silicon the memory is part of the chip package. There is no slot, no aftermarket upgrade, and no second chance: whatever you choose at checkout is what that machine has for its whole life. That is what makes this different from a PC buying decision, and it is why "you can always add more later" is not available as a fallback.

It also means the cost of guessing high and the cost of guessing low are not symmetric. Guessing high costs you the upgrade price once. Guessing low costs you a slower machine for years, or a resale and a repurchase.

The three readings

Take these on your current Mac, under your real workload. Not a benchmark, not a stress test: the apps you actually keep open on a normal working day.

1. Sustained swap, the one that decides it

sysctl -n vm.swapusage

Run it once a day for a week, at the end of a working day rather than after a fresh restart. Swap is disk standing in for memory, and it is the clearest signal that your Mac has run out of the real thing.

• Used stays at or near zero all week. Your current memory is keeping up with your current workload, with headroom.
• Used climbs during the day and resets when you restart. You are at the edge. This is the group where the extra 8 GB buys real comfort.
• Used is in the gigabytes most days. You are past the edge already.

One caveat that matters: a machine with more memory than the one you are buying will understate the problem, and one with less will overstate it. If you are measuring on an 8 GB Mac to decide between 16 and 24, read the numbers as "how far past 8 do I go", not as a verdict on 24.

2. Memory pressure, not free memory

memory_pressure -Q

Free memory is the number everyone looks at and the one that answers nothing. On the machine used for the measurements in our worked example, free memory sat at 1.2% of 64 GB while swap was at zero bytes and the system reported 64% free by pressure. Both figures were correct at the same instant. An operating system that leaves memory idle is wasting it; pressure is the figure that tracks whether memory is actually keeping up.

Watch the pressure graph in Activity Monitor while you work instead of the percentage. Green that stays green under your real load is the answer you are looking for.

3. Peak, not current

top -l 1 -o mem -n 12 -stats pid,command,mem
/usr/bin/footprint -p <pid>

The second command prints phys_footprint_peak, the high-water mark for that process since it started. Activity Monitor will not show you this, and it changes the picture: in the worked example, Docker was sitting at 0.47 GB with a peak of 2.75 GB, roughly six times its current size. An app that quietly takes six times its resting size once a day is exactly the kind of thing that decides whether 16 GB is comfortable or tight.

Add the peaks of the handful of apps you genuinely keep open together. That sum, not the sum of their current sizes, is the load your next Mac has to absorb.

Reading the result

The case where more memory is the wrong purchase

If your top app's peak is several times its resting size, or a single app is responsible for most of your total, you are not short of memory in general. You have one badly behaved program, and an extra 8 GB buys it more room to misbehave in.

That case is worth separating out before you pay, because the fix is different: quit and reopen that app on a schedule, or set a ceiling for it. The measured reading guide shows how to read current against peak, and the leak test separates the two cases in about an hour.

And to be explicit, since this page is published by a company that sells a memory tool: if the measurements say you need more memory, buy more memory. No software, ours included, creates RAM that is not there. What software can do is tell you which of the two situations you are in, which is exactly the question this page is about.

What about 32 GB, or the Pro chips?

The same three readings answer that too. The procedure does not care which configurations are on the page in front of you: measure the load, compare it against the option you are considering, and keep in mind that the sum you should compare against is the sum of peaks, not the sum of current sizes.

If the machine you are measuring on is an 8 GB Mac, start with is 8 GB enough instead: the readings are the same, but the thresholds that matter are different at that size.

Prices, configurations and which chips are offered change every cycle, so this page deliberately does not quote them. Check what Apple shows you at checkout on the day, and put your measured number next to it.

The short version

• Run sysctl -n vm.swapusage once a day for a week, at the end of the day.
• Zero swap all week means 16 GB is doing fine. Daily swap means buy 24 GB.
• Check peaks with /usr/bin/footprint -p, not current sizes.
• Ignore free memory entirely. Watch pressure.
• If one app dominates, fix the app before you pay Apple for the difference.

If you want those readings continuously instead of by hand, that is what RAMKeeper does in the menu bar, and the free build covers the measuring half: per-app and per-renderer attribution with current against peak. The commands above give you the same numbers for free, which is the point of printing them.

Disclosure: this guide is published by RAMKeeper, which sells a Mac memory tool. Every command on this page ships with macOS and none of them require our app.