What is DROID Dataset?
DROID Dataset — a large in-the-wild robot manipulation dataset collected by a multi-lab consortium, notable for scene diversity rather than task repetition.
DROID — Distributed Robot Interaction Dataset — was assembled by a consortium of 13 university labs and released in 2024. The hardware is a Franka Panda arm mounted on a rolling cart, which is what let one rig move between locations: roughly 76,000 trajectories, about 350 hours, spread across 564 scenes in 52 buildings. The task list is deliberately broad rather than deep — on the order of 86 task types — with each location contributing its own objects and its own layout.
Each episode carries four camera streams, two mounted on the wrists and two stereo cameras on the cart, plus three natural-language instructions written independently by different annotators. That three-annotation design is unusual and deliberate: it gives the same episode several valid phrasings, which is what a model needs in order to learn that "pick up the cup" and "grasp the mug" describe the same behavior. Distribution is in RLDS, the same format that carries Open X-Embodiment.
What DROID is for is scene and object diversity. A single-lab dataset teaches one kitchen; DROID teaches that kitchens differ. If the problem you have is that a policy works in your test room and fails everywhere else, that is the gap this kind of set targets — and the practical question about any in-the-wild collection is not how many hours it holds but how many distinct scenes and objects those hours are spread across.
Related terms
-
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 Manipulation Data
Robot Manipulation Data — episodes of a robot arm moving objects, recorded together with the commands that produced the motion.
-
Vision-Language-Action Model
Vision-Language-Action Model — a model that takes camera images and a written or spoken instruction and outputs robot actions directly.
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.