What WindowServer is on a Mac, and why it is using CPU
WindowServer is the macOS process that draws every window and manages every display. What it does, what its numbers mean, and what actually helps.
By Chethan Kumar S N · Updated
WindowServer is the second thing people notice about a Mac that feels unwell. The fans come first. Then someone opens Activity Monitor, sorts by CPU, and finds a process they have never heard of sitting near the top with a number that looks like a mistake. It is not an app anyone installed, it cannot be found in the Applications folder, and the answers online run from “that is normal, ignore it” to “your Mac is dying”, which between them cover everything and explain nothing.
It is a system process, it does a specific job, and its numbers mean something once you know how they are measured. This page is that, plus the short list of things that genuinely move it.
It is also one of two unfamiliar names people end up looking up after that trip to Activity Monitor. The other one is the kernel itself, which appears with the process ID 0 and climbs when the machine is fighting heat rather than when anything on screen is moving. What kernel_task is on a Mac is the page for that one, and it is a different story: this process draws your windows, and that one is how macOS slows a hot machine down.
What it actually does
Apple’s developer documentation is unusually direct here, which is worth quoting because the whole confusion is about what this thing is. Quartz Window Services, the API applications use to ask about what is on screen, is described as providing information about the windows managed by the macOS window server. The same page says that includes both the onscreen windows seen on the user’s desktop and any offscreen windows used by the running applications.
Quartz Display Services, the sibling API for screens, is described as providing direct access to features in the macOS window server for configuring and controlling display hardware.
Put those two sentences together and you have the job description. It manages windows, and it owns the displays.
The part people miss is that nothing draws straight to your screen. An app draws its window into a buffer of its own, and the window server composites the buffers into the single image the display shows. Menus, the pointer, window shadows, the Dock, the animation when you open Launchpad, all of it is assembled in the same place. That is why the name is a server rather than a manager: apps are clients asking it to put a window somewhere, and it is the only thing in the system that touches the display hardware.
Where it lives on your Mac
You can read all of this off your own machine in a terminal, and it is more interesting than the name suggests. WindowServer is not a background app. It is a launchd system daemon, it is declared in a plist in /System/Library/LaunchDaemons, and the program it runs is unusual for a daemon: it lives inside a framework rather than in /usr/libexec.
$ pgrep -x WindowServer
483
$ ps -o user,pid,time,comm -p 483
USER PID TIME COMM
_windowserver 483 6731:46.83 /System/Library/PrivateFrameworks/SkyLight.framework/Resources/WindowServer
$ launchctl print system/com.apple.WindowServer | head -12
system/com.apple.WindowServer = {
path = /System/Library/LaunchDaemons/com.apple.WindowServer.plist
type = LaunchDaemon
state = running
program = /System/Library/PrivateFrameworks/SkyLight.framework/Resources/WindowServer
arguments = { .../WindowServer -daemon }
domain = system
runs = 1
pid = 483
Three things in that output are worth reading twice. It is owned by _windowserver, a hidden system account rather than your user. Its parent is launchd, so it is not something an app started and can stop. And runs = 1 says it has started once since this Mac booted, so the process you are looking at is the one that came up at boot.
The binary itself is small, about 204 KB, immutable, Apple-signed, and universal (arm64e on Apple silicon). Almost none of the code that draws your screen is in it. That is all in the framework around it and in the GPU drivers it drives.
The plist’s more revealing section is the list of services the process registers with the system. These are the names other parts of macOS use to find it:
| Service | What it is for |
|---|---|
| com.apple.windowserver | The window server itself |
| com.apple.CARenderServer | Core Animation’s render server |
| com.apple.CoreDisplay.master | Display configuration and control |
| com.apple.iohideventsystem | The hardware input event system |
| com.apple.VirtualDisplay | Displays that are not physically attached |
| com.apple.windowserver.watchdog | The check that catches it not answering |
That table explains a lot about how this process behaves. Core Animation renders inside it, which is why every animation on your Mac is its work. The input event system is one of its services, which is why a stuck window server can look like a trackpad problem as easily as a display problem. And virtual displays are its business too: on the Mac this was checked on, the AirPlay agent’s binary refers to com.apple.VirtualDisplay, and its error strings include the CoreGraphics virtual display start call, so an AirPlay or Sidecar screen arrives through the same door as a monitor on a cable. The watchdog row is the same private arrangement configd has, a liveness check for one process; the system-wide watchdog that can restart a hung Mac is a separate daemon with hardware behind it.
Why it never shows up under My Processes
Open Activity Monitor and switch the process list to My Processes and WindowServer disappears, which is the first thing that makes it look suspicious. It is not hiding. In Apple’s grouping, the processes owned by neither root nor your account sit under Other User Processes, and _windowserver belongs to neither.
The rest of that menu is a decent map of Activity Monitor while you are in there. All Processes, Hierarchically is the one to use when a process looks like it is using resources on behalf of something else, because it shows who started whom. Windowed Processes shows the processes that can create a window, which in practice means apps. System Processes shows the ones macOS owns.
While you are in this part of the app, read Apple’s own note on quitting a process, because it is the reason this guide tells you not to touch WindowServer. Quit is the same as choosing File and then Quit inside an app: it waits until it is safe and it declines if quitting would lose data or interfere with something else. Force Quit is immediate, and Apple’s sentence about it is the one that matters here: if the process is used by other apps or processes, those apps or processes could experience problems. The same page notes that if you try to quit a process you do not own, you will be asked to authenticate as an administrator, because you do not get to decide this.
Every window on your screen is being drawn through WindowServer. Force quitting it does not free up your Mac. It takes the session with it.
Reading the CPU number properly
The reason WindowServer’s percentage looks alarming is that people read it as a share of the whole Mac. It is not. It is measured against a single core, which is why a busy process can show a figure well above 100 per cent, and why the searches about Activity Monitor and numbers over 100 exist at all.
A quick check makes the convention obvious. A four thread test program on this Mac, which has ten cores, reported itself at 396 per cent while it ran:
$ sysctl -n hw.ncpu
10
$ ps -o pid,%cpu,comm -p 41965
PID %CPU COMM
41965 396.0 ./spin
So on a ten core Mac, 40 per cent for WindowServer is four per cent of the machine, and 100 per cent is one core of ten. That one reframe removes most of the alarm.
Then there is the question of what the number even is at rest. Measured on the Mac this page was written on, an M1 Pro running macOS 27 with a heavy background load, WindowServer sat between 20 and 24 per cent of one core:
| What was measured | Reading |
|---|---|
| CPU | About 20 per cent of one core, steady |
| Threads | 21 to 24, two of them active |
| Processor time since boot | 6,731 minutes, about 112 hours |
| Uptime at the time | 24 days |
| Physical memory footprint | 1,219 MB |
| Resident size | 143 MB |
| Cores in the machine | 10 |
The interesting line is the third one. If you divide 112 hours of processor time by the 590 hours this Mac had been up, you get about a fifth of one core averaged over the life of the process. That is what a steady baseline looks like: not zero, because the screen is being redrawn all day, and not three whole cores either.
The two memory numbers measure different things too, and man top is the honest dictionary for the pair. Its MEM column is the physical memory footprint of the process, which is the bigger number and the one that reads like Activity Monitor. Resident size is the smaller one. WindowServer maps a lot of shared memory for window buffers, framebuffers and the display path, so its footprint is much larger than the private data it actually holds, and a 1.2 GB reading is not a leak on its own.
Apple’s own test for a memory problem is elsewhere in the app. Activity Monitor’s Memory tab has a Memory Pressure graph, which Apple defines as how efficiently memory is serving your processing needs, determined by the amount of free memory, swap rate, wired memory and file cached memory. Green pressure with a big WindowServer number is a normal Mac. Red pressure is a real problem, and WindowServer is one of the last suspects rather than the first. Why a Mac is running slow starts from that graph and works outwards, and if the number that crept up was your free space rather than your memory, System Data is the Storage pane row that holds the caches behind both figures.
What actually makes it busy
Here is the honest split between what is documented and what is folklore.
Effects and animations. This one has a setting, so you can do something about it. Under System Settings, in Accessibility and then Display, Apple ships switches for exactly the things that keep a compositor working. Reduce transparency is described as replacing the transparent effect used on some backgrounds in macOS with a solid background to improve contrast and readability. The same pane carries Reduce motion and Auto-play animated images, and the system also offers Dim flashing lights for flashing content. All of them are worth trying if the number bothers you and you do not mind the interface getting plainer. This is not measured here, so treat it as the lever Apple gave you rather than as a promised saving. It costs nothing to test on your own Mac.
Displays. The window server owns display configuration, and each display is another surface it composites. That makes the popular external monitor explanation plausible rather than proven, and it is easy to settle in two minutes: unplug the display, watch the number, plug it back in, watch it again. If the figure halves when the monitor goes away, you have your answer and no guide can give it to you better.
A display over the network. AirPlay and Sidecar screens are virtual displays created through the same process, so when you are mirroring to a TV it is doing more than usual, and that is expected rather than broken.
Something on screen that never stops moving. A video call, a live dashboard, a game, an emulator. WindowServer’s job is to get whatever changed onto the display, so a screen full of constantly updating content is a screen full of work. And anything being recorded adds a reader on top: when a screenshot is taken or an app records through Apple’s ReplayKit, the frame grab is run by the replayd daemon, whose own code names this process’s world in a method called captureWindowServerScreenshot.
An app that has stopped answering. Activity Monitor marks a process that is not responding in red, and Apple’s note is that this is the state in which the process appears in the list. The window server carries on showing that app’s last frame, which is why a frozen app looks like a frozen window rather than a hole in the screen.
Moving windows around, which turns out to be small. This was worth measuring, because it is what people assume is expensive. On this Mac, a Finder window was moved 54 times in ten seconds while the process’s processor time was read before and after. The ten second baseline had already spent 2.32 seconds of processor time, and the moving version spent 2.47. The difference is about a fifteenth of a second, which is noise against a baseline that busy. That test used scripted moves rather than a real drag, so it is a weak signal about interactive dragging, but it is a fair signal about the thing people actually worry about: the window server is not gasping because you nudged a window.
What actually helps
In order, cheapest first.
Ask whether there is a problem. Convert the percentage to cores and see how small it is. Check the Memory Pressure graph. Ask whether the Mac is slow in ways you can feel. A number that looks big in isolation is not a diagnosis.
Try the two switches Apple provides. Reduce transparency and Reduce motion, both in Accessibility and then Display, are the sanctioned way to cut the effects that keep a compositor busy. Some people keep them on permanently for exactly this reason, and on older Macs it is one of the cheapest speed-ups available.
Take away the display you are not using, and test it in both states so you know rather than guess.
Restart the Mac if you want a clean process. WindowServer is a launchd daemon that starts at boot, so a restart genuinely gets you a new one, which is the sanctioned reset. It is also the only reset worth doing here.
Do not force quit it. It needs an administrator password because it is not yours, Apple’s own warning about force quitting applies to it more than to anything else on the list, and every app you have open is drawing through it.
If you are curious rather than worried, use the tools built for it. Activity Monitor’s toolbar has Sample Process, which Apple describes as creating a report on a selected process over a period of three seconds, and Spindump, which it describes as creating a report for unresponsive apps that were terminated using force quit. The command line has the same tools and says the same thing about permissions:
$ sample WindowServer 1 1
sample[42181]: sample cannot find any existing process you have access to which has a name like 'WindowServer'; try running with `sudo`.
For a process that is not yours, reading its internals needs root, which is the system telling you the same thing Activity Monitor did when it asked for a password.
Where window managers fit
A window manager for macOS is a client of all this, not a replacement for any of it. It asks the system, through the Accessibility route, to move and resize windows that belong to other apps, and every one of those movements is drawn by the same process on this page. That is why the honest framing is not “a window manager will make your Mac faster”. It will not, and an app that animates windows on every action is adding work rather than removing it.
What a manager changes is how much arranging you do by hand. Tiling built into macOS covers halves, quarters and a centre, and how to tile windows on a Mac is the whole of it. If you have two screens, the moves between them are a different problem with its own page, moving windows between monitors.
Ribbon takes the other approach: instead of placing one window each time you name a spot, it keeps the windows you use as a scrolling strip, so opening a sixth window makes the strip one column longer rather than making everything narrower. It is $15, once, for up to 3 Macs, with a full refund within 10 days, and it runs on macOS 14 Sonoma and later on Apple silicon and Intel Macs. What it does to WindowServer is what any window manager does, which is to ask it to draw a window in a new place, and that is the cheap part.
The short version
WindowServer is the part of macOS that draws your screen and manages your displays, it has been running since your Mac booted, it is owned by a hidden system account so you cannot accidentally manage it, and its CPU percentage is measured against one core rather than against your whole machine. Some use is a constant, because your screen is being redrawn all day. If the number climbs and stays high, look at what is on your screens, try Apple’s two effect switches, and check for a display you have forgotten about. And leave the process alone: the window it would take down with it is yours.
Everything on this page is about the layer underneath your windows. If what brought you here was the arrangement rather than the drawing, the pages to read next are how to tile windows on a Mac and, if there is a second screen on your desk, moving windows between monitors.
Questions
What is WindowServer on my Mac?
It is the part of macOS that draws your screen. Apple's developer documentation describes Quartz Window Services as providing information about the windows managed by the macOS window server, including both the onscreen windows on your desktop and the offscreen windows running apps keep, and describes Quartz Display Services as providing direct access to features in the window server for configuring and controlling display hardware. So it manages windows and owns the displays, and every pixel you see has been through it. It is a system process rather than an app you installed, it is started by launchd at boot, and it is owned by the hidden _windowserver user rather than by you.
Is it normal for WindowServer to use a lot of CPU?
Some CPU use is unavoidable, because it redraws whenever anything on screen changes. Start by reading the number correctly: it is measured against a single core, so it can go above 100 per cent, and on a ten core Mac 40 per cent is four per cent of the machine. On the Mac this was written on, running a busy background load, it sat at roughly 20 per cent of one core with 24 threads which is about a fifth of one core averaged across its whole life. Judge it by whether the Mac is actually slow and whether the number climbs and stays high, not by the raw figure.
Can I quit WindowServer?
No, and it is not worth trying. It is owned by _windowserver rather than by your account, so Activity Monitor asks for an administrator password if you try to quit it, and Apple's own note on force quitting says that if the process is used by other apps or processes, those apps or processes could experience problems. Everything you have open is drawing through it. If you want it started fresh, restart the Mac: it is a launchd daemon that starts at boot, so a restart is the clean way to get a new one, and there is even a service registered under the name com.apple.windowserver.watchdog for the times it stops answering.
Why is WindowServer using so much memory?
The two numbers you can see measure different things. On the Mac this was written on, WindowServer's physical memory footprint read about 1,219 MB while its resident size was about 143 MB, which is a lot of shared graphics and window buffer memory mapped rather than private data it owns. Apple's own test for memory trouble is the Memory Pressure graph in Activity Monitor, which it defines as how efficiently memory is serving your processing needs, determined by the amount of free memory, swap rate, wired memory and file cached memory. If pressure is green, that column is not your problem.
Does an external monitor make WindowServer use more CPU?
It is the most common explanation and the easiest one to test on your own machine, because you can unplug the display and watch the number for a minute. It is a reasonable suspicion: the window server is the process that configures display hardware, each display is another surface to composite, and displays that arrive over the network, such as AirPlay and Sidecar, are virtual displays created through one of the services it registers. What is not measured here is a before and after figure, so treat the theory as a theory and take the two minutes to check it.
Ready? Buy Ribbon for $15, or read all the guides.