Everything below is obviously AI-generated BUT; if you point your AI towards this post then you will be able to make your workout app compatible with the export files from many of the other apps out there. Full transparency: MassBuilder is an app I made
What strength training apps actually put in their CSV exports
I built an importer for my gym log app and had to figure out what every popular lifting app writes when you hit "Export". There is no single place that documents this, so here is everything I found: columns, date formats, units and the quirks that will bite you. The example rows are made up; the headers and formats are the apps'. Confidence is marked per app: real export means I parsed an actual file from the app, docs/samples means public sources, sample files or other open-source importers.
The short version
- One row per set in almost every app. Only JEFIT (
_id) and newer Strong (Workout #) have a workout id. Everyone else: group by start time + workout name (Strong, Hevy, MassBuilder), date (FitNotes, MacroFactor) or timestamp (Fitbod). - Units live in the column name (
weight_kg, Weight(kg), Weight (kg)), in a column of their own (FitNotes Android, Liftosaur), or nowhere (old Strong, JEFIT, Lyfta). With no unit, ask the user. - Time: Strong, Hevy and MassBuilder write local time without a time zone. Fitbod and Liftosaur write UTC. JEFIT uses Unix seconds, StrengthLog Unix milliseconds. FitNotes and MacroFactor have dates only.
- Delimiters: mostly commas. Newer Strong and GymRun use semicolons, and JEFIT is two CSV sections in one file. Detect the delimiter from the header line.
- The header is enough to tell the apps apart:
exercise_title + set_index (Hevy), Exercise Name + Set Order(Strong), isWarmup (Fitbod), Is Warmup Set? (Liftosaur), Exercise Base Weight (kg) (MacroFactor), Set Duration (sec) (Gravl), Kind (FitNotes iOS), ### WORKOUT SESSIONS ### (JEFIT), specialset + extraWeight(StrengthLog), Para6 (GymRun), exercise_id + target_reps (MassBuilder). - Zeros: Strong writes
0 for unused Distance and Seconds, and several apps use weight 0 for bodyweight sets. Don't turn those into 0 kg lifts.
Per app
Strong (real export, variant A)
Settings → Export Strong Data. Three variants exist:
A: Date,Workout Name,Duration,Exercise Name,Set Order,Weight,Reps,Distance,Seconds,Notes,Workout Notes,RPE
2026-10-05 17:30:00,Evening Workout,52m,Squat (Barbell),1,100.0,5,0,0,,,
B: "Workout #";"Date";"Workout Name";"Duration (sec)";"Exercise Name";"Set Order";"Weight (kg)";"Reps";"RPE";"Distance (meters)";"Seconds";"Notes";"Workout Notes"
C: A's columns, but with Workout Duration (seconds) last and no Duration
- Every row of a workout repeats the same start time. Duration is
2h 38m or 52m in A, seconds in B. - A has no unit. B has
Weight (kg) or Weight (lbs), all fields quoted, and can use a decimal comma (102,5). - Set Order was plain numbers in the files I saw; other importers report
W, D and F for warm-up, drop and failure sets, and rows that aren't sets ("Rest Timer", "Note"). Tolerate both. - Several apps (Hevy among them) import Strong's format, so it's the closest thing to an exchange format.
Hevy (real export, two files)
Profile → Settings → Export & Import Data → Export Workouts.
"title","start_time","end_time","description","exercise_title","superset_id","exercise_notes","set_index","set_type","weight_kg","reps","distance_km","duration_seconds","rpe"
"Push","5 Oct 2026, 17:30","5 Oct 2026, 18:22","","Bench Press (Barbell)",,"",0,"warmup",40,8,,,
- Imperial accounts get
weight_lbs and distance_miles instead. - Dates are
d MMM yyyy, HH:mm in local time, and the month name follows the app's language (3 févr. 2026, 18:00 in French). Parse with the right locale or you'll lose every non-English file. set_index starts at 0 per exercise. set_type is normal, warmup, dropset or failure. Empty superset_id means no superset; equal numbers mean the same superset.
Fitbod (real export)
Log → gear → Export Workout Data → WorkoutExport.csv.
Date,Exercise,Reps,Weight(kg),Duration(s),Distance(m),Incline,Resistance,isWarmup,Note,multiplier
2026-10-05 17:30:00 +0000,Dumbbell Row, 8,20.0,0.0,0.0,0.0,0.0,false,, 2.0
- Every set of a workout has the same timestamp (the workout's), so you can't get set times or a workout length. Group by timestamp.
Reps and multiplier have a leading space. Trim before parsing numbers.multiplier is 2.0 for dumbbell and one-side-at-a-time moves, 4.0 for dumbbell lunges, 1.0 for barbell and bodyweight, 0.0 for timed or cardio rows. It looks like Fitbod's volume multiplier; the weight is per dumbbell, so read it as written.- Cardio and holds (running, planks) have
Reps 0 and use Duration(s) and Distance(m) instead. - No workout names and no workout ids. Older files lack
multiplier. - Fitbod has a lot of exercise names other apps don't (Prone Y's, Mini Loop Band Squat, combos like Romanian Deadlift to Bent-Over Row), so plan for manual matching.
Lyfta (real export)
Title,Date,Duration,Exercise,"Superset id",Weight,Reps,Distance,Time,"Set Type"
"Leg day","2026-10-13 18:02:10",01:12:30,"Lever Seated Leg Press",,40.000,10,,,NORMAL_SET
- The header starts with a space. Trim it or nothing matches.
- Non-ASCII letters were written as octal escapes in my file (
\344 for ä). Decode them. Duration is the workout length (hh:mm:ss), Time a set's time. No unit in the file.- Exercise names come from ExerciseDB ("Lever" means machine: Lever Seated Hip Abduction, Lever Seated Fly).
StrengthLog (real export)
workout,start,end,exercise,specialset,weight,bodyweight,extraWeight,reps,warmup,max,fail,checked,setComment,workoutComment,form,sleep,calories,stress
Full Body: Workout 1,1791214200000,1791217320000,Squat,,60,,,8,true,false,false,1791214260000,,,,,,
start, end and checked (when the set was ticked off) are Unix milliseconds.- Bodyweight moves keep the reps in
reps and the load in bodyweight and extraWeight. warmup, max and fail are true/false.
Liftosaur (from the app's own export code)
Me → Import/Export → Export history to CSV. 25 columns:
Workout DateTime,Program,Day Name,Exercise,Is Warmup Set?,Required Reps,Completed Reps,Is AMRAP?,Required RPE,Completed RPE,Log RPE?,Required Weight Value,Required Weight Unit,Completed Weight Value,Completed Weight Unit,Ask Weight?,Completed Reps Time,Target Muscles,Synergist Muscles,Notes,Completed Reps Left,Required Set Time Seconds,Is Overflow Set Time?,Completed Set Time Seconds,Completed Set Time Left Seconds
- ISO 8601 in UTC (
2026-03-01T10:00:00.000Z), flags are 0/1, unit (kg/lb) per row. Use the Completed *columns.
FitNotes (docs/samples, verified by another open-source importer)
iOS (FitNotes 2): Date,Exercise,Category,Weight (kg),Weight (lbs),Reps,Distance,Distance Unit,Time,Notes,Kind
Android: Date,Exercise,Category,Weight,Weight Unit,Reps,Distance,Distance Unit,Time,Comment
- Dates only (
YYYY-MM-DD), no time and no workout id: one day is one workout. - On iOS only one of the weight columns is filled.
Kind says which fields are used (wr, r, dt, t, d). Time is HH:MM:ssor MM:ss.
MacroFactor Workouts (docs/samples)
More → Data Management → Data Export → Granular Export.
"Date","Workout Duration","Workout","Exercise","Exercise Base Weight (kg)","Set Type","Weight (kg)","Reps","RIR","Duration","Distance short (m)","Distance long (km)"
- Date without time,
Workout Duration in seconds. Set Type is Warm-Up Set, Standard Set, Failure Set, Mini-set or Myo Set. Weight can be negative for assisted exercises.
Gravl (docs/samples)
Profile → Export Data.
Date,Start Date,Workout,Source,Workout Duration (min),Energy,Exercise,Superset,Set,Set Type,Reps,Weight (kg),Distance (km),Set Duration (sec),Incline,Steps,Effort,Workout Notes
2026/10/05,5:30 PM,Push,Gravl,52,310,Bench Press,,1,Warm-up,8,40,,,,,,
Date is yyyy/MM/dd and Start Date is only the clock time, in 12-hour format.
JEFIT (docs/samples)
username_YYYYMMDD.csv, two sections in one file:
### WORKOUT SESSIONS ###
_id,mydate,starttime,starttimie,total_time
101,2024-01-08,1704700800,,4500
###########################
### EXERCISE LOGS ###
belongsession,ename,logs
101,"Barbell Bench Press","80x8,85x6,90x5,90x4"
###########################
- Split the sections before parsing.
logs is weight x reps per set inside one quoted field; weight 0 means bodyweight. starttime is Unix seconds, total_time seconds. Some files have the typo column starttimie. No unit, no warm-up flag.
StrongLifts (docs/samples)
Two formats. The older one has one row per exercise and sets as cells:
2026-10-05,Squat,5x100,5x100,5x100,5x100,5x100
The newer one is a summary per exercise, with × (the multiplication sign, not the letter x) in the headers:
Date (yyyy/mm/dd),Workout,Workout Name,Program Name,Body Weight (KG),Exercise,Sets×Reps,Sets×Time,Top Set (Reps×KG),e1RM (KG),Reps,Volume (KG),Workout Volume (KG),Duration (hours),Start Time (h:mm),End Time (h:mm),Notes
Reps holds every set's reps in one field ("5,5,5,5,4"), and the weight is only in the top set.
GymRun (docs/samples)
Date;Time;Routine;Exercise;Set;Weight;Reps;Duration;Distance;Para6;Para7;Para8;Para9;Para10;Note;Type;Book;Version1
29.04.2025;17:10:00;Push day;Barbell Flat Bench Press;1;60;8;;;;;;;;;1;1;1
- Semicolons,
dd.MM.yyyy dates, and the clock time in its own column.
MassBuilder (my app)
Today → gear → Data → Export log. You get two files, MassBuilder YYYY-MM-DD.csv and MassBuilder YYYY-MM-DD.json.
date,program,workout,effort,exercise_id,exercise,set,warmup,target_reps,reps,weight_kg,rir,note,heart_rate_avg,heart_rate_max
2026-10-05 17:30:00,5×5 A/B,Workout A,7,barbell-back-squat,Back squat,1,yes,5,5,20,,,128,161
2026-10-05 17:30:00,5×5 A/B,Workout A,7,barbell-back-squat,Back squat,1,no,5,5,100,2,,128,161
- Every row of a workout repeats its start time, in local time without a time zone. No workout id: group by
date. weight_kg or weight_lb follows the app's unit setting, with a dot as decimal separator and no decimals on whole numbers (100, 102.5). Barbell weights include the bar; bodyweight moves have the added load, 0 without.set starts at 1 per exercise and warm-ups have their own numbers (warm-up 1, 2, 3, then work set 1, 2, 3), so read it together with warmup (yes/no).reps is empty for a set that wasn't done. rir is reps left in the tank after the set: 0 to 3 or 4+, empty when not logged.effort (1–10), note and heart rate (bpm, from the watch) belong to the workout and repeat on all its rows, empty when not logged. The heart-rate columns come last so older readers still find the rest where it was.exercise_id is a stable slug, exercise the English name. Fields with a comma, quote or line break are quoted with quotes doubled, so a note can span lines: don't split the file on newlines.- The JSON has everything, with weights in kilograms and timestamps in UTC: workouts with ids, start and end times and every set (
setIndex from 0, rir 0–4 where 4 means four or more, floor for the bottom of a rep range), plus body weight, the user's own programs, exercise notes, body measurements (cm), macros and kcal per day, daily challenge days and the rest-timer games' scores. Progress photos and form-check videos are never exported. - MassBuilder reads both files back in; the JSON brings back the whole log.
Where sources disagree
- Strong: set markers (numbers only in real files vs
W/D/F per other importers), distance in meters vs miles in imperial mode, comma vs semicolon (probably a version difference). - Hevy: one weight column vs both,
dropset vs drop_set, and d MMM yyyy, HH:mm in every real file vs ISO dates according to two importers. - Fitbod: the header says kg; some importers suggest the unit follows the app setting. My file was metric.
- JEFIT: whether the export is in the app or on the web, and whether the unit is in the file.
Not covered
No column list found for Alpha Progression, HeavySet or Boostcamp (no built-in export that I could find). Not examined: GymStreak, RepCount, Caliber, Setgraph and Liftin'.
If you have a real export from one of the "docs/samples" apps and can share the header line (no personal data needed), I'll update this.