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

WhatsApp for web works on a Mac in any recent browser. Go to web.whatsapp.com, open WhatsApp on the phone, choose Linked devices, then Link a device, and scan the QR code on the Mac screen. That is the whole setup. What usually goes wrong comes later: the tab gets closed by accident, notifications stop, and the session drops after a couple of weeks. This guide covers the setup step by step, the limits WhatsApp itself publishes for the web version, and three ways to move WhatsApp Web out of a browser tab into a window with its own Dock icon.

Linking WhatsApp Web on a Mac, step by step

WhatsApp's help article on linking a device describes the flow from the phone side. In short:

1. On the Mac, open web.whatsapp.com in Safari, Chrome, Edge, Firefox or Opera.
2. On the phone, open WhatsApp. On Android, tap the menu, then Linked devices, then Link a device. On iPhone, tap Settings or the profile picture, then Linked devices, then Link device.
3. If asked, confirm on the phone with Face ID, a fingerprint, or the phone's unlock PIN. In the browser, WhatsApp may also ask to create or use a passkey.
4. Point the phone at the QR code on the Mac screen.

Chats appear after a short wait. WhatsApp's article on message history on linked devices explains why it is not instant: the phone sends an end-to-end encrypted copy of recent history to the new device, where it is stored locally, and that can take a few minutes for large chats.

If the QR code will not scan, the usual causes are a dim or reflective screen, a zoomed browser window, or a phone that is offline. Reset the browser zoom with Command-0, raise the screen brightness, and check that the phone has a connection.

What WhatsApp Web commits the user to

The web version is not a full copy of the phone. WhatsApp publishes four limits that shape everyday use. Each was checked on WhatsApp's help pages on October 18, 2026.

Four linked devices. One phone can link up to four other devices, according to the linking article. WhatsApp Web in a browser, the desktop app, an iPad and a second computer each count as one.

The 14-day rule. The same article says the primary phone has to be used to log in to WhatsApp at least once every 14 days to keep linked devices connected. A phone left in a drawer for a holiday is the most common reason a Mac session ends without warning.

Less history than the desktop app. The history article states plainly that WhatsApp Desktop syncs more message history than WhatsApp Web. To search older messages, the phone is the reference.

Browser minimums. WhatsApp's supported browsers page lists Chrome 100, Edge 100, Firefox 115, Safari 15 and Opera 86 as the lowest versions, and says calling works best on those five browsers.

What the web version does offer is listed in WhatsApp's own article About WhatsApp Web: free calls over the internet connection, chat folders, pinned chats, keyboard shortcuts, and file sharing. It does not need any download, which is why it is the default for people on managed work Macs or older systems.

Why a browser tab is a poor home for WhatsApp

None of the limits above explain why so many people search for a better way to run WhatsApp Web on a Mac. The tab does.

A messaging app is something that should always be open and easy to reach. A browser tab is neither. It sits among dozens of others, closes with Command-W when a different tab was meant, and disappears entirely when the browser quits. Command-Tab cannot reach it directly, and there is no Dock icon to show an unread count.

Notifications are the second problem. Browser notifications depend on the browser running, on the site being open in some tab, and on permission granted for that browser in macOS. When any one of the three is missing, messages arrive silently.

The third problem is account separation. A personal WhatsApp in the same browser profile as work tools means work extensions, history and cookies share space with private chats. And a second WhatsApp account, such as a business number, cannot be open in the same browser profile at the same time.

All three problems have the same fix: give WhatsApp Web a window of its own.

Option one: Safari's Add to Dock

On macOS Sonoma 14 and later, Safari can turn any page into a web app. Apple's article on Safari web apps gives the steps:

1. Open web.whatsapp.com in Safari.
2. Choose File, then Add to Dock.
3. Name it WhatsApp and click Add.

The new app lives in the Applications folder of the home folder, opens from the Dock or Spotlight, and shares no cookies or website data with Safari. That last point means WhatsApp has to be linked again inside the new window, using a new QR code. It also means it counts as another device toward the limit of four.

Allow notifications inside the web app, not in Safari. Apple notes that the unread badge on the Dock icon only works when the website's notification request is answered within the web app. After that, the app appears under its own name in System Settings, then Notifications.

The limits: Sonoma or later is required, and the web app can only use Safari extensions.

