Field notes · data collection modalities

How much data, collected which way

Robot manipulation training data spans five genuinely different collection methods — from passive internet video down to a human physically teleoperating the exact robot arm. Scale drops by orders of magnitude at each step down this ladder. This page lays out what's actually disclosed, by whom, per modality — see the companion Robot Learning at Scale link map for the underlying sources.

How to read this. Bars use a log scale — each gridline is 10× the last — because the true range here is seven orders of magnitude (hours to tens of millions of hours). A striped bar means the number is a derived estimate, not the source's own stated figure. flagged means the figure comes from a 2026 company disclosure not yet independently reproduced. Where a category has no honest aggregate to report, that's stated directly rather than filled in.
Scale by collection modality hours of data · log scale
Internet video Egocentric, head-mounted Wrist / hand-mounted UMI (handheld gripper) Robot teleoperation
Internet video — no robot, no action labels
CosmosNVIDIA · 2025
20.0M hrs
V-JEPA 2Meta · 2025
1.0M hrs
Egocentric video — head-mounted camera, human, no robot
Ego4DMeta · 2021
3,670 hrs
Ego-Exo4DMeta · 2024
1,422 hrs
EgoDexApple (Vision Pro) · 2025
829 hrs
EPIC-KITCHENS-100Bristol/others · 2018/2020
100 hrs
Wrist / hand-mounted camera — distinct from UMI's gripper tool
no standalone dataset at scale identified
—
UMI — handheld gripper tool, human operator, no robot present
UMI, largest single taskColumbia/TRI/MIT · 2024
~12 hrs
Robot teleoperation — human drives the real robot directly
RT-1Google · 2022
~722 hrs
RoboTurkStanford · 2019
111 hrs
DROIDBerkeley · 2024
350 hrs
1 10 100 1K 10K 100K 1M 10M+

Striped fill = derived estimate, not the source's own stated number (RT-1: 130,000 episodes × 20s, the midpoint of the paper's own stated 10–30s/episode range at 3Hz control; UMI: no paper-wide total exists — bar shown is the single largest reported task-level collection, ~1,400 episodes at 12 person-hours, extrapolated only as an upper illustrative bound, not a claim about UMI's typical scale). BridgeData V2 (60,096 trajectories) is omitted from this hours-based chart — no reliable episode-length figure could be confirmed to convert it honestly; see its demo-count entry in the table below instead.

Internet video

2 sources + partial

No robot, no action labels, not necessarily egocentric — third-person web-scale video, used to pretrain a general visual/world model before any robotics-specific data is introduced.

1M – 20M hrs range across the two disclosed figures — a mean is close to meaningless at 20× spread; report the range.
SourceScaleWhat it's used for
CosmosNVIDIA 20,000,000 hrs World Foundation Models pretraining corpus: driving + robotics + human-interaction + industrial video. Feeds synthetic-data generation for GR00T and other manipulation policies.
V-JEPA 2Meta 1,000,000+ hrs Action-free internet video pretraining. The robot-capable variant (V-JEPA 2-AC) is then post-trained on under 62 hrs of unlabeled DROID robot video — a small, separate second stage.
GR00T N1NVIDIAnot quantified "internet-scale" The Eagle-2 VLM backbone is described as pretrained on internet-scale data, but no dataset size is given in the paper — the web tier of GR00T's four-tier pyramid is stated qualitatively only.
Genie / Genie 2 / Genie 3DeepMindnot disclosed — None of the three Genie blog posts or papers give a training-data hour count — scale is described only as "internet-scale video," with no figure across any of the three generations.

Egocentric video, head-mounted

4 sources

A person wears a head- or chest-mounted camera doing everyday or task-specific activity. No robot, no handheld tool — the camera rides the body. This is the tier GR00T N1 names as the base of its data pyramid (Ego4D, Ego-Exo4D, EPIC-KITCHENS, Assembly-101, HOI4D, HoloAssist are all cited as sources) without giving an aggregate figure of its own.

≈ 1,505 hrs mean across the 4 sourced datasets (3,670 + 1,422 + 829 + 100, ÷ 4) — spans 100 to 3,670 hrs, a real but much narrower spread than internet video.
SourceScaleNote
Ego4DMeta 3,670 hrs 3,025 hours of daily-life egocentric video from 74 locations across 9 countries.
Ego-Exo4DMeta 1,422 hrs 221 hrs egocentric + matched exocentric (third-person) footage of skilled human activities, paired for cross-view learning.
EgoDexApple 829 hrs 338k demonstrations, 194 tasks, captured via Vision Pro hand-tracking — headset-based, not a worn camera per se; the closest bridge to the wrist-cam category below.
EPIC-KITCHENS-100Bristol et al. 100 hrs Kitchen-activity footage, extended version of the original EPIC-KITCHENS release.

