Google Family Link for Mac: the family dashboard in one window

Searching for Google Family Link on a Mac produces three kinds of result, and none of them is the answer. There is an App Store listing that names only iPhone and iPad. There are sites offering to run the Android version inside an emulator. There are Google's own pages, which talk confidently about phones and Chromebooks and barely mention a computer. The reader sitting at a desk wants to know what to open and whether it will be enough. Google does not publish a Mac application for Family Link and does not intend to, because the parent side of the service already runs in a browser. What is worth knowing is exactly how much of it runs there, what stays on the phone, and how to stop treating a page that gets opened every day as one tab among forty.

What Family Link actually runs on

Google keeps a device compatibility page for Family Link, and it is unusually blunt for a marketing site. On the child side, supervision runs on Android devices with version 7.0, Nougat, and higher. Devices on Android 5.0 and 6.0, Lollipop and Marshmallow, may also be able to have settings applied to them, which is a careful way of saying results vary. Chromebooks are covered separately: supervision runs on Chrome OS version 71 or higher when a child signs in with their own account.

On the parent side, the same page states that parents can run Family Link on Android devices running 7.0 and higher, and on iPhones running iOS 16 and higher. That is the whole list of devices. There is no Mac entry, no Windows entry, and no mention of a desktop client anywhere in the site navigation, which runs Overview, Device Compatibility, FAQ and Sign in.

It is worth noticing that Google's own pages disagree slightly with each other on the iPhone number. The FAQ answers the question about iOS by saying parents can run Family Link on iPhones running iOS 11 and higher, while the compatibility page says iOS 16. The App Store listing, which is the one that governs whether the download actually happens, is stricter than both. When three Google pages give three numbers, the App Store listing is the one that decides.

None of this is a criticism of the product. It is a reminder that a feature page and a store listing are maintained by different teams on different schedules, and the store listing is the one enforced by software.

Why the iPhone app will not install on a Mac

Apple Silicon Macs can install some iPhone and iPad apps directly from the Mac App Store, which makes the question reasonable rather than naive. Whether a particular app appears there is not a technical question about the Mac. It is a flag the developer sets, and the App Store listing shows the result.

The Google Family Link listing, published by Google LLC, records its compatibility as requiring iOS 17.0 or later, with iPad requiring iPadOS 17.0 or later. There is no Mac line. There is no Apple Vision line either. The listing also shows a download of 207.2 MB, a Utilities category, a 4+ age rating, and localisation into English and 55 more languages.

How to read that section on any store page

This check takes a few seconds and saves a lot of searching. On an App Store page, the Compatibility block lists every device family the developer has enabled. An iOS app that a Mac can install shows a line reading that it requires a given version of macOS and a Mac with an Apple M1 chip or later. If that line is absent, searching the Mac App Store will not turn the app up, no matter how recent the machine is.

Family Link has no such line, so the answer is settled. That also disposes of the emulator suggestions, which propose installing Android on a Mac in order to install a parental control app inside it. The complexity is real, the maintenance burden is real, and the whole exercise is unnecessary given what Google already provides in a browser.

The browser route is the one Google points at

Google's FAQ answers this directly. Asked whether parents can use Family Link on a web browser, the answer given is that parents can manage pretty much all of their child's account settings and features on a web browser, with no app download needed. The same point appears at the bottom of both the FAQ and the compatibility pages, phrased as a note for anyone without a smartphone: supervision can be set up online.

That changes the shape of the decision. There is nothing to install, so the question is not which app to get. The question is whether a dashboard that gets opened at breakfast, after school and at bedtime deserves an icon and a window of its own, or whether it should stay a tab that gets lost behind email.

The phrase "pretty much all" is doing some work in that sentence, and it is worth respecting rather than glossing over. Google does not publish a feature by feature comparison between the app and the browser, so the honest way to find out whether a specific control is present for a specific account is to sign in and look. Screen time limits, app approvals, content filters and location are the four things most parents open Family Link for, and checking them in that order takes a couple of minutes.

Where supervision itself stops, regardless of the window

