WhatsApp on a Mac not working: what to check, in order

The window that worked yesterday is showing a QR code again. Or it opens but nothing arrives until it is clicked. Or a call connects with no sound going out. Problems in this category are frustrating out of proportion to their difficulty, because the possible causes are spread across four places at once: the phone, the Mac, the browser, and the network. Poking at them in the order they come to mind is how an afternoon disappears.

A fixed order fixes that. What follows works from the cheapest check to the most expensive, and most cases end in the first two sections.

Start on the phone, not on the Mac

The first check takes one minute and decides which half of the problem is worth investigating.

Open the app on the handset and send or receive something. If that fails, nothing done on the Mac will help, and the real work is phone network, app updates, or a restart of the handset itself.

If the phone is healthy, open Linked devices on it and look for the Mac. The answer splits the whole diagnosis in two.

If the Mac is not in the list, the session has ended and the next section applies. If the Mac is in the list but behaving badly, the connection is alive and the fault is in display, permissions, or notification routing, which are covered further down. Skipping this step is what leads to clearing caches and reinstalling an app to fix something that was never on the Mac.

Sessions that end by themselves

Unexpected sign outs are usually documented behaviour rather than a defect, and there are three common sources.

Phone inactivity. Leaving the handset unused for around two weeks signs out every linked device at once. This catches people who keep the number on a spare phone that lives in a drawer, and no amount of Mac side configuration prevents a repeat. The fix is a habit on the phone, not a setting on the Mac.

The device ceiling. Four devices can be linked at a time. A Mac app, a browser session, a tablet and a forgotten laptop is the full allowance, and the symptoms of hitting it are a refused link or an older device dropping when a new one is added. Open the list and sign out anything unrecognised.

Local cleanup. For anyone running the account in a browser, ordinary housekeeping takes the session with it.

If you delete browsing data, all website-related data is also removed in Chrome. The next time you visit the website, you'll need to sign in again. Source: support.google.com

Settings that discard cookies on quit, and extensions that clear site storage on a schedule, produce the same result. A session that dies every Friday is almost always meeting a cleanup routine rather than a bug.

Nothing installs, or the app will not start

When installation is the failure point, the environment is usually the cause.

The App Store listing states macOS 12.1 or later. On anything older the install either refuses or completes and then fails to launch. Check the version from the Apple menu under About This Mac before troubleshooting anything else, because this single line resolves a large share of cases.

Below that version the productive move is to stop trying to install and open the web version instead, since it depends on the browser rather than the operating system. An older Mac that cannot take the app usually runs the web version without complaint.

At a supported version, work through reinstalling from the purchased list in the App Store and restarting the Mac. If it still refuses, open the account in a browser. Success there proves the fault is specific to the installed app rather than to the account or the network, which narrows the next step considerably.

The window opens but never finishes loading

A blank panel or an endless spinner points at the browser layer. Four checks, in this order.

Browser version first. An old build can fail against a service that has moved on, so update before investigating anything more exotic.

Extensions second. Content blockers and anti tracking extensions sometimes stop the connections the page depends on. Disable all of them, reload, and if that works, re enable them one at a time until the culprit appears.

Cookie policy third. Blocking site data outright prevents login state from persisting, which presents as a page that loads and then immediately asks to be linked again.

Network fourth. Corporate and campus networks filter traffic, and a proxy can allow the page to load while blocking what it needs. Switching to a phone hotspot for sixty seconds settles whether the network is involved.

If none of the four helps, open the account in a different browser. A fault that appears in one browser and not the other is configuration. A fault that appears in both is the network or the account.

Notifications that never arrive

Missing alerts have three distinct layers, and checking them out of order wastes the most time of anything in this list.

The first layer is where permission was granted. For a page saved to the Dock as its own window, the request has to be answered inside that window rather than in Safari.

The web app then appears in Notifications settings: From the Apple menu, choose System Settings, click Notifications in the sidebar, then select the web app from the list of applications on the right. Web apps are listed as the name of the web app, not the URL of the website. Source: support.apple.com

