WindowServer on Mac: what it is, why it is high, and what actually helps

What WindowServer actually does

Open Activity Monitor on any Mac and WindowServer is near the top of the CPU list, owned by a user called _windowserver. It is not an app you installed and it is not malware. It is the compositor: the single process that takes the contents of every window from every app, stacks them in the right order, adds the shadows, the translucent menu bar, the Dock magnification and the Mission Control animations, and sends the finished frame to each display, up to 120 times a second on a ProMotion screen.

Because it sits between every app and your display, two things follow. First, it is never idle while you are doing anything on screen, so a few percent of CPU is its resting state. Second, it carries a copy of the surfaces apps hand it. A Mac with forty windows across three Spaces and a 5K display has far more pixels to hold and blend than a laptop with Safari open, and WindowServer's memory and CPU reflect that directly.

It also handles input. Mouse moves, trackpad gestures and keystrokes are routed by WindowServer to the window in front. That is why, when it hangs, the whole Mac feels frozen even though the apps underneath are fine.

What normal looks like, and what is not

People worry because the number is big compared with other processes. Compare it with the right baseline instead:

The rule of thumb: steady is fine, climbing is not. If WindowServer sits at 3 GB all day with two monitors plugged in, that is the cost of two monitors. If it was 1.5 GB this morning, 4 GB at lunch and 9 GB now, and closing windows does not bring it down, it has a leak and only a log out or restart clears it.

For CPU, spikes are normal. Dragging a window, scrolling a long page, switching Spaces or playing video can push it to 40 or 50 percent for a moment. Sustained 60 percent or more while nothing is happening on screen is not normal and usually points at one app that keeps redrawing (a screen recorder, a video call, a browser tab with an animation, a wallpaper that moves).

Why WindowServer is high right now

WindowServer does not get busy on its own. Something is giving it more to draw, or something is leaking. The usual causes, roughly in order of how often they turn out to be the answer:

1. External displays. Each extra display is a whole extra frame to compose. 4K and 5K screens multiply the pixel count, and a scaled resolution ("Looks like 1440 x 900" on a 4K panel) makes macOS render at double size and then shrink it, which is the single most expensive thing you can ask WindowServer to do all day.
2. Many windows and Spaces. Every open window has a surface WindowServer keeps, even if it is behind others. Dozens of Finder and browser windows across several desktops add up.
3. Apps that redraw constantly. Video calls, screen sharing, screen recorders, games, dashboards with live charts, browser tabs with animated ads, terminal windows scrolling logs. The app's own CPU is one cost; the redraw it forces through WindowServer is a second one.
4. Transparency and motion. Blurred menu bars, translucent sidebars and the Dock magnification all cost GPU time per frame. Small on an idle Mac, noticeable when combined with the causes above.
5. A memory leak in macOS itself. Several macOS versions have shipped with WindowServer leaks, most famously on the 2021 M1 Pro and M1 Max MacBook Pros running macOS 12.0, where memory grew to tens of gigabytes within hours. Those bugs get fixed in point updates, but new ones appear. A leak looks like climbing memory that does not fall when you close windows.
6. A buggy third-party app. Window managers, display tools, menu bar utilities and some video conferencing apps can trigger WindowServer growth. The tell is that the growth starts when the app launches.

Is it safe to quit WindowServer?

No, and it is the one process in Activity Monitor where "Force Quit" has an immediate, visible consequence. WindowServer owns your login session. Ending it (from Activity Monitor or with killall WindowServer in Terminal) takes down every window on screen and drops you at the login screen. Any unsaved work in any app is gone. macOS restarts WindowServer automatically a second later, which is why some guides describe it as a "reset": it is, but it is exactly the same as logging out, only without the chance to save.

If you want the reset, do it the polite way: Apple menu, Log Out, then log back in. You get the same fresh WindowServer and macOS asks apps to save first. Most apps and browsers reopen their windows and tabs afterwards.

It is also not a virus. There are no legitimate copies of WindowServer outside /System/Library/PrivateFrameworks/SkyLight.framework, and the Activity Monitor entry always runs as _windowserver. Something impersonating it would be a different name or a different user.

How to bring WindowServer down, in order

1. Find what is feeding it

   In Activity Monitor, sort the CPU tab by % CPU. If an app sits above WindowServer and both move together, that app is the cause. Look for video calls, screen recorders, games and browser tabs with video or animation. Quit that app first and watch WindowServer settle within a few seconds.

2. Close windows you are not using

   Not just the app in front: minimised windows, windows on other Spaces and the thirty Finder windows behind everything. Each one is a surface WindowServer keeps alive. Press ⌘W generously. Merging browser windows into one also helps.

3. Use the default resolution on external displays

   System Settings, Displays, pick the external display and choose Default for display. Scaled modes force 2x rendering. If you need more desktop space, a lower native setting costs far less than a scaled one.

4. Reduce transparency and motion

   System Settings, Accessibility, Display, turn on Reduce transparency and Reduce motion. The menu bar and sidebars go flat. On an older or very busy Mac this takes a visible chunk out of WindowServer's load. In Desktop & Dock, turning off Dock magnification helps a little too.

5. Unplug and replug the display, or change its refresh rate

   If WindowServer jumped when you connected a monitor and never came back down, disconnect it for ten seconds. For ProMotion MacBook Pros, setting the built-in display to 60 Hz halves the frames WindowServer has to produce.

6. Log out and back in

   Apple menu, Log Out. This restarts WindowServer cleanly and clears any leaked memory. It is faster than a restart and apps reopen with their windows. Do this whenever memory has climbed and will not come down.

7. Restart, then update macOS

   If a log out does not hold and the growth returns within an hour, restart. If it keeps happening on an otherwise quiet Mac, check System Settings, General, Software Update: WindowServer leaks are the kind of bug Apple fixes in point releases, and the fix only arrives if you install it.

How to tell a leak from a busy day

Activity Monitor shows you a snapshot, and a snapshot cannot tell you which way a number is heading. That is the whole difficulty with WindowServer: 4 GB might be two monitors doing their job, or the first hour of a leak. The only reliable test is time.

Two quick checks you can do by hand. First, note the memory figure, close every window you can, wait a minute, and look again: on a healthy Mac it falls clearly. Second, open the Memory tab and watch the Memory Pressure graph at the bottom: if it is green, WindowServer's size is not hurting you yet, whatever the number says. Yellow or red with WindowServer at the top of the list is when a log out stops being optional.

If you would rather not babysit it, Safe to Quit tracks each process over hours and flags the ones that grow and do not shrink, so you get told "WindowServer has tripled since 9am" instead of guessing from one number.

The famous one: the M1 Pro and M1 Max leak

In late 2021, owners of the new 14 and 16 inch MacBook Pros on macOS 12.0 and 12.0.1 found WindowServer growing to absurd sizes, in some reports past 80 GB on a 64 GB machine, with the Mac swapping itself to a crawl. The thread on Hacker News reached the front page and the quotes below come from it. Reboots were the only fix until Apple addressed it in the following updates, and a few things that reliably triggered it (certain display setups, the Music app's visualiser, specific third-party window tools) became well-known workarounds.

It matters today for one reason: it taught a generation of Mac owners to force quit WindowServer, and that advice still circulates. The leak is long fixed. The log out is still the right move; the killall is not.