Your cycling file questions, answered.

Yes. The Workshop tools and Studio are free to use without an account. You can inspect a recording, make supported edits and download the result without entering payment details. No subscription is needed for the tools available in this release.

You can inspect FIT, GPX and TCX files. Supported CSV tables can be converted to GPX. Each tool lists the formats it accepts, and availability also depends on the file’s contents: a route without timestamps cannot support the same time-based edits as a recorded activity. Use Inspect first if you are unsure what your file contains.

FIT is commonly used by cycling computers and watches and can contain detailed sensor and device information. GPX is primarily used for GPS tracks and routes; extra sensor data depends on extensions. TCX can describe activities, laps and fitness measurements. Converting between them can lose information that the destination format or writer does not support. Review the conversion summary before downloading.

KADALTO reads and edits ride files in your browser. The file itself is not uploaded for processing. Online maps request the viewed region from a map provider, and terrain correction requests height tiles for your route. Those requests reveal geographic areas to the relevant servers. You can disable the online map background; manual edits do not need terrain requests.

No. An edit creates a separate output file. In Studio, your original recording, current ride and pending preview stay separate: review a preview, apply it, then export. Keep your original download somewhere safe. Closing or reloading the tab ends the in-memory editing session, so export before leaving.

Open Trim, choose your file and mark the section on the map or chart. You can remove sections, keep one section or trim the ends. Review the selection before downloading. Closing time gaps is a separate setting: it shifts later timestamps earlier. Hiding recording gaps on the chart only changes the display and does not change the exported file.

Yes, when the files and their timelines are compatible. Add every part to Merge, check their order and review any overlap or boundary warning. The tool checks each adjacent pair before creating a combined file. Use recordings from the same ride; unrelated sessions or conflicting timestamps may require a different choice rather than an automatic merge.

Yes, supported FIT and GPX recordings can use terrain matching or manual elevation edits. Terrain matching estimates ground height along recorded GPS positions. Compare the original and corrected profiles and choose a smoothing setting before applying. Terrain is not a survey of the ridden surface: bridges, tunnels, steep terrain and inaccurate GPS positions can produce differences.

Different services may calculate climbing from different heights, smoothing methods and noise thresholds. KADALTO’s profile-based D+ estimate can also differ from the device total stored in a file. Strava may recalculate the result after import. Compare the underlying elevation profile and the stated method; matching one displayed total is not proof that an elevation profile is more accurate.

Choose an output format accepted by the destination and review the verified download before importing it. KADALTO checks its generated file, but another service can apply its own size limits, duplicate detection, activity rules or recalculation. We cannot guarantee acceptance or identical statistics on every platform. Keep the original so you can compare or export again.

It depends on the source data and the output format. A GPS route cannot gain sensor readings that were never recorded. Some destination formats or supported writers cannot carry every field, lap or device detail. The conversion summary explains supported preservation and losses; the export tool can also provide a readable CSV or JSON view of inspected ride data.

Use Hide start & finish to remove points near the ride’s boundaries while keeping the useful route. Review the affected area on the map and inspect the result. A later return to the same place can still reveal it, and a route can contain other identifying details. Boundary hiding reduces exposure; it does not guarantee anonymity.

Recording gaps are hidden by default: the chart collapses missing time so the profile is easier to explore. Turning the option on shows the gaps on the original elapsed-time axis. Neither choice adds missing measurements, removes recorded points or changes timestamps in a download. Use the editing tool’s separate time settings if you want to change the file.

A matching filename extension does not guarantee a supported recording. The file may be incomplete, malformed, contain a different object type or use fields that cannot be preserved safely by the requested edit. Read the error and its suggested next step. A fresh export from the original device or app may help. Renaming the extension does not convert the data.

An indoor ride or a file without valid GPS coordinates can still contain speed, heart rate or power. A missing street background can also mean the map provider is unavailable. The local route view remains available when usable positions exist. Online maps cannot reconstruct GPS positions that are absent from the recording.

It changes supported device identity metadata in a FIT activity. It does not recreate the original device’s sensors, improve GPS accuracy or prove that a different device recorded the ride. Review the before-and-after identity and keep the original recording. Models without a verified numeric FIT identity may use a clearly labelled name-only option.

Each input file is limited to 20 MiB. Very large or complex recordings can also reach processing limits, especially on a phone. Batch processing reports each file separately, so one rejected file does not hide successful outputs. Download completed work before closing the tab; the editing session is not saved to a cloud account.

No. KADALTO can inspect and perform supported edits on readable files, but this release is not a universal damaged-file recovery service. If the original recording is truncated or unreadable, first try another export from the recording device or its companion app. Do not replace your only original with an attempted repair.