Comparison
For tracking coding time itself, WakaTime is the better pick. Its editor plugins record time automatically and break it down by project, language and editor, with AI-tool usage on top. Toggl wins when coding hours have to become billable rates, profitability reports or approved team timesheets. Dayflow, our free Mac app, fits when you want the whole workday recorded, not just editor time.
WakaTime and Toggl answer different questions about the same hours. WakaTime counts coding time automatically through plugins inside your editor and breaks it down by project, language and editor. Toggl (formerly Toggl Track) counts whatever you run a timer or log a timesheet entry against, then turns those hours into billable rates and team reports. If you mainly care about Toggl’s desktop side, our Toggl for Mac comparison goes deeper.
Disclosure: Dayflow, the third tool in the tables below, 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. The method here is a comparison of each vendor’s own documentation as checked on October 4, 2026, plus Dayflow’s published facts for version 2.2.0.
| Tool | Best for | How it tracks | Price | Platforms |
|---|---|---|---|---|
| WakaTime | Developers who want coding metrics by project, language and editor, plus AI tool usage | Automatically, through open source editor plugins that send activity to a web dashboard | Free plan; Basic $9/mo billed monthly or $99/yr billed yearly | 100+ editors, IDEs and terminals via plugins; web dashboard |
| Toggl (formerly Toggl Track) | Freelancers and teams who bill for development hours | Manual and real-time timers, timesheets, calendar integrations; vendor also lists automated background tracking in the desktop app | Free for up to 3 users; Starter $9/user/mo billed annually or $12/user/mo billed monthly | Web, Mac, Windows, iOS, Android, browser extensions |
| Dayflow (ours) | Mac users who want a record of the whole workday, not only editor time | Screen capture at one frame every 10 seconds, with AI writing a timeline | $0, MIT licensed; optional Pro $20/mo | macOS 14 or later |
You install a plugin in your editor and it records coding time per project, language and editor, then sends it to WakaTime’s web dashboard. There’s no start button to forget and no end-of-day reconstruction. For developers who already know they won’t keep a timer running through a context switch, this is the whole argument.
WakaTime’s reports are built around the units a programmer thinks in: projects, languages and editors. On top of that sit programming goals and private leaderboards. The free plan includes unlimited projects and 1 programming goal, so you can try the model on real work before paying.
This is the feature Toggl doesn’t attempt. WakaTime tracks AI adoption, model usage and spend, and AI-generated versus human-written lines across tools such as Claude Code, Cursor, Copilot and Codex. If you want to know how much of a week’s code came from an assistant, or what that assistant cost, WakaTime is the only tool of the three that lists it.
The vendor lists plugins for 100+ editors, IDEs and terminals. That means coverage depends on whether your editor is supported, not on which desktop app you happened to install. Switching from one IDE to another usually means installing another plugin rather than changing trackers.
The Team and Business plans add team dashboards, and the Team plan has a 14-day trial with no credit card required. For a lead who wants coding and AI-usage metrics across a group, that’s a closer fit than a general-purpose timesheet.
Toggl is built for people who invoice or report on time. Paid plans add billable rates, and Premium adds profitability reports and timesheet approvals. The vendor pages read for WakaTime don’t list billing features at all. If you’re a contract developer, Toggl gets you much closer to a client-ready number. Our guide on how to track billable hours on a Mac covers that workflow in more detail.
A developer’s day includes code review in a browser, standups, spec writing, debugging sessions spent reading logs, and planning calls. WakaTime only sees the editor and terminal. A Toggl timer can be started against any of those, and calendar integrations sit next to the timer for meeting-heavy days.
Premium includes Jira and Asana integrations. If your hours have to line up with tickets for a client or a sprint report, that matters more than language breakdowns.
Toggl now combines time tracking with planning: timelines, tasks and capacity management. The free plan already includes tasks and boards alongside timers, focus mode and calendar integrations.
Toggl runs on the web, Mac, Windows, iOS and Android, plus browser extensions, so you can log time from a phone after a client call. The vendor states that it does not take screenshots or record keystrokes. Toggl AI also answers natural-language questions about workspace data, and the vendor lists an MCP server and an AI Task Creator.
It depends on what you mean by coding time.
WakaTime measures. Its plugins record activity in the editor and terminal, so the number doesn’t depend on your memory. The catch is its definition: coding equals time in a supported editor or terminal. Reading documentation, reviewing a pull request on the web or sketching an architecture on paper doesn’t count.
Toggl records what you declared. A timer captures intent, and it can cover non-editor work, but it’s only as good as your habit of starting and stopping it. The vendor lists automated background tracking and a timeline in the desktop app, yet the product is presented primarily as timers and manual entry rather than a full automatic record.
If you rely on estimates to fill gaps in a timesheet, the time estimation test is a short exercise that compares your sense of time with a clock. It’s not a diagnostic, but it shows how far a guess can drift.
| Capability | WakaTime | Toggl | Dayflow (ours) |
|---|---|---|---|
| Automatic capture | Yes, inside supported editors and terminals | Vendor lists automated background tracking and a timeline in the desktop app; primarily timers and manual entry | Yes, whole screen at one frame every 10 seconds |
| Timers | Not the model; tracking is plugin-based | Manual and real-time timers, timesheets | Not the model; capture runs in the background |
| Coding metrics by project, language and editor | Yes | Not listed | No |
| Invoicing and billing | Not listed; see the vendor’s pricing page | Billable rates on paid plans; for invoicing, see the vendor’s pricing page | No invoicing |
| Team reports | Team dashboards on Team and Business | Team reports; timesheet approvals and profitability reports on Premium | No |
| Website blocking | Not listed | Not listed; free plan includes a focus mode | No |
| AI features | Tracks AI adoption, model usage and spend, AI vs human lines | Toggl AI for workspace questions, MCP server, AI Task Creator | AI writes the timeline via local AI, your own provider, or Pro |
| Data location | Cloud; server location not stated | Cloud, synced across web, desktop and mobile | Recordings and timeline on your Mac; analysis local or cloud depending on mode |
| Free tier | 1 week of history, unlimited projects, 1 goal | Free forever for up to 3 users | $0 for the full app |
| Platforms | 100+ editors, IDEs and terminals; web dashboard | Web, Mac, Windows, iOS, Android, browser extensions | macOS 14 or later |
| Open source | Plugins yes, license not confirmed; hosted service no | No | Yes, MIT |
| Tool | Plan | Billed monthly | Billed yearly |
|---|---|---|---|
| WakaTime | Free | $0 | $0 |
| WakaTime | Basic | $9/mo | $99/yr ($8.25/mo) |
| WakaTime | Premium | $14/mo | $153.96/yr ($12.83/mo) |
| WakaTime | Team | $21/dev/mo | $231/dev/yr ($19.25/dev/mo) |
| WakaTime | Business | $24/dev/mo | $264/dev/yr ($22/dev/mo) |
| Toggl | Free | $0 (up to 3 users) | $0 |
| Toggl | Starter | $12/user/mo | $9/user/mo billed annually |
| Toggl | Premium | $24/user/mo | $16/user/mo billed annually |
| Toggl | Enterprise | Contact vendor; see the vendor’s pricing page | Contact vendor |
| Dayflow | Free | $0 | $0 |
| Dayflow | Pro | $20/mo | See Dayflow pricing |
For one developer tracking coding time, here’s what a year costs on the cheapest plan that does the job. WakaTime Free is $0 if a rolling week of history is enough. If you want your full history, that requires Premium: $153.96 a year billed yearly, or $168 a year at $14 a month. Basic sits at $99 a year, but the vendor limits read here only say full history requires Premium, so check WakaTime’s pricing page for what Basic keeps. Toggl Free covers one person’s timers at $0. Once you need billable rates, Starter costs $108 a year billed annually ($9 × 12) or $144 a year billed monthly ($12 × 12). Dayflow is $0 with local AI, or with your own provider (whose charges apply), and $240 a year on Pro.
The trials differ too: 14 days on WakaTime’s Team plan with no credit card, and 30 days on Toggl’s paid plans.
Yes, as two separate records. They measure different things, so running both doesn’t double-count in any meaningful sense: WakaTime tells you what happened in the editor, Toggl tells you what you billed. The vendor documentation reviewed here doesn’t describe an integration between them, so expect to reconcile the two by hand.
The cost can stay at $0 if WakaTime’s one-week history and Toggl’s free plan are enough. The friction is the second habit. Toggl still needs timers, so pairing it with WakaTime doesn’t remove the start-and-stop routine.
The gap is the rest of the workday. WakaTime only captures activity inside supported editors and terminals. Toggl is primarily timers and manual entry, so its record reflects what someone remembered to log. Neither gives you a complete, readable account of a day that moved between an IDE, a browser full of docs, a pull request review and three chat threads.
Two smaller gaps follow from that. Both tools are cloud services, so your activity lives on a vendor’s servers. And neither is fully open source: WakaTime opens its plugins but not the hosted service, and Toggl isn’t open source.
Dayflow covers that gap on a Mac. It records the whole screen at one frame every 10 seconds, stores the recordings and timeline on your Mac, and has AI write a timeline you can read back or export as Markdown. That’s useful for automatic standup updates or for feeding a summary tool, as in the Codex work summary workflow. The source is MIT licensed.
The caveats matter. With local AI, through Ollama or LM Studio, screenshot analysis stays on-device but needs your own hardware. With your own cloud provider or Dayflow Pro, selected screenshots leave your Mac; under the privacy policy Pro deletes screenshots after processing and may retain Activity Data for sync. Our page on local and cloud processing spells out each mode. AI summaries can also miss or misread work, so check them before sharing.
If you’re weighing all the Mac time trackers rather than just these two, our roundup of Mac time trackers and the best time trackers for developers on Mac cover the wider field.
Be direct about this, because for the job in the title Dayflow often isn’t the answer.
For tracking coding time itself, WakaTime is the better tool. It records editor activity automatically, reports it in developer terms, and is the only one of the three that measures AI coding usage. Expect to pay for Premium if you want more than a week of history.
Toggl is the better tool when coding hours are something you sell. Billable rates, approvals, profitability reports and Jira integration matter more than language stats once a client is paying.
Dayflow (ours) is the option for a different question: what did the whole day actually look like, including the parts outside the editor, with the record kept on your Mac. It sits next to WakaTime or Toggl rather than replacing the job either one does best.
No. WakaTime only captures activity inside supported editors, IDEs and terminals, through its open source plugins. Time spent reviewing pull requests in a browser, reading documentation, sitting in meetings or answering chat isn't part of its record. If you want those hours counted, you need a timer-based tool like Toggl or, on a Mac, a whole-screen recorder like Dayflow.
Yes. WakaTime has a free plan with unlimited projects and 1 programming goal, but it keeps only 1 week of dashboard history. Paid plans start with Basic at $9 a month billed monthly or $99 billed yearly. Full history requires Premium, which costs $14 a month billed monthly or $153.96 billed yearly. The 14-day Team trial needs no credit card.
Not the way WakaTime does. Toggl is built around manual and real-time timers, timesheets and calendar integrations. The vendor also lists automated background tracking and a timeline in its desktop app, but the vendor documentation summarized here doesn't list per-language or per-editor coding metrics. If automatic, editor-level coding stats are the goal, WakaTime is the closer match.
Yes. WakaTime says it tracks AI coding usage, including AI adoption, model usage and spend, and AI-generated versus human-written lines, across tools such as Claude Code, Cursor, Copilot and Codex. Toggl's AI features do something different: Toggl AI answers natural-language questions about workspace data, alongside an MCP server and an AI Task Creator. Dayflow lists no AI-usage metrics.
No, Toggl is the better choice for that. Dayflow has no invoicing, billable rates, timesheet approvals or team reports. Toggl offers billable rates on paid plans, starting with Starter at $9 per user per month billed annually or $12 billed monthly, and adds profitability reports, timesheet approvals and Jira and Asana integrations on Premium. Dayflow helps you remember the work; Toggl handles the billing side.
Both are cloud services. WakaTime's plugins send coding activity to its hosted dashboard, and the server location isn't stated on the vendor pages reviewed. Toggl is a web service whose data syncs across its web, desktop and mobile apps. Dayflow stores recordings and the timeline on your Mac; screenshot analysis stays on-device with local AI, or goes off-device if you choose a cloud provider or Pro.
Partly. WakaTime's editor plugins are open source, but the hosted service is not, and the plugins' specific license wasn't confirmed on the vendor pages reviewed for this article. Toggl is not open source. Dayflow is open source under the MIT license, and the app costs $0, with an optional Pro plan at $20 a month for managed cloud analysis.
No. Dayflow is Mac only and needs macOS 14 or later. If you code on another operating system, WakaTime works through plugins for 100+ editors, IDEs and terminals rather than a Mac app, and Toggl has a web app plus Windows, Mac, iOS and Android apps and browser extensions. On a Mac, Dayflow can run alongside either one.
Toggl states that it does not take screenshots or record keystrokes. Its tracking is based on timers, timesheets and calendar integrations, with automated background tracking and a timeline listed for the desktop app. WakaTime records editor activity through plugins rather than the screen. Dayflow does capture the screen, one frame every 10 seconds, and keeps the recordings on your Mac.
Both have $0 plans. WakaTime's free plan keeps only 1 week of history, and full history on Premium costs $153.96 a year billed yearly. Toggl's free plan covers timers for up to 3 users, and billable rates start with Starter at $108 a year billed annually. Which is cheaper depends on whether you need long-term history or billing.
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