Take the data with you

The angles JSON is the richest single file: per-joint minimum, maximum and range, every frame's angle for every joint, your tags with their timecodes, and a plain-English definition of what each angle actually measures. The angles CSV is the flat version — one row per frame, one column per joint, with a time column.

The landmarks exports carry all thirty-three tracked points per frame, with depth and visibility per point where the engine provides them, in normalised coordinates with the frame size recorded so you can put them back into pixels.

Every file says what it is. Which joints were measured by the engine and which were calculated from the landmarks. Which smoothing filter was applied, with its exact settings, or nothing if the numbers are raw. Which section of the original video the file covers, with the parent's own frame numbers and timecodes rather than a fresh count from zero. Which landmark source was used, and the engine version that produced it.

A file that has been processed and does not say so is a file nobody downstream can check. So a download always tells on itself.

A rep counter exports as JSON any pose engine can run: the stages, the joint angles each one requires, the corrective cues attached to them, and the definition of every angle in terms of body keypoints. The Export tab hands you a ready-made runtime for your engine — QuickPose, Apple Vision, ML Kit, MediaPipe, TensorFlow.js or a COCO-17 model — in Swift, Kotlin, TypeScript or Python.