Meta Business Suite desktop: pages and ads in one window

Anyone managing a page and an ad account from a Mac reaches the same question within a week. The inbox needs checking several times a day, the ads need watching, and a browser tab is a poor home for both. The search for a Meta Business Suite desktop app follows naturally, and the answer is short: Meta publishes it for the browser and for phones, with nothing to install on macOS. That is not the end of the matter, because the browser version can be given a window, a Dock icon, and its own sign in. What follows is what Meta actually publishes, and what to do with it.

What Meta publishes for the desktop

Meta's own product page is unusually direct about the shape of the product. It describes managing business activity on Facebook, Messenger, and Instagram from one place, then says that whether it is being used on desktop or mobile, the suite makes it easy to view notifications and respond to messages quickly. The instruction at the bottom of that page removes any ambiguity: use the button to open Meta Business Suite in the browser, or scan the QR code with a mobile device to download the app.

In other words, desktop means a browser, and the app means a phone or tablet. The desktop entry point is business.facebook.com, and there is no macOS installer anywhere in Meta's own documentation for this tool.

The App Store side confirms it from the other direction. The Meta Business Suite listing is published by Meta Platforms, Inc. for iPhone and iPad and requires iOS 15.1 or later. The separate Meta Ads Manager listing, formerly Facebook Ads Manager, is also iPhone and iPad, weighs 119.6 MB, and carries the same iOS 15.1 floor, with an average of 4.5 across roughly 51,000 ratings. Neither listing includes Mac among its supported devices, so the route that sometimes works for iPad apps on Apple silicon is closed here.

Desktop is where some of the work only happens

This matters because the desktop version is not a reduced copy of the phone app. Meta's page states that from Meta Business Suite on desktop, other Meta tools such as Ads Manager, Commerce Manager, and Business Settings can be reached quickly. Business Settings in particular is where people, partners, and asset permissions are administered, and that is not casual phone work.

The same is true of the parts that exist on both. Publishing feed posts and stories for Facebook and Instagram without switching accounts, scheduling them for later, saving drafts, and uploading assets to the media library are all listed as features of the suite. Doing them on a wide screen with a real keyboard and a file dialog is faster by a wide margin, and uploading a set of images from a Mac is not a phone task at all.

That combination is the reason a browser tab starts to feel wrong. A tool used for a few minutes at a time, several times a day, that also handles the one screen where permissions and billing live, deserves a more stable home than a favicon in a crowded tab bar.

Why a tab is the wrong container for an inbox

The suite's Inbox reads and replies to messages and comments across Facebook, Messenger, and Instagram in one place, with Automated Responses available for faster replies. The Home screen carries a To-Do List and an Activity tab that shows what has happened across both platforms. All of that is queue shaped work, and queue shaped work wants a container that can be checked and dismissed.

A tab fails at this in three specific ways. It cannot be reached from the application switcher, so the keystroke that gets to Mail does not get to the inbox. It gets closed during unrelated cleanups, and reopening it means a fresh sign in prompt often enough to be annoying. And it sits next to whatever else the browser is being used for, which for anyone doing paid media means sitting next to the research, the invoices, and the personal accounts.

A window with its own icon fixes all three at once, and it costs nothing. The two routes below are already on the machine.

Building the window with Safari

Starting with macOS Sonoma 14, Safari can save any page as a web app. Apple's documentation gives the sequence: open the page in Safari, choose File then Add to Dock from the menu bar, type a name, and click Add. The window is saved to the Applications folder of the home folder, and it opens from the Dock or from Spotlight.

Two properties described by Apple decide how useful this is for business accounts. A web app functions independently of Safari and shares no browsing history, cookies, website data, or settings with it, which keeps a work sign in from mixing with everything else. And for websites that send notifications, the web app's icon in the Dock can show the number of unread notifications, which is the behaviour that makes an inbox window worth building.

The settings panel, opened by clicking the window's name in the menu bar, allows the Application URL, name, and icon to be changed later, and holds an Extensions tab for enabling extensions individually. Setting a recognisable icon is worth thirty seconds, because a Dock with three of these in it is otherwise three identical squares.

Building the window with Chrome

