Introduction
A command to move the gripper five centimeters forward has a different physical meaning on a short tabletop arm, a mobile manipulator and a humanoid with a moving torso. Cross-embodiment learning tries to reuse data or policies across those bodies without pretending their joints, cameras and end effectors are identical.
This article explains action normalization, task-space control, embodiment tokens, shared latent spaces, retargeting, modular policies and robot-specific output heads. It examines multi-robot datasets and models, then separates what transfers easily, such as object semantics, from what remains embodiment-bound, such as contact geometry and torque. The evidence section asks which robots were included, whether the target robot was held out and how much fine-tuning remained. It also covers different action frequencies, dual-arm coordination, camera placement and the limits of calling a dataset cross-embodiment when its tasks do not overlap.
Key findings
- Visual semantics and task structure usually transfer more readily than precise motor commands.
- A shared action representation reduces mismatch but cannot erase different reach, compliance, grippers or control rates.
- Embodiment tokens identify the robot; target data is still needed when the model has not learned that body’s dynamics.
- Cross-embodiment evaluation should hold out a robot and report performance before and after adaptation.
- Dataset diversity is useful only when tasks and labels are aligned enough for the model to learn shared structure.
MULTI-BODY DOES NOT ALWAYS MEAN ZERO-SHOT
Cross-Embodiment Model Tracker
Track which Physical AI models genuinely support multiple robot bodies, what adaptation they require and whether zero-shot transfer is actually demonstrated.
Isaac GR00T N1.7
- Model
- Isaac GR00T N1.7
- Organization
- NVIDIA
- Support type
- Native multi-embodiment pretraining + target post-training
- Source embodiment
- Mixed humanoid / bimanual / semi-humanoid data
- Target embodiment
- Target robot configured through post-training
- Robot platforms
- Multiple robot embodiments
- Action representation
- Shared model representation with embodiment-specific data/configuration
- Adaptation required
- Yes - post-training for target embodiment/task is part of the workflow
- Fine-tuning
- Typically yes
- Zero-shot status
- True zero-shot transfer to an unseen embodiment is not assumed
- Real-world evidence
- Official real-robot workflows
- Verification
- Verified model capability; zero-shot embodiment claim not generalized
- Source
- NVIDIA GR00T
LingBot-VLA 2.0
- Model
- LingBot-VLA 2.0
- Organization
- Robbyant / Ant Group
- Support type
- Native multi-embodiment support
- Source embodiment
- 20 robot configurations
- Target embodiment
- Supported configurations / adapted robots
- Robot platforms
- 20 configurations spanning different robot morphologies
- Action representation
- 55-dimensional canonical action representation reported by project
- Adaptation required
- Configuration mapping and task adaptation may still be required
- Fine-tuning
- Task/robot dependent
- Zero-shot status
- Not treated as proven true zero-shot embodiment transfer
- Real-world evidence
- Official real-robot evidence
- Verification
- Verified multi-configuration training; zero-shot scope kept separate
- Source
- LingBot-VLA 2.0
XR-1
- Model
- XR-1
- Organization
- Beijing Humanoid Robot Innovation Center
- Support type
- Native cross-embodiment learning
- Source embodiment
- Heterogeneous training robots
- Target embodiment
- Six real robot embodiments in evaluation
- Robot platforms
- Six evaluated embodiments
- Action representation
- Unified Vision-Motion Codes
- Adaptation required
- Three-stage training includes task-specific post-training
- Fine-tuning
- Yes in the published training pipeline
- Zero-shot status
- Generalization is reported, but this database does not relabel it as zero-shot unseen-body transfer without matching protocol
- Real-world evidence
- >14,000 real-world rollouts across >120 tasks reported
- Verification
- Research result
- Source
- XR-1 project
RDT-1B
- Model
- RDT-1B
- Organization
- Tsinghua University / collaborators
- Support type
- Shared action-space model adapted across robot forms
- Source embodiment
- 46 multi-robot datasets
- Target embodiment
- Single-arm, bimanual and mobile manipulators
- Robot platforms
- Multiple modern manipulators
- Action representation
- Physically Interpretable Unified Action Space
- Adaptation required
- Fine-tuning / few-shot adaptation used for target skills
- Fine-tuning
- Yes for many target settings
- Zero-shot status
- Zero-shot object/scene generalization is reported; unseen-embodiment zero-shot is not inferred
- Real-world evidence
- Real-robot bimanual evaluations
- Verification
- Research result
- Source
- RDT-1B project
Octo
- Model
- Octo
- Organization
- UC Berkeley / collaborators
- Support type
- Multi-embodiment pretrained policy with target fine-tuning
- Source embodiment
- Cross-embodiment robot datasets
- Target embodiment
- Multiple target robots
- Robot platforms
- Multiple manipulation robots
- Action representation
- Shared policy representation with target adaptation
- Adaptation required
- Yes
- Fine-tuning
- Yes
- Zero-shot status
- Not represented as true zero-shot embodiment transfer
- Real-world evidence
- Real-robot adaptation/evaluation
- Verification
- Verified open project
- Source
- Octo project
Gemini Robotics 2
- Model
- Gemini Robotics 2
- Organization
- Google DeepMind
- Support type
- Cross-embodiment transfer demonstrated by developer
- Source embodiment
- Multiple robot forms
- Target embodiment
- Multiple robot forms shown in official research
- Robot platforms
- Humanoid and manipulation platforms
- Action representation
- Closed internal representation
- Adaptation required
- Exact adaptation budget is not uniformly disclosed
- Fine-tuning
- Not publicly normalized across demonstrations
- Zero-shot status
- Do not assume zero-shot unseen-body transfer
- Real-world evidence
- Official real-robot demonstrations
- Verification
- Official claim / demo
- Source
- Gemini Robotics 2
Methodology
Native multi-embodiment support, separate adaptation to multiple robots and true zero-shot unseen-embodiment transfer are labeled separately. Marketing claims are not upgraded into stronger evidence categories.
Cross-embodiment datasets and policy systems
The table focuses on representation and adaptation. Robot counts alone do not establish successful transfer.
| System | Robots included | Shared representation | Target transfer method | Held-out robot evidence | Public status | Main limitation |
|---|---|---|---|---|---|---|
| Open X-Embodiment / RT-X | 22 embodiments reported | Normalized trajectory and language dataset mixture | Cross-dataset training and target adaptation | Cross-embodiment studies reported | Data project public | Heterogeneous quality and action definitions |
| Octo | Nine training platforms reported | Tokenized observations with diffusion action head | Fine-tuning and robot-specific interfaces | Target-platform adaptation reported | Code and checkpoints public | Not zero-configuration on arbitrary robots |
| OpenVLA | Multiple source embodiments through Open X data | Tokenized multimodal policy | Target-robot fine-tuning | Real target-robot evaluations reported | Code and 7B weights public | Large model and embodiment-specific integration |
| GR00T N1.6 | Several humanoid embodiments targeted | Embodiment-conditioned policy representation | Adapters, fine-tuning and synthetic data | NVIDIA reports multi-embodiment evaluation | Open model release reported | Independent hardware replication limited |
| OSCAR | Multiple embodiments reported | Embodiment-aware predictive and action representation | Cross-robot adaptation | Author-reported held-out transfer | Paper; artifacts incomplete | Recent work with limited replication |
| HumanEgo | Human ego data and robot embodiments | Shared human-robot task representation | Retargeting and robot adaptation | Author-reported robot transfer | Paper | Human motion lacks direct robot force and action labels |
Performance values are omitted because tasks, targets and adaptation budgets are not comparable.
Definition learning across different bodies
Cross-embodiment learning uses data from one or more bodies to improve a policy or representation for another. Bodies may differ in arm length, number of joints, gripper type, mobility, cameras and control frequency. The target can be present during pre-training or held out entirely.
Multi-robot training is not automatically cross-embodiment transfer. If every robot performs unrelated tasks, the model may learn separate modes without sharing useful structure. Strong evidence shows that source-robot data improves a common target task or reduces target data compared with training from scratch.
How action spaces are aligned
Joint commands are embodiment-specific, so many datasets convert actions into task space end-effector translation, rotation and gripper state. Values are normalized by scale and control interval. A model may also predict keypoints, object-relative waypoints or latent action tokens that a robot-specific decoder converts into commands.
Task-space actions simplify sharing but hide feasibility. Two robots can request the same hand motion while one hits a joint limit or collides with its torso. Embodiment-specific heads, kinematic projection and low-level controllers restore robot constraints after the shared policy proposes an action.
Embodiment tokens and adapters
An embodiment token tells the model which hardware is active. Adapters modify a subset of parameters for the target robot, reducing fine-tuning cost. These mechanisms help separate common task knowledge from body-specific control, but they need representative target examples and do not create unseen mechanical capabilities.
Retargeting and shared latent spaces
Retargeting maps a source trajectory onto the target robot while respecting reach and joint limits. Shared latent spaces instead learn a representation where similar task phases align across bodies. Retargeting is explicit and interpretable; latent alignment can capture broader patterns but may conceal failure when bodies interact differently with the object.
Camera placement and action frequency
A wrist camera on one robot may be a head camera on another. The model must separate object appearance from viewpoint and know the transform between camera and action frame. External cameras can standardize observations in a laboratory but may not exist at deployment.
Action frequency changes the meaning of a delta. A ten-millimeter command at 5 hertz is not equivalent to the same command at 50 hertz. Datasets resample trajectories or include timing, but resampling can smooth contact events. Target controllers need explicit rate and latency handling.
Key datasets and models
Open X-Embodiment aggregates data from many institutions and enabled RT-X cross-robot studies. Octo and OpenVLA turn that mixture into open policies intended for target adaptation. Their public artifacts make it possible to inspect normalization and fine-tuning, although deployment still requires robot-specific code.
NVIDIA’s GR00T targets humanoids with embodiment-conditioned learning and synthetic data. OSCAR explores embodiment-aware predictive control, while HumanEgo studies transfer from human first-person behavior into robot embodiments. These newer results expand the source bodies but remain author-reported and task-specific.
Evidence from real robots
A strong experiment trains on several source robots, holds out the target embodiment and evaluates a common task before target fine-tuning. It then reports adaptation data and compares with a target-only baseline. Merely evaluating on a robot that contributed training data measures multi-robot coverage, not held-out transfer.
Real tests should include target camera geometry, gripper contact and control rate. Simulation can expand robot diversity but may understate mechanical mismatch. Reported gains are most credible when source data improves target performance with the same target-data budget and when negative transfer is disclosed.
What transfers across robots and what does not
Object identity, language grounding, coarse task phases and some object-relative motion patterns often transfer. Reaching toward a handle or moving an object from one region to another has shared structure. Learned visual features can recognize the same object across cameras after adaptation.
Precise grasp pose, force, collision clearance, balance and timing remain tied to the embodiment. A parallel gripper and five-finger hand create different contacts. A humanoid must coordinate torso and feet, while a fixed arm does not. Transfer should therefore be layered shared semantics and planning above embodiment-specific control and safety.
Failure modes and practical applications
Normalization can compress rare but important actions. The policy may confuse two robots with similar observations but different limits. A target adapter can overfit a small dataset. Retargeting may preserve hand position while producing unnatural joint motion. Negative transfer can make target learning slower than a target-only baseline.
Credible uses include initializing policies for new arms, sharing perception and task representations across a fleet and reducing demonstrations for related grippers. Zero-data transfer to arbitrary humanoids remains experimental. Deployment should measure target performance, not rely on source-robot benchmark scores.
Limitations and missing information
- Robot counts do not reveal task overlap, dataset balance or data quality.
- Held-out-embodiment protocols are uncommon and inconsistent.
- Task-space normalization can hide feasibility and timing differences.
- Closed humanoid datasets limit independent transfer analysis.
- Contact-rich and whole-body transfer remains substantially harder than semantic transfer.
Conclusion
Cross-embodiment learning is valuable because robot data is expensive and many tasks share visual and semantic structure. The transferable part, however, is not the entire controller. Object understanding, language and coarse task phases usually move across bodies more easily than contact, timing and dynamics.
Open X-Embodiment, Octo and OpenVLA provide the clearest public infrastructure for multi-robot learning. GR00T and newer embodiment-aware systems extend the idea toward humanoids, with less independent evidence. A rigorous transfer claim should hold out a target robot, state the adaptation budget and compare against target-only training. The practical architecture uses shared representations and task-space intent above robot-specific kinematics, control and safety.
Frequently asked questions
What is cross-embodiment robot learning?
Cross-embodiment learning uses data or representations from one robot or body to improve another. The robots may differ in joints, arm length, grippers, cameras or mobility. A strong result shows that source data reduces target training or improves a held-out target task compared with training only on target-robot data.
How can one policy work on different robots?
The policy can use normalized task-space actions, embodiment tokens, shared latent representations and robot-specific action heads. A kinematic or low-level controller converts common intent into feasible commands. Most systems still require target calibration, adapters or fine-tuning because cameras, reach, timing and contact differ across robots.
What is action normalization?
Action normalization converts robot commands into a shared scale and representation, such as end-effector position deltas and gripper state. It makes heterogeneous datasets easier to combine. The process must account for control frequency and physical limits; otherwise identical normalized values can produce different speeds, reach or contact on different hardware.
What transfers well across robot embodiments?
Visual object features, language grounding, task order and object-relative motion often transfer better than low-level control. For example, several robots can learn that a handle should be approached before a drawer moves. Exact grasp pose, force, collision clearance, balance and actuator timing usually need embodiment-specific adaptation.
Do cross-embodiment models need fine-tuning?
Usually. Fine-tuning or adapters align the policy with the target robot’s observations and actions. Some studies report zero-shot transfer for limited task-space interfaces, but arbitrary new robots differ in camera placement, kinematics and dynamics. The required target data should be reported rather than hidden inside integration work.
How should cross-embodiment transfer be evaluated?
Hold out a target robot, evaluate before adaptation, then fine-tune with a stated amount of target data. Compare with a target-only baseline using the same budget. Report task success, unsafe contacts, latency and failures. Tests should distinguish a new robot from a familiar robot performing a new object or task.
Sources and methodology
The comparison records source robots, shared action representation, target adaptation and held-out-robot evidence. Multi-robot datasets were not treated as transfer evidence unless the primary material evaluated reuse across embodiments.
Counts and release status come from official project pages and papers. Success rates are not combined because targets and adaptation budgets differ. Verification date July 11, 2026.
Related TechniaHQRobot guides
Fact-check report
Verified July 11, 2026
Confirmed
- Open X-Embodiment reports 22 robot embodiments.
- Octo and OpenVLA provide public code and checkpoints.
- The article separates multi-robot training from held-out-robot transfer.
Not confirmed or incomplete
- Comparable before-and-after adaptation results are not available across all systems.
- Closed humanoid datasets and failure logs remain unavailable.
- Some recent 2026 project artifacts are incomplete.
Likely to change quickly
- New embodiment adapters and datasets may alter transfer results.
- Repository and checkpoint availability can change.
Share this article
Share the current TechniaHQRobot article page.
Continue reading
Open the latest robotics reporting, Physical AI analysis and hardware notes.