WhatsApp on a Mac: what it does and where it breaks down

The Mac app looks like the phone app. It is not the same thing, and the difference is structural rather than cosmetic. A WhatsApp account is registered to a phone number and lives on a phone. Every other device, including a Mac, attaches to that account as a companion. WhatsApp states this directly: linked devices such as Windows, Mac, Web, iPad and wearables cannot be used as the primary device on an account.

Once that is clear, most of the odd behaviour stops being mysterious. Missing search results, duplicated notifications, a QR screen appearing after weeks of normal use, a second number that refuses to show up. All four follow from the same architecture.

The account is on the phone, the Mac is a window onto it

Registration happens on the phone. Linking new devices happens from the phone. Installing the Mac app does not create anything; it opens another view onto something that already exists.

Linking takes one of two forms. Either the Mac displays a QR code and the phone's camera reads it, or a phone number is typed on the Mac and a code appears on the phone for approval. Both require the phone to be physically present at that moment.

After linking, the phone can be switched off and the Mac keeps working. This is the part that changed with multi-device support. Older versions of the browser client relayed everything through the handset, so the Mac went silent whenever the phone lost signal. Now each linked device connects to WhatsApp on its own. That independence is the reason the desktop client feels like a real app rather than a mirror, and it is also the root of the history problem described below.

Encryption is per device, which is why history is thin

End to end encryption applies between the sender and each receiving device separately. A message arriving on a Mac was encrypted for that Mac, not forwarded from the phone after the fact.

That has an awkward consequence. Anything sent before the Mac existed as a device was never encrypted for it. To show older conversations, the phone has to re-encrypt and re-send them. WhatsApp describes this as the phone sending an encrypted copy of the most recent message history right after linking, stored locally on the new device.

Most recent, not all. The company states explicitly that not every message and chat is synced to linked devices, that the desktop app syncs more history than the browser version, and that the phone remains the place to see or search a full archive. As of September 2026 there is also a published known issue in which some linked devices fail to show up to a year of chat history.

The practical rule is that the Mac holds a partial ledger that began on the day it was linked. Relinking after a logout starts a fresh partial ledger, sometimes shorter than the previous one.

This changes how searching should be treated. An empty result on the desktop proves nothing about whether a message exists, only that it is not in the local copy. Asking a contact to resend something that is sitting in the phone's archive is a small waste, but it happens constantly, and it is the clearest everyday symptom of the companion architecture. Anything that has to be findable later belongs somewhere other than a chat thread.

What the Mac client can actually do

The companion role does not mean a reduced feature set. The Mac app covers:

• Voice and video calls with up to 32 participants
• Screen sharing during a call, and call links that can be shared in advance
• Joining a group call that is already in progress, plus call history
• Drag and drop file sharing into any chat
• Opening a PDF, annotating it with highlights and strikethrough, and returning it to the chat, powered by Adobe Acrobat
• Status posts that disappear after 24 hours, Channels, and Communities

It runs on macOS 12.1 or newer. Calls require granting microphone access, and video calls require camera access, at the operating system level. Skipping those prompts produces a call that rings and then stays silent, which is frequently mistaken for a network fault.

One inconsistency is worth noting before planning an installation. The download page and the supported operating systems article both give macOS 12.1 as the minimum, while a separate help article about downloading the desktop client states macOS 11 or later. The documentation has not been reconciled, so a machine on macOS 11 sits in an undefined zone. Anyone in that position should plan around the browser version rather than assume the app will install.

The list above also explains why the desktop client is worth a slot for some people and not for others. Typing long replies, running calls with screen sharing, and moving files off a Mac are all genuinely better on a computer. Reading and reacting to short messages is not, and that is most of what many accounts carry.

The browser version is a different animal

"Using WhatsApp on a Mac" covers two arrangements that behave differently, and conflating them causes a lot of confusion.

The browser version runs at web.whatsapp.com and needs no installation. WhatsApp lists it as supported on Windows, Linux and macOS, with calling working best in Chrome, Edge, Firefox, Safari and Opera. The published minimum versions are Chrome 85, Edge 85, Firefox 115, Safari 15.2 and Opera 85. For a Mac that cannot move past an older macOS release, this is the route that stays open, since browsers keep updating long after an operating system stops receiving new applications.

