Cross-embodiment transfer is training one policy on data from bodies with different joint counts, action dimensions and sensors, or moving a policy to an unseen body. Open X-Embodiment pools data from 22 robot embodimentsSource 3, and human video adds a body whose actions are estimated from imagesSource 8.

An infographic framed by robot dataset thumbnails reading 1M episodes from 311 scenes, 34 research labs across 21 institutions, 22 embodiments, 527 skills and 60 datasets.
Open X-Embodiment pooled robot data into one training set: 1M episodes from 60 datasets, 22 embodiments and 527 skills, contributed by 34 labs at 21 institutions.
Paper figure: Open X-Embodiment Collaboration / arXiv. Licence: CC BY 4.0.

Try “Translate between bodies”.

Cross-embodiment
Describe hand motion, not joints, and human videos become usable
Way to share one action list
Adjust more
All 32 slots for: Shared relative EEF space
7-DoF arm7 joint targets + gripper (illustrative)8 shared dims (toy); wrist and hand actions not separately modelled
dim 1: driven dimdim 2: driven dimdim 3: driven dimdim 4: driven dimdim 5: driven dimdim 6: driven dimdim 7: driven dimdim 8: driven dimdim 9: unused dimdim 10: unused dimdim 11: unused dimdim 12: unused dimdim 13: unused dimdim 14: unused dimdim 15: unused dimdim 16: unused dimdim 17: unused dimdim 18: unused dimdim 19: unused dimdim 20: unused dimdim 21: unused dimdim 22: unused dimdim 23: unused dimdim 24: unused dimdim 25: unused dimdim 26: unused dimdim 27: unused dimdim 28: unused dimdim 29: unused dimdim 30: unused dimdim 31: unused dimdim 32: unused dim
bimanual setuptwo arms, two grippers (illustrative)8 shared dims (toy); wrist and hand actions not separately modelled
dim 1: driven dimdim 2: driven dimdim 3: driven dimdim 4: driven dimdim 5: driven dimdim 6: driven dimdim 7: driven dimdim 8: driven dimdim 9: unused dimdim 10: unused dimdim 11: unused dimdim 12: unused dimdim 13: unused dimdim 14: unused dimdim 15: unused dimdim 16: unused dimdim 17: unused dimdim 18: unused dimdim 19: unused dimdim 20: unused dimdim 21: unused dimdim 22: unused dimdim 23: unused dimdim 24: unused dimdim 25: unused dimdim 26: unused dimdim 27: unused dimdim 28: unused dimdim 29: unused dimdim 30: unused dimdim 31: unused dimdim 32: unused dim
humanoid29 illustrative coordinates; not hardware DoF8 shared dims (toy); wrist and hand actions not separately modelled
dim 1: driven dimdim 2: driven dimdim 3: driven dimdim 4: driven dimdim 5: driven dimdim 6: driven dimdim 7: driven dimdim 8: driven dimdim 9: unused dimdim 10: unused dimdim 11: unused dimdim 12: unused dimdim 13: unused dimdim 14: unused dimdim 15: unused dimdim 16: unused dimdim 17: unused dimdim 18: unused dimdim 19: unused dimdim 20: unused dimdim 21: unused dimdim 22: unused dimdim 23: unused dimdim 24: unused dimdim 25: unused dimdim 26: unused dimdim 27: unused dimdim 28: unused dimdim 29: unused dimdim 30: unused dimdim 31: unused dimdim 32: unused dim
human hand, egocentric video3D hand keypoints tracked from video8 shared dims (toy); wrist and hand actions not separately modelled
dim 1: driven dimdim 2: driven dimdim 3: driven dimdim 4: driven dimdim 5: driven dimdim 6: driven dimdim 7: driven dimdim 8: driven dimdim 9: unused dimdim 10: unused dimdim 11: unused dimdim 12: unused dimdim 13: unused dimdim 14: unused dimdim 15: unused dimdim 16: unused dimdim 17: unused dimdim 18: unused dimdim 19: unused dimdim 20: unused dimdim 21: unused dimdim 22: unused dimdim 23: unused dimdim 24: unused dimdim 25: unused dimdim 26: unused dimdim 27: unused dimdim 28: unused dimdim 29: unused dimdim 30: unused dimdim 31: unused dimdim 32: unused dim

Shared relative EEF space: N1.7 README: 20K hours of EgoScale human video

Shared relative EEF spaceGR00T N1.7

NVIDIA describes N1.7 relative end-effector actions shared across human and robot data. EgoScale separately specifies wrist deltas and retargeted hand joint actions; this eight-slot strip does not implement those adapters.

The N1.7 README reports 20K hours of EgoScale human video alongside robot demonstrations. The separate EgoScale paper also uses aligned human-robot mid-training.

Pad eachrobot's ownlistno way inTranslatebetweenbodiesno way inDescribewhere thehand goesOne armTwo armsHumanoidPersonon videoOnly this way can a person'svideo fill the robot's slots
driven by this sourcezero-paddinghatched: illustrative link, not model dimensionsunused
Robots have different bodies; describing actions as where the hand moves lets one model learn from many robots and from people on video.
How this was made

