Where Does WakaTime Store Config and Data?
WakaTime tracks coding time per project from editor plugins with the API key in ~/.wakatime.cfg. Dashboards aggregate heartbeats into reports.
Last updated
WakaTime centers on one config file with the API key. Editor plugins send heartbeat pings per file and project to the WakaTime account, which builds dashboards, goals, and leaderboards. The key file lives in the home directory on every machine.
That makes the key the migration: copy it or paste from settings and tracking resumes. Project mapping rules keep names stable across different checkout paths. Exact behaviors may vary by plugin version; keep plugins updated for new editors. Editor extensions show today totals inline.
Where WakaTime stores this, by platform
%userprofile%\.wakatime.cfg
API key plus settings here; heartbeats go to the account. Copy the key to new machines or paste from dashboard settings.
~/.wakatime.cfg
Same key file as Windows in the home directory. Plugins per editor send heartbeats under one account.
~/.wakatime.cfg
Same layout as other platforms. Project rules stabilize names across checkout paths. Dashboards aggregate everything.
Frequently asked questions
How do I add another editor?
Install the plugin for the new editor and paste the same API key from the dashboard settings. Heartbeats resume under the existing account. Project rules map paths to names consistently across machines.
Notice an outdated path? Let us know.