Microsoft's latest engineering sprint has shaved roughly 20 percent off the time it takes to switch between chats in Teams, a fix the company says lands this month alongside patches that reduce freezes tied to WebView2 loading and extend earlier video performance gains. The update, rolling out in June 2026, delivers measurable snappiness to the collaboration tool that 320 million people use every month—but it does nothing to address the elephantine idle memory footprint that continues to frustrate Windows users.

Chat-switching latency has long been a friction point for knowledge workers who pivot between multiple conversations. The 20 percent reduction, confirmed by Microsoft's Teams engineering group through internal telemetry, means flipping from a project channel to a direct message now feels perceptibly quicker. In practical terms, the delay drops from about 1.2 seconds to just under a second on a median corporate laptop—still not instantaneous, but a meaningful step toward the fluidity users expect from a flagship business app.

The WebView2 bottleneck finally gets attention

The freeze reduction is arguably more impactful for daily reliability. Teams migrated from Electron to Edge WebView2 in 2021, a move that promised tighter OS integration and lower overhead. But WebView2 still launches a full Chromium renderer process per component, and until now, loading that engine could briefly lock the UI. Heavy users—those with a dozen tabs, multiple org tenants, and a side panel of apps—regularly hit a 2-3 second hang when first opening the client or waking a secondary window.

Microsoft's engineering team traced these hangs to a race condition in the WebView2 initialization sequence. The fix, which rolls out automatically with the June update, serializes component loading to avoid contention and pre-warms the renderer during sign-in. Early adopters in the Technology Adoption Program (TAP) report that the jarring freeze when clicking the Calendar tab has all but disappeared, and the app now surfaces the meeting view without the telltale (Not Responding) badge.

Video performance builds on earlier work

The engine improvements continue on the video stack overhaul that began in 2025. That earlier work decoupled the video pipeline from the UI thread, reducing frame drops during screen sharing and letting the rendering run at the display's native refresh rate on high-DPI panels. The June update adds what Microsoft calls “adaptive bitstream renegotiation,” which shifts encoder settings mid-call when network jitter spikes, instead of waiting for a full quality-loss event. In internal demos, call-recovery time after a 5-second packet burst dropped by 35 percent—enough to keep a Teams Room from blanking during a board presentation.

None of these changes require a client update. All the work sits in the ring-scoped service payload that Teams refreshes every two weeks. Enterprise admins who manage deployments via the Teams admin center or Group Policy will see the build string bumped to 1.7.00.16572 (the June ring) but need take no action.

Memory: the silent productivity killer

Here is where the celebration stops. None of the June engineering touches the primary complaint that saturates Microsoft’s own feedback hub and every sysadmin forum: Teams’ idle memory consumption. On a standard Windows 11 24H2 workstation with 16 GB of RAM, the teams.exe process routinely sits at 600–800 MB when doing absolutely nothing. Open a couple of chats and a document tab, and it climbs past 1.2 GB. Launch a video call, and the combined browser host, media engine, and renderer processes push 2.4 GB. For older machines still running 8 GB of RAM—common in education, frontline, and even some corporate thin clients—Teams alone can trigger the disk-swapping spiral that makes Windows feel broken.

“The 20 percent chat speed-up is nice, but if Teams is paging out my Excel data because it won’t let go of memory, I’m not sure what we’ve gained,” wrote a contributor in the Microsoft Teams: IT Pro and Deployment community, echoing a sentiment that routinely clocks hundreds of upvotes. Similar threads on Reddit’s r/sysadmin and r/MicrosoftTeams track the number of open handles that the Teams processes cling to after a meeting ends—sometimes north of 3,000—suggesting a leak in the media subsystem that doesn’t release allocated resources when the call is over.

Microsoft has publicly acknowledged the memory debt. In a 2024 post on the Microsoft 365 roadmap, the Teams Performance team committed to a “memory reduction sprint” targeting a 25 percent baseline drop. That sprint delivered a 10–12 percent improvement by mid-2025, largely by cutting duplicate processes in the multi-tenant architecture. But the low-hanging fruit is gone. The remaining bloat lies in the WebView2 framework itself, the chat list rendering, and the event-driven notification infrastructure that keeps Teams’ “always on” personality alive. Optimizing those pieces without destabilizing the integration fabric with Outlook, SharePoint, and Loop components is a multi-year architecture challenge.

Why WebView2 makes memory discipline hard

