Why is Microsoft Teams using so much CPU and memory on my Mac?
Last reviewed: 19 November 2026.
Teams displays its chats, channels and meetings through web views, so its memory is spread across the Teams app and the helper processes that draw those views. Meetings use the most CPU, because your camera, other people's video, screen sharing and background effects all have to be encoded or decoded in real time. Microsoft recommends a four-core processor from 2018 or later for meetings with more than 10 participants.
What does Teams need from a Mac?
Microsoft's minimum requirements for the Teams client on macOS are a dual-core processor, 4.0 GB of RAM, 1.5 GB of free disk space, and one of the three most recent versions of macOS. For large meetings (10 or more participants) and Teams Live Events, Microsoft recommends a four-core processor from 2018 or later; for avatars and Mesh, 8 GB of RAM or more.
Every Apple silicon Mac meets those processor recommendations. On older Intel Macs with two cores, large meetings can keep the CPU close to full.
Which Teams processes use CPU and memory?
Search Activity Monitor for Teams. The Microsoft Teams app and its helper processes all have Teams in their names, so the search shows them together; add up their Memory figures for the total. Helper names differ between Teams versions, so go by the search results rather than one expected name.
How do you reduce Teams' load during a meeting?
- Turn your camera off when you do not need it. Sending video means encoding it continuously; turning it off lowers CPU and network use at once.
- Stop sharing when you are done. Screen sharing captures and encodes your display for as long as it runs.
- Remove background effects. Blurred or replaced backgrounds are calculated for every video frame. Choose no effect if the Mac is struggling.
- Close other video apps. Another app using the camera or decoding video competes for the same CPU and GPU time.
- Restart Teams after long meetings. Quit with Command-Q and reopen. If problems with the local app persist, Microsoft documents clearing the cache (see below).
When should you clear the Teams cache on a Mac?
Microsoft describes clearing the cache as a targeted step for a small number of problems with the local client, not a general first step. It does not fix missing messages or wrong unread counts, and it deletes diagnostic logs needed to find their cause. The first start afterwards takes longer because Teams rebuilds the cache.
For new Teams on a Mac, quit Teams (Command-Q), then run these two commands in Terminal and restart Teams:
rm -rf ~/Library/Group\ Containers/UBF8T346G9.com.microsoft.teams
rm -rf ~/Library/Containers/com.microsoft.teams2
How can Thrum help with Microsoft Teams?
Thrum keeps a live CPU graph in the menu bar. One click shows the eight processes using the most CPU, so you can see when Microsoft Teams is among them and how much it takes. An optional alert tells you when a process stays above a CPU level you choose (50 to 200% of one core) for 1 to 10 minutes. Click Microsoft Teams in the list for its PID, threads and memory, and Quit or Force Quit it after a confirmation.
Thrum is $4.99 once with a 14-day free trial and no account. It requires macOS 26 Tahoe on Apple silicon or Intel.
Questions
How much RAM does Microsoft Teams need on a Mac?
Microsoft lists 4.0 GB of RAM as the minimum for the macOS client, and 8 GB or more for avatar and Mesh experiences.
Does clearing the Teams cache delete my chats?
No. Chats and files are stored in Microsoft 365 and download again. It does delete local settings and the logs Microsoft support uses for diagnosis.