Wrist / hand-mounted camera

0 standalone sources

A camera worn on the wrist or hand itself — distinct from a head-mounted rig and distinct from UMI's handheld gripper-jaw tool. This is the category the trajectory implies should exist between "egocentric video" and "UMI," and it largely doesn't as a standalone public dataset.

No dataset found. This is a genuine gap, not an omission — see below.
⚠ Searched specifically for a large-scale, standalone "human wears a wrist camera, no gripper tool, no headset" dataset. Found none. The closest adjacent things: DROID mounts a wrist camera, but as one sensor on an actual robot teleop rig — the wrist-cam footage isn't a separable human-only dataset. EgoDex captures hand pose via Vision Pro headset tracking, which is functionally hand-centric but mechanically a headset, not a worn wrist camera. As far as this research found, "pure wrist-cam, human-only, at scale" is a real hole in the public literature, not a category anyone has published a flagship dataset for yet — UMI effectively occupies the niche this category would fill, by putting a camera at the point of manipulation but attached to a gripper tool rather than the wrist itself.

UMI — handheld gripper tool

5 task-level figures, no aggregate

A human holds a physical gripper-jaw tool with a mounted camera and performs the task by hand — no robot present during collection, but the resulting trajectory is directly usable as robot action data. UMI's paper (Columbia/TRI/MIT, 2024) never states a corpus-wide total — every number in it is per task.

No paper-wide aggregate exists. Per-task episode counts below are the only real numbers published.
TaskEpisodesNote
Cup arrangement, in-the-wild 1,400 episodes 12 person-hours, 3 demonstrators, 30 locations — the largest single collection reported in the paper.
Cup arrangement, narrow domain 305 episodes 2 demonstrators, controlled setting.
Dynamic tossing 280 episodes —
Bimanual cloth folding 250 episodes 2 demonstrators.
Dish washing 258 episodes 1 demonstrator.
⚠ UMI's own headline claim is collection throughput, not corpus size: the paper reports 48–64% of bare-hand demonstration speed, and roughly 3× faster than teleoperation in matched 15-minute collection windows — a rate, never converted to an absolute demos/hour figure or grand total across tasks. The funnel-chart bar above uses the largest single reported task (1,400 episodes / 12 person-hours ≈ 117 episodes/hr) purely as an illustrative upper bound, not a claim about UMI's typical or average scale.

Robot teleoperation

6 sources

A human directly drives the real robot — leader-follower rigs (ALOHA-style), VR teleop, joysticks. Highest fidelity (the action labels are the exact robot's own joint commands, no retargeting needed) and by far the most expensive per hour: the robot hardware, the space, and a skilled operator all have to be present simultaneously.

≈ 394 hrs mean across the 3 sources with genuine hour figures (RT-1 ~722 est., DROID 350, RoboTurk 111 ÷ 3) — BridgeData V2, ACT, and Mobile ALOHA use demo-counts, not hours, and aren't averageable into this figure.
SourceScaleNote
RT-1Googlederived 130,000 episodes
≈722 hrs (est.)
700+ tasks, 13 robots, 17 months of collection. Hour figure derived from 130k episodes × 20s (midpoint of the paper's own stated 10–30s/episode range at 3Hz control) — not the paper's own stated total.
DROIDBerkeley 76,000 trajectories
350 hrs
564 scenes, 84 tasks, 50 collectors across 3 continents, 12 months. Author-stated figure, not derived.
BridgeData V2Berkeleyhrs not disclosed 60,096 trajectories 24 environments, 13 skills, low-cost hardware. The paper reports trajectory count, not aggregate hours, and no reliable per-episode duration could be confirmed to convert it honestly — left as a demo-count rather than a guessed hour figure.
RoboTurkStanford 111+ hrs 54 crowdsourced users, 3 tasks, 1 week — the only crowdsourced (vs. single-operator) figure in this table.
Mobile ALOHAStanford 50 demos/task No aggregate hours stated — demo-count is the unit the paper reports in.
ACT / ALOHAStanford ~10 min/task The paper's headline result: strong performance from roughly 10 minutes of demonstration per task — the smallest figure in this entire page.
The one takeaway that survives scrutiny. The trajectory — internet video → egocentric video → UMI → robot teleop — really does drop by orders of magnitude at each step: internet video (10⁶–10⁷ hrs) is roughly 1,000× egocentric video (10³ hrs), which dwarfs UMI and teleop (10⁰–10² hrs, mostly reported in episode-counts rather than hours at all). But two categories in the middle of this ladder — wrist-mounted cameras and UMI's own aggregate scale — simply aren't documented publicly with real totals. That's not a gap in this page's research; it's a gap in what the field has chosen to disclose.