WhatsApp Web in its own Mac window

The search for a whatsapp web app for mac usually starts after the same small failure repeats a few times. A message arrives, nothing appears on screen, and the reply goes out forty minutes late because the browser tab holding web.whatsapp.com had been closed during a tab cleanup. The fix looks obvious at first glance: install something. The part worth thinking about is what exactly gets installed, because WhatsApp now runs on macOS in at least three different shapes, and the three differ in ways that decide whether notifications survive, whether a second number is possible, and how many of the phone's limited linking slots get consumed.

None of these are hard to set up. Choosing between them takes about ten minutes if the trade-offs are laid out, and takes months of low-grade annoyance if they are not.

Three shapes WhatsApp takes on a Mac

The first shape is the official desktop application. WhatsApp distributes a native macOS build through the Mac App Store and from its own site, rebuilt on Apple's Catalyst framework so that it runs as a real Mac application rather than a packaged web page. It gets a Dock icon, a badge, and system notification settings of its own.

The second shape is web.whatsapp.com in an ordinary browser tab. It requires no installation, works in Safari, Chrome, Firefox, and Edge, and behaves like every other tab. That is precisely the problem. It gets closed by accident, it disappears behind thirty other tabs, and it shares one notification identity with every other site in that browser.

The third shape sits between the two. Recent versions of macOS and Chrome can turn a web page into a standalone application window. In Safari, File then Add to Dock creates a web app that appears in the Applications folder. In Chrome, the equivalent command installs the page as an app. A browser built to keep each web app in its own window does the same thing as its default behavior rather than as a per site action.

Shape	Where the session is stored	Own Dock icon	Uses a linked device slot	Second number on the same Mac
Native macOS app	Inside the app	Yes	Yes	No
Browser tab	Browser profile storage	No	Yes	Only with a second profile
Standalone web app window	Per web app storage	Yes	Yes	Yes, one window each

The linked device slot is the real budget

WhatsApp's account lives on the phone. Everything else is a linked device, and the phone can carry up to four of them at once. That number is the constraint most people hit without noticing, because a work laptop, a home Mac, a tablet, and one abandoned session from a machine that has since been wiped will fill it completely.

Each storage container counts as one slot, not each application. Two Chrome profiles each signed into web.whatsapp.com are two linked devices. A Safari web app and a Safari tab are two more, since Apple documents that a web app keeps its own cookies and website data separate from the browser it was created in. The native app is one. Nothing here is shared, and nothing is free.

The practical consequence is that experimenting has a cost. Trying four different setups in one afternoon can fill every slot, at which point WhatsApp asks which existing device to remove before linking a new one. Before setting anything up, it is worth opening Linked Devices on the phone and logging out of every entry that is not currently in use. Old sessions do expire on their own if the phone stays offline long enough, but waiting for that is slower than clearing them manually.

Re-linking is also not free in attention. Each new container needs the QR code scanned again from the phone, and message history on a freshly linked device syncs from scratch.

Where notifications actually break

Notifications are the reason most people go looking for an app in the first place, and they break in a specific order. The web version needs permission from the browser before it can post anything to macOS. If browser notifications were denied once during some unrelated cookie banner, WhatsApp never gets a second chance to ask until the permission is reset by hand.

Even with permission granted, a tab that has been closed delivers nothing. There is no background process. The session is only alive while the page is loaded, which is why the failure feels random: it depends entirely on whether that tab survived the last cleanup.

A standalone window changes the shape of this problem, because macOS then sees a distinct application. Apple's documentation on Safari web apps describes the result plainly.

A web app works separately from Safari. It does not share browsing history, cookies, website data, or settings with Safari. Source: support.apple.com

Separation at that level is what makes per application rules possible. A Focus mode can allow messages from one app and silence another. Notification style, badges, and grouping can be set differently for chat and for email. None of that is available for a tab, because System Settings has no concept of a tab. It sees one browser.

Running two numbers on one Mac