A model trained on many robots needs one action list that every body can write into. Each bar here is an illustrative 32-slot vector. The robot rows use toy widths: 8 coordinates for a 7-DoF arm (seven joint targets and a gripper; DoF counts the joints that move independently), 16 for two arms with two grippers, and 29 for a humanoid, which is not its hardware DoF count. A person on video has no joint targets at all, only 3D hand keypoints tracked from the footage.

Padding gives each robot its own leading slots and fills the rest with zeros; this toy models no adapter for human data. Motion transfer, in the Gemini Robotics 1.5 report, aligns embodiments during training; the 3 hatched slots are an illustrative link, not a disclosed latent. A shared relative end-effector (EEF) space describes where the hand or gripper moves relative to where it is, so a tracked human hand can fill the same 8 slots. NVIDIA's GR00T N1.7 README reports relative EEF actions shared across robot data and 20K hours of EgoScale human video; the EgoScale paper (Zheng 2026) separately uses wrist deltas, retargeted hand joint actions and aligned human-robot mid-training. The strips do not implement those adapters.

Shared relative end-effector space is illustrated with 8 shared slots. N1.7 reports 20K hours of EgoScale human video; EgoScale separately uses wrist deltas, hand joint targets and aligned mid-training. These operations are not implemented by the strips.

Current cross-embodiment mapping
strategy
Shared relative EEF space
human video
N1.7 README: 20K hours of EgoScale human video
embodiments
4
strip width
32 slots
Original slot illustrations; strip widths and the 8-, 16- and 29-coordinate robot rows are toy choices.
10K hours
pi0 own demonstrations
7 configurations, 68 tasks; additional public data is separate
22 embodiments
OXE v9 dataset
RT-X experiments used nine, not all 22
20K hours
N1.7 human pretraining
EgoScale human video, alongside robot demonstrations; README report
about 2×
PI generalization gain
human-robot co-fine-tuning; four human-only generalization scenarios

Counting robot and human data

π0's 10,000 hours are its own data from 7 robot configurations and 68 tasks; by timesteps, the open-source OXE, DROID and Bridge data are 9.1% of the mixtureSource 1. RT-X experiments used 9 of OXE's 22 embodimentsSource 3, and GR00T N1.7's rounded 20K pretraining hours are EgoScale human videoSource 7.

Moritz Reuss wrote in October 2025 that "OXE is mostly low-quality data" and that imitation learning lacks good ways to measure data qualitySource 4. Re-Mix's learned mixture weights beat uniform weights by 38% on averageSource 11, and Toyota Research Institute's controlled study of 89 policies found co-training with cross-embodiment robot data improves generalization to distribution shifts and unseen tasksSource 28.

Robot action interfaces

π0 zero-pads every action vector to the largest robot's 18 dimensionsSource 1. Octo curates 25 OXE datasets with delta end-effector control and aligns grippers to one convention, adding lightweight encoders or heads for new spacesSource 2, while CrossFormer trains one transformer on 900K trajectories from 20 embodiments without manually aligning observation or action spacesSource 12.

HPT maps each embodiment's proprioception and vision to a few tokens for a shared trunk, scaling to 52 datasetsSource 13. LAP writes low-level actions as natural language, and LAP-3B reports over 50% average zero-shot success on unseen robots, about twice the strongest prior VLAsSource 14.

Motion Transfer across robot embodiments

Gemini Robotics 1.5 trains on ALOHA, bi-arm Franka and Apptronik Apollo data plus Internet text, images and video, with Motion Transfer, an architecture and training recipe that aligns embodiments. On tasks demonstrated only on another robot it helps, less so for Apollo, in ablations run interleaved on one work cell; one checkpoint drives all three robots, though the long-horizon agent adds bi-arm Franka post-training, and the report specifies an orchestrator over the VLA but not the alignment representationSource 5. DeepMind says tasks shown only to ALOHA 2 "just work" on Apollo and bi-arm Franka, and vice versaSource 15.

DeepMind says On-Device 2, natively multi-embodiment with Motion Transfer, adapts to new bi-arm robots in a few hours, typically from fewer than 200 examplesSource 6.

Relative end-effector actions for robots and humans

GR00T N1 embedded state and action with embodiment-aware encodersSource 16; N1.6 moved most embodiments to state-relative action chunks, which NVIDIA found smoother and more accurate than absolute actionsSource 17. N1.7 shares relative end-effector deltas between human and robot embodiments and calls this a key factor in cross-embodiment performanceSource 7.

Shared actions
The hand's motion transfers between bodies; joint angles do not
The robot copies the person's
Faint: the person's check mark, placed at the robot's startJoint angles copied · strays 6.8 cm

Arm lengths, poses and the stroke are illustrative; the geometry is exact

Sent as joint angles, a person's stroke comes out skewed on a robot of other proportions; sent as the hand's motion, it matches.
How this was made

