Mac Slow on Microsoft Teams? Here's What's Eating Your Performance

Microsoft Teams has a reputation among Mac users that ranges from “mildly annoying” to “actively hostile to my hardware.” If you’ve noticed your fans spool up the moment Teams launches, your battery drain double, or general lag whenever Teams is the foreground app — you’re not imagining it. Teams is heavy. The good news is most of the heaviness is fixable.

Why Teams is so demanding

Teams is an Electron app — meaning it’s a packaged Chromium browser running a web app. That alone makes it heavier than a native app would be, but Teams compounds the problem with:

• Multiple background processes for chat, calls, presence, and notifications
• A telemetry/diagnostic engine that runs constantly
• Real-time sync with SharePoint, OneDrive, and Outlook
• A separate process per channel/team in some configurations
• Aggressive cache that grows without bounds

On a healthy Mac, all of this is annoying but tolerable. On a Mac under any other strain (full disk, low free RAM, 30 Chrome tabs), it tips you over.

Free up RAM in one clickSweep frees inactive memory and pauses the processes hogging your CPU. Get Sweep free →

Make sure you’re on the new Teams, not Classic

Microsoft released a fully rewritten Teams in 2023, branded as “new Teams.” It’s significantly lighter than the old version. If you upgraded macOS but never reinstalled Teams, you might still be on Classic Teams.

Check:

• Open Teams. Is there a toggle in the top-left for “Try the new Teams” or similar? You’re on Classic. Switch.
• If the app icon is the white-on-purple “T” with rounded corners, you’re on new Teams.

Switching alone often reduces Teams’ RAM use by 30-50%. It’s the single biggest fix on this list and it’s free.

Check Activity Monitor for what’s actually running

Activity Monitor → CPU tab → search for “teams.” You’ll typically see:

• Microsoft Teams — main app process
• Microsoft Teams Helper (multiple) — Electron renderer processes
• Microsoft Teams (GPU) — graphics
• Microsoft Teams (Plugin) — for embedded content

For an idle Teams (no active call, just open) you should see total CPU under 10%. If it’s 30%+ idle, Teams has a problem and one of the fixes below should help.

Fix 1: Disable GPU hardware acceleration (counterintuitive but it works)

This is paradoxical. Hardware acceleration is supposed to make things faster. In Teams on Mac, especially Intel Macs, it’s frequently broken — the app falls back constantly between GPU and CPU rendering, and that thrashing eats more CPU than just running on CPU would.

To toggle:

1. Click your profile picture in Teams
2. Settings → General
3. Find “Disable GPU hardware acceleration”
4. Toggle it on (yes, on)
5. Quit and relaunch Teams

If your Teams was idle-spiking before, it’ll probably calm down significantly. If performance gets worse, toggle back off.

Fix 2: Clear the Teams cache

Teams caches every chat, every avatar, every emoji, every shared file thumbnail. This cache grows without bound until it hits multiple gigabytes and starts slowing the app.

Manual clearing for new Teams:

1. Quit Teams completely (right-click Dock icon → Quit, then check Activity Monitor and force-quit any leftover Teams Helper processes)
2. Open Finder, Cmd+Shift+G, paste: ~/Library/Group Containers/UBF8T346G9.com.microsoft.teams/
3. Move the entire folder to the Desktop
4. Reopen Teams — it’ll re-create the folder and re-cache as needed

For Classic Teams the path is ~/Library/Application Support/Microsoft/Teams/.

You’ll need to sign in again. After a fresh start, Teams typically uses noticeably less RAM and feels snappier.

Fix 3: Disable read receipts and registration of presence

Teams has a “presence” engine that constantly reports your activity status (Available, Busy, In a Meeting, etc.) and reads everyone else’s. Disabling it doesn’t change much for your colleagues — they can still message you — but it cuts a constant background drain.

Settings → Privacy → look for read receipts and similar telemetry options. Toggle off what you don’t need.

Fix 4: Limit channels and teams you’re a member of

