Keeping WhatsApp on a Mac current without reinstalling it

There is no Check for Updates item in the obvious place, the version number in the About window means nothing on its own, and searching for how to update WhatsApp on a Mac returns two sets of instructions that contradict each other. Both sets are correct. They describe two different copies of the same application, installed from two different places, which update by two entirely different mechanisms.

The evidence is visible without opening anything. WhatsApp's own download page states that WhatsApp Desktop is available for macOS 11 or later and offers the file directly, while also pointing to the Apple App Store. The App Store listing for the same application states that it requires macOS 12.1 or later. Same name, same icon, different minimum system version, different update path.

So the first question is not how to update. It is which copy is on this Mac.

Working out which copy is installed

The quickest check is the App Store itself. Open it, click Updates in the sidebar, and look for WhatsApp in the list of installed applications it manages. If the App Store knows about the app, it owns the update process. If it does not appear there at all, the copy came from the download page and the App Store will never update it, no matter how many times Update All is clicked.

A second check is the version number. WhatsApp's App Store listing currently shows version 26.36.74, updated within the last week, with release notes that say only that the app is updated regularly to fix bugs, optimise performance, and improve the experience. A copy several versions behind that has not been updating.

This matters more than it looks. The most common reason someone concludes that an application cannot be updated is that they have been checking the wrong place for months. Nothing is broken. The update instructions simply belong to the other copy.

Two installations of the same application can even coexist, one in the Applications folder from the download page and one from the App Store. In that case each keeps its own state, and the one that gets launched is whichever the Dock icon points at, which explains the occasional report of messages appearing in one copy and not another.

Updating the App Store copy

This route is the simple one because macOS handles it. In the App Store, Settings has an Automatic Updates option. With it on, WhatsApp updates in the background with nothing to do. With it off, updates wait in the Updates section of the sidebar until Update is clicked beside the app, or Update All is clicked for everything.

Two things are worth knowing about this path. Updates arrive on Apple's schedule for delivery rather than the developer's schedule for release, so there can be a short lag after a version ships. And the App Store copy carries the higher stated minimum system version, macOS 12.1 or later, which is why a Mac on macOS 11 can run the copy from the download page while the App Store refuses to install anything.

Updating the copy that came from the download page

Here the update is a replacement. Download the current file from WhatsApp's download page, and install it over the existing copy in the Applications folder.

Nothing is lost by doing this, which is the part that makes people hesitate. The application bundle is program code. The account link, the message cache, and the settings live in the user library, not inside the bundle, so replacing the bundle does not sign the account out or delete the history. Quitting the application before replacing it is still worth doing, since a running application being overwritten can behave unpredictably until it is restarted.

The drawback of this route is that it is manual and therefore easy to forget. A messaging application that has fallen six months behind is usually one that was downloaded once, from the website, by someone who assumed the App Store would look after it.

Copy	Where it came from	How it updates	Stated minimum macOS
App Store build	Apple App Store	Automatically, or from Updates in the sidebar	macOS 12.1 or later
Direct download	WhatsApp download page	Download the current file and replace it	macOS 11 or later
Browser version	web.whatsapp.com	Nothing to update, the page is served each time	Whatever the browser supports
Standalone app built from the page	A site to app tool	The page updates itself, the app shell updates on its own schedule	Varies by tool

The bottom two rows are the interesting ones, because they behave differently from anything installed.

Why the version number moves so often

Messaging applications ship changes constantly, and the release notes rarely explain what changed. WhatsApp's current listing is a good example: a version number in the twenties, updated days ago, with generic notes.

Most of those releases are not features. They are fixes, performance work, and changes that keep the desktop client talking correctly to a service that is itself changing. That is the real reason to care about updating at all. A messaging client is a network client, and a network client that falls far enough behind eventually stops connecting properly rather than merely missing a feature.

It also explains a frustration that comes up often. Someone updates the desktop app expecting a feature they have seen on their phone, and it is not there. Desktop releases follow their own schedule, and a feature can exist on mobile for months before the desktop build receives it. Updating more aggressively does not change that.

When an update refuses to install

Three failures account for most cases where the update will not go through, and each has a different cause.

The first is the system version. An application that has raised its minimum macOS above what the machine runs will simply stop being offered. The App Store shows nothing, no error explains why, and the installed copy keeps running on the last compatible version indefinitely. Checking the current listing against the version of macOS in System Settings settles this in under a minute.

The second is ownership of the copy. An application installed from a download page will never appear in the App Store's Updates list, so clicking Update All has no effect on it and never will. This is the most common case, and the fix is to replace the file rather than to troubleshoot the App Store.

The third is storage or a stalled download, which usually resolves by quitting the App Store, reopening it, and starting the update again.

What is almost never the cause is the account or the sign in state. A linked messaging session and an application update are unrelated systems, and signing out to fix an update problem creates a second problem without addressing the first.

The version that never needs updating

WhatsApp also runs in a browser at web.whatsapp.com, linked to the phone in the same way the desktop application is. This version has no update process at all, because there is nothing installed to update. Whatever is loaded is whatever the service is serving that day.

That is the practical advantage of a web interface, and it is easy to undervalue until an application has gone stale twice. There is no version to check, no file to download, and no difference between machines. Sign in on another Mac and it is already current.

What it gives up is everything that comes from being an application. A browser tab has no icon in the Dock, delivers notifications only while the browser is running, disappears among other tabs, and shares one signed in session with every other tab in that profile.

Getting both at once

The middle position is a tool that turns a website into a standalone Mac app. The result is an ordinary application bundle with its own name, its own icon, and its own isolated session, showing the web interface exactly as a browser would, because it is the same page.

For updates, this arrangement splits the problem in two, and the split is the whole point.

The content updates itself. The page is fetched from the service each time the app runs, so changes appear without any download, exactly as they do in a browser. There is no version of the messaging interface to keep current, no App Store entry to check, and no stale build sitting in the Applications folder.

The shell updates separately. The application that draws the window is real software and does need its own updates, for the browser engine it embeds if for nothing else. That is one update path to think about instead of one per service, which is the actual saving when several sites have been turned into apps.

macOS includes a limited version of the same idea. Starting with macOS Sonoma 14, Safari can save a webpage as a web app through Add to Dock, and Apple's documentation notes that the web app is saved to the Applications folder of your home folder and shares no browsing history, cookies, website data, or settings with Safari. It updates the same way, by fetching the page. The limitation appears with more than one account, since separating sessions cleanly is exactly what browser based shortcuts do least well. The Features page covers how a separate profile per app changes that, and the Supported services list shows which sites are already prepared as configurations.

Deciding which copy to keep

For an application that exists as a real native build, as WhatsApp does, the native build is usually the right choice, and the only decision is making sure it actually updates. That means installing it from the App Store and turning on Automatic Updates, or accepting that the download page copy needs replacing by hand occasionally.

For everything that has no native Mac build, which is most of the services people keep open all day, the calculation is different. There is no installer to choose between, so the question becomes whether that service deserves its own window and icon, or whether it is fine as a tab. A service checked twice a day is fine as a tab. A service that needs to be reachable in one click, to notify when no browser is open, or to stay signed into a second account permanently, is not.

The FAQ covers what happens to these apps when the sites behind them change, which is the question most people ask second.

What to change first

Open the App Store, click Updates, and see whether WhatsApp is listed. If it is, turn on Automatic Updates in App Store settings and the problem is solved permanently. If it is not, the installed copy came from the download page, so replace it once from there, and for the sites that have no native Mac app at all, build them into standalone applications with a site to app tool such as Kagemusha so their content stays current on its own.