How much RAM you actually need
How to size memory from the pressure your machine is under now, why running short quietly costs speed, and when a matched pair beats one stick.
Updated
On this page
Size memory for the load the machine is under, not for a number that sounds about right. That load is something you can measure while you work, and it settles most of the question. The rest is reading it correctly and leaving room above it.
What the machine is using now
The figure that matters is not how much memory is free. A modern operating system fills spare memory with cached files on purpose, because idle memory helps no one, and hands it back the moment a program asks. So a machine reporting almost no free memory may be under no strain at all. What you want is the pressure underneath that.
On Windows, open Task Manager, then Performance, then Memory. Read two lines: In use, the memory programs hold right now, and Committed, the total they have been promised against physical memory plus the page file. When committed climbs past the memory installed, the machine is leaning on disk to cover the gap. On macOS, open Activity Monitor, then Memory, and read the Memory Pressure graph at the bottom. Green means the machine is comfortable; yellow and red mean it is working to keep up. That graph is the honest answer, not the used-memory figure above it.
Take the reading while you are actually working — the applications you keep open together, the tab count you really run to, the background you forget is there. A machine measured at rest tells you what a machine at rest needs, which is not the question.
What running short costs
When programs ask for more memory than the machine has, nothing fails. The operating system moves the least recently used pages out to disk — the page file on Windows, swap on macOS — to free room for what you are touching now. The moment something reaches for a page that was moved out, the machine has to fetch it back before the program can continue, and the program waits the whole time.
That wait is the cost, and it does not show up as a number. It shows up as a hitch when you switch back to a tab, a stutter when a background task wakes, a save that pauses longer than it should. A fast SSD makes the fetch quicker and the hitch shorter, which is why running short on a modern machine is bearable rather than painful. It does not close the gap: memory answers in tens of nanoseconds, and even a quick drive answers in tens of microseconds — a thousandfold longer. The drive softens the fall. It does not stop you falling.
So the goal in sizing is to keep committed memory under what is installed during the work you actually do, with room above it for the background you did not count.
Sizing to what you do
Start from the reading and add headroom, because the load is never only the one program you have in mind. The operating system, the browser and its tabs, a chat client, a password manager, and whatever syncs in the background all hold memory before your real work opens.
Light work — browsing, office documents, one game at a time — sits comfortably where mainstream machines already do. Keep many tabs open next to a photo or video editor, run a virtual machine, or game with a launcher, a browser, and a chat overlay all live, and the comfortable figure steps up. Heavier still is the work that holds large files in memory by nature: high-resolution editing, local compilation, several virtual machines at once. There the question stops being whether you have enough and becomes how much the work will grow into.
None of these is a line you cross at a fixed number. Each is a band, and where you land in it depends on how much runs beside the task you are thinking of. Size for the machine you use, background included, not for the one program in front of you.
One kit or two sticks
Two sticks are usually better than one, and the reason is bandwidth. A memory controller with two channels can read from two sticks at once, roughly doubling how fast data moves between memory and the processor. Most work does not notice; integrated graphics, which borrow system memory in place of their own, notice a great deal, and some games feel it too.
The trap is buying one stick now and planning to match it later. Two sticks run together only if they can agree on a speed, and a stick bought months apart from a different production run may refuse the pace its partner keeps, dropping both to a slower setting — or failing to run as a pair at all. Filling every slot works against you from the other side: many boards can only hold their rated speed with two sticks installed, and drop it when all four slots are populated, because the controller is driving twice the load.
So buy the capacity you want as a matched kit, in as few sticks as reach it. That is why a kit here carries its stick count: a 32 GB kit as two 16 GB sticks and the same 32 GB as four 8 GB sticks are not the same purchase, and the pair leaves you room to grow that the full set does not.
How we track a kit's capacities
A kit sold at several capacities is one product with several sizes here, not several unrelated products. Each size is tracked on its own, with its own current price and its own price history. The sizes do not move together — a run on 32 GB kits does not touch what 16 GB sells for — so folding them into one figure would misprice every size.
The kit's own page is where the sizes separate. The price that leads the page is the cheapest size currently tracked; below it, each size is listed with its own price, and the chart draws one line per size. Decide the capacity you are sizing for before you read the price.
Every RAM kit in our catalog is on one page.
Common questions
- Is 16 GB enough?
- For browsing, office work, and most games one at a time, usually yes. If you keep many tabs open beside a creative application, run virtual machines, or game with a lot in the background, 32 GB removes the stalls that 16 GB starts to show.
- Do I need two sticks instead of one?
- A matched pair lets the controller read across two channels at once, which is worth the most on a machine leaning on integrated graphics. Buy the capacity you want as a kit rather than one stick you plan to match later, because a mismatched second stick may refuse to run at the same speed.