What is Sim-to-Real Transfer?
Sim-to-Real Transfer — training a policy in simulation and getting it to work on physical hardware, across the gap between the two.
The standard tool is domain randomization: vary lighting, textures, friction and object mass in simulation until the real world looks like one more sample from the same distribution. The other half is system identification — measuring the real robot's dynamics and setting the simulator to match. MuJoCo and NVIDIA's Isaac Sim, with Isaac Lab on top, are the common engines; both run thousands of parallel environments on a single GPU.
The gap is not uniform. Locomotion and coarse reaching cross it well. Contact-rich tasks cross it badly: tight-tolerance insertion, deformable objects, cables, granular material and cloth all depend on contact physics that simulators approximate, and the approximation is where the policy fails. A sim-trained policy that works in the lab and fails in the field is usually failing on friction or contact stiffness, not on vision.
The cost structure is why sim is attractive: once the environment exists, extra samples are nearly free, and the expense is the engineering to build and validate the scene. The decision rule is task-first — if the failure mode you care about is contact, simulation is a supplement and real data is the product; if it is navigation or locomotion, simulation alone can be enough. Pipelines of this kind are engineering work rather than stocked data: a project is scoped to the task, and the deliverable is a validated environment plus the data it generates.
Related terms
-
Robot Data Augmentation
Robot Data Augmentation — generating additional training episodes from existing ones by transforming images, goals or scene configurations.
-
Robot Manipulation Data
Robot Manipulation Data — episodes of a robot arm moving objects, recorded together with the commands that produced the motion.
-
Mobile Robot Navigation Data
Mobile Robot Navigation Data — sensor logs of a robot moving through space, with the poses, maps and trajectories needed to train or evaluate navigation.
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.