The native application handles one WhatsApp account. A personal number and a work number cannot both be signed in there at the same time, which is the single most common reason people go back to the web version after installing the official app.

The web version can run twice, but only if the two sessions are stored in different places. Two tabs in the same browser profile share one cookie jar and therefore one session. Two separate Chrome profiles work. Two standalone web app windows work, since each keeps its own storage. This is the same mechanism that separates two Slack workspaces or two Google accounts, and it applies identically to every web application a person runs during the day, which is why solving it once per app tends to be less work than solving it once per account. A list of the services commonly set up this way is kept on the supported apps page.

Worth noting: both sessions still count against the four linked device slots on the phone, and each number needs its own phone to scan its own QR code.

What a window gives that a tab does not

A window has a name at the system level. That sounds trivial until the consequences add up. Command Tab reaches it directly instead of landing on a browser and then requiring a hunt through tabs. Mission Control shows it as a separate thing. It can be assigned to a specific desktop or a second display and it will return there after a restart. It carries a Dock badge showing unread count. It cannot be closed by a keyboard shortcut aimed at the tab next to it.

There is also a subtler effect. A chat application that lives in the same window as work documents makes checking messages nearly free, which sounds efficient and is not. Every incoming message becomes a candidate for immediate attention. When messaging occupies a separate window, switching to it is a deliberate act, and the ten seconds of friction is enough to defer most of the interruptions that were not urgent. The difference between grouping web apps by window and grouping them by tab is covered in more detail under workspaces.

Setting it up without burning slots

The order of operations matters more than the choice of tool, because linking is the step with a limit attached. A sequence that avoids waste looks like this.

Start on the phone, in Settings under Linked Devices. Everything listed there is consuming one of the four slots. Old laptops, a browser used once at an airport, a machine that was reset months ago: log all of them out. Most people find at least one entry that no longer corresponds to a device they own.

Decide next how many WhatsApp numbers actually need to be reachable from this Mac. One number is the common case and the native application covers it cleanly. Two numbers means two containers, and the containers should be created before either is linked, so that the QR code is scanned once per container rather than repeatedly during experimentation.

Create the container. In Safari, open web.whatsapp.com and choose File then Add to Dock, giving it a name that identifies the number rather than just saying WhatsApp, because two identically named Dock icons defeat the purpose. In Chrome, create the profile first, then install the page as an app from inside that profile. In a browser organized around per app windows, add the service twice and assign each instance to the workspace it belongs to.

Only then scan the QR code, once per container. Wait for message history to finish syncing before deciding whether the setup works, since a freshly linked device shows an incomplete conversation list for the first few minutes and that looks like a failure when it is not.

Finally, set notification behavior per window in System Settings, and add the work container to any Focus mode that should let messages through. This last step is the one that makes the whole exercise worthwhile, and it is also the one most often skipped.

When a plain browser tab is still correct

Not every situation calls for an installed app. On a shared or managed Mac, leaving a WhatsApp session permanently signed in is a real risk, and a tab that closes with the browser is the safer choice. Someone who reads WhatsApp twice a week does not need a Dock icon competing for attention. And a machine already at four linked devices may simply not have room for another container.

The web version also stays current automatically, with no update to install and no App Store dependency. For occasional use, that is enough. The case for a dedicated window gets strong at the point where messages arriving during the workday need to be seen within minutes, or where two numbers have to coexist.

Memory is a smaller factor than people expect. A standalone web app window is still a browser process, so it costs roughly what the equivalent tab cost, not less. The saving is not in resources. It is in the number of decisions per day, and in the fact that a window cannot be lost inside a tab strip.

What to change first

Open Linked Devices on the phone and remove every session that is not actively in use, because that decides how much room is left for anything else. Then pick one shape and commit to it for a week: the native app if there is only one number, or a standalone window per number if there are two. If the same question is about to repeat for Slack, mail, and a calendar, the per app setup stops scaling and the boundary is better drawn once at the browser level, which is what SpaceDeck is built to do.