Where Does Strong Store Workout Data?
Strong keeps workouts on-device and in cloud sync with CSV export through the share sheet. Exports never import back.
Last updated
Strong records offline and syncs to cloud with exports as the lone exit. Workout CSVs leave through the share sheet with body metrics as separate files. Nothing documented lives in user folders.
The one-way rule shapes every workflow. Exports analyze elsewhere but never return, so the live account stays the archive. Package identity anchors the sandbox for the curious with no files promised inside.
Where Strong stores this, by platform
/data/data/io.strongapp.strong
Private sandbox for the verified package with offline persistence and cloud sync. No documented routine files. Export CSVs through Profile settings Data Management.
/var/mobile/Containers/Data/Application/<guid>/Documents
Sandboxed container for the verified store ID with the same export flow. Body metrics export per metric apart from workouts. Share-sheet dismissal saves nothing.
Frequently asked questions
How do I export Strong workouts?
Use Profile Settings Data Management Export on either platform, delivering a semicolon CSV through share or email. Body metrics export separately per metric. Dismissing the share sheet saves nothing, so complete the send.
Does Strong work offline?
It works offline with persistence across force-stops, syncing when able. No documented file path exposes the routines, so the sandbox stays opaque. Export remains the only exit door.
Can I import Strong CSVs back?
Nowhere by design. Exported files import into nothing, not even Strong itself. Treat exports as analysis copies for spreadsheets rather than backups restorable in-app.
Notice an outdated path? Let us know.