Hubstaff download for Mac: what to install and what to wrap

Two different people search for a Hubstaff download for Mac. One has been asked to install the tracker and wants to know what it will do once it is running. The other never tracks a minute and lives in the dashboard, approving timesheets and pulling reports, and is looking for something to install that does not exist in the form expected. Both questions have clean answers, and the answers are opposites: one half of Hubstaff must be installed, and the other half is a web page that deserves a window.

What the Mac download actually is

Hubstaff's download page lists desktop apps for Mac, Windows, and Linux, mobile apps for iOS and Android, and a Chrome extension that it states runs on Google Chrome 47 or newer. The Mac build is the one relevant here, and the Mac time tracker page gives the specifics.

It runs on macOS Sierra 10.12 or newer, and the supported list published on that page runs from Sierra 10.12 through macOS Tahoe 26, taking in High Sierra, Mojave, Catalina, Big Sur, Monterey, Ventura, Sonoma, and Sequoia along the way. The app is small: Hubstaff's own answer is that releases vary but the Mac tracker is around 8 to 14 MB.

What it records is described plainly on the same page. Screenshots are optional and captured one to three times per ten minutes, with the frequency adjustable or the feature switchable off for each team member. Activity rates are based on mouse and keyboard usage. Apps and URLs can be tracked. Idle limits can prompt a person to stop tracking or resume after a period of no activity. Manual time entries exist for hours that were missed or need correcting.

Hubstaff's own answer to whether it tracks outside working hours is that with the standard Mac desktop app, tracking is tied to the timer, that activity data and optional screenshots are captured only while someone is actively tracking, and that each person can see when the timer is running. The page adds that settings vary by configuration and recommends that organisations disclose how they use it. Anyone installing it on request should read that sentence carefully and then check the configuration their own organisation has chosen.

Why this half cannot be wrapped

A tool that turns a website into a standalone Mac app produces a real application from a URL: its own icon, its own window, its own browser profile, running a Chromium engine. It is the right answer for a great many web interfaces. It is not a substitute for this download, and it is worth being exact about why.

Screenshots, keyboard and mouse activity rates, and application and URL tracking are readings taken from the operating system, not from a page. No window wrapped around a web interface can capture them, because the data does not exist inside the page. A wrapper cannot see which application has focus, cannot sample input, and cannot photograph the screen.

So the tracker has to be installed if tracked activity is expected of the account. Trying to replace it with a browser window produces timesheets with no activity data, which is a worse outcome than not tracking at all, because it looks like a configuration fault rather than a decision.

There is a lighter route that Hubstaff itself documents for people who only need hours rather than activity: the browser timer in the dashboard and the Chrome extension, which logs hours to projects and tasks, offers reminders at intervals, and accepts manual entries. That is the honest middle option, and it is a Hubstaff feature rather than a workaround.

The half that is a web page

Everything a manager does is in the dashboard. Timesheets are reviewed and approved there. Time off requests and breaks are managed there. Budgets for clients and projects are set there, with notifications as limits approach. Bill rates and pay rates are configured per person, payments are sent, and client invoices are raised from tracked billable time. The Mac page names more than twenty reports covering profitability, projects, budgets, and billable hours, and more than thirty integrations including QuickBooks, Slack, and Zapier.

Scheduling sits there too: one off or recurring shifts, with attendance alerts. So do projects and to-dos, and Hubstaff Tasks for teams using it as a project tool.

That is a full working day for anyone running a team, and it happens in a browser tab that competes with everything else in the browser. The asymmetry is worth naming: the person being tracked gets a real application with a Dock icon, and the person doing the approving gets a tab.

Which is why the answer to a manager searching for a download is not the tracker. It is a window for the dashboard.

The mobile apps are worth a line here because they solve a different part of the same problem. Hubstaff's download page describes the mobile app as tracking time on the move, with GPS time tracking, geofences that clock people in and out automatically at a job site, and location based alerts for late, missed, or abandoned shifts. That is field work, not desk work. A manager checking whether a shift started does it from a phone; a manager approving a week of timesheets does it from a desk, and the desk is the half with no application.

What it costs per seat

Hubstaff's pricing page carries the plan figures in its own structured data, and they set the context for how much of the dashboard gets used.

