Sunlight behind a frosted, frozen window — something is there, but you can't see it clearly.

Photo by Sarazhizmailov on Pexels

screen-timechromebrowsersmac

Screen Time Doesn't Track Chrome on Mac. Here's How to Actually See Your Browser Usage

macOS Screen Time can break down the sites you visit in Safari. In Chrome, Arc, Brave, Firefox, and Edge it's silent. Here's why that happens and the one way around it that actually works.

Mike5 min read

Screen Time Doesn't Track Chrome on Mac. Here's How to Actually See Your Browser Usage

Open Screen Time on your Mac. Scroll to Chrome. You'll see one line: Chrome — 4h 12m. That's it. No breakdown of which sites. No split between docs.google.com and reddit. No per-tab anything.

Do the same for Safari and you'll see a full list of domains, with time spent on each. Why the difference? And what can you do about it?

Short answer: Apple gives Screen Time privileged access to Safari's tab data that it does not give to any other browser. To see Chrome (or Arc, Brave, Firefox, Edge) at the same level of detail, you have to go outside Screen Time. Here's how.

Why Screen Time can see Safari but not Chrome

Screen Time was originally a parental-controls feature. Its entire job is "tell the parent what apps and sites the kid used." Apple owns Safari, so it built Safari to report tab-level data into Screen Time automatically. It's a first-party integration, no permissions required, no extensions needed.

For any other browser, the same integration would require that browser to either:

  1. Use a private macOS API that Apple reserves for Safari — which it can't, because that API isn't public.
  2. Voluntarily report its history to Screen Time via some Apple-provided hook — which doesn't exist.
  3. Run a persistent background process that reports tab changes — which would raise all sorts of privacy and UX flags.

So Chrome doesn't report anything, Arc doesn't report anything, and Firefox doesn't report anything. Screen Time sees Chrome as one opaque app that was frontmost for 4h 12m. Whether that was four hours of Figma (via Figma-in-Chrome) or four hours of Reddit, Screen Time has no idea.

What this means if you actually use Chrome

In practice, the people most affected by this are:

  • Developers who live in GitHub, Linear, and localhost on Chrome or Arc.
  • Designers who use Figma's web app.
  • Operators and PMs whose whole day is Notion, Google Docs, Airtable, and Slack web.
  • Writers and researchers with Arc as their main browser.

For these folks, Screen Time's bottom line is literally useless. The only data point it produces — "Chrome: 4 hours" — aggregates across work and distraction so completely that you can't act on it.

Two things people try that don't really work

Chrome's built-in "Time spent" dashboard. Chrome has a small usage feature buried in its settings. It's unreliable, doesn't survive a profile wipe, and breaks if you use more than one Chrome profile, which most professional users do. The data lives in Chrome, not your Mac, so it disappears when you uninstall. Don't rely on it.

Browser extensions like Webtime Tracker or RescueTime's Chrome extension. These work within one browser. But if you also use Safari for banking, or Arc for personal browsing, the extension doesn't know. You end up with three separate partial records that you'd have to manually merge. On top of that, many of these extensions ship your full browsing history to a cloud server for analysis. That's a lot of data to trade for a bar chart.

If you're all-in on one browser and fine with the extension's privacy trade-off, the extension route works. For most people, neither condition holds.

The one method that actually works: Automation permission

macOS has a permission called Automation that lets one app ask another app about its state via AppleScript. Granting Automation permission from Focus Meter (or Timing, or RescueTime's desktop app) to Chrome lets that tracker periodically ask Chrome: "what's the URL of your frontmost tab?"

Chrome replies, the tracker records it, and moves on. Same mechanism works with Arc, Brave, Edge, and Firefox (via a slightly different mechanism for the Gecko engine).

What you get:

  • Site-level time for every browser, not just Safari.
  • Cross-browser aggregation: docs.google.com from Chrome + Arc shows up as one number.
  • Local data: a well-built tracker stores everything on your Mac, unlike extension-based trackers.
  • Granular categorization: you can tag github.com as productive while leaving youtube.com as distracting — even though both live inside Chrome.

The trade-off is a one-time permission grant per browser. macOS will prompt you the first time the tracker tries to read each browser's tab, and you click Allow. You'll see this in System Settings → Privacy & Security → Automation, where each browser is listed with the apps that can query it.

A three-minute setup

If you want this working in under five minutes:

  1. Install Focus Meter from the Mac App Store.
  2. Open Settings → Privacy and turn on Browser URL Tracking.
  3. Browse to Chrome. macOS prompts for Automation permission. Click Allow.
  4. Repeat for each browser you actually use (Arc, Safari, Firefox, etc.).
  5. Use your Mac normally.
  6. Open Reports → Websites after a day. The list is sorted by time spent, across every browser.

From that point on, "Chrome: 4h 12m" becomes "docs.google.com: 1h 52m, github.com: 47m, reddit.com: 31m, gmail.com: 18m, (64 other domains)." That's the level of detail that actually changes decisions.

What about Firefox?

Firefox is slightly different because it doesn't speak the same AppleScript dialect as Chromium-based browsers. Focus Meter supports it through the same UI, but the first time you launch the browser after installing the tracker you'll see a Firefox-specific permission prompt. Once granted, it works the same way.

What about private / incognito browsing?

A reasonable default: don't track it. Focus Meter has Ignore Incognito / Private Browsing turned on by default. Your banking, medical searches, and everything else you went incognito for stays out of the database entirely. Turning it off is an explicit choice, not the default.

The short version

  • Screen Time's site-level data is Safari-only because Apple gave Safari a private integration.
  • Chrome's built-in time feature and most extensions are patchy, profile-dependent, or cloud-dependent.
  • A native macOS tracker with Automation permission is the one method that gives you real, local, cross-browser URL data.
  • Granting the permission takes about a minute per browser. Setup is one-time; the data compounds from there.