WhatsApp on a Mac: the setup order that holds up

Installing WhatsApp on a Mac takes about two minutes. Scanning a QR code finishes it. The reason so many setups get redone a week later is that three decisions belong before that QR code, and skipping them produces problems that look unrelated to the install: duplicate notifications, a device that keeps getting logged out, a work number that never appears on the computer at all.

What follows is the order that avoids rework. The decisions come first, the clicking comes second, and there are two things worth checking once a month afterwards.

Decision one: which phone owns the account

A WhatsApp account belongs to a phone number, and the handset where that number is registered becomes the primary device. A Mac cannot take that role. So the first thing settled is not a Mac setting at all. It is which phone, and therefore which number, the Mac will show.

For anyone carrying two handsets this is a real fork. Link the personal phone and the Mac carries personal conversations. Link the work phone and it carries work. There is no supported way to see both numbers inside one desktop client, so this choice determines what kind of work the computer is for.

There is a timing consideration too. Moving an account to a new handset unlinks every connected device. If a phone replacement is coming in the next few weeks, doing the Mac setup afterwards saves doing it twice.

Decision two: the app or the browser

Both routes are free, and they behave differently enough that picking one before installing matters.

The desktop app requires macOS 12.1 or newer according to the download page and the supported operating systems article. A separate help page about downloading the desktop client still says macOS 11 or later. Those two figures have not been brought into line, which means a machine sitting on macOS 11 is in undefined territory and should be planned around rather than assumed.

The browser version runs on Windows, Linux and macOS. Calling works best in Chrome, Edge, Firefox, Safari and Opera, with published minimums of Chrome 85, Edge 85, Firefox 115, Safari 15.2 and Opera 85. Old hardware that cannot move past an earlier macOS still reaches a current browser, so this route stays open the longest.

The decision that matters more than either: do not run both. An installed app plus a forgotten signed-in tab delivers every message twice, in two different visual styles, and spends two device slots instead of one. Choosing one route and closing the other is a two second action now and a recurring annoyance if deferred.

Decision three: how many slots this costs

A phone can have up to four devices linked at once. Computers, tablets, watches and companion handsets all draw from the same four.

Before linking anything, open the linked devices list on the phone and count what is already there. Old work laptops, a tablet linked once during a trip, a browser session from a machine no longer in use. These accumulate quietly. Log out whatever is not in active use, then link the Mac into a slot that is genuinely free.

Linking into a full budget silently displaces something else, and if that something was a device used daily, the failure arrives later with no obvious cause. Counting first removes an entire category of confusing symptoms.

It helps to think of the four slots as a budget with a planned allocation rather than a queue. A typical sensible split is one for the main computer, one for a tablet or watch, and two left free for temporary needs such as a borrowed machine or a hotel workstation. Filling all four permanently means every future situation requires evicting something, usually in a hurry.

The install, in order

  1. Open the linked devices list on the phone and log out anything unused
  2. Check the macOS version; anything below 12.1 goes the browser route
  3. Download the Mac app from the WhatsApp download page or the Apple App Store, both free
  4. Launch it and scan the QR code with the phone camera, or enter a phone number and approve the code that arrives on the handset
  5. Wait for history to transfer, which can take a few minutes depending on how many conversations exist. Only recent history arrives
  6. Grant microphone and camera access so calls work when they are needed rather than during one
  7. Set the macOS notification behaviour for the app
  8. Place the window where it will stay, and leave it there

Steps one and two are the ones that cannot be done later without redoing everything after them. Everything from step three onward is quick.

Notifications are configured in two places

This is where setups most often end up half finished, because two separate control panels govern the same behaviour.

Inside WhatsApp, the choices are whether notifications appear at all, whether message previews are shown, whether sender names are shown, and which conversations are muted individually.

In macOS System Settings, the choices are the alert style, lock screen visibility, notification centre retention, and whether the app is allowed through a Focus mode. That last one is the real payoff of installing the app rather than using a tab. As a distinct application, WhatsApp can be admitted to a Focus mode on its own. As a browser tab, it shares an identity with Gmail, Slack and everything else in that browser, and cannot be separated from them.

If the browser route was chosen, check the per-site notification permission once. Browsers record allow and deny per site, and a site that was denied cannot prompt again. Anyone who has ever dismissed a batch of permission requests may be carrying a block they do not remember setting.

A practical default: start with notifications enabled for a small set of conversations and expand if something is missed. Starting with everything on and pruning later requires a judgement call every single time.

If two numbers have to reach the same Mac

Account switching exists, but WhatsApp documents it as a mobile feature. It does not work on linked devices, and it is not present in the WhatsApp Business app. Secondary accounts can only be created from the primary handset.

