Compatibility and input methods
Bring readable workout data. Know the route.
Compatibility describes how data reaches the dashboard, not a partnership or an automatic connection. Implementation reviewed on 20 October 2026; individual vendor layouts have not all been tested.
What works now
Manual entry works for the fields in the workout form. GPX files with valid track points have a local parser. Screenshot scanning uses the built-in vision service with a review step. All methods lead to the same editable workout form after account sign-in.
Garmin Connect: GPX file upload
Export an activity as GPX, then upload it under Log Run. The parser calculates distance from coordinates, elapsed time from first and last timestamps, pace from that elapsed time, and elevation gain from positive changes. Date, heart rate and cadence depend on available fields. Summary-only GPX files without track points are rejected. There is no Garmin account connection.
App summaries and fitness displays: screenshot or manual entry
The image route accepts readable PNG, JPEG and WebP completed-workout summaries, up to 10 MB. It can read visible supported fields and a visible source label, but layouts and photos vary. Strava and Apple Fitness values can always be transcribed manually. Confirm the source yourself if a screenshot has no identifiable branding. An uploaded image does not authorize access to its originating app.
Apple Watch, Apple Fitness and Apple Health are different
Apple Watch records activity; Apple Fitness can show a completed workout summary. Enter visible summary values or review image extraction. The Apple Health XML database, HealthKit access and automatic Apple Watch syncing are not implemented.
Not supported as file imports
FIT, TCX, CSV, Apple Health XML and pasted bulk data have no working parser here. Do not upload them as GPX. There are no direct Strava, Garmin, Apple or other provider account connections, no website scraping and no background syncing.
Metrics and meaningful limits
Supported summary fields are activity type, date, distance, pace, time, average heart rate, cadence, calories and elevation. Missing units require confirmation. Screenshot imports do not reconstruct GPS tracks, detailed trends or unseen splits. Only compatible summary fields are saved; general wellness records and proprietary recovery scores are outside the current scope.
Supported input routes at a glance
| Source | Working input method | Available metrics | Limits |
|---|---|---|---|
| Garmin Connect | User-exported GPX track file | Calculated distance, elapsed time, pace, elevation gain; date and sensor fields when present | Track points required. No account connection. |
| Readable workout summaries | PNG / JPEG / WebP screenshot | Visible supported summary fields, reviewed and corrected before saving | 10 MB maximum. Layout-dependent; no full route or split reconstruction. |
| Strava summaries | Manual entry; readable images use the general scanner | Only visible, supported workout values | No direct Strava syncing or vendor-layout guarantee. |
| Apple Watch workouts in Apple Fitness | Manual entry; readable images use the general scanner | Only visible, supported workout values | No HealthKit, Apple Health archive parser or watch connection. |
| Other apps, websites and treadmill displays | Manual transcription; readable images use the general scanner | Only supported workout summary fields | Not automatic website access or universal format support. |
No direct account connections or automatic sync. FIT, TCX, CSV, Apple Health XML and bulk pasted data are not supported imports. Open Log Run to import or enter data.
Ready to use your own data? Sign in and open Log Run, then compare your recordings.