Tracking Time Without Internet
"Works offline" and "safe offline" are different claims
Time tracking has a habit of failing in exactly the places you most need it: a flight, a basement plant room, a client site with no guest wifi, a village with one bar of signal. Most trackers say they work offline. What that phrase means varies more than it should.
This guide separates two claims that get conflated — works offline and safe offline — sets out what the major trackers actually do as of mid-2026 according to their own documentation, and ends with a five-minute check you can run before trusting any of them with a week of work.
The difference the marketing copy hides
Nearly every modern tracker can record an entry with no connection. The client writes it locally and pushes it up when the network returns. The interesting question is what happens in between, because during that window the local copy is the only copy.
The vendors are refreshingly direct about this in their own support documentation, which is worth reading before a trip:
•
Toggl Track: entries created offline sync when you reconnect, and unsynced ones are flagged in the entry list. Toggl's support documentation explicitly tells you not to log out of or refresh the app while entries are unsynced, because doing so can lose them.
•
Clockify: the same shape. Offline mode on mobile and desktop stores entries locally and syncs on reconnect, and Clockify's help pages warn that logging out while in forced offline mode with unsynced data loses that data.
•
Harvest: the mobile apps track offline and sync later, while the web dashboard needs a connection. Reviews that flatly say Harvest has no offline mode appear to be describing the web app only — worth knowing if that claim is what put it on or off your list.
None of that makes them bad tools; it is a reasonable design for a cloud product. It does mean the risky moment is not the flight. It is the airport afterwards, when you are troubleshooting a login on hotel wifi with a week of unsynced entries sitting on the device.
The failure mode is not theoretical either. On Toggl's own community forum, a user described running the desktop app offline for roughly four months because of a broken network setup, then needing help recovering the unsynced local entries. Long offline stretches are where this bites hardest, and they are exactly the stretches people plan for when they go looking for an offline tracker.
Local-first moves where the risk sits
There is a structural alternative: make the device's own store the source of truth and treat the server, if there is one, as a copy. An offline week is then not a pending upload — it is simply the data, in its normal place. There is no sync boundary to lose things at, because nothing is queued up waiting to cross one.
That is how TickTappy works. There is no account until you want one: entries are written to a local database — SQLite in the mobile app, IndexedDB in the browser — and read back from there whether you are online or not. If you do turn on sync, which is the paid part at $4.99 a year or $24.99 once, the app keeps a queue of pending operations and shows a connectivity indicator in the header, so what has not gone up yet is visible rather than assumed.
The trade is real and worth stating plainly: local-first means losing the device loses the data, unless sync is on or you have a device backup. Cloud-first tools trade that risk for the sync-boundary one. Neither is free; pick the failure you would rather live with.
Who actually needs offline tracking
Flights and long journeys
A flight is the most productive uninterrupted block many people get all month, and the one most likely to go unrecorded. Trains and ferries with intermittent signal are worse, because the app keeps half-connecting and you cannot tell what has synced.
Field work and buildings that eat signal
Plant rooms, warehouses, construction sites, hospitals, basements and thick-walled older offices are where signal goes to die, and they are full of billable hours. Add anywhere with a guest wifi captive portal that logs you out every hour.
Metered data, and not wanting to upload your day
On expensive roaming data an app that phones home constantly is a cost as well as a nuisance. And some people simply prefer that a record of their working day not leave the device by default, which is a preference a local-first tool satisfies by construction rather than by promise.
A five-minute check before you rely on it
•
Turn on airplane mode and start an entry. Does it show up in your history straight away?
•
Force-quit the app and reopen it, still offline. Is the entry still there? This is the check that catches web apps living in a tab you were about to close.
•
Does the app tell you what has not synced yet? An unsynced marker is the difference between a warning and a surprise.
•
Do not log out, reinstall, clear site data or reset anything while entries are pending. In the major cloud trackers this is the documented way to destroy them.
•
Reconnect deliberately and confirm the entries landed before wiping anything.
•
Know where the data physically is: a server copy, a device database, or a browser storage bucket you could clear by accident.
Where TickTappy fits
TickTappy is offline-first because it began with no server at all: the app works with no account and no connection, and sync was added later as an option rather than a requirement. It is the right tool if you want tracking that never depends on a network, and the wrong one if you need a shared team timesheet, per-project billing rates or integrations.
For the feature-by-feature version, see
best offline time tracker. For the comparison people ask about most,
TickTappy vs Toggl Track. And if the network is unreliable because you are rarely in one place,
time tracking for remote workers covers the rest of that setup.
Track it as it happens instead
TickTappy starts with one tap on a coloured tag and stops with another. Free core, no account, works offline.
Frequently asked questions
Does time tracking work without internet?
In most modern trackers, yes — the app records the entry locally and uploads it when the connection returns. The difference between tools is where that entry lives in the meantime and how clearly the app tells you it has not synced yet.
Can Toggl Track work offline?
Yes. Toggl's support documentation says entries created offline sync once you reconnect, and unsynced entries are flagged in the list. The same documentation warns against logging out of or refreshing the app while entries are unsynced, because that can lose them.
What happens to unsynced time entries?
They sit in the app's local storage until it can reach the server. Logging out, reinstalling or clearing the app's data while entries are pending can destroy them — a risk both Toggl and Clockify document in their own help pages.
Is offline tracking safe for a long trip?
It is, with two habits: check that entries survive a force-quit while offline before you leave, and reconnect deliberately at the end rather than logging out or reinstalling first. Very long offline stretches carry the most risk, since everything you tracked is sitting on one device.
Does TickTappy need an account or an internet connection?
No. The core app runs with no account and no connection, storing entries in a local database on the device. Sync across devices is optional and paid, at $4.99 a year or $24.99 once, and the app shows a connectivity indicator so pending sync work is visible.
Also see
Sources