Teams’ current architecture relies on Edge WebView2 to render every panel—chats, channels, files, calendar, and third-party apps—as separate browser views. Each view carries its own JavaScript heap, GPU texture cache, and network context. While this isolation prevents a misbehaving add-in from crashing the entire client, it multiplies the memory baseline by the number of views loaded. Even when a user never opens the “Files” tab, the rendering engine pre-loads it to make the first click feel instant.

Microsoft defends this trade-off. “The seamless context switching customers value would be impossible without some degree of pre-loading,” explained a program manager during a February 2026 MCAPS session. “We’re working to compress idle tab heaps and share more of the graphics cache across views, but each percentage point we win back risks a latency spike somewhere else.” That tension—speed versus resource efficiency—defines the current era of Teams engineering.

The real-world impact on IT admins

For endpoint management teams, the memory problem is moving from a nuisance to a compliance issue. Hardware-refresh cycles have lengthened to 4–5 years in many enterprises, and frontline Windows 11 devices are frequently spec’d with 8 GB of RAM to control cost. When Teams pushes memory pressure above 80 percent, Windows starts terminating background processes—often the security agent, VPN client, or device management services that IT depends on for posture checks.

“We’re seeing increased tickets where users complain that their laptop ‘slows down at 10 a.m.,’” notes a senior architect at a Fortune 500 manufacturing firm who preferred not to be named because his company works closely with Microsoft. “Tracing those incidents almost always leads to Teams’ memory usage peaking when people jump on their first morning meeting. The June update likely won’t change that curve—it’s a UI responsiveness fix, not a resource management one.”

Admins can partially mitigate the issue by disabling GPU acceleration for WebView2 or capping the cache size via registry keys, but those changes often degrade video quality and defeat the purpose of the recent rendering improvements. Microsoft’s own documentation warns that “modifying WebView2 runtime settings outside supported policies may result in unexpected application behavior.” Most organizations leave the defaults untouched and hope the engineering team in Redmond eventually gets a handle on the leaks.

Competitors are watching

The memory discussion matters because competitive pressure is mounting. Zoom’s Windows client, written in native C++ with a custom UI framework, typically idles below 300 MB. Google Meet runs in the browser where Chromium’s tab-sleeping heuristics can throttle it to 150 MB after 5 minutes of inactivity. Slack—another Electron-based app—has been slimming its footprint aggressively, dropping from 800 MB to 450 MB idle over the last 18 months after a rewrite of its data-sync layer. Teams, still the heavyweight, is the one that IT architects single out when evaluating alternatives.

Microsoft’s bundling advantage—Teams comes with Microsoft 365 E3 and E5, which enterprises already own—has insulated it from direct attrition. But as hybrid work normalizes and every dollar of license cost gets scrutinized, the overhead of Teams on device lifecycle management is creeping into TCO discussions. A $200 RAM upgrade across a fleet of 10,000 laptops from 8 GB to 16 GB is a $2 million unplanned spend, and that’s before considering the battery life eaten by a constantly busy WebView2 engine.

The path forward: incremental gains, no silver bullet

Microsoft isn’t ignoring the problem, but the roadmap suggests incrementalism. Upcoming work flagged in the Microsoft 365 admin center points to “intelligent tab sleeping” for secondary views that haven’t been accessed in 10 minutes, a feature expected in Q3 2026. The same sprint plans to merge the chat and channel renderers into a single view when screen real estate is tight—a move that could cut base memory by another 15 percent. A more radical project, codenamed Project Mercury within Teams, explores moving the notification broker to a lightweight Win32 service that would let the main WebView2 host truly idle when the user isn’t interacting with the app.

Those ambitions will take time. “The notification pipeline touches every aspect of the real-time collaboration stack—presence, calling, activity feed—so moving it to a separate lightweight process is a delicate surgery,” cautioned the same program manager. “We’re aiming for a preview in late 2026, but no commitments yet.”

For users on the receiving end of the June 2026 update, the immediate takeaway is positive: Teams finally feels more like a modern Windows application and less like a clunky web page dressed in a native shell. Chat switching is faster, freezes are rarer, and video calls recover from network wobbles more gracefully. But the quiet memory drain persists, and until Microsoft ships a fundamental architectural shift, every Teams window left open will keep siphoning performance from the PCs that businesses rely on.

IT professionals should communicate the June performance boosts to their user base as a quality-of-life win, while monitoring memory trends with tools like Process Explorer or the Windows Performance Analyzer to determine whether the video and freeze fixes inadvertently raise the idle footprint. Early TAP telemetry suggests no regression—but also no breakthrough on the memory front. The release is a reminder that modernizing a monolithic collaboration client built on web technologies is a marathon, not a sprint, and that sometimes the most impactful improvements are also the least visible.