Where Does Hevy Store Workout Data?
Hevy keeps routines and workouts in its cloud account with CSV exports and a Pro API. No user-accessible local files exist.
Last updated
Hevy centralizes training data in cloud accounts. Routines as templates plus logged sessions with measurements sync everywhere after login. Local storage stays cache with no documented files.
Exports split by audience. CSV flows serve coaches and spreadsheets with one reversible Strong import allowed. Pro API keys serve programmers with endpoint docs. Package identity anchors the sandbox while files stay server-side.
Where Hevy stores this, by platform
/data/data/com.hevy
Private sandbox for the verified package with cache only and no documented workout files. Routines and sessions live account-side with CSV and API exits. Watches sync without local artifacts.
/var/mobile/Containers/Data/Application/<guid>/Documents
Sandboxed container with the same cloud account model. No Files.app path holds routines. Export and API flows match Android exactly.
Frequently asked questions
How do I export Hevy workouts?
Use Profile Settings Export and Import Data for workout and measurement CSVs aimed at coaches and spreadsheets. Strong-format CSVs import back once reversibly while other formats stay unsupported. Pro API keys unlock programmatic reads of routines and histories.
Where does Hevy store my routines?
Through cloud accounts available on any device after login with local cache only. Watches sync routines without leaving files. The verified package names a sandbox holding nothing quotable.
Does Hevy have an API?
Through the developer settings key with documented endpoints for workouts, routines, templates and histories. Free tiers lack access. CSV exports serve everyone else without code.
Notice an outdated path? Let us know.