Chrome offers the same outcome through More, then Cast, save, and share, then Install page as app. On some sites an install button appears at the right of the address bar instead.

The important difference is again the session. A Chrome installed app runs inside the profile it was created in and shares that profile's signed in state. For one account that is convenient, since the window opens already signed in. For several accounts it means one Chrome profile each, which is a heavier arrangement than it sounds once four clients are involved.

Chrome also warns when an installed app tries to change its own name or icon, offering the choice to update, ignore, or uninstall. That prompt is worth reading rather than dismissing.

More than one business portfolio

Agencies and freelancers hit the real limitation quickly. Managing several businesses means several sets of assets, and switching between them inside one window means re-orienting every time. The person who has just replied to a message under the wrong brand only needs to do it once to start looking for a better arrangement.

Separate windows solve this because separate sessions are the default in the Safari route. Each web app holds its own cookies, so two windows can hold two signed in identities, named and iconed per client. Nothing is shared between them, and closing one does not disturb the other.

Route	Sign in state	Reach	Requirement
Browser tab	Shared with the browser	Tab bar only	None
Safari, Add to Dock	Separate per window	Dock and switcher	macOS Sonoma 14 or later
Chrome, Install page as app	Shared with that profile	Dock and switcher	Chrome installed
Purpose built site to app tool	Separate per app	Dock and switcher	The tool itself

The table describes containers, not capabilities. Every route shows the same suite with the same features, because in all four cases the page being rendered is the same page. What differs is how many identities can be live at once and how quickly each one can be reached. The guide covers keeping several of them straight.

Which screen the window should open on

A window that opens on the wrong screen gets clicked through every morning, so the starting address deserves a decision rather than a default. The suite's Home screen carries the To-Do List and the Activity tab, which suits someone whose first question each day is what happened overnight. For a person whose job is replying, the Inbox is the better anchor, because the queue is the work and the summary screen is a detour.

Paid media changes the answer again. Meta lists Ads Manager among the tools reachable from the desktop version, and anyone watching spend daily is opening that screen far more often than the publishing calendar. Pointing one window at the reporting view and leaving the publishing side to a second window separates two jobs that happen to live under one login, which is the same principle that makes a mail application and a calendar application separate despite sharing an account.

None of these choices are permanent. The web app settings panel allows the Application URL to be retyped, or set to the current page with one click, so a window created on the home screen can be repointed at the inbox after a week of using it. The practical method is to build the window on whatever page is open right now, use it for several days, notice which screen it actually gets driven to, and then set that screen as the address.

Scheduling is one more case worth separating. Posts and stories can be scheduled ahead or saved as drafts, and that is a planning session rather than a daily check. A window that opens on the planning view will be opened once a week, and giving it its own name makes it obvious in the Dock that the weekly job has not been done yet.

Notifications, sign in, and what does not follow

Three things behave differently in a new window, and all three are better discovered deliberately than during a busy afternoon.

Notification permission is granted per application. Permission already given in the browser does not carry across, so the prompt has to be accepted inside the new window before the Dock badge can show anything. For an inbox window, this is the first thing to test.

Two factor prompts happen inside the window that asked for them. Since the window has never seen the browser's session, the first sign in is a full sign in, including whichever verification method the account uses. Doing it at creation time rather than at the moment a reply is urgent is the difference between a tool and an obstacle.

Links from elsewhere still open in the default browser. A notification email about a comment, or a link pasted into a chat, goes to whatever browser macOS is configured to use, not to the new window. That is an operating system routing rule rather than a shortcoming of any route, so the browser stays in the picture and should stay signed into an account that makes sense.

File dialogs, by contrast, behave normally. Uploading creative assets to the media library opens the standard macOS panel, because as far as the system is concerned the window is a real application. Anyone worried that a lightweight route would compromise on uploads can stop worrying about that one. The supported services list shows which sites are already prepared as windows, and the pricing page covers what keeping several of them tidy costs.

What to change first

Build one window on the desktop suite, sign in there once, accept the notification prompt, and use it for a week before changing anything else. If a second client or a second portfolio appears, give it its own window with its own name and icon rather than switching inside the first, and a tool such as Kagemusha keeps the set consistent as it grows.