Clockify desktop app on a Mac: the timer without a browser

A timer that lives in a browser tab has a specific failure mode. The tab gets buried, the timer keeps running through lunch, and the correction happens the next morning from memory. That is usually what sends someone looking for a Clockify desktop app on a Mac. The good news is short: it exists, it is native, and it costs nothing. The part worth knowing before installing anything is that the desktop app covers one job, the timer, and hands everything else back to the browser. Which means the tab does not disappear. It changes role.

What the Mac desktop app actually is

Clockify publishes a genuine macOS application, not a repackaged web page. The requirement stated on the download page is macOS 12.0 or higher, and the download is free regardless of plan.

Its scope is deliberately narrow, and reading the feature list makes that clear. There is the timer itself, with a description field and a play button. There is manual mode for entering past work, reached by the icon next to the play button. There is a list of recent entries grouped by day, each one restartable with a single click. There is autocomplete on descriptions, and there is the ability to create a project, task or tag from inside the time entry details window.

Around that core sit the things that only a native app can do. The timer and the project name can be shown in the macOS status bar, with the project colour if wanted. The app can be hidden from the Dock. A custom global keyboard shortcut can start and stop the timer from anywhere, and the window itself carries Cmd+S to start, Cmd+T to stop, Cmd+N for manual entry, Cmd+D to discard and Cmd+Y to sync. A Pomodoro timer can fire a notification at the end of an interval and start a break entry on its own.

Two behaviours matter more than they first appear. The app can stop the timer when the Mac sleeps, powers off or the lid closes, and start it again when the Mac wakes or unlocks. And the app works offline, saving entries locally and syncing when the connection returns. Both of those are things a browser tab cannot do at all, which is the honest case for installing the desktop app even if the browser stays open all day.

One offline caveat is documented and easy to trip over. Projects, tasks, tags and clients cannot be created while offline, and unsynced data is lost if the app is logged out before it reconnects.

The App Store build and the website build are not the same app

This is the detail that trips up most setups, because both builds are official and both are called the same thing.

You can also download Clockify for Mac directly from the Clockify's website. This version includes the Idle detection and Auto tracker features. Please note that due to recent changes in the App Store's policies, these features are not available in the App Store version. Source: clockify.me

Idle detection is the feature that notices the Mac has been untouched and offers to discard the dead minutes. Auto tracker records which apps and websites were used, visible only to the person tracking. Neither is present in the Mac App Store build. For anyone whose original complaint was a timer left running through a meeting, that is the difference between solving the problem and not.

The trade runs the other way on sign in. Apple login is only available in the App Store build, so a workspace standardised on Apple ID accounts has a reason to prefer that one. Google sign in and email verification codes work in both. Custom domain and subdomain logins are supported in either build, with the workspace chosen during login.

There is no route that gives both Apple login and idle detection at the same time. Choosing the build is therefore a real decision, and it is worth writing down which one was installed, because the two look identical once running.

What the desktop app hands back to the browser

The settings menu in the top right corner of the desktop app is the clearest statement of scope. Two of its entries are not features. They are exits: go to reports in the web version, and manage projects in the web version.

That pattern holds across the product. Reports, project administration, invoicing, approvals, scheduling, expenses, time off policies, rate configuration and workspace settings all live in the web application. So does the setting that controls whether regular members can create projects, clients and tags at all, which has to be changed in a browser before the desktop app will let them.

Some desktop behaviour is even governed remotely. Time format follows the profile settings set on the web. Duration format follows the workspace setting on the web. Change either one in the browser and the native app follows.

So the realistic daily shape for anyone past solo use is two tools, not one. The native app holds the timer and the status bar. The browser holds everything that involves looking at other people's time, billing a client, or approving a week. The question is not whether the browser stays. It is whether the browser stays as a tab.

That distinction is the whole point. A tab has no fixed position, no Cmd+Tab entry and no Spotlight name. Reaching a report means bringing the browser forward and then hunting through whatever else the browser is holding. The cost is not load time. It is the search, repeated several times a day, and the accidental close during a tab cleanup that puts a sign in screen between a manager and an approval queue.