There is a Free plan at $0, which includes time tracking and limited screenshots. Starter is $4.99 per seat per month billed annually, or $7 billed monthly. Grow is $7.50 annually, or $9 monthly. Team is $10 annually, or $12 monthly, and Hubstaff's own billing explanation uses the Team plan at $10 per seat per month as its worked example. Enterprise is listed at $25. The paid plans start at two seats, seats are charged whether or not every member tracks, and the trial runs 14 days with no credit card required.

Two consequences follow. First, a two seat account on Grow is an annual commitment measured in low hundreds of dollars, and the window the dashboard is used in costs nothing either way, so improving it is a ten minute job rather than a budget line. Second, the higher the tier, the more of the value is in dashboard features rather than in the tracker: reporting, approvals, budgets, and integrations are all pages, and a tier bought for reports that nobody opens is the most expensive outcome available.

The routes side by side

Route	Activity and screenshots	Logs hours	Timesheets and reports	Own Dock icon	Isolated session
Hubstaff Mac desktop app	Yes	Yes	Read only in part	Yes	Yes
Hubstaff Chrome extension	No	Yes	No	No	Shares the browser
Browser timer in the dashboard	No	Yes	Yes	No	Shares the browser
Dashboard in a standalone web app	No	Yes	Yes	Yes	Yes, one profile per app

The first row is compulsory where activity data is expected. The last row is the one that fixes the manager's day. They are not competitors, and a lot of accounts want both on the same Mac: the tracker for the hours, and a separate window for approvals and reports so that closing a browser does not close the business.

The case that decides it: more than one organisation

Anyone who belongs to several Hubstaff organisations hits the limit of a browser tab immediately. A contractor with seats in three clients' accounts, an agency running its own account plus a client's, or an operations lead covering two companies all face the same mechanic: separate sign ins cannot coexist in one browser profile, because they share cookies, and one signs the other out.

The usual workarounds are a second browser, a private window that has to be signed into every time, or a sign out and sign in cycle several times a day. None of them is expensive on any single occasion, which is exactly why they persist for years.

A generated app carries its own browser profile, so each organisation gets a window that stays signed in. Extensions keep working, because the engine is Chromium based, which means a password manager fills each login as it did in the browser. Tab mode can be enabled per app, so one window can open the dashboard, the reports page, and the timesheets page as three tabs on launch. The features list covers the per app profile and the tab controls, and the tool runs on macOS 12 and later.

Questions that settle this quickly

Is activity data expected on this account? If yes, install the desktop app and read the configuration. No window replaces it.

Who is asking, the tracked or the tracking? A tracked team member needs the download. A manager needs a window for the dashboard, and possibly no download at all.

How many organisations are involved? One is simple. Two or more makes profile isolation the requirement, not a preference.

Would the Chrome extension or browser timer be enough? For a freelancer billing hours with no screenshot requirement, Hubstaff's own lighter options avoid installing anything that samples input.

What is actually being paid for? If the plan was bought for reports, approvals, and budgets, then the dashboard is the product, and the product currently has no window of its own.

Is this Mac shared? A machine used by more than one person, with a dashboard session left signed in inside the general browser, is a payroll and reporting interface one click away for whoever sits down. Moving it into its own app with its own profile does not make it secure by itself, but it stops the session from being a by-product of ordinary browsing, and it makes signing out a deliberate act rather than something nobody thinks about.

What actually improves

The tracker does not change. Installed, it does what the configuration says it does, and that is between the account and the people in it.

What changes is the other half. A dashboard with a Dock icon is reached by keystroke rather than by scanning a tab strip, and quitting the browser at the end of the day no longer closes it. Approvals and invoicing happen in a window with nothing else in it, which reduces the small errors that cost real money. Several organisations stay signed in at once, so covering two accounts stops being a sign out cycle. And the page inside stays current because it is the same web interface Hubstaff keeps updating: there is no separate build to wait for. The guide walks through building the first app from a URL, and the supported services list shows what arrives preconfigured.

What to change first

Install the Mac tracker if the account expects activity data, and read the organisation's tracking settings before starting it. Then give the dashboard its own window, since that is where approvals, budgets, and reports happen: Kagemusha is free for up to three apps, which is enough for one dashboard per organisation before anything is spent.