Option two: Chrome's Install page as app

Chrome offers the same idea on older systems. Google's Chrome web apps help page gives the menu path: open web.whatsapp.com, click More, then Cast, save, and share, then Install page as app.

The result opens in its own window with a Dock icon. Because it shares the regular Chrome profile, the existing WhatsApp session carries over without a new QR code, and Chrome extensions remain available.

That shared profile is also the drawback. The app is still tied to Chrome's profile, so private chats sit beside whatever else that profile holds. Running two WhatsApp accounts side by side means creating a second Chrome profile and installing the app again from it.

Option three: a separate app from a site to app tool

A site to app tool builds a standalone .app around a web address, using a browser already on the Mac. The difference from Chrome's own feature is that each app gets its own browser profile. WhatsApp's cookies and session live only in that app.

This suits three cases. Two WhatsApp accounts at once, such as personal and business, become two apps that stay signed in independently. Private chats are kept fully apart from the work browser. And Chrome extensions can still be switched on for that one app if needed.

The tool from this site's developer lists WhatsApp among its 300 plus presets on the supported services page, so the address, icon and name are filled in automatically. Its user guide points to the settings worth changing for a chat app:

• Notifications are off by default. Turn them on, and messages arrive through macOS Notification Center.
• Quit Confirmation asks before Command-Q closes the app, which prevents the most common way a chat window disappears.
• Show in Dock keeps the icon visible so Command-Tab reaches it.
• Tab Restore reopens the last state at launch.

It needs macOS 12 or later and a Chromium browser such as Chrome, Brave or Edge. The free tier covers up to three apps with every feature, and the pricing section lists the one-time fee for more.

When the desktop app is the better choice

A window of its own fixes the tab problem, but it is still WhatsApp Web inside. For some people the official desktop app is simply the better tool, and it is worth checking before building anything.

WhatsApp's help article About WhatsApp for desktops lists what the Mac app adds, with the Mac tab selected. It supports voice and video calls with up to 32 people, screen sharing during video calls, and joining a group call after it has started. It can show call notifications even when the app is closed. And it gives access to up to three years of message history, which is a clear step beyond the recent history the web version receives.

The same article sets the entry requirement: macOS 12.1 or newer. It can be downloaded from the WhatsApp download page for Mac or from the App Store.

So the decision is short. If calls, screen sharing or deep history search are a regular part of the day, and the Mac meets the system requirement, install the desktop app. If the Mac is older, managed by an employer that blocks new apps, or needs two accounts at once, the web version in a window of its own remains the practical answer. Both can be linked at the same time, as long as the total stays within four devices.

The three options compared

	Safari web app	Chrome web app	Site to app tool
Lowest macOS	Sonoma 14	What Chrome supports	Depends on the tool
Needs a new QR scan	Yes	No	Yes
Own cookies and session	Yes	No, shares Chrome profile	Yes
Two accounts side by side	One web app each	Needs a second Chrome profile	One app each
Chrome extensions	No	Yes	Yes, per app
Cost	Free	Free	Free tier, then one-time

Each option uses one of the four linked device slots, so count the devices already linked before adding another.

Keeping the session alive

Once WhatsApp has its own window, three habits keep it working.

Open WhatsApp on the phone at least once every two weeks. It sounds trivial, but the 14-day rule is the most frequent reason for an unexpected logout.

Remove old links. In WhatsApp on the phone, Linked devices shows every connected browser and computer. WhatsApp's unlink article explains that tapping a device and choosing Log out ends that session. Clearing out an old browser tab frees a slot for the new window.

Add the app to Login Items in System Settings, under General, so WhatsApp is open before the first message of the day arrives.

Finally, watch for the unrecognized device prompt. WhatsApp's linking article says that when it detects a device it does not recognize, the phone asks for confirmation, with Link device and Don't link as the two choices. If that prompt appears when nobody on the Mac just scanned a code, choose Don't link, then review the list under Linked devices and log out anything unfamiliar. A chat window that is always open is convenient, and it is also worth a glance at that list once a month.

What to change first

Pick one window for WhatsApp Web today: Safari's Add to Dock on Sonoma or later, Chrome's installed app on older systems, or a separate app with its own profile from a tool such as Kagemusha when two accounts or strict separation matter. Then turn on notifications inside that window and unlink the old browser tab.