Supported loggers

Will Lapfly read your data?

Lapfly imports the loggers below. Some upload as the native file the device writes; others need a quick CSV or data export from the maker's own software first. Drag and drop the file, and Lapfly detects the format automatically.

LoggerFileUpload as How to get the fileNotes & limitations
i2M Chrome / Chrome Pro 2 .dat Native Copy the .dat file straight off the logger and upload it. Files holding several sessions are split automatically. Native device file, no export needed. Older $SETTINGS firmware can mislabel channels; if labels look wrong, export a CSV from the i2M software instead.
i2M Chrome (CSV export) .csv Export Export a CSV from the i2M desktop software. Recommended over the legacy .dat when a logger's channel labels come through wrong.
AiM (Race Studio) .xrk, .drk Native Upload the session file Race Studio records (.xrk or .drk) directly. Which channels are available depends on your AiM device and configuration.
MoTeC .ld, .ldx Native Upload the logged .ld / .ldx file directly. Channel names come through as the file spells them; sample rates are inferred and unusual data types are skipped.
2D (Datarecording) .csv Export Export a CSV from the 2D software. Recognised by its column names and mapped for RPM, wheel speeds, lean, brakes, suspension, temperatures and GPS.
aRacer .loga Export Save the ECU Memory Log (.loga) from the aRacer software. Channels are read straight from the ECU; disconnected or all-zero sensors are dropped automatically.
RaceChrono (Pro) .csv Export Export a CSV from RaceChrono Pro (v3). Phone / GPS based, and includes lean angle and IMU data. Timestamps are the phone's local clock.
RaceBox .csv Export Export a CSV from the RaceBox app. GPS and IMU only, with no throttle, brake or RPM channels.
Racelogic VBOX .vbo Native Upload the VBOX .vbo file directly. GPS only: position, speed, heading and altitude.
GoPro .mp4 Native Upload a clip recorded with GPS switched on; Lapfly reads the GPS embedded in the video. Needs a GPS fix in the clip. GPS only, with no bike-sensor channels.
Generic GPS CSV .csv Export Any CSV with a time column and GPS latitude, longitude and speed. A best-effort fallback rather than a validated profile; unmapped columns pass through under their own names.

No logger matches that search. Not sure about your file? Contact us.

Accepted file types: .dat .csv .xrk .drk .ld .ldx .vbo .mp4 .loga · up to 300 MB per file.

File compatibility is not the same as every analysis being available. Lapfly reading your file only means it can load the channels that are in it. Each analysis also needs the right sensors to have been recorded. A GPS-only file cannot show throttle, brake, suspension or engine work no matter how cleanly it loads.

What each analysis needs

Fly, delta time, corner & sector, theoretical best

GPS position and speed. Any GPS source works, including a phone, VBOX or GoPro.

Braking & trail braking

A front-brake sensor, plus GPS speed; lean angle adds the trail-braking metrics.

Throttle / brake overlay & corner exit

Throttle and brake channels.

Engine & shift analysis

RPM, plus a gear or shift-drum channel for shift detection.

Suspension

Fork and shock travel channels, plus the stroke length you enter for any travel-limit reading.

Lean angle

A lean-angle channel (many phone and IMU sources provide this).

Lapfly does not sell hardware or recommend a particular logger. Use whatever records the channels you want to analyse. Compatibility here is about whether Lapfly can read the file, separate from which logger is right for your bike.

Not sure about your file?

Send it over and we will tell you what Lapfly can do with it: support@lapfly.com

Start your free trial