Open Activity Monitor, click the Memory tab, and look at the small breakdown table near the bottom. Wired Memory is always there, quietly holding a few gigabytes. It never goes down when you quit apps. It doesn't budge when you free up space. For most people it just sits there, looking suspicious.
It is not suspicious. This post explains what wired memory actually is, why it exists, what makes it grow beyond the usual range, and the small number of things you can do about it. If you want the wider picture of how these memory categories fit together, start with what memory pressure actually means and what App Memory is - the two types you will see most often in Activity Monitor.
What wired memory actually is
Every operating system has a kernel - a core piece of software that sits between your apps and the hardware, managing memory, CPU scheduling, file access, networking, and everything else the system does. The kernel needs its own memory to work, and that memory has to be available at all times, instantly, without any delay.
That requirement is the reason wired memory exists. The term "wired" comes from the concept of pinning memory pages in place: macOS tells the hardware that these particular chunks of RAM must stay where they are. They cannot be swapped out to disk, compressed, or handed to another process. The kernel calls this locking or wiring a page, and once a page is wired, only the code that wired it can free it.
In practice, wired memory holds things like: the kernel itself and its data structures, network and I/O buffers, loaded device drivers, memory reserved for GPU command processing, and low-level filesystem metadata. According to Apple's Activity Monitor guide, wired memory is "information the system needs immediate access to and therefore can't be stored on disk."
None of this is waste. It is the price of having a responsive operating system. Without wired memory, the kernel could theoretically be paged out during a disk write, which would deadlock the entire machine. The wired constraint prevents that class of problem.
What makes wired memory grow
A fresh macOS boot on a 16 GB Mac typically shows around 1.5-2 GB of wired memory. That baseline can climb for several reasons, and most of them involve software that runs in kernel space.
Virtual machines are the biggest single cause of elevated wired memory on developer and power-user Macs. Parallels Desktop, VMware Fusion, and UTM all need to lock guest RAM so the virtualisation layer can guarantee the guest OS has exclusive access to it. Running a Windows virtual machine with 8 GB assigned to it can add several gigabytes to your wired figure while it is open.
Security and endpoint software is next. Enterprise antivirus tools, endpoint detection products, and kernel-level VPN clients often install kernel extensions (kexts) that wire memory for their own scanning buffers and data structures. The amount varies wildly by product, but some security suites add 500 MB or more of wired memory on their own.
Audio interface drivers are a common cause on creative Macs. Professional audio hardware typically ships with kernel extensions for low-latency audio routing. These drivers wire memory to guarantee that audio buffers are never delayed by memory management.
External GPU or display drivers for non-Apple hardware, USB hub firmware, and any third-party kernel extension can all contribute. The pattern is the same: code running in kernel space allocates wired memory, and that memory stays wired as long as the driver is loaded.
To understand how wired memory relates to all the other rows in Activity Monitor, the guide to using Activity Monitor on Mac covers the full layout with each number explained.
Why you cannot free wired memory like other types
App Memory and Cached Files can both be reclaimed. App Memory shrinks when you quit apps. Cached Files are explicitly designed to be evicted the moment any process needs more space. Compressed memory can be decompressed and returned. Wired memory is different: only the code that allocated it can free it, and that code is the kernel or a kernel extension running in privileged space.
No user-space tool, including third-party memory cleaners, can touch wired pages. When a memory cleaner claims to free wired memory, it is either measuring something else or making a misleading promise. The allocation sits in a part of the address space that user processes simply cannot reach.
This is not a limitation of macOS - it is a security and stability guarantee. If user-space code could free kernel memory at will, any app could crash or compromise the OS. The boundary is intentional and correct.
What this means practically: do not chase the wired memory number with cleanup tools. It will not move in response to anything they do. The only levers that actually work are quitting the software that wired the memory, or restarting the machine entirely.
When wired memory becomes a problem
For most Macs in most situations, wired memory is not a problem. 1.5-3 GB on a 16 GB Mac is normal and leaves plenty of room for everything else.
It becomes worth investigating when the number is significantly higher than that range, or when it is growing steadily over time without a restart. Specific thresholds to watch for:
- Over 4-5 GB on a 16 GB Mac without a virtual machine running is a signal something unusual has allocated a large amount of kernel memory. This is not always a crisis, but it narrows your headroom for App Memory and can push memory pressure into yellow sooner than expected.
- Growing over days or weeks without a restart suggests a kernel-level memory leak - a driver or kernel extension that is allocating memory and not releasing it. If you notice your wired figure has climbed from 2 GB to 4 GB over a fortnight without adding any new software, a restart is overdue and worth noting whether the figure starts climbing again.
- After installing new software. If wired memory jumped after you installed a particular app or driver, that software is almost certainly responsible. The correlation is usually straightforward to spot.
Wired memory on its own does not make individual apps slow. It does reduce the available pool of RAM that your apps can use, so a machine with elevated wired memory will reach memory pressure at a lower App Memory load than a comparable machine with a smaller wired footprint.
What you can actually do
The options here are narrower than with App Memory or Cached Files, but they are real.
Quit virtual machines when you are not using them. This is the single highest-impact action for most people with elevated wired memory. Closing Parallels or VMware Fusion releases the guest RAM that was wired, often freeing several gigabytes immediately. You do not need to uninstall anything - just close the VM.
Audit your security software. If you are running enterprise endpoint software or kernel-level VPN clients, check whether there is a lighter-weight version or whether the software is actually needed. On a personal Mac, consumer-grade security software rarely provides enough benefit to justify the memory overhead.
Check for unnecessary kernel extensions. In System Settings, under Privacy and Security, you can see which kernel extensions (also called system extensions in recent macOS) are loaded. Any extension from software you have uninstalled but not fully cleaned up may still be active and consuming wired memory. Removing the parent software properly should clear it.
Restart regularly. If your wired memory creeps upward over time, a restart resets it to baseline. Unlike App Memory, there is no shortcut - a full restart is the reset. Most Macs benefit from a weekly restart for this reason alone.
For the memory types that tools can actually help with - primarily the inactive App Memory slice that builds up during a working day - Shiny clears that in one menu-bar click. But wired memory sits outside what any user-space tool can touch. Knowing the boundary saves time and prevents chasing numbers that will not move.