November 12, 2025
RAMageddon: WhatsApp Edition
Meta replaces WhatsApp for Windows with web wrapper that uses 1 GB RAM when idle
Users rage as the 'upgrade' guzzles memory and feels slower, some call for open messaging
TLDR: WhatsApp for Windows was replaced with a browser-based wrapper that idles near 1GB and feels sluggish, with notifications hiccups. The community is split: some rage over bloat and demand open messaging or multi-device support, while others argue RAM use isn’t the real issue—performance and control are.
Meta just swapped WhatsApp for Windows out for a browser-in-a-box: the new app is basically a WebView (a mini browser) loading web.whatsapp.com. Tests claim it slurps around 1GB just sitting idle and can spike toward 3GB with busy chats. The vibe? People are furious, calling it “Chrome with stickers” and blaming layoffs for turning a once-native app into a sluggish, notification-missing headache.
The drama lit up fast. One camp is shouting “open protocols now!”, dreaming of email-style messaging that isn’t locked to one company. Another group is baffled, asking why Meta dumped its earlier native Windows app when it’s “just a chat frontend.” Meanwhile, the pragmatists rolled in with the classic hot take: RAM is meant to be used, so chill. But even they got side-eye when users complained the new version feels slow, breaks Do Not Disturb, and delays alerts.
Travelers jumped in begging for multi-phone support like Telegram, and Linux fans grumbled they still can’t make calls on desktop. Conspiracy corner says Meta’s cutting costs while cozying up to Apple Watch, forcing Windows users onto the web wrapper. Whether you call it “RAMageddon” or just lazy engineering, the comment section crowned this an upgrade nobody asked for.
Key Points
- •WhatsApp for Windows 11 has been replaced with a WebView2 wrapper that loads web.whatsapp.com.
- •The rollout is occurring via the Microsoft Store as version 2.2584.3.0.
- •Reported tests show the new app uses around 300MB idle on the login screen and averages about 1.2GB RAM when idle after login, peaking near 2GB while loading chats.
- •The previous native UWP/WinUI app typically used around 190MB, dropping below 100MB when idle, with peaks near 300MB during heavy activity.
- •The article reports sluggish performance and notification issues with Windows 11 features, and says users will eventually be forced to migrate to the WebView2-based app.