Each team you’re in adds background sync work. If you’ve been added to 40 teams over your tenure but only actively use 5, leave the dormant ones.

• Click “Teams” in the sidebar
• Right-click each team → Leave or Hide

Hiding doesn’t reduce sync load (the team still syncs), but leaving does. Be careful not to leave teams you’ll need to rejoin — some require an admin to add you back.

There’s a faster waySweep diagnoses what’s eating your performance and clears it in seconds. Try Sweep free →

Fix 5: Disable auto-start

Teams sets itself to launch at login. If you don’t actually need Teams open the moment you sit down, kill the auto-start.

System Settings → General → Login Items. Find Teams in either list and remove it (or toggle the background item off).

When you do need Teams, it’s still in your Applications folder. Open it manually.

Fix 6: Don’t use Teams in a browser AND the desktop app

If you have Teams running in the desktop app and a browser tab, you’re paying double the RAM cost for the same functionality. Pick one and close the other.

For light Teams use (occasional chat, no calls), the browser version is much lighter.

Fix 7: Update macOS and Teams together

Teams gets monthly updates with performance fixes. macOS updates sometimes break Teams in subtle ways, then Teams updates fix it. Running 6-month-old Teams on the current macOS is asking for trouble.

• Teams: profile picture → Check for updates
• macOS: System Settings → General → Software Update

Fix 8: Check for runaway plugins

Teams has integrations with everything (Outlook, Planner, OneDrive, etc.). One broken plugin can cause Teams to spin its wheels permanently.

Check Activity Monitor for any non-standard process with “Teams” or “Microsoft” in the name. If something is using a lot of CPU sustained even when Teams is idle, that’s a candidate. You can disable individual integrations from within Teams settings.

Fix 9: Restart it daily

This isn’t really a fix, more a coping mechanism: Teams develops memory leaks over hours of running. By end of day on Friday, a Teams that started Monday morning at 1 GB RAM might be at 5 GB.

Just quit Teams at end of day. Or better, command-Q it before going to bed. The cold start in the morning is faster than waking it up from a week of memory accumulation.

What about the system around Teams?

Teams behaves better on a Mac that has free RAM and disk space. The wider Mac state matters more than people realize. A few things specific to Teams:

• Free RAM helps Teams’ Electron processes breathe
• A clean ~/Library/Caches/ directory means Teams isn’t competing with bloated system caches
• Removing the leftover preferences from old apps (which Teams’ update process sometimes scans for compatibility checks) reduces startup work

This kind of cross-cutting cleanup is tedious to do by hand. Sweep handles it in one scan — surfaces every cache, log, language pack, and forgotten file — and shows you exactly what’s about to be removed before doing anything. It also has an app uninstaller that handles the leftovers macOS leaves in ~/Library when you drag an app to the trash. Notarized by Apple, free to download.

Don’t restart — cleanSweep clears the buildup that’s actually slowing your Mac. No reboot needed. Free for macOS →

A note on Teams and battery

Teams will absolutely murder your battery on Intel Macs. On Apple Silicon it’s notably better, but still not great. If you’re on a long-haul flight or a coffee-shop work session and need to conserve, consider:

• Quit Teams entirely if you don’t expect calls
• Use Teams in a browser if you only need chat
• Don’t let Teams run in the background “just in case”

Battery preservation > availability for chat in most situations.

When you’ve tried everything and Teams is still slow

The honest answer: on Intel Macs from 2018 and earlier, Teams will probably never feel snappy. Microsoft’s Mac development priorities have always lagged Windows, and the Electron foundation is what it is.

If you can’t change apps (most can’t, IT mandate), the realistic targets are:

• Keep Teams alive for as few hours per day as possible
• Use the browser version for read-only catch-up
• Restart Teams when it gets sluggish
• Keep your Mac otherwise clean so Teams isn’t competing with anything else

That’s the playbook. Not glamorous, but it’s the difference between a Mac that overheats by 11 AM and one that makes it to lunch.