Putting WhatsApp Web in a window of its own on a Mac

Anyone searching for WhatsApp for web on a Mac has usually already noticed that a Mac application exists. The search happens anyway, for one of three reasons: the Mac is too old to run the app, the Mac belongs to someone else and installing software is not an option, or the browser version was opened once as a test and simply became the habit.

All three are reasonable. The browser version works, it is officially supported, and WhatsApp lists it on the download page as the route to take when a device is not supported. The problem is not that it works. The problem is where it lives, because a browser tab is a poor container for something that gets checked forty times a day.

What the web version actually is

WhatsApp Web is a linked device, not a separate account. The phone remains the account holder, and the browser session is one of several screens that the phone authorises. Nothing about that changes when the official Mac app is used instead, which is the first thing worth knowing: the choice between browser and app is a choice about the window, not about the account.

Two published rules follow from the linked device model, and both apply equally to the browser and the app.

The first is a device count. WhatsApp's help centre states that a primary phone can link up to four devices at a time. A browser session on a Mac counts as one of the four, the same as an installed app would.

The second is a renewal window:

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

For a phone in daily use nobody ever notices this. For a second phone that lives in a drawer, the browser session on the Mac will stop working roughly every two weeks, and the fix is always on the phone rather than on the Mac.

The help centre also carries a standing notice that some linked devices may not display up to one year of chat history, with the full history staying on the primary phone. Searching for an old message from the Mac is therefore not guaranteed to find it. That limitation belongs to the linked device model, not to the browser, so switching to the installed app does not remove it.

Why the browser version persists even where the app runs

The official Mac app states a requirement of macOS 12.1 or newer. That single number decides the first case outright. A Mac kept on Big Sur or earlier, often deliberately, to keep an old audio interface or a particular version of a creative application working, cannot run the app at all. The browser is not a compromise on those machines, it is the supported route.

The second case is a Mac that is not yours to modify. A managed work laptop, a shared machine at a studio, a family computer where installing software would mean explaining why. A browser session needs no installation and leaves nothing behind when the browser data is cleared.

The third case is accounts. A browser holds one signed in session per service per profile. That constraint cuts both ways: it is the reason two WhatsApp accounts cannot comfortably share a browser, and it is also the reason someone who wants work chat and personal chat kept apart ends up putting one of them in a browser and the other in the app. Using both routes at once is a legitimate setup, not a workaround.

The fourth reason is simply inertia, and it is the most common one. The tab was opened, it worked, and nothing forced a decision afterwards.

Three things a tab does badly

Leaving the web version in a tab is free, and the cost is paid in small amounts many times a day.

A tab has no entry in the Command Tab switcher. Reaching it means reaching the browser first and then locating the tab, which is a two step process for something that should be one. On a crowded tab strip the second step involves reading favicons.

A tab shows its unread count in the page title, and page titles are truncated to a handful of characters once enough tabs are open. The count that was supposed to be the reason to keep the tab visible becomes unreadable at exactly the point where it would be most useful.

A tab is one accidental Command W from being gone. Reopening it is usually quick, but not always, because a cleared session means scanning a QR code with the phone again. The phone is not always within reach at the moment the tab closes.

None of these are complaints about WhatsApp. They are properties of tabs, and they apply equally to every other service that lives in one.

There is a fourth property that shows up over longer periods. A tab that is always open becomes invisible. The eye stops registering a favicon that has been in the same position for three weeks, which is why a conversation can sit unread for a day in a tab that was never closed. An icon in the Dock behaves differently, not because it is prettier, but because it carries a badge that changes and sits in a place the eye visits for other reasons.

Giving the web version a window

Since macOS Sonoma 14, Safari can turn any page into a standalone application. Open the page, choose File then Add to Dock, type a name, and the result is an app with a Dock icon, its own entry in Command Tab, and no tab strip.

The separation is real rather than cosmetic:

A web app functions independently of Safari. It shares no browsing history, cookies, website data, or settings with Safari. Source: support.apple.com

Two consequences matter here. The session inside the window is its own, so it survives clearing Safari's data and does not compete with anything signed in inside Safari. And a second account on the same service can be signed into a second window without either one disturbing the other, which is the cleanest answer to keeping work and personal conversations apart on one Mac.

Apple's documentation also notes that the toolbar is streamlined, with a back button, a forward button, a Share button and any Safari extension buttons, and that switching to full Safari requires the Share button and an explicit Open in Safari. The unread count appears as a badge on the Dock icon rather than inside a truncated page title, provided notification permission is granted inside the window rather than in the browser.

The name typed into the dialog is worth a moment of thought. It becomes the Dock label, the Command Tab entry and the string that has to be typed into Spotlight, so a name that starts with the purpose or the account rather than the service is reached in fewer keystrokes.

Where the app is saved, and how to remove it

A Safari web app is stored in the Applications folder inside the home folder, not the shared Applications folder at the root of the disk. That distinction explains most of the confusion about apps that appear to have vanished: Finder, then Go, then Home, then Applications is where they are. Deleting one is a matter of dragging it to the Trash from that folder. Dragging its icon out of the Dock only removes the icon, which is why unused windows accumulate quietly and why the folder is worth reviewing once in a while.

One more consequence of the separate data store deserves a mention before it surprises anyone. The first launch of a new window shows a signed out page, because nothing carries over from the browser. For WhatsApp that means scanning the code once with the phone. After that the window holds its own session and the phone is not needed again until the 14 day sign in comes around.

The four routes, side by side

Route	Minimum macOS	Installs software	Own Dock icon	Two accounts at once
Official Mac app	12.1	Yes	Yes	Not in one copy
Browser tab	Whatever the browser needs	No	No	One per browser profile
Safari web app	Sonoma 14	No download	Yes	Yes, one per app
Site to app tool	Depends on the tool	Yes	Yes	Yes, one per app

The table answers the common cases quickly. On macOS 12.1 or newer with one account and no restrictions, the official app is the simplest choice and it is free. On an older Mac, or a managed one, the browser is the route, and giving it a window is what makes it comfortable. Where two accounts are in play, one window each is the only arrangement that avoids signing in and out.

There is one row the table does not capture. Safari's route requires macOS Sonoma 14, which means the Macs most in need of the browser version, the ones below macOS 12.1, cannot use it. On those machines a tool that turns a website into a standalone Mac app is the only way to get a window with no tab strip, because the built in route arrived years after the operating system they are running.

Where a dedicated tool changes the answer

Once more than one or two services are involved, building each window by hand stops being worth the time, and three differences start to matter.

The first is coverage of older systems, described above. The second is starting from a preset rather than from a blank dialog: more than 300 services ship as ready made entries with the correct address, name and artwork already filled in, and the list on Supported services is a fair guide to which sites other people found worth pulling out of a tab strip.

The third is what happens when a link inside the window is clicked. Chat is full of links, and a window that hands every one of them to the default browser pulls the session straight back into the tab strip it was supposed to replace. Control over that behaviour is the difference between a window that stays a window and one that quietly becomes a browser again. The rest of what separates the two routes is on Features, with the steps on the Guide.

What to change first

Check the macOS version before anything else, because it decides the shortlist. On macOS 12.1 or newer with a single account, install the official app and stop there. Otherwise take the browser version out of the tab strip and give it a window of its own, using Safari on macOS Sonoma 14 or later, or Kagemusha on an older Mac or when a second account needs a window of its own.