The plan decides how much of the web side matters

Clockify charges per seat, and every active or invited user on the Team page occupies one paid seat, including the owner, admins and managers. Deactivated users do not. Prices below are the published rates, annual billing first.

Plan	Annual billing	Monthly billing	What it adds
Free	$0, up to 5 users	$0	Timer, timesheet, auto tracker, calendar, mobile and desktop apps, reports limited to a 1 month data range
Basic	$3.99 per seat, per month	$4.99	Add time for others, hide pages from members, kiosk, bulk edit, imports, billable rates
Standard	$5.49 per seat, per month	$6.99	Time off, invoicing, approval, lock time, attendance and overtime, QuickBooks
Pro	$7.99 per seat, per month	$9.99	Scheduling, forecasting, expenses, labour cost and profit, alerts, GPS tracking
Enterprise	$11.99 per seat, per month	Contact required	Control and security features

One detail in the free row is easy to miss. Reports exist on the free plan, but the data range is capped at one month, which means any question about last quarter is a paid question. That cap tends to be what pushes a solo user onto Basic or Standard rather than any single headline feature.

The row that changes the window question is the free plan's report range of one month. A solo user on the free plan opens reports rarely, so a tab is fine. From Standard upward, invoicing and approvals arrive, and those are weekly obligations with deadlines attached. That is the point at which the browser side stops being occasional and starts being routine.

Giving the web side a window of its own

Since macOS Sonoma 14, Safari can save any page as a standalone application through File then Add to Dock, or the Share button then Add to Dock. The result lands in the Applications folder inside the home folder and behaves like an app.

A web app functions independently of Safari. It shares no browsing history, cookies, website data, or settings with Safari. Source: support.apple.com

The window's settings panel allows the Application URL to be changed, which is the setting most worth using. A window that opens directly on the reports screen, or on the approvals queue, saves a click on every visit for the rest of the year.

Chrome offers the equivalent through the three dot menu, then Cast, save, and share, then Install page as app.

A web app is an app built for the web that you can access on any device. Source: support.google.com

The caveat with Chrome is inheritance. A window created from a Chrome profile signs in as whatever account that profile holds, and it keeps sharing that session afterwards. For one login this is fine. For two it means creating a second Chrome profile first.

Route	Setup	Dock and Cmd+Tab	Session per window	Extensions	Suits
Browser tab	None	No	No	Browser wide	Free plan, solo use
Native Clockify app	Download and install	Yes	One login at a time	None	The timer, offline, status bar
Safari, Add to Dock	Two clicks	Yes	Yes	Safari extensions, per window	One workspace, daily reports
Chrome, install page as app	Three clicks	Yes	Follows the Chrome profile	Chrome extensions, per profile	Already on Chrome
Site to app tool	Pick the URL once	Yes	Yes, per app	Depends on the engine	Several workspaces or clients

What a purpose built window covers is set out on the Features page, and the build steps are in the Guide.

Several workspaces, and the account problem underneath

Clockify allows a workspace to be switched from inside the desktop app, so a contractor tracking against three of a client's projects inside one workspace has nothing to solve.

The harder case is separate accounts. An agency tracking time inside each customer's own Clockify workspace, or a contractor given a seat in a client organisation alongside a personal account, has genuinely different logins. A browser holds one session per site per profile. The usual workarounds are a private window that forgets everything on close, a second browser that remembers, or signing out and back in several times a day. Each of those is how an hour ends up billed to the wrong client.

Windows built as separate applications each keep their own session and their own cookies, which is what lets two accounts stay signed in at once with two icons in the Dock. The same separation answers a quieter problem: a reporting window that stays signed in survives a browser restart caused by something entirely unrelated, such as an extension update.

Anyone weighing this against the other tools already living in tabs will find the common ones on the Supported services page.

What to change first

Install the website build of the Mac app rather than the App Store build unless Apple login is required, since that is the one with idle detection and the auto tracker. Then take the reports and approvals screen out of the tab strip and give it a window with a fixed Dock position and its own opening URL. If more than one Clockify login is involved, a separate permanently signed in Kagemusha window per account is the version that holds up.