Comparison
Timing vs Tracker: two automatic time trackers for Mac, compared
If you have already decided that timers are not for you, the shortlist of automatic Mac time trackers is short, and Timing is on it. It has been doing this for years, and it does it well. This is a comparison written by the people building the other one, so read it with that in mind — the facts below are the ones you can verify yourself.
What the two have in common
Both are Mac apps that record what you do without you starting anything. Both watch the frontmost application, the document or window title, and the website you are on, and both turn that stream into hours you can report on. Neither asks you to press start.
If you only need “automatic instead of manual”, either one solves your problem.
Where they differ
Maturity
Timing is an established, actively developed product with a long release history, a large feature surface, and years of accumulated handling for the awkward cases. Tracker is in early access and not released yet.
That is the single most important line in this article. If you need a time tracker on your Mac this week, Timing is the one that exists.
Where the data lives
Timing is a Mac app with cloud sync available in its higher tiers, which is what lets your timeline follow you between machines.
Tracker has no cloud component at all. The entire backend is a SQLite file on your disk. There is no account to create, no server to sign in to, and nothing to sync — which is a feature if your window titles carry client names under an NDA, and a limitation if you work on a desktop and a laptop. The reasoning is spelled out in why your time tracker should be local-only.
How work becomes a client
This is the real design difference.
Timing captures a rich, detailed timeline of everything, and gives you a large toolkit for slicing that timeline into projects afterwards. It is a powerful model, and the detail is genuinely useful when you want to know where your week went.
Tracker starts from the other end. You write one or two rules per client up front — a URL pattern or a window-title pattern — and every sample is filed as it arrives. github.com/acme is Acme. A window title containing Northwind is Northwind. Anything matching no rule stays neutral until you decide.
The trade-off is direct. Rules mean less to review later, because the classification already happened; they also mean you get out what you put in, and a badly written rule quietly mislabels a week. A rich timeline means more to review, and more to discover.
Idle time
Both address the problem of walking away from a running machine. Tracker’s approach is to cut the gap out of the day entirely, so the exported CSV contains keyboard time rather than wall-clock time.
How you pay
Timing is sold as a subscription, with the sync and higher-end features in the upper tiers.
Tracker is free during early access and a one-time license after launch. That is not a claim to be cheaper — a one-time license and a subscription are different bets, not different prices. It follows from the architecture: there is no server to keep running on your behalf, so there is nothing to rent.
Footprint
Tracker is a Rust and Tauri menu-bar app. It has no dock icon and no main window competing for space; you open the menu bar when you want a number and close it again.
An honest recommendation
Choose Timing if you want the mature option, if you want a detailed timeline you can explore and re-slice after the fact, if you move between two Macs, or if you need something available today.
Choose Tracker if the deciding factor is that client data never leaves your machine, if you would rather define a few rules once than review a timeline every week, if you prefer buying software to renting it, and if you are comfortable waiting for an early-access app to mature.
There is no version of this comparison where one tool is wrong. They optimise for different anxieties: Timing for “I want to see everything I did”, Tracker for “I want the hours filed correctly and nothing about my clients on someone else’s disk”.
If you are still deciding between automatic and timer-based tracking in the first place, the Toggl comparison covers that fork, and the FAQ answers the short questions about how Tracker handles clients, exports and storage.
Summarize withChatGPTClaudePerplexity