How To Track Your Browser Usage on Mac: Arc, Chrome, and Safari
The browser is where Mac productivity data goes to die.
If your tracker says "Chrome: 5h 12m," you still do not know what happened. Chrome could be work. Chrome could be research. Chrome could be YouTube. Chrome could be three hours of GitHub review and two hours of news tabs you opened between builds.
App-level browser time is almost never enough.
What you want is website-level time: GitHub separate from Google Docs, Google Docs separate from Reddit, Reddit separate from YouTube. That is the difference between screen time and focus tracking. The complete guide to focus tracking on Mac explains how website data fits into the larger system.
Why browser tracking is different
Most apps map cleanly to a rough category. VS Code is usually productive. Slack is usually neutral. Spotify is usually background or neutral. A browser is different because it is a container for everything.
One process name can contain:
- Work docs
- Code review
- Admin dashboards
- Social media
- Video
- Shopping
- News
- Research
That is why Apple's Screen Time feels so weak for professionals. It can show browser time, but it rarely explains browser time. If you use Chrome or Arc heavily, the gap gets worse.
Chrome
Chrome is the most important browser to track because so much work lives in it. Google Docs, GitHub, Linear, Notion, analytics dashboards, and internal tools all appear as Chrome unless your tracker reads the active URL.
Focus Meter uses macOS Automation to read the active tab URL from Chrome. There is no extension. The browser does not need to send anything to Focus Meter's servers because there are no servers involved. The active domain is stored locally on your Mac.
The Chrome tracking page has the detailed breakdown, including sample weekly numbers and caveats.
Arc
Arc is built around workspaces, profiles, and pinned tabs. That makes it feel organized, but it can hide the same problem: everything is still inside one browser.
If Arc is open for six hours, you need to know whether that time went to docs, code review, research, or distraction. Focus Meter treats Arc similarly to Chrome for URL-level tracking because Arc is Chromium-based and exposes active tab data through macOS automation.
The practical review is the same: do not ask "how long was Arc open?" Ask "which domains inside Arc got the time?"
Safari
Safari has the strongest native privacy story, and Screen Time handles Safari better than it handles third-party browsers. But the default view still tends to be too coarse for work.
Focus Meter can read Safari's active URL with macOS Automation permission. That lets you categorize domains the same way you would in Chrome: docs as productive, Reddit as distracting, email as neutral, and so on.
Safari-first users usually care about privacy. That is exactly why browser data should stay local. Focus Meter does not need an account or cloud processing to build a useful website report.
Firefox
Firefox is more limited on macOS automation. Focus Meter can still track Firefox as an app, but URL-level tracking may not be as complete as Chrome, Safari, or Arc.
That does not make Firefox unusable. It just means the data may be coarser. If you need exact domain-level breakdowns, use one of the browsers with better macOS automation support for your work profile.
The category pass that matters
After one day of browser tracking, review your top domains and categorize only the ones that matter. The app and website tracking hub has examples of how common domains and apps are usually treated.
| Domain type | Suggested category |
|---|---|
| GitHub, Linear, docs, API docs | Productive |
| Gmail, Slack web, admin dashboards | Neutral |
| YouTube, Reddit, X, news | Distracting |
| Unknown internal tools | Decide after a week |
Do not spend an hour categorizing every domain. Your top ten will explain most of the week.
The browser report to review every Friday
At the end of the week, look at four numbers:
- Total browser time.
- Productive browser time.
- Distracting browser time.
- Uncategorized browser time.
The first number is least important. The split is what matters.
If total browser time is high but productive browser time is also high, your work probably lives on the web. If total browser time is high and distracting time is climbing, you have a focus problem. If uncategorized time is high, your categories are not telling the truth yet.
Screen Time cannot do this well enough
Screen Time is fine for a rough household view. It is not built for someone whose entire job happens inside a browser.
A useful browser tracker needs:
- Domain-level tracking
- Custom categories
- Idle detection
- Weekly trends
- Local storage
- No extension requirement
That is why browser tracking is one of Focus Meter's core jobs. Without it, your report will always overstate the app and understate the behavior. For older Screen Time context, read why Screen Time does not track Chrome.
Start with Chrome, then use the settings guide to tune website categories after a real day of data.