One limit has nothing to do with Macs and everything to do with expectations, so it belongs here. Google's FAQ states that children or teens signed into iOS devices, web browsers or other unsupervised devices can only be partially supervised. Settings for YouTube and Google Search continue to apply when the child is signed in and using Google apps and services. Other features, including managing which apps the child can use, filtering what they see in Chrome, and setting screen time limits, do not apply to activity on an iOS device or on the web.

The same FAQ is equally direct about filtering in general. Family Link does not block inappropriate content, it provides filtering options, and Google states plainly that those filters are not perfect and that explicit or graphic material makes it through sometimes.

Two smaller facts round out the picture. An account issued by a school or a workplace cannot be used to manage a family group or to supervise anyone, so a personal Google account is required. And Google suggests budgeting about fifteen minutes to set up a child's account and Android device, which is a useful number for anyone deciding whether to start the job now or after dinner.

Three ways to give the dashboard a window

Route	Requirement	Session	Icon and name
Safari, Add to Dock	macOS Sonoma 14 or later	Separate from Safari	Set at creation, editable later
Chrome, Install page as app	Any recent Chrome	Shared with the Chrome profile	Managed by Chrome
A site to app tool	Varies by tool	Separate for each app	Set freely

Apple documents the Safari route in its support article on web apps, updated in May 2026. From macOS Sonoma 14 onward, choosing File and then Add to Dock in Safari, or using the Share button and then Add to Dock, saves the page as a web app. It lands in the Applications folder inside the home folder rather than the system one, so no administrator password is involved, and it opens from the Dock or from Spotlight. Apple states that it functions independently of Safari and shares no browsing history, cookies, website data or settings with it.

That isolation is the interesting part for this particular dashboard. A parent account signed in inside a separate window is not the same session as the browser, which means a child borrowing the Mac and opening Safari does not find the supervision console already unlocked in a tab.

Chrome's route installs the page as an app belonging to the Chrome profile that created it, so an existing signed in session carries over. That saves a sign-in and costs the isolation. The third route exists because the first two make one window at a time through a menu, and households rarely stop at one. Supported services lists the kinds of sites that most often end up handled this way, and a family dashboard behaves like the rest of them.

Build the window on the page that gets opened

The instinct is to point the window at the sign-in page. A better result comes from pointing it at the screen where the recurring task starts, because almost nobody opens a parental control dashboard for a general look around.

Three tasks recur. Approving an app request, usually within minutes of being asked. Extending or cutting screen time for the evening. Checking where a phone is. Those are different screens with different urgencies, and a window named for the task is findable in the application switcher in a way that a window named for the brand is not.

Apple's settings panel makes a wrong starting page cheap to fix. Opening the web app, clicking its name in the menu bar and choosing Settings exposes an Application Name field, an Application URL field with a Set to Current Page button, and an Icon picker that accepts any image. Navigate to the right screen, press Set to Current Page, and the window opens there from then on. The same panel carries a Privacy tab that clears the site's stored data including cookies and caches, which is the correct way to sign a window out completely, and an Extensions tab for enabling or disabling Safari extensions inside it. The Guide covers how those settings interact once more than one window exists on a machine.

What to verify before relying on it

Notifications need attention, and Apple's rule is specific. For an unread count to show as a red badge on the Dock icon, the site's notification request has to be answered inside the web app rather than in Safari. A permission granted in the browser earlier does not carry across. Once answered in the right place, the entry appears in Notifications settings listed under the web app's name rather than the website's address.

Link routing is the second thing, and it surprises people. A supervision link arriving by email or message opens in whatever browser macOS is set to use, not in the new window, because that is an operating system rule rather than a setting inside the window. Keeping the browser signed in to the same parent account avoids a confusing moment at exactly the point when speed matters, which is usually an app request.

The third check is the one that decides whether any of this is worth doing. Sign in to the browser dashboard and walk through the controls actually used in that household, not the full feature list. If screen time, app approvals, filters and location are all present and behave the way the phone does, a window is a genuine improvement. If a needed control turns out to live only in the phone app, the phone stays in the loop and the window handles the rest. Five minutes of looking answers it, and reasoning about it does not.

What to change first

Open the browser dashboard, confirm the controls that get used are all there, then build one window on the single screen opened most often and name it for the task rather than the brand. Keep the phone for anything that has to be answered while out of the house. If one window turns into several, a tool such as Kagemusha keeps them consistent instead of rebuilt by hand each time.