That leaves two workable arrangements:

Approach Slots used Notification identity
One number on the Mac, the other on the phone only 1 Clean, single source
Browser version signed in twice, in two browser profiles 2 Both appear as the browser

Which one fits depends on volume. Maintaining two browser profiles for a number that receives a handful of messages a day is not worth the overhead. If both numbers run all day, picking up a handset repeatedly costs more.

One more detail affects the choice. The browser version receives less synced history than the desktop app, by WhatsApp's own description, so running two numbers through browser profiles means two thin archives rather than one. For a number that carries anything worth finding later, the desktop app is the side to put it on.

What the history transfer will and will not bring

Step five in the install list deserves its own explanation, because the wait at that point sets expectations that turn out to be wrong.

When a device is linked, the phone sends an encrypted copy of recent message history to it. Not all of it. WhatsApp states that not every message and chat syncs to linked devices, that the desktop app syncs more than the browser version, and that the phone remains the place to see or search a complete archive. There is also a published known issue in which some linked devices fail to display up to a year of chat history.

The practical consequence should be decided during setup rather than discovered during a deadline. A search that returns nothing on the Mac is not evidence that a message never existed. The habit worth forming on day one is to check the phone before asking a contact to resend anything, which removes a surprising amount of pointless back and forth.

It also means the desktop client is a working surface rather than an archive. Contract terms, addresses, account numbers and anything else that has to survive belong somewhere durable, not in a thread that may be re-truncated the next time the device reconnects.

Things worth learning on day one

A few behaviours pay for themselves immediately. Files can be dragged from Finder straight into a chat window, which for many people is the entire reason the desktop client exists. PDFs open inside the app and can be highlighted or struck through and sent straight back, a feature WhatsApp notes is powered by Adobe Acrobat. Calls support up to 32 participants with screen sharing, call links that can be circulated beforehand, and joining a group call already in progress. That last set is why the microphone and camera permissions belong in the setup rather than in the middle of an incoming call.

Where the window lives

The final step is placement, and it is the one most often skipped. Decide the window position and size, keep the app in the Dock, and do not move it. For the browser route, pin the tab or pull it out into its own window so it does not drift into a row of fifty others.

Anyone running several web services does this repeatedly: two Gmail accounts, two Slack workspaces, a calendar, now WhatsApp. Collapsed into browser tabs, the act of finding the right one becomes a dozens-of-times-a-day cost that never appears in any settings screen. Keeping each service in its own window with its own notification identity is the structural fix, which Features covers and Supported apps lists the scope of.

Two things to check monthly

The linked devices list is worth reopening every few weeks. Unrecognised entries should be logged out. WhatsApp recommends keeping push notifications enabled on the phone so an unexpected link can be reviewed and removed from the notification itself, and warns that linking through unofficial apps or websites can result in a temporary or permanent account ban.

The second is the clock. Linked devices log out if the primary phone goes unused for more than 14 days, and a linked device idle for 30 days disconnects automatically. Relinking takes under a minute, but history reloads as a fresh recent slice, sometimes shorter than before. Anything that needs to be findable in a year does not belong only in a chat thread.

What to change first

Count your linked devices before installing anything, and pick either the app or the browser rather than both. Then place the window somewhere fixed and set the Focus mode rule once, because that is the part that decides whether WhatsApp interrupts you on your terms or on its own. If the same layout problem repeats across every service you use, SpaceDeck is built for that shape of it.

Frequently asked questions

What should be decided before installing WhatsApp on a Mac?

Three things: which handset owns the account, whether to use the desktop app or the browser version, and how many of the four linked device slots are already occupied. The slot count matters most, because linking into a full budget silently disconnects another device.

Is it a problem to use the Mac app and WhatsApp Web at the same time?

It works, but every message produces two notifications and the pair consumes two of the four available device slots on a single computer. Choosing one route before setup keeps notifications clean and leaves slots free for other devices.

The QR code will not scan. What else can be done?

Linking also works by entering a phone number and approving the code that arrives on the handset. If neither route completes, check whether all four device slots are already in use and whether WhatsApp on the phone is up to date. The Mac app also requires macOS 12.1 or newer.

Do microphone and camera permissions have to be granted during setup?

They can be granted later, but doing it during setup avoids scrambling through System Settings while a call is ringing. WhatsApp needs microphone access for voice calls and camera access for video calls, both at the operating system level.

How often should the setup be revisited?

Roughly monthly. Review the linked devices list for anything unfamiliar or unused, and keep in mind that the primary phone needs to be used within 14 days and each linked device within 30 days to stay connected.

Back to all posts