Meta drops native WhatsApp app for Windows 11, RAM usage spikes massively

Meta has pushed a major client-side change to WhatsApp for Windows 11, according to a new report shared by Windows Latest. The publication indicates that WhatsApp’s native Windows app has been replaced with a WebView-based build that loads the web version inside Microsoft’s Chromium framework. The report highlights that the transition is already rolling out and sets the stage for a noticeable shift in user experience.

WhatsApp for Windows shifts back to a web version

The latest update introduces a version of WhatsApp that essentially opens web.whatsapp.com through WebView2. This marks a return to a browser-like approach after years of work on the native WinUI/UWP client.

Early testing suggests that the new version consumes far more system memory compared to the previous app. On the login screen alone, memory usage reportedly reaches around 300MB, with background processes tied to the Chromium framework running at all times. Once logged in, users may see RAM usage rise above 1GB and potentially climb higher when handling multiple active chats.

The report adds that performance has taken a noticeable hit. Navigating conversations appears slower, and animations and transitions feel less responsive. The new app also struggles with Windows 11-specific behaviours, including notification handling and Do Not Disturb mode. These issues, combined with heavier system resource demands, make the updated client feel less integrated with the operating system.

According to the report, this change is likely connected to internal restructuring at Meta, which may have resulted in the native app team being downsized. By maintaining a single web-based codebase, Meta reduces development overhead, but the user-facing impact is substantial.

The new build is rolling out as version 2.2584.3.0 through the Microsoft Store. Those who still have the previous native client installed may temporarily avoid upgrading, though the report claims that all users will eventually be logged out and required to move to the new version.

(via)