Robots and people have different joints and different link lengths, so one body's joint angles mean little to another. GR00T N1.7 writes actions as deltas from the hand's current pose, shared by robot and human embodiments, and NVIDIA calls this a key factor in its cross-embodiment performance: because the representation is the same for human and robot data, priors learned from human video carry over to robot control. EgoScale likewise uses relative wrist motion, and N1.6 moved most embodiments to state-relative action chunks.

The drawing is two easels on one bench. At the left a mannequin arm holds a pen to its squared sheet and draws a check mark. At the right a robot arm with shorter links holds its pen to the other sheet. The copy box between them carries the person's movement to the robot, and its lever picks what is sent. To the left, the shoulder and elbow angles go across as they are, and on the shorter arm they trace a smaller, skewed stroke. To the right, the hand's motion from the stroke's start goes across, the robot works out its own angles for it, and its ink lands on the faint check mark, which is the person's stroke placed at the robot's start.

The arms' lengths, the poses and the stroke are illustrative; the geometry is exact. Real arms have more joints, which makes copying angles across bodies harder still.

NVIDIA, Isaac GR00T repository (2026); NVIDIA GEAR, GR00T N1.6 (2025); Zheng and colleagues, EgoScale (2026).
A three-stage diagram with photographs: egocentric human videos of hands doing chores, paired human and robot play data, and a humanoid robot hand performing dexterous tasks after post-training.
EgoScale pretrains on human video, mid-trains on aligned human and robot play, then post-trains on robot tasks. The pretraining stage uses 20,854 hours of egocentric video with wrist motion and retargeted hand actions.
Paper figure: Ruijie Zheng et al. / arXiv. Licence: CC BY 4.0.

EgoScale uses relative wrist motion and retargets 21 human hand keypoints to the 22-DoF Sharpa hand, with embodiment-conditioned adapters for proprioception and hand actions around a shared backbone and action expertSource 8. Morphometric Imitation (September 2026) retargets reconstructed hand-object interactions across hand morphologies, then refines them with residual RL; on a Sharpa hand its policies reached 89.3% zero-shot success in 300 real trials on 30 objectsSource 10.

Closing the visual embodiment gap

Mirage masks out an unseen target robot and inpaints the source robot in real timeSource 18. RoVi-Aug synthesizes training images with other robots and viewpoints and deploys zero-shot on an unseen robot, and co-training with it raises success by up to 30%Source 19.

Latent actions as a shared interface

LAPA learns discrete latent actions between video frames, pretrains a VLA on them and fine-tunes on robot data; training only on human video still transfers positivelySource 20. LAC-WM (Stanford and Meta FAIR, October 2026) conditions a robot world model on a latent action space shared across embodiments; picking action chunks for a VLA on five unseen LIBERO tasks, it raised average success from 82.4% with an explicit-action world model to 92.0%Source 32.

Human-to-robot transfer recipes

Simar Kareer's EgoMimic treated human and robot data equally and found an extra hour of hand data worth more than one of robot dataSource 21. On December 16, 2025, Kareer and Physical Intelligence colleagues co-fine-tuned π0.5 on human data, with 3D hand positions as actions, and the most relevant robot data. PI reports about 2× performance on four scenarios present only in human data, without trial counts, and transfer that improves as robot pretraining diversifiesSource 9.

A pipeline of photographs: a human hand demonstrates a task, the hand is inpainted out of the video, a rendered robot gripper is overlaid in its place, and a real robot then performs the task.
Phantom trains a robot policy without robot data by erasing the human hand from demonstration videos and rendering a robot arm in its pose. The policy then deploys zero-shot on a real robot, with success up to 92%.
Paper figure: Marion Lepert et al. / arXiv. Licence: CC BY 4.0.

EgoScale's Ruijie Zheng and coauthors instead pretrain on human video, mid-train on aligned human-robot data and post-train on task robot data, and find adding aligned mid-training best overallSource 8. EgoBridge aligns human and robot policy latents with optimal transport and reports a 44% absolute success gain over human-augmented cross-embodiment baselinesSource 22. EgoLAP (Princeton, Toyota Research Institute and Physical Intelligence, October 2026) routes human and robot trajectories through a shared chain of language actions and reached 80.1% mean real-world task progress on bimanual YAM robots, 2.3 times the alternative action representationsSource 31.

Phantom needs no robot data: it inpaints the human arm, overlays a rendered robot and deploys zero-shot, with success up to 92%Source 23. Masquerade robotizes in-the-wild human video and fine-tunes on 50 robot demonstrations per task, beating baselines by 5 to 6 timesSource 24. Figure reports that Index human-video pretraining, all else fixed, raised Helix 2.5's zero-shot success in 30 unseen homes from 9% to 56%Source 25, and Generalist's GEN-1 base model pretrains on over half a million hours from wearable devices on humans, with no robot dataSource 29.

Scaling the number of embodiments

Across about 1,000 procedurally generated locomotion bodies, adding embodiments generalizes more broadly than adding data on fixed onesSource 26. Skild reports training one model on 100,000 simulated robots and testing zero-shot on robots excluded from trainingSource 27. DreamZero adapted from AgiBot G1 to a YAM bimanual robot with 55 trajectories, about 30 minutes of play data, though its authors describe the result only qualitativelySource 30.