Dataset profile
cadene/droid_1.0.1: Large-Scale Franka Manipulation Dataset
The cadene/droid_1.0.1 dataset delivers 95,600 robot manipulation episodes totaling 27.6 million frames captured at 15 FPS from Franka robotic arms, released under the permissive Apache-2.0 license. Created using the LeRobot framework, the data is structured across 95 chunks with synchronized multi-view video streams (286,800 total videos), making it suitable for training vision-language-action models, imitation learning policies, and world models that require diverse real-world manipulation trajectories. Robotics teams building foundation models or deploying teleoperation systems can integrate this dataset immediately for commercial applications without restrictive licensing barriers.
Quick facts
- Scale
- 95,600 episodes, 27.6M frames
- License
- Apache-2.0
- Robot platform
- Franka robotic arm
- Frame rate
- 15 FPS
- Format
- Parquet episodes + video
- Commercial use
- Permitted
Dataset composition and structure
The cadene/droid_1.0.1 dataset organizes 95,600 manipulation episodes into 95 chunks of 1,000 episodes each, with episode data stored in Parquet format and synchronized video streams provided separately. Each episode captures Franka arm interactions at 15 frames per second, yielding a total of 27,612,581 frames across the entire collection. The multi-camera setup produces 286,800 video files, averaging three video perspectives per episode to support spatial reasoning and viewpoint-invariant policy learning. This chunked architecture enables efficient streaming and partial loading during training, allowing teams to scale data ingestion without exhausting local storage or memory. The LeRobot v2.1 codebase underpins the data pipeline, ensuring compatibility with modern robotics stacks and reproducible preprocessing workflows. All episodes belong to a single training split, simplifying curriculum design for teams that prefer custom validation partitioning based on task diversity or temporal distribution.
- 95 chunks of 1,000 episodes enable incremental data loading
- Three synchronized video streams per episode support multi-view reasoning
- LeRobot v2.1 pipeline ensures reproducible preprocessing
Licensing and commercial deployment
Released under the Apache-2.0 license, cadene/droid_1.0.1 grants robotics teams unrestricted rights to use, modify, and distribute the data in both research and commercial products. Unlike datasets encumbered by non-commercial clauses or attribution-share-alike requirements, Apache-2.0 permits proprietary model training, SaaS deployment, and integration into closed-source robotics platforms without revenue-sharing obligations. This licensing posture makes the dataset particularly valuable for startups and enterprise teams building differentiated manipulation capabilities where training-data provenance must withstand procurement and legal review. Teams should retain a copy of the Apache-2.0 notice in any derivative works, but no further compliance burdens apply. The permissive terms also facilitate dataset mixing, allowing engineers to blend cadene/droid_1.0.1 with proprietary teleoperation logs or other open collections to increase task coverage and domain diversity without license conflict.
Procurement and integration workflow
Robotics teams can download cadene/droid_1.0.1 directly from Hugging Face, where the dataset has already accumulated over 381,000 downloads, signaling broad adoption and community vetting. The chunked Parquet structure integrates seamlessly with PyTorch DataLoader pipelines, Dask for distributed preprocessing, and cloud object stores like S3 or GCS for on-demand streaming during large-scale training runs. Because the data was generated using LeRobot, teams already operating LeRobot-based pipelines inherit compatible observation schemas, action spaces, and metadata conventions, reducing integration overhead to near zero. For organizations that require additional annotations, re-labeling of specific task segments, or augmentation with proprietary scene variations, the dataset's open format and permissive license support derivative dataset creation without renegotiating access terms. Procurement leads should note that no vendor lock-in, usage metering, or API rate limits apply, enabling predictable budgeting and infrastructure planning for multi-month training campaigns.
Known limitations and fit considerations
While cadene/droid_1.0.1 offers substantial scale and permissive licensing, the dataset does not enumerate task labels or semantic annotations in the public metadata, limiting its utility for teams that require supervised task classification or goal-conditioned training out of the box. The exclusive focus on Franka hardware means that policies trained solely on this data may require sim-to-real transfer, domain randomization, or hardware adapter layers when deploying to other manipulator kinematics such as UR5, Kinova, or custom grippers. The 15 FPS capture rate, while sufficient for many manipulation primitives, may undersample fast dynamics like impact-based insertion or high-speed pick-and-place, necessitating supplementary high-frequency datasets for those behaviors. Teams targeting mobile manipulation, outdoor navigation, or multi-robot coordination will find limited signal here, as the data centers on single-arm tabletop interactions. Finally, the absence of publicly documented evaluation benchmarks or canonical train-test splits requires practitioners to design their own validation protocols, which can complicate reproducibility claims and cross-team performance comparisons.
Related pages
Use these to move from category-level context into specific task, dataset, format, and comparison detail.
FAQ
What is the cadene/droid_1.0.1 dataset and what does it contain?
The cadene/droid_1.0.1 dataset is a large-scale robot manipulation collection comprising 95,600 episodes and 27.6 million frames recorded from Franka robotic arms at 15 frames per second. Created using the LeRobot v2.1 framework, each episode pairs Parquet-serialized state-action trajectories with three synchronized video streams, yielding 286,800 total video files. The data is partitioned into 95 chunks of 1,000 episodes each to facilitate incremental loading and distributed training. All episodes are assigned to a single training split, and the dataset does not include explicit task labels or semantic annotations in the published metadata, leaving task segmentation and goal inference to downstream processing pipelines.
What license governs cadene/droid_1.0.1 and can I use it commercially?
The dataset is released under the Apache-2.0 license, one of the most permissive open-source licenses available. Apache-2.0 grants you the right to use, reproduce, modify, and distribute the data in both research and commercial settings without paying royalties, obtaining additional permissions, or disclosing proprietary modifications. You may train foundation models, deploy teleoperation systems, or integrate learned policies into commercial robots and SaaS products. The only requirement is to include a copy of the Apache-2.0 license notice in any redistributed or derivative works. This makes cadene/droid_1.0.1 suitable for startups, enterprise R&D teams, and academic labs alike, with no restrictions on revenue generation or proprietary use.
Who should use the cadene/droid_1.0.1 dataset?
Robotics teams building vision-language-action models, imitation learning policies, or world models for tabletop manipulation will find this dataset highly relevant, especially if they operate Franka robotic arms or can apply sim-to-real transfer techniques. The scale—95,600 episodes and 27.6 million frames—supports pre-training of large transformer-based policies and provides sufficient diversity for data augmentation experiments. Teams already using the LeRobot framework benefit from immediate compatibility with observation schemas and metadata conventions, reducing integration time. Commercial entities that require permissive licensing for proprietary model training will appreciate the Apache-2.0 terms, which impose no revenue-sharing or non-commercial restrictions. Organizations with established data pipelines for Parquet and multi-view video ingestion can onboard this dataset with minimal infrastructure changes.
When is cadene/droid_1.0.1 not the right choice for my project?
If your deployment targets non-Franka manipulators—such as UR5, Kinova, or custom grippers—you may face kinematic mismatches that require adapter networks, domain randomization, or additional real-robot data collection to bridge the sim-to-real gap. The dataset does not provide task labels or goal annotations in the public metadata, so teams needing supervised task classification, language-conditioned goals, or semantic segmentation must invest in annotation pipelines or heuristic labeling before training. The 15 FPS capture rate may undersample fast dynamics like impact insertion or high-speed bin picking, making supplementary high-frequency datasets necessary for those behaviors. Finally, mobile manipulation, outdoor navigation, bimanual coordination, and multi-robot scenarios receive no coverage here, so teams focused on those domains should source alternative or complementary datasets to achieve task coverage.
How do I download and integrate cadene/droid_1.0.1 into my training pipeline?
The dataset is hosted on Hugging Face and can be downloaded using the Hugging Face datasets library or direct HTTP access to the repository at https://huggingface.co/datasets/cadene/droid_1.0.1. The chunked Parquet structure integrates naturally with PyTorch DataLoader, Dask, and cloud object stores like S3 or GCS, enabling efficient streaming and partial loading during distributed training. Because the data was generated with LeRobot v2.1, teams already operating LeRobot-based workflows inherit compatible schemas for observations, actions, and metadata, minimizing preprocessing boilerplate. For custom pipelines, you can parse the Parquet episode files and synchronize video frames using the published metadata in meta/info.json, which specifies chunk boundaries, episode indices, and video paths. No API keys, usage metering, or vendor approvals are required, so you can scale data ingestion predictably across on-premise clusters or cloud compute.
What are the main technical limitations I should plan for?
The dataset focuses exclusively on Franka arm interactions, so kinematic and gripper differences will require transfer learning or hardware-specific fine-tuning when deploying to other platforms. Task diversity and semantic annotations are not documented in the public metadata, meaning you must infer task boundaries from state-action sequences or apply unsupervised segmentation methods if goal-conditioned training is essential. The 15 FPS sample rate, while adequate for many manipulation primitives, may miss fast transients in contact-rich or high-speed tasks, potentially necessitating augmentation with higher-rate datasets or simulation. The absence of canonical train-test splits and standardized benchmarks places the burden of evaluation protocol design on your team, which can complicate reproducibility and cross-study comparisons. Finally, the dataset does not cover mobile bases, outdoor environments, or multi-agent scenarios, so pipeline architects must source additional data if those capabilities are in scope.
Need data like cadene/droid_1.0.1: Large-Scale Franka Manipulation Dataset?
If your project needs similar modality, scale, or licensing, truelabel can surface comparable open datasets or match you with capture partners that deliver to spec.
Access on Hugging Face