Comparison
Pick WakaTime if you want coding time broken down by project, language and editor, plus AI tool usage across Claude Code, Cursor, Copilot and Codex. Pick Timing if you need everything on the Mac tracked, stored locally, and turned into billable-hour reports. Dayflow, our free open-source app, fits developers who want an AI-written timeline of the whole day without paying.
WakaTime measures coding: open source plugins inside your editors and terminals record time per project, language and editor, plus AI tool usage, and send it all to a hosted dashboard. Timing measures the whole Mac: every app, website and document, stored locally by default, with reports built to turn hours into billable records.
Disclosure: Dayflow, the third option in this article, is our product. It’s a free, MIT-licensed Mac app that records the screen at one frame every 10 seconds and has AI write the day into a readable timeline. If you are mostly weighing Timing against Dayflow, our Timing alternative page covers that directly. For the wider field, see our list of the best time tracker for Mac options.
Method: this is a comparison of vendor documentation. WakaTime and Timing facts come from their own pages as checked on October 4, 2026. Dayflow facts come from our published product details for version 2.2.0. Nothing below is based on benchmarks or hands-on trials.
| Tool | Best for | How it tracks | Price | Platforms |
|---|---|---|---|---|
| WakaTime | Coding time and AI usage metrics per project, language and editor | Editor and terminal plugins send activity to a web dashboard | Free plan; Basic $9/mo monthly or $99/yr; Premium $14/mo monthly or $153.96/yr; Team and Business per dev | 100+ editors, IDEs and terminals via plugins; web dashboard |
| Timing | Whole-Mac tracking and billable hours | Automatic tracking of apps, websites and documents, plus manual entries | Professional $9/mo billed annually or $11/mo monthly; Expert $11/mo annually or $14/mo monthly; Connect per user | Mac |
| Dayflow (ours) | A readable AI-written record of the whole workday | Screen recording at one frame every 10 seconds, analyzed by AI into a timeline | $0, MIT licensed; optional Pro $20/month | Mac (macOS 14+) |
It understands code. WakaTime’s plugins sit inside the editor, so they know which project you have open, which language you are writing and which editor you are in. Its dashboard breaks time down along exactly those lines. Timing sees that Xcode or VS Code was in front of you; WakaTime sees that you spent the afternoon writing Rust in one repository.
It tracks AI coding tools. This is the clearest point of separation in 2026. WakaTime lists AI adoption tracking, model usage and spend, and a split between AI-generated and human-written lines, across tools such as Claude Code, Cursor, Copilot and Codex. If you want to know how much of your week was spent prompting an agent versus typing, or what that agent cost, WakaTime is the only one of the three that documents it.
It meets you in more places. Plugins cover more than 100 editors, IDEs and terminals. If you move between a terminal, a JetBrains IDE and a code editor, coverage follows you through each, as long as a plugin exists.
It has developer-shaped motivation features. Programming goals and private leaderboards are listed features. The free plan includes 1 programming goal. Timing and Dayflow have nothing equivalent.
It has team coding dashboards. The Team and Business plans add team dashboards, aimed at team leads and decision makers who want coding-time and AI-usage numbers across a group. There’s a 14-day trial on the Team plan with no credit card required.
It costs nothing to start. The free plan gives unlimited projects. The catch is history: the dashboard keeps 1 week, and full history requires Premium.
It sees the whole Mac. Timing records time automatically across apps, websites and documents, down to specific URLs and Mail threads. For a developer, that matters because much of the job happens outside the editor: reading docs, reviewing pull requests in a browser, answering questions in chat, sitting in calls. WakaTime only captures activity inside supported editors and terminals, so all of that is invisible to it.
It keeps data on the Mac by default. Timing says tracked times are stored locally and never leave your Mac unless you opt into sync. Sync and cloud backup are listed on all plans, but they are optional. WakaTime, by design, sends activity to its hosted dashboard, and its pages don’t say where that server lives.
It is built for billable hours. Timing lists billing status tracking, customizable reports with rounding, and integrations including two-way ClickUp, Linear and Clio sync and a GrandTotal invoicing integration, with availability depending on plan. A freelance developer who bills by the hour can go from raw activity to a client-ready record in one app. Our guide on how to track billable hours on a Mac walks through that workflow in more detail.
It adds AI summaries on top of tracking. Timing lists AI activity summaries and an MCP integration on all plans, plus AI-powered suggestions for time entries. WakaTime’s AI features measure AI coding tools; Timing’s AI features help describe your own time.
It has manual entries and extra inputs. Manual time entries, iOS activity import and call tracking are listed, which helps fill gaps the automatic tracker cannot see.
It is scriptable. Scripting, a Web API and Zapier are listed, depending on plan, which suits developers who want to pipe time data into their own tools.
| Capability | WakaTime | Timing | Dayflow (ours) |
|---|---|---|---|
| Automatic capture | Yes, inside supported editors and terminals | Yes, apps, websites and documents across the Mac | Yes, screen recorded at one frame every 10 seconds |
| Coding metrics (project, language, editor) | Yes | Not listed | No |
| Manual time entries | Not listed | Yes | Not a timer app; recording is automatic |
| Invoicing | Not listed | GrandTotal invoicing integration and billing status (plan dependent) | No |
| Team reports | Team dashboards on Team and Business | Shared projects and team collaboration on Connect | No |
| Website blocking | Not listed | Not listed | No |
| AI features | Tracks AI coding usage, model usage and spend | AI activity summaries, MCP integration, AI suggestions for entries | AI writes the day into a timeline; local AI, your own provider or Pro |
| Data location | Cloud dashboard; server location not stated | Local, with optional sync | Recordings and timeline on your Mac; analysis local or cloud depending on mode |
| Free tier | Yes, 1 week of history, unlimited projects, 1 goal | None; 30-day trial | Yes, $0 for the full app |
| Platforms | 100+ editors, IDEs and terminals; web dashboard | Mac | Mac, macOS 14 or later |
| Open source | Plugins yes, hosted service no | No | Yes, MIT |
| Tool | Plan | Listed price |
|---|---|---|
| WakaTime | Free | $0 |
| WakaTime | Basic | $9/mo billed monthly, or $8.25/mo billed $99 yearly |
| WakaTime | Premium | $14/mo billed monthly, or $12.83/mo billed $153.96 yearly |
| WakaTime | Team | $21/dev/mo billed monthly, or $19.25/dev/mo billed $231/dev yearly |
| WakaTime | Business | $24/dev/mo billed monthly, or $22/dev/mo billed $264/dev yearly |
| Timing | Professional | $9 per month billed annually, or $11 per month billed monthly |
| Timing | Expert | $11 per month billed annually, or $14 per month billed monthly |
| Timing | Connect | $16 per user per month billed annually, or $20 per user per month billed monthly |
| Dayflow | Free | $0 |
| Dayflow | Pro (optional) | $20 per month |
What one developer actually pays depends on what “fits the job” means.
For WakaTime, the free plan works if you only care about the current week. If you want your coding history to stick around, the pages read say full history requires Premium: $153.96 a year billed yearly, or $168 a year if you pay $14 monthly. Basic costs $99 a year billed yearly, or $108 paid monthly, but the facts we checked don’t spell out how much history Basic keeps, so see the vendor’s pricing page before choosing it.
For Timing, the cheapest plan is Professional at $108 a year billed annually, or $132 a year paid monthly. Professional covers 1 Mac and has limited web app access. If you work across two Macs or need integrations that are plan dependent, Expert costs $132 a year billed annually or $168 a year paid monthly. Timing notes that prices may vary by region or tax.
Dayflow is $0. If you use your own AI provider, that provider’s charges apply, since the free app does not include paid API usage. Local AI through Ollama or LM Studio costs nothing beyond your own hardware. If you choose Dayflow Pro for managed cloud analysis, that’s $240 a year at $20 a month.
If you want to see what your hours are worth before paying for a tracker, the real hourly rate calculator does that math.
For more options in the same space, our best time trackers for developers on Mac roundup covers a wider set, and Timing vs Rize compares Timing with another automatic tracker.
WakaTime has an obvious blind spot: anything outside a supported editor or terminal. Code review in a browser, a design discussion on a call, an hour reading an RFC, debugging a production issue from a dashboard. For many developers, that is a large share of the week, and WakaTime simply does not see it.
Timing covers that ground at the level of apps, URLs and documents. What it records is where you were. A Mail thread name or a URL often tells you a lot, but a block like “Browser, 45 minutes” may still leave you reconstructing what you actually did.
Then there’s cost and openness. WakaTime’s free plan keeps only a week of history, and its hosted service is not open source. Timing has no free tier at all and is not open source.
Dayflow is aimed at that gap. It records the screen at one frame every 10 seconds, and AI turns that into a readable timeline of the whole day, editor and everything else. Recordings and the timeline stay on your Mac. With local AI, screenshot analysis stays on-device; with your own provider or Dayflow Pro, selected screenshots are processed off-device, and our local and cloud processing page explains each boundary. You can export a date range as Markdown from Settings, which makes it useful for automatic standup updates or feeding into a Codex work summary. The app is $0 and MIT licensed.
That fills the “what did I actually do all day” gap. It does not fill WakaTime’s coding-metrics role or Timing’s billing role, and AI summaries can miss or misread work, so check them before you share anything. If you want a rough sense of how your week splits before choosing any tool, try the where does my week go calculator.
Dayflow is the wrong choice in several common developer situations, and in each one a tool covered here does the job better.
If your own needs are closer to staying on task than measuring output, our piece on ADHD programmers staying on task may be more useful than any tracker comparison.
These two tools answer different questions, so the choice is usually easy once you know which question is yours.
Choose WakaTime if you want numbers about coding: time per project, language and editor, plus how much you rely on Claude Code, Cursor, Copilot or Codex. Start on the free plan and move to Premium if you want history beyond a week.
Choose Timing if you need the whole Mac tracked and turned into billable records, with data local by default. Use the 30-day trial and expect at least $108 a year on Professional billed annually.
Choose Dayflow, our app, if you want a free, open-source record of the entire workday written as a timeline, and you don’t need coding stats, invoicing or team reports. You can read more about how it works on the product details page.
Yes, WakaTime has a Free plan at $0 with unlimited projects and 1 programming goal, but the dashboard keeps only 1 week of history. Full history requires Premium, which is $14 a month billed monthly or $153.96 billed yearly. A Basic plan sits between them at $9 a month, or $99 billed yearly. The paid plans add longer-term records on top of the free tier.
No. Timing is subscription only and has no free tier. It offers a 30-day trial with no credit card required. After that, the cheapest plan is Professional at $9 a month billed annually or $11 billed monthly. Professional covers 1 Mac and has limited web app access, so check whether it fits before the trial ends.
WakaTime only captures activity inside supported editors, IDEs and terminals, through plugins for more than 100 of them. Time in a browser reading docs, in Slack, in email or in a video call does not show up in its dashboard. If you need that wider picture, an app that tracks the whole Mac, such as Timing or Dayflow, covers it instead.
Timing's documented tracking works at the level of apps, websites and documents on the Mac, down to specific URLs and Mail threads. Per-language and per-editor coding metrics are not among its listed features. That breakdown is WakaTime's core job, so a developer who wants language and editor stats should look at WakaTime rather than expect Timing to provide them.
Yes. WakaTime lists AI coding usage tracking across tools such as Claude Code, Cursor, Copilot and Codex. Its pages describe AI adoption, model usage and spend, and a split between AI-generated and human-written lines. Neither Timing nor Dayflow lists anything comparable, so if measuring AI coding tools is the goal, WakaTime is the one to use.
Timing, and it beats Dayflow here too. Timing lists billing status tracking, customizable reports with rounding, two-way ClickUp, Linear and Clio sync, and a GrandTotal invoicing integration, depending on plan. Dayflow has no invoicing or billing features at all, and WakaTime is built around coding metrics rather than client billing. Freelance developers who invoice by the hour should start with Timing's 30-day trial.
WakaTime plugins send coding activity to its hosted cloud dashboard, and its pages do not state the server location. Timing says tracked times stay on your Mac unless you opt into sync, which all plans list. Dayflow stores recordings and the timeline on your Mac, and analysis can stay on-device with local AI or go to your own provider or Dayflow Pro.
Not for coding metrics. WakaTime gives per-project, per-language and per-editor numbers, programming goals, leaderboards and AI usage tracking, none of which Dayflow offers. Dayflow does something different: it records the whole screen at one frame every 10 seconds and has AI write a readable timeline of the day, which helps with standups and recall rather than coding stats.
They measure different layers, so they do not overlap much: WakaTime runs as plugins inside your editors, while Timing tracks apps and websites across the Mac. Neither vendor's pages we read describe an integration between them, so you would get two separate dashboards. Running both also means paying for both if you need more than WakaTime's 1 week of free history.
No. Dayflow requires macOS 14 or later and runs only on Mac. If your machine is on an older macOS release, Dayflow will not install. WakaTime works through editor and terminal plugins rather than a standalone Mac app, so it depends on your editor's support instead. Check Timing's site for its own system requirements.
Dayflow is $0 and open source. Full recordings stay on your Mac, with local AI available for on-device analysis.
Download for MacOS macOS 14+ · MIT licensed · no account required