What differs is not the message list but everything around it. The browser version receives less synced history than the desktop app, by WhatsApp's own description. Its notifications belong to the browser rather than to WhatsApp. Its window is a tab, subject to being discarded when memory runs short, which quietly ends notification delivery until the tab is revisited.

Both arrangements consume one linked device slot each. Running the app and leaving a browser tab signed in costs two of four, for one person on one machine. That is the single most common way a slot budget disappears without anybody noticing.

A reasonable rule: use the desktop app when WhatsApp is part of daily work, use the browser version when the need is occasional or the hardware is old, and avoid running both on the same machine.

Where it breaks down, part one: notification identity

Install the Mac app and macOS treats WhatsApp as its own notification source. That is the correct outcome. Run it as a browser tab instead and the notification source becomes the browser, shared with Gmail, Slack, a calendar and everything else. A Focus mode cannot admit one conversation and hold the rest, because the operating system cannot distinguish sources inside a single application.

The common failure is running both. A Mac app that was installed last month plus a forgotten web tab produces two notifications for one message, arriving in different shapes. The usual reaction is to silence both, which is how an important channel goes quiet.

There is a second layer to this. Browser notifications are granted per site, and a site that was once blocked cannot ask again. Anyone who batch-dismissed permission prompts at some point may have a standing block they have no memory of creating.

Separating windows and notification sources per service is the whole reason a category of tools exists for this, and Workspaces explains how that separation is normally structured.

Where it breaks down, part two: one number per Mac

WhatsApp supports two accounts on one device, but the documentation confines that feature to mobile. It does not work on linked devices, and it is not available in the WhatsApp Business app. Secondary accounts can only be created from the primary mobile device, and only mobile companion devices are able to switch between accounts.

The asymmetry is easy to miss. On the phone, both numbers are reachable and switching takes two taps. Sitting down at the Mac, exactly one of them exists, whichever one the desktop client was linked to. Nothing warns about this. One number simply stops producing desktop notifications, and the omission is usually discovered late.

Workarounds exist, and each has a price. Two browser profiles, each signed in to a different number through the browser version, does work, and it burns two slots on one computer. A separate macOS user account gives cleaner isolation at the cost of logging in and out of the machine itself. Neither produces the thing people actually want, which is two numbers visible side by side in a single place.

It is also worth knowing that a second handset can be attached to the same account as a companion phone. Linked device types include Windows, Mac, Web, Android tablets, iPad, WearOS watches, companion phones, Meta AI glasses and VR headsets. A companion phone occupies one of the same four slots that a Mac does.

Where it breaks down, part three: the timers

Three limits govern how long a connection survives, and none of them are adjustable.

Rule	Value
Devices linked at once	4
Phone left unused before linked devices log out	14 days
Linked device left idle before automatic disconnect	30 days

A Mac showing an empty QR screen after a holiday is almost always one of these three, not a fault. Reconnecting is quick, but it resets the local history to whatever the phone chooses to send at that moment.

The 14 day rule catches people whose phone is not their main computer. Someone travelling with a laptop and a phone left at home, or using a work handset only during office hours, can cross the threshold without touching anything. The phone does not need to send messages to reset the clock. It needs to be used.

The 30 day rule catches the opposite case: a spare machine linked once and then ignored. A second office Mac, a family computer, a laptop kept for travel. Each of those looks connected in the list right up until it is silently dropped, which is why the list is worth reading rather than trusting.

The timers double as a security feature. WhatsApp recommends keeping push notifications enabled on the phone so that an unrecognised link can be reviewed and removed from the notification itself, and warns that linking through unofficial apps or websites can lead to a temporary or permanent account ban. Checking the linked devices list is a maintenance task, not a one time setup step.

What to change first

Open the linked devices list on the phone and count what is connected, then remove anything unused so the slot budget is honest. After that, decide whether this Mac deserves a dedicated window or a browser tab, and base the answer on how many times a day WhatsApp interrupts you rather than on convenience. If the same question applies to several services at once, the layout is the thing to solve, and SpaceDeck is built around keeping each one in its own window.