I’m replacing an aging desktop that I use for work, mostly with a browser open, documents, spreadsheets, email, and video calls. It has started slowing down when I switch between those tasks, and memory usage often stays close to full even when I’m not doing anything unusually demanding. This machine is for my day-to-day work, not gaming or heavy media editing.
What is considered a normal amount of RAM for everyday use now? I’m trying to understand what a sensible baseline is for this kind of workload, and how much headroom matters if I tend to keep several work apps and browser tabs open throughout the day.
Open Task Manager during a typical busy hour and watch Memory and Disk while switching between your usual apps. A high memory percentage by itself is not necessarily bad. Windows uses spare RAM for caching and can reclaim it when applications need more. The stronger warning signs are sluggish switching, frequent tab reloads, and sustained disk activity while memory is nearly exhausted.
For a new everyday work desktop, I’d treat 16 GB as the baseline. It handles a browser, Office-type applications, email, and video meetings without requiring much micromanagement. I would choose 32 GB if you routinely keep dozens of tabs open, work with large spreadsheets, run several communication apps, or expect to keep the computer for many years. The extra RAM is mostly about avoiding slowdowns during busy periods rather than making simple tasks noticeably faster.
I would only buy 8 GB for very light use and a strict budget. It can run the workload you described, but there is little breathing room once a browser, meeting software, cloud syncing, security tools, and background applications are active. Microsoft’s Windows 11 minimum is just 4 GB, but that is an installation requirement, not a useful target for a work computer.
Make sure the replacement has an SSD as well. If the aging desktop still uses a hard drive, some of the slowdown blamed on RAM may actually be paging to slow storage. Browser memory-saving features can help by suspending inactive tabs, but I would rather start with enough memory than depend on tabs constantly unloading and reloading.
Whether or not the machine returns to normal after a reboot is important. If the machine is fast when it starts up, but then slows down over a few days as memory fills up, something is using up memory as time goes on. A browser extension, a meeting application, or another utility may be causing problems. Adding more RAM would slow the machine down less, but it wouldn’t actually solve the issue.
@bytebuilder2893studi is right to focus on disk activity, but I’d sort Task Manager by memory and leave it open when the problem occurs. Browsers have their own task manager too, which can expose a single bloated tab or extension. Testing with extensions disabled or a clean browser profile is a quick way to separate a software problem from a genuinely undersized system.
For the replacement, you should avoid the entry-level configuration and opt for an upgradeable option. The middle-tier is the best choice for regular office use. You may want to consider buying the higher-end if you are going to keep it open-ended all the time, but it is better to get an upgradeable one instead of spending a significant amount upfront.
Run your usual workload, then look at “Available” and “Committed” under Task Manager’s Memory page instead of judging the big percentage alone. If several gigabytes remain available and the committed figure is well below its limit, the RAM is doing its job. The slowdown is probably elsewhere, such as a busy processor, cloud syncing, antivirus scans, or an old drive.
Video calls can make this look worse than expected. Cameras, background effects, screen sharing, and integrated graphics may all borrow system memory. A machine that behaves normally until a meeting starts may simply have too little headroom for that combination.
For the replacement, avoid the smallest memory option. The normal midrange configuration suits the workload you described, while doubling that amount is mostly buying room for messy habits: lots of tabs, large files, several chat clients, and leaving everything open for weeks. Don’t expect extra memory to make Word launch twice as fast. Its main benefit is keeping the system from stumbling when you switch tasks.
I agree with @signallab about upgradeability, with a catch: check how the slots are populated. “Upgradeable” is less useful when every slot is occupied from day one and an upgrade means throwing out the installed modules. For a desktop, an open slot and a sensible starting configuration can save more money than paying the manufacturer’s markup upfront.
Watch out for single-stick configs on the cheaper models. One module means single channel, and on a desktop leaning on integrated graphics that actually drags down the video call scenario @novapanda described, not just raw capacity. I’d rather two smaller matched sticks than one big lonely one.
The page file setting is missing from this diagnosis. If it was disabled or manually capped at some point, the computer can become sluggish or unstable as physical memory fills. Leave it system-managed unless you have a specific technical reason not to. Normal page-file activity is harmless. Constant paging that makes every app switch pause is the problem.
I’m skeptical of judging a machine by the memory percentage at all. Some systems sit near the top of the graph for hours and remain responsive because cached data is discarded when needed. Others become miserable at a lower percentage because a browser tab, sync client, or security process is hammering the processor and storage. If clicking back into a spreadsheet gives you a blank window, browser tabs repeatedly rebuild themselves, or audio breaks up during calls, then you have actual memory pressure rather than an unattractive number in Task Manager.
For the replacement, I would skip the cheapest memory configuration. Choose the normal office tier if you close things occasionally. Move up one tier if your browser is effectively your entire workspace, especially with several web apps, shared documents, chat clients, and meetings running together. Tab count can be misleading here. A handful of heavy web applications may consume more memory than a large pile of ordinary pages.
I wouldn’t make @vectorbyte5017node’s matched-pair advice an absolute rule, either. Dual-channel memory helps integrated graphics, but filling every slot with smaller modules can turn a later capacity upgrade into a replacement job. On a desktop with only a couple of slots, a single larger module may be the less annoying configuration if adding its mate later is cheap and easy. Check the service manual rather than trusting a store listing that merely says “upgradeable.”
Budget matters too. I’d rather put money into more memory and a decent solid-state drive than pay for a higher processor tier that will spend most of its life waiting for browser tabs and documents. Just don’t assume a new machine with more RAM will cure a leaking extension or badly behaved background utility. If performance steadily worsens over several days and immediately returns after a restart, that pattern still deserves investigation.
A standard shutdown is not always as tidy as the reboot would suggest: Windows Fast Startup can retain some of the system state, so it is best to use Restart to retest if the memory consumption and performance aberration return to normal. It is best to compare the memory footprint and performance of the machine after a fresh reboot with the same memory footprint several days later.
In Task Manager, under the Details tab, bring the “Commit size” column to view and sort by it in case of a slowdown. Browsers tend to split their processes, but one ought to keep an eye on a particular process or a set of processes that consistently grow in memory consumption when in a seemingly idle state: that is a sign of a memory leak. If the commit sizes remain consistent and the spikes occur when the drive is utilized most heavily, one is most likely to witness paging activity or other disk-related activity that taxes the memory.
As for the replacement, it is best to get the regular memory configuration for the everyday use machine and test it under one’s actual workload during the return period. After launching the ugly spreadsheet, a call, screen-sharing session, and the browser profile one actually uses, one can see if the new machine is ready to keep up or if a higher density is necessary. It is better to size the machine according to the actual workload rather than a fresh demo session or a browser tab without any relevant activities.
Don’t spend money just to make Task Manager’s graph look prettier. Open Resource Monitor and watch “Hard Faults/sec” while switching apps. Brief bursts are normal, despite the wonderfully alarming name; sustained spikes paired with pauses mean Windows is fetching memory from storage. For the replacement, check whether the RAM is soldered before choosing capacity. If it cannot be upgraded, buy extra headroom now. If it uses standard modules, start with the regular office configuration and expand only if your real workload actually pushes it.