WindowServer on a Mac: what it is, and why it uses so much CPU and memory

What is WindowServer on a Mac?

The part of macOS that puts every window, menu and pointer on the screen. Apps draw their own windows; WindowServer combines them into the picture you see, many times a second, on every display. Nothing appears on a Mac without it.

Why is WindowServer using so much CPU?

Because there is a lot to draw. Its load rises with the number of open windows, the number and resolution of displays, transparency and blur effects, and anything that moves: video, animations, scrolling, screen sharing. On our MacBook Air, with a browser and a few apps open, ps read WindowServer at 23.5% of one core after two and a half days running.

Why does WindowServer use so much memory?

Every window it draws needs a picture of itself in memory, and larger, sharper screens need larger pictures. Activity Monitor's Memory column counts that graphics memory too, which is why it can read in gigabytes. On our Mac, ps showed WindowServer's own resident memory at 36 MB; the rest of what Activity Monitor reports is the windows it is holding.

What happens if I quit WindowServer?

You are logged out. Force quitting it closes every app and returns you to the login window, with any unsaved work lost. It restarts by itself, at the same load once your windows are back.

How do I reduce WindowServer CPU and memory?

1. Close windows you are not using, especially minimized ones and browser windows with video or animation.
2. Reduce transparency: System Settings, Accessibility, Display, Reduce transparency. Blur behind menus and sidebars is redrawn whenever what is behind it changes.
3. Check scaled resolutions. A scaled display setting makes the Mac draw a larger picture and shrink it. The default setting for a display is the least work.
4. Look for screen recorders and overlays. Apps that watch or draw over the screen add to what WindowServer composes.
5. Restart now and then. A Mac that has been up for weeks can collect windows nobody remembers opening.

Fewer windows without losing them: too many windows open and closing all windows at once.

Measured on 16 October 2026 on a MacBook Air (M1), macOS 27.0.1, with ps -axo %cpu,%mem,rss,etime for WindowServer while a browser and a few apps were open, at 2560 by 1600. Activity Monitor counts memory differently from ps, so its figures read higher.