Mac memory pressure. Read the graph before the RAM total.
A high RAM total is only one reading. Use pressure, swap and your actual workload together to decide whether your Mac needs attention.
By MacMonitor · Published · Updated · macOS 26; app requires macOS 14 or later
Short answer: open Activity Monitor → Memory and look at Memory Pressure while doing your usual work. Used RAM alone is not a fault. Persistent yellow or red pressure together with slowdowns is a reason to reduce the workload and investigate which apps are growing.
macOS uses otherwise idle RAM for cached files. Pressure also reflects factors such as swap rate, wired memory and cached memory, so a high used-memory number is not the same as a shortage.
Green, yellow and red
Graph
What to do
Green
Memory is serving the workload efficiently. Watch trends if an app keeps growing.
Yellow
Check whether pressure is brief or sustained. Save work and reduce an unnecessary workload if responsiveness suffers.
Red
The workload is putting memory under substantial pressure. Save work, close nonessential apps normally, and reassess.
What swap and compressed memory tell you
Compression keeps more inactive data in RAM. Swap uses startup-disk storage for memory contents. A nonzero swap total alone does not establish a problem; compare its growth with pressure and the experience of using the Mac.
Find the app behind the pressure
Open Activity Monitor from Applications → Utilities and choose Memory.
Sort the Memory column. Note the leading apps before changing anything.
Save work and quit one nonessential app normally; compare pressure during the same task.
If one app repeatedly grows during a reproducible task, check its updates and report that task to its developer.
Check under a representative workload before buying hardware. A restart can reset the symptom but does not identify its cause. Do not delete swap files or use a RAM purge as a substitute for diagnosis.
Read pressure during the task that feels slow
A screenshot taken while the Mac is idle cannot explain how memory behaves during a video call, a build or a large document import. Open Activity Monitor while doing the work that concerns you, then watch the graph for a while. Note what you launched and whether the slowdown started at the same time as a sustained change in pressure.
Keep the observation modest. One high memory total does not prove a leak, and one quiet sample does not prove that a recurring problem is fixed. What helps is a repeatable pattern: the same task, the same application, and a change you can observe more than once.
Separate useful caching from a growing workload
Memory can be used for active applications, system requirements, compressed contents and cached files. Those categories have different roles. Trying to make the used-memory number as small as possible can lead to unnecessary resets that throw away useful work without improving the experience of using the Mac.
Instead, ask whether applications remain responsive and whether pressure settles after the task completes. If you can identify a specific app that keeps growing during repeated work, save the steps that reproduce it. A useful report describes the document, operation or extension involved without including private content unnecessarily.
Example: many tabs versus one demanding document
Suppose your browser is open alongside a document editor and a development tool. This fictional example could involve many ordinary processes or one unusually demanding document. Closing random background processes is a poor way to distinguish them.
Save your work, then reduce one nonessential workload at a time. Close a known set of tabs, finish or pause a build through its own interface, or close the large document normally. Compare pressure and responsiveness after each change. If nothing improves, restore the work you need and reconsider the original assumption rather than continuing to close applications indiscriminately.
Interpret swap with available storage
Swap uses the startup disk, so storage constraints can matter during a memory-heavy workload. However, a nonzero swap figure is not a recommendation to delete swap files. Those files are managed by macOS. Inspect ordinary storage candidates through the free-space guide if the disk itself is constrained.
Compare the trend instead of judging one absolute number. Note whether swap grows while pressure remains elevated and whether the work is noticeably slower. A restarted Mac and a Mac that has completed a long work session are different baselines, so record that context before comparing screenshots.
Investigate a suspected memory leak carefully
A leak is a specific software problem, not a synonym for high RAM use. An application may legitimately retain more data as you open documents or perform a long operation. To investigate suspicious growth, try to reproduce it with a known task and compare what happens after closing the relevant document or completing the operation.
Update the application through its supported channel and check whether an extension or plugin is involved. If you can reproduce the problem, report the app version, macOS version, the sequence of actions and the observed behavior to its developer. Do not publish private documents or account data as part of that report.
Decide whether your workload needs different hardware
Use several representative work sessions before drawing a purchasing conclusion. A brief yellow graph during an occasional export is a different requirement from sustained pressure throughout your ordinary day. List the applications and projects that need to run together, and separate essential simultaneous work from tasks you can run at different times.
Check upgrade options for the specific Mac model rather than assuming memory can be added later. If a replacement is under consideration, use the real workload as the basis for comparison. A generic RAM percentage from another person’s Mac is not a reliable sizing recommendation.
What to record in a short memory note
Observation
Why it helps
Task and applications open
Explains what the Mac was being asked to do.
Pressure color over time
Distinguishes a brief event from sustained pressure.
Swap trend and available storage
Adds context without treating swap as a fault by itself.
One deliberate change
Makes the before-and-after comparison easier to interpret.
Responsiveness after the change
Connects the measurements to the problem you actually experienced.
Questions about yellow and red memory pressure
Does yellow mean I must quit everything?
No. Look at how long it lasts and whether the workload is affected. Save work and reduce a nonessential task if needed. An orderly change is preferable to force-quitting applications without knowing which one matters.
Can clearing caches reduce memory pressure?
Disk caches and active memory are different things. Removing files from a cache directory is not a general solution to a memory-heavy workload. Start with the application and task involved, and keep storage cleanup as a separate investigation.
Should a monitor display the same figures as every other tool?
Different tools can group applications or summarize categories differently. Compare the definition and time window of each figure. A grouped app total and a per-process row are not necessarily measurements of the same thing.
What if pressure improves only after restarting?
Record what was open before the restart and which task brought the symptom back. A restart changes many conditions at once, so it cannot identify a single responsible application by itself. Reopen essential work in a deliberate sequence and watch whether the same pattern returns. If it does, keep the sequence and software versions for a focused support report. Avoid presenting a quiet graph immediately after startup as a permanent repair or a reason to buy a memory-cleaning utility.
Follow the trend in MacMonitor
The Activity view and menu bar show memory readings, with memory pressure, swap and thermal history in Health. Available measurements vary by hardware and permissions. Monitoring does not add physical memory.