Robot data formats compared: LeRobot, RLDS, HDF5 and MCAP
The format decides whether the training job can read what the operators recorded. What each of the four common formats stores, from its own documentation.

Contents
The file format is the last decision in a collection and the first thing the training engineer meets. A dataset in the wrong layout costs days of conversion, and a conversion can quietly drop a stream or shift a timestamp. Four formats cover most robot-learning work. This guide describes each from its own documentation.
What every format has to hold
Whatever the container, a teleoperated episode is the same set of things: camera frames, the robot's joint and gripper states, the actions commanded, timestamps on one clock, and metadata such as the task, the operator and the outcome1. Formats differ in how they pack these and in which tools read them.
LeRobotDataset
Hugging Face describes LeRobotDataset v3.0 as a standardised format for robot learning data. States, actions and timestamps are stored in Apache Parquet. Camera frames are concatenated and encoded as MP4. Metadata in JSON and Parquet records the schema, frame rates, normalisation statistics and episode segmentation2.
Version 3.0 packs many episodes into each Parquet and MP4 file, where version 2 used one file per episode. It ships with lerobot 0.4.0 and later, with a converter from version 2.12. Datasets can be opened in a browser visualiser that shows the camera recordings beside state and action charts2.
It suits teams that train with the LeRobot code or share data on the Hugging Face Hub.
RLDS
In RLDS a dataset is a collection of episodes, and each episode is a sequence of steps. A step carries flags that mark the first and last step and, optionally, an observation, an action, a reward and a discount. All steps in a dataset must have the same fields3.
RLDS matters for robot learning chiefly because the Open X-Embodiment collection uses it. Each of its datasets is a sequence of episodes in the RLDS episode format, loaded through TensorFlow Datasets4. The collection pools more than one million trajectories from 22 robot types5.
It suits TensorFlow pipelines and teams that co-train with cross-embodiment data.
HDF5
HDF5 is a general container for arrays, and robot learning uses it by convention. In robomimic's layout a dataset is a single HDF5 file with a group per trajectory, and each trajectory holds arrays of states, actions, rewards and observations. Images are stored as 8-bit arrays in height, width, channel order6. ALOHA's recorder writes an HDF5 file per episode and ships scripts to visualise and replay it7.
It suits teams that want a simple layout they can inspect with standard tools. Since the layout is a convention, two HDF5 datasets are not necessarily compatible.
MCAP
MCAP is an open-source container for multimodal log data. It holds multiple channels of timestamped messages in any serialisation, including Protobuf, ROS and JSON. Its maintainers state that it is the default log format in ROS 28.
MCAP is a logging format. It records everything a robot published, in time order, and leaves episode structure to a later step. It suits vehicles and ROS-based robots where the raw log is the record of truth.
Side by side
| Format | Stores | Reads into | Typical use |
|---|---|---|---|
| LeRobotDataset v3.02 | Parquet tables, MP4 video, JSON and Parquet metadata | LeRobot, PyTorch, Hugging Face Hub | Imitation learning and VLA fine-tuning |
| RLDS34 | Episodes of steps | TensorFlow Datasets | Open X-Embodiment style co-training |
| HDF567 | Arrays per trajectory | robomimic, ALOHA code, any HDF5 reader | Single-task policies, lab pipelines |
| MCAP8 | Timestamped message channels | ROS 2 tooling | Raw logs from vehicles and ROS robots |
Converting
Conversion is routine but not free. Hugging Face's guide to porting large datasets uses DROID as its example. The dataset is 1.7 TB in RLDS form and 8.7 TB as raw data, and it has to be converted from TensorFlow records before LeRobot can read it9.
Vendors that deliver data name their formats in similar terms. Robotics Center lists HDF5 for ACT, ALOHA and robomimic, RLDS for Open X-Embodiment and Octo, and LeRobot with Parquet10. RoboPilots delivers LeRobot, RLDS or HDF5, and MCAP or ROS 2 bags for vehicles1.
Choosing
- Ask what the training code loads today. That is the delivery format.
- Record raw, deliver converted. Keep the original recording so that a conversion bug can be fixed without collecting again.
- Write the schema down. Camera names, resolutions, frame rate, action space and units. A policy trained on a dataset expects the same camera names and resolution at deployment11.
- Load a sample before collecting at scale. Ten episodes through the real training loader will expose most format problems.
- Store the protocol version and outcome with every episode. Filtering later depends on it.
The end state is a dataset that loads into the training job with no manual steps, in a layout documented well enough that a new engineer can read it on their first day.
Questions buyers ask
What is the LeRobot dataset format?
LeRobotDataset v3.0 stores low-dimensional signals such as states, actions and timestamps in Apache Parquet, camera frames as MP4 video, and metadata describing the schema, frame rates, statistics and episode boundaries. It is included in lerobot 0.4.0 and later.
What is RLDS?
RLDS is a format in which a dataset is a set of episodes and each episode is a sequence of steps holding an observation, an action and flags such as is_first and is_last. It loads through TensorFlow Datasets and is the format of the Open X-Embodiment collection.
Can RLDS data be converted to LeRobot format?
Yes. Hugging Face documents the port of the DROID dataset from RLDS to LeRobotDataset v3.0. DROID is 1.7 TB in RLDS form.
Sources
- How to collect teleoperation data for robot learning (LeRobot, RLDS, HDF5). RoboPilots, 9 Oct 2026. Accessed 11 Nov 2026.
- LeRobotDataset v3.0. Hugging Face LeRobot documentation. Accessed 11 Nov 2026.
- RLDS: reinforcement learning datasets (README). Google Research (GitHub). Accessed 11 Nov 2026.
- Open X-Embodiment repository. Google DeepMind (GitHub). Accessed 11 Nov 2026.
- Open X-Embodiment: robotic learning datasets and RT-X models. arXiv (Open X-Embodiment Collaboration), 13 Oct 2023. Accessed 11 Nov 2026.
- robomimic: dataset overview. robomimic documentation. Accessed 11 Nov 2026.
- ALOHA repository (README). Zhao et al. (GitHub). Accessed 11 Nov 2026.
- MCAP: a container file format for multimodal log data. Foxglove. Accessed 11 Nov 2026.
- Porting large datasets to LeRobot Dataset v3.0. Hugging Face LeRobot documentation. Accessed 11 Nov 2026.
- Custom robot data collection services. Robotics Center. Accessed 11 Nov 2026.
- Imitation learning on real-world robots. Hugging Face LeRobot documentation. Accessed 11 Nov 2026.
Updated 11 Nov 2026: First published.