The WhatsApp Mac app, and the one thing it will not do

Most services that people want as a Mac app do not ship one. WhatsApp is the opposite case. There is a real Mac build, it costs nothing, and it runs further back into old macOS releases than Chrome does. So the search for a WhatsApp Mac app rarely ends at the download button. It ends at a specific wall: a personal number and a work number cannot both live in that app at the same time, and WhatsApp says so in its own documentation. Everything worth deciding here follows from that.

What actually ships, and the version floor

The download page lists a Mac build alongside Windows, Android, iOS and iPadOS, and states the requirement plainly: the Mac app needs macOS 12.1 or newer. The App Store listing agrees. WhatsApp Messenger is published by WhatsApp Inc. as a single listing covering several platforms, and its compatibility section reads iOS 15.1 or later for iPhone, iPadOS 15.1 or later for iPad, watchOS 10.0 or later for Apple Watch, and macOS 12.1 or later for Mac. The listing gives the download size as 397.4 MB and the price as free.

That macOS 12.1 floor is lower than it looks, and it matters more than any feature comparison in this article. Chrome states its own requirement as macOS 13 Ventura and up. Safari web apps, the built in Add to Dock feature, require macOS Sonoma 14 or later.

Line those three numbers up and the usual advice inverts. On a Mac running Monterey, the official WhatsApp app installs and runs, current Chrome does not, and Safari has no Add to Dock command in the File menu. The browser routes are the ones that are cut off, and the native app is the one that still works. Anyone maintaining an older machine, or a second Mac kept around for a specific job, should check the OS version before reading any further, because it decides which half of this article applies.

The reverse case is just as clean. On a current Mac, all four routes are open, and the choice comes down to what happens when a second account enters the picture.

Linked devices set the rules for every route

WhatsApp is built around a primary phone. Every other place the account appears is a linked device, and the help centre states the limits directly.

You can now use the same WhatsApp account on multiple devices at the same time, using your primary phone to link up to four devices. You'll need to log in to WhatsApp on your primary phone every 14 days to keep linked devices connected to your WhatsApp account. Source: faq.whatsapp.com

Two consequences follow, and both apply no matter which route ends up in the Dock.

The first is that the Mac is not special. The official Mac app, a WhatsApp Web session in a browser tab, and a wrapped window pointed at the same page are all the same kind of thing to the account: one of four slots. A Mac at home, a Mac at work, a browser session on a borrowed laptop and a tablet fill the budget. Adding a fifth means unlinking something.

The second is the 14 day clock. The requirement is a login on the primary phone, not on the Mac. A phone left switched off in a drawer for a fortnight will quietly disconnect every linked session, including the app on the Mac. That failure looks like a bug and is not one.

The help centre also carries a standing note that some linked devices do not display up to one year of chat history, with the full history remaining on the primary device. Worth knowing before treating any Mac window as the archive.

Where the official app stops: the second account

This is the part that sends people looking for alternatives, and it is documented rather than folklore. WhatsApp supports two accounts on one phone, with a separate phone number for each, and describes the boundary of that feature in the same article.

Secondary accounts can only be created from your primary mobile device. Only mobile companion devices can switch between accounts. This feature is not available on linked devices. Multiple accounts are currently only supported on mobile devices. Source: faq.whatsapp.com

Read that against a normal working setup. A freelancer with a personal number and a business number, a shop owner whose staff account is separate from the family group, a consultant carrying a second SIM for one client: all of them can switch accounts on the phone and none of them can do it on the Mac. Installing the official app twice does not help, because the second copy is the same app bundle reading the same stored session.

The workable answer is not a different app. It is a different session container. WhatsApp Web treats each browser profile as its own device, so two profiles can each be linked, one from each phone or each account, and both stay connected at once. That is why the wrapper route exists for this particular service, and why the argument for it here is different from the argument for wrapping a note taking site or a dashboard.

Note the accounting: the two sessions do not compete for the same four slots, because they belong to different accounts. Each account keeps its own budget of four linked devices.

What WhatsApp Web needs from the browser underneath

If the second window is going to be a browser session, the browser version becomes the thing to check. The help centre lists WhatsApp Web as supported on Windows, Linux and macOS, notes that calling works best on Chrome, Edge, Firefox, Safari and Opera, and gives minimum versions of Chrome 85, Edge 85, Firefox 115, Safari 15.2 and Opera 85.

Those floors are low, and current browsers clear them by a wide margin. The practical point is not the number but where it is enforced. A window built on top of a Chromium browser already installed on the Mac reports that browser's version, so the day Chrome updates itself, the wrapped window is updated too. Nothing is rebuilt and nothing is pinned to the version that existed on the day the icon was created.

That also explains a difference the feature tables usually miss. A wrapped window keeps Chrome extensions available inside it, because it is running on the installed browser rather than on a bundled engine. A password manager or a translation extension works in the WhatsApp window the same way it works in a tab. Safari web apps take a different approach: Apple documents that they run Safari extensions and share no browsing history, cookies, website data or settings with Safari, which gives session isolation without the Chrome extension library. Which of those two matters depends entirely on what is already installed.

How far the web page has caught up

The download page describes the Mac build in a single sentence about what it adds: calling, screen sharing and a faster experience. That sentence is the clearest statement available of where the native build is supposed to be ahead, and it is worth reading carefully rather than as marketing.

Calling is on that list, yet the help centre also documents calling on WhatsApp Web and names the browsers where it works best. Both statements can be true at once. Calls run in the browser, and the native build handles them without depending on which browser is installed or what else that browser is doing at the time. For someone who takes voice calls on the Mac every day, that is a reason to keep the official app as the primary session.

Screen sharing sits in the same category. So does speed, which on a machine with a browser holding forty tabs is less about the app being fast and more about the browser being busy. A window built from the site sidesteps part of that by running in its own process with one page in it, which is a smaller improvement than a native build but a real one.

The rest of the daily surface is the same page in both cases. Chats, search, media, groups, channels and status render identically, because the native build and the web session are showing the same product. This is the honest reason the wrapper route is viable for this service: the gap is narrow and specific, not general. Anyone whose Mac usage is reading and replying to messages will not find the difference. Anyone who runs calls from the Mac will.

The four routes side by side

	Official Mac app	WhatsApp Web in a tab	Safari Add to Dock	Site to app window
Minimum macOS	12.1	Browser's own floor, 13 for Chrome	14	Browser's own floor
Cost	Free	Free	Free	Free tier, paid tier for more apps
Second account on the same Mac	Not supported	One session per browser profile	One per web app	One per app
Own Dock icon and switcher entry	Yes	No	Yes	Yes
Chrome extensions inside the window	No	Yes	Safari extensions	Yes, on an installed browser
Counts as a linked device	Yes	Yes	Yes	Yes
Custom name and icon	No	Not applicable	Yes	Yes

The bottom row is not decoration. Two WhatsApp windows on one Mac are useless if both show the same green icon and the same name in the switcher. Being able to set the name to the account it holds is what makes the arrangement survive contact with a busy afternoon. The adjustable pieces are listed on the Features page, and Supported services shows whether a given site is available as a ready made preset rather than a URL to type in.

Before wrapping it, check these three

Notifications have to be granted in the window itself. Apple's documentation is specific: to get the unread count badge on the Dock icon, respond to the site's notification request inside the web app, not in Safari. The same logic applies to any separate session. A permission already granted in the browser does not carry across, and the first symptom is a window that receives messages silently.

Logging out unlinks the device. Closing the window is fine and the session survives. Choosing log out inside WhatsApp Web frees the slot and requires a fresh QR scan from the phone to get it back. On a shared Mac that is the correct behaviour. On a personal Mac it is an easy way to lose a setup that took five minutes to arrange.

Decide where files land. Media saved out of a conversation goes to whatever download location that session uses, and a separate profile can have a separate one. Sorting that out on day one prevents a month of searching two Downloads folders. The Guide covers how these per app settings are stored.

What to change first

Check the macOS version before anything else, because on Monterey the official app is the route and the browser options are closed. If the Mac is current and one number is all that is needed, install the official app and stop there. If a second account has to be reachable without picking up the phone, give it its own window with its own profile and its own name, which is what a tool such as Kagemusha is for.