What is a WindowServer and why it consumes a lot of CPU and RAM resources on macOS

Process name "WindowServer"Would make us think of"Windows Server & Hosting"But he has nothing to do with it Windows by Microsoft.

What is and what does the process do WindowsServer on macOS (Activity Monitor)

Many complain about the fact that the trial WindowServer sometimes consumes a lot of resources from the processor (CPU) and RAM, which automatically leads to running difficulty a macOS pe Mac, iMac or MacBook.
The resource consumption ratio of the process WindowServer is available in real time for any user when accessing Activity Monitor.

What is a WindowServer and why it consumes a lot of CPU and RAM resources on macOS

Apparently, the process WindowServer it starts to consume sometimes a lot of RAM and CPU resources, which automatically leads to lowering system performance. The applications start to freeze, the windows Finder they are difficult to open, the screensaver starts to appear jerky and the access to the system settings is delayed.

The process WindowServer belongs to the operating system macOS (system process) and deals with everything the visual side on desktop, Dock Bar si Menu Bar. This process makes management between the visual side (what the user sees) and the hardware side. All folders si files who are on desktop, the effects of transparency but by Dock si Menu Bar are administered by WindowServer.
This process is launched immediately after starting the operating system, and without it you can not access anything from Mac. That's why it's not even good to close it Activity Monitor, even if you are allowed to do so. You will find that once the process is closed WindowServer, you will go directly to the "login screen".

How can we do that WindowServer not to consume much memory and CPU

The process WindowServer usually has short periods of time in which it requires a large volume of resources, after which everything returns to normal. However, if you do not want these periods to take place, consider the following:

1. Try to reduce the number of folders and files on your Desktop as far as possible.
For example, if you have 50 files on your desktop and 5 folders, try to put them all together in one folder. Thus through the process WindowServer will pass a single visual element instead of 55.

2. Close the windows Finder which you do not use or use a single window Finder open with multiple tabs.

3. Disable the transparency effects of macOS.
Disabling these visual effects will increase anyone's performance Mac. Do this from: “System Preferences”→“Accessibility”→“Display”→“Cut Back transparency".

What is a WindowServer and why it consumes a lot of CPU and RAM resources on macOSThe transparency effect of the Dock, Menu Bar, Finder si Launchpad.

4. Disable automatic rearrangement in Mission Control.
Go to “System Preferences"The"Mission Control"And uncheck the option"Automatically rearrange Spaces based on most recent use".

5. Close apps you do not use.
It was established that the volume of consumption of WindowServer is also influenced by the graphic effects present in the applications.

After you make all these changes or part of them, restart the operating system.
Definitely the service WindowServer will not consume as much RAM and CPU as before.

What is a WindowServer and why it consumes a lot of CPU and RAM resources on macOS

About the author


I am pleased to share my experiences with computers, mobile telephony and operating systems, develop web projects and provide the most useful tutorials and tips.
I like to "play" on the iPhone, MacBook Pro, iPad, AirPort Extreme and on operating systems macOS, iOS, Android and Windows.

Leave a Comment


  • This has not worked, I've tried everything. Currently preparing for a factory reset of the Operating System to see if performance can be restored.

  • The date is missing. This is a beginner's mistake. You should always make the date bold and clearly visible so that you can immediately gauge the relevance of an article before reading it.

    Other than that thank you for the explanations.