Search any Mac forum for “Microsoft Teams killing my Mac” and you'll find the phrase appearing almost word for word, across Reddit threads, Microsoft's own community boards, and IT help desks. It's one of the most common complaints about work software on Apple hardware. The frustration is understandable. An app whose core purpose is sending messages and hosting video calls has no obvious reason to be using as much memory as a video editor.
The reason is architectural, not accidental. Understanding it doesn't make Teams lighter, but it does make the problem less mysterious and the solutions more obvious.
Why Microsoft Teams uses so much memory
Teams on Mac is built on Electron, the same framework used by Slack, VS Code, Discord, and a long list of other widely-used desktop apps. Electron lets developers build desktop apps using web technologies: HTML, CSS, and JavaScript. The trade-off is that every Electron app ships with a complete copy of Chromium, Google's open-source browser engine, bundled inside it. When you launch Teams, you are effectively launching a browser. That browser engine must initialise before anything else, which is why Teams uses several hundred megabytes of RAM before a single channel has loaded.
The picture gets more complicated if you use multiple organisations. Every Microsoft tenant or organisation account you're signed into runs as its own renderer process, equivalent to a separate browser tab with its own independent memory allocation. Someone who is a member of their company's Teams, a partner company's Teams, and a community or external workspace might easily have four, five, or six renderer processes running at once.
Beyond the baseline, calls and screen-sharing add significant additional load. Video encoding and decoding, screen capture, and real-time audio processing all compete for both RAM and CPU. After a Teams call ends, some of that memory is released promptly; some accumulates over the session. This is why Teams at 9 AM on a Monday looks different in Activity Monitor from Teams at 5 PM on a Friday.
What "killing my Mac" actually means
For most people, the real problem isn't Teams's number in Activity Monitor in isolation. It's what that number means in combination with everything else that's running.
macOS is designed to use as much RAM as possible. An app sitting at 2 GB isn't automatically a problem. The issue starts when the total memory demand across all your open apps approaches your Mac's physical RAM limit. When that happens, macOS begins using free space on the SSD as overflow memory, a process called memory swapping. An SSD is fast by storage standards but still dramatically slower than RAM. When your Mac starts swapping, you'll notice it: apps take longer to come to the front, switching between things feels slightly sticky, the fan picks up, and the whole machine feels like it's working harder than it should.
The clearest indicator is the Memory Pressure graph at the bottom of Activity Monitor's Memory tab (press Command-Space, type “Activity Monitor”, click Memory). Green means your Mac has headroom; yellow means it's working harder; red means sustained pressure and heavy swapping. For a full breakdown, see what memory pressure means on Mac.
On a 16 GB Mac, Teams at 3 GB is probably fine. On an 8 GB Mac with Chrome, Slack, and a few other apps also open, the same 3 GB can tip the balance. Context is everything.
Is the new Teams really lighter?
Microsoft shipped a significant rewrite of Teams, variously called “new Teams” or “Teams 2.0”, across 2023 and 2024. The company cited memory reductions of roughly 30-50% in their own testing, and independent users generally confirmed that the new version was meaningfully lighter than the original.
On Windows, the new Teams moved away from Electron entirely in favour of Edge WebView2, which allowed it to share system components rather than bundling its own Chromium. On Mac, the architecture remains Electron-based, which means the memory floor is still set by that bundled browser engine.
In practice in 2026, Teams on Mac typically uses:
- Fresh launch, one organisation: around 600 MB to 1 GB. The Chromium core plus Teams's initial interface and data.
- After signing into two or three organisations: 1-2 GB is normal territory, with each additional tenant adding its own renderer process.
- During or after a video call: noticeably higher. Screen-sharing in particular can push Teams well above its resting baseline.
- After a full work day with calls: 3-4 GB is realistic. Memory accumulates over long sessions and doesn't always release promptly when calls end.
The new Teams is genuinely better than the old one. But “better than before” and “not heavy” are different things. It's still an Electron app on Mac and still carries the architecture's costs.
Practical fixes that work
A few things make a real difference:
Quit Teams when you're not actively in a call or conversation. This is the most important step and the one most people skip. Closing the Teams window doesn't quit the app; background notification services keep running and accumulated memory stays allocated. Pressing Command-Q actually quits Teams and clears everything. Even if you use Teams all day, quitting and relaunching it at the start of each morning resets the previous session's accumulation. A fresh Teams on Monday uses substantially less RAM than one that has been running since Wednesday.
Sign out of organisations you don't actively use. Every tenant you're signed into is its own process. Former employer accounts, community organisations, or low-activity external workspaces all consume memory even when you haven't opened them in weeks. Signing out of those accounts removes their processes entirely. You can sign back in when needed.
Disable rich link previews. In Teams settings, under Messaging, turn off link previews. It's not a dramatic change, but it reduces how much content Teams keeps loaded during a session.
Limit active workspaces during calls. Closing channels you don't need while on a long call reduces how much data Teams holds in memory. The effect is modest but consistent.
For broader guidance on freeing up RAM across your whole Mac, how to free up RAM on Mac covers the approaches that genuinely work.
Should you use Teams in a browser?
For many people, yes. Opening teams.microsoft.com in Safari or Chrome rather than using the desktop app means Teams shares your existing browser's Chromium infrastructure instead of running its own separate instance. The memory saving is real: in typical use, the web version uses roughly half what the desktop app uses at rest.
The trade-offs are genuine. Some meeting features behave differently in the browser. Native notifications that arrive when your browser is in the background are less reliable than the desktop app's. Switching to Teams from another app requires going to your browser rather than clicking a dedicated Dock icon.
If your day involves frequent, back-to-back calls with screen-sharing, the desktop app is harder to replace. If you use Teams mainly for chat with occasional calls, the web version is worth a week's trial. Adding teams.microsoft.com to your Safari Dock from the File menu takes two minutes. If you already run Chrome alongside Teams, switching to a browser tab eliminates one Chromium instance entirely; the memory impact is larger than most people expect. For more on Chrome's own footprint, see Chrome on Mac: why it eats RAM.
When Teams's memory use is actually a problem
The same principle applies as with any heavy app: absolute numbers matter less than context. Teams at 2 GB on a 16 GB Mac with a green Memory Pressure graph is not a problem. The same number on an 8 GB Mac already running Chrome and Slack is a different situation.
Signs Teams is actually causing trouble:
- The Memory Pressure graph in Activity Monitor stays yellow or red during your working day.
- Other apps slow down noticeably while Teams is open or during calls.
- Teams becomes sluggish toward the end of a long session, with channels taking a moment to load or the search feeling slow.
- Quitting Teams makes the rest of the Mac feel faster almost immediately.
- The fan runs more than usual on days with heavy Teams use.
If none of those apply, Teams is heavy but not harmful. If they do, quitting Teams daily, reducing active organisations, and trying the browser version are the highest-impact steps. If the problem persists across all your apps, it may simply be that 8 GB is tight for modern work software. For a broader look, see how to free up RAM on Mac. And if Slack is also open all day, the two together can be a significant drain; the causes and fixes are similar: Slack on Mac: 2GB RAM and what to do about it.