The upload page accepts only the files that match the recording kind of the project. The tables list what each format needs. A format marked Coming soon cannot be selected or uploaded in the console yet.
Who can do this: anyone who can upload to the project.
Robot recordings
| Format | What the files need | Status |
|---|---|---|
| MCAP | MCAP recordings with the extension .mcap. Choose it when the robot logged ROS topics, cameras and IMU. | Available |
| ROS bag | Files with the extension .bag. | Coming soon |
| ROS 2 db3 | Files with the extension .db3. | Coming soon |
| LeRobot folder | One folder per recording, with meta/info.json, data and videos at its root. Upload meta/episodes.jsonl too when the workflow needs episode metadata. | Available |
| HDF5 | Files with the extension .h5 or .hdf5. The vendor layouts (Embodiflow, Agilex, Realman, Dobot) are all coming soon. | Coming soon |
Human recordings
| Format | What the files need | Status |
|---|---|---|
| First-person MCAP | MCAP files with the extension .mcap, in the same folder as device_meta.json. Audio is refused by default. Needs the first-person human source to be turned on for this deployment. | Available |
| Human LeRobot folder | One folder per recording, with the same layout as a LeRobot folder. | Available |
| Video | Fixed-camera video files: .mp4, .mov and .mkv. | Coming soon |
| BVH motion capture | Files with the extension .bvh. | Coming soon |
How the format is chosen
The format is set by the project. When the files fit more than one format for the project, the upload page asks you to choose Format for this import. Choose the one that matches your recording.
Why was my file refused?
A file whose extension is not accepted for this upload is skipped and listed as not a type this upload accepts. An MCAP file that is not a valid MCAP file is listed as not a valid MCAP file.