Only after answering in the right place does the window appear in that list under its own name. A badge that never shows up while alerts otherwise work is nearly always this.

The second layer is Notifications settings itself. The entry changes name when the container changes, so someone who moved from the app to a browser may find the browser's permission was never granted. Select the current name in the list and confirm alerts are allowed.

The third layer is Focus. An allow list built around the old container silently excludes the new one. Nothing appears broken, and nothing gets through either.

Calls connect but audio or video is missing

When the other side cannot hear or see anything, permissions are the first suspect rather than the network.

macOS records camera and microphone access per application, so a container that was set up recently starts with nothing granted. Open Privacy and Security in System Settings, look at the camera and microphone lists, and confirm the current container appears there. If it is absent, starting a call once produces the prompt.

Two follow ups save a second round of confusion. Quit and reopen the container after granting access, because the change may not apply to a running process. And close other conferencing apps first, since a camera held by another application can present as a black frame rather than as an error.

Old messages or media are missing on the Mac only

A conversation that is complete on the phone but truncated on the Mac looks like data loss and is not.

The account lives on the handset, and a linked Mac is a view onto it. What syncs across after linking is weighted toward recent activity, so older exchanges and older photos or videos are frequently not present on the companion even though the phone still has them. Opening the item once on the phone often brings it across.

Three checks settle it. Confirm the content is still on the handset, which proves nothing has been lost. Give a newly linked session time, because syncing continues after the window becomes usable and a fresh link is not finished the moment it opens. And check storage on the phone, since media cleared there will not appear on any device.

When a specific file is needed now, forwarding it from the phone is faster than waiting. Reinstalling the Mac app does not retrieve anything the handset no longer holds.

Before reinstalling, step back one place in the order

A stubborn fault makes reinstalling tempting, and it is worth knowing how little it repairs.

Reinstalling addresses a damaged application or a failed update. It does nothing for a session ended by phone inactivity, a full device allowance, a notification permission granted in the wrong window, or missing camera and microphone access. Starting there rather than at the top of this list usually means meeting the same symptom again half an hour later.

If a reinstall is genuinely warranted, do it while the phone is within reach, because re registering requires scanning a code. Sign the old entry out of Linked devices before removing anything, so the freed slot is available when the new installation asks for one. Doing it in that order avoids the specific irritation of finishing a reinstall only to be refused a link.

The wrong account answers

Opening what should be the work number and seeing the personal one is not a malfunction. It is two views sharing one store.

Login state lives in cookies and site data. Two tabs in the same browser profile are a single visitor as far as the service is concerned, so the second sign in overwrites the first. The repair is separation: a page saved as its own Dock window, a second browser profile, or a browser that gives each web app its own compartment. How far that separation reaches in the third case is set out on the Workspaces page.

After separating, recount the linked devices. Two accounts on one Mac consume two of the four slots, so a tablet and an old laptop will push the total over the limit quickly.

When the fix keeps undoing itself

If the same symptom returns after being cleared correctly, the configuration rather than the setting is the problem.

Three patterns recur. Sessions that die with every cleanup. Notification permissions that need rebuilding so often that something else goes quiet each time. Two numbers where one keeps falling out. All three share a cause, which is one browser holding everything under one set of cookies and one notification identity. Patching that with settings works until the next condition is added.

Changing the arrangement comes down to three questions: whether storage is separated per compartment, whether one service can run twice under different accounts, and whether notifications are attributed per compartment rather than to the browser as a whole. Which services behave correctly in that model can be checked against Supported apps before committing to anything.

What to change first

Run the order rather than guessing: phone, linked device list, then the specific layer the symptom belongs to. Write down three lines when it is solved, covering whether the phone was healthy, whether the Mac was still linked, and which layer held the fault, because the second occurrence then takes five minutes instead of an afternoon. If the same failure keeps returning by design rather than by accident, the thing to evaluate is per compartment isolation, which is described for SpaceDeck.