What you just got
You dropped an export from a fitness app into the converter, and a file called
openbody.json landed in your downloads. Here’s what that file actually is — and why
it’s worth keeping.
It’s just your history, written down plainly
openbody.json is a plain, human-readable file that lists your workouts and
measurements — the runs, lifts, rides, climbs, heart-rate readings, and body
measurements the converter found in your export. It isn’t an app, and it isn’t locked to
anything. It’s text you can open, read, copy, and move around freely. Nothing about it
depends on OpenBody, on the app you exported from, or on this website still being here
tomorrow.
If you open it in any text editor, you’ll see readable entries — each one a workout or a measurement, with its date, what it was, and the numbers that go with it. A single reading looks about like this:
{ "type": "heart-rate", "value": 61, "unit": "bpm", "startTime": "2026-06-14T07:02:00Z" }That’s the whole idea: no mystery format, no secret database. Just your data, laid out so a person (or any other tool) can read it.
Why a portable copy matters
Your training history usually lives inside one app — and that means it can move, change, or vanish on someone else’s terms. A portable copy is the opposite: it’s yours, sitting in a plain file you control. Apps come and go, subscriptions lapse, companies get acquired and shut things down. The copy you just downloaded outlives any single one of them.
What you can do with it now
Curious what’s actually inside? See the shape of the data → walks through real records — a measurement, a set, a run, a full session — in about five minutes. And if you want the exact, technical definition, the specification has every detail.