What is LeRobot?
LeRobot — an open-source library and dataset format for robot learning, which fixes how episodes, video and state are stored so datasets can be shared.
LeRobot is an open-source project from Hugging Face that does for robot data roughly what a standard image format did for computer vision: it fixes a layout, so a dataset written by one lab can be read by another lab's training script without a conversion project. Low-dimensional state and action live in Parquet files, camera streams live as MP4, timestamps tie the two together, and datasets and trained checkpoints are hosted next to the code.
The value is in the tooling around the format. Recording, converting from other formats, training and evaluating are all covered, and the library ships reference implementations of several policy architectures that train on a LeRobot dataset without modification. For a team holding data in a homegrown format, conversion is usually the first piece of work — and doing it into a standard format rather than another bespoke one is what makes the data reusable by the next person who touches it.
For a buyer, the format question belongs at specification time, not at delivery. A dataset delivered in a documented, widely supported format is one you can hand to a new engineer without a briefing; a folder of HDF5 files with a README describing half the fields costs a week before anyone trains anything. If the target format is LeRobot, put it in the brief — retrofitting after collection is possible, but it is work that did not have to happen.
Related terms
-
Robot Manipulation Data
Robot Manipulation Data — episodes of a robot arm moving objects, recorded together with the commands that produced the motion.
-
Open X-Embodiment
Open X-Embodiment — a pooled collection of robot datasets spanning 22 different robot embodiments, built to test whether data from one robot helps another.
-
Robot Data Annotation
Robot Data Annotation — attaching labels to robot episodes: what the task was, whether it succeeded, and when key events happened.
Keep reading
-
Full glossary
Every term we explain, in one list.
-
How to buy training data
Where these terms actually show up, and which ones change a quote.
-
Help center
How a project runs, from specification to delivery.
Submit a sourcing request
Tell us the language, the hours, and what the data needs to look like. You will get a real number and a real timeline — not a range. If we cannot source it well, we will tell you that instead.
- Pilot batch before the full run, so problems surface early.
- Consent documentation delivered with the data.
- No medical or clinical data. No recorded telephone calls.