FAQ

Physical AI

World model training data: who publishes it and who does not

Of the major world-model programmes, only a handful — Cosmos, V-JEPA 2 and the original Genie, plus AgiBot's Genie Envisioner — publish usable training-data figures. That asymmetry tells you something about the field.

World models are the most-discussed and least-documented area of Physical AI. Here is what each programme actually publishes about its training data — and the gaps are as informative as the numbers.

What a world model is

The Cosmos paper gives the usable definition: a world foundation model is “a digital twin of the physical world that a Physical AI can safely interact with” — formally, a model that “predicts the future observation at time t+1” given past observations and the current perturbation.

The appeal for robotics is obvious. If you can predict what happens next, you can plan without acting, generate training scenarios without collecting them, and evaluate a policy without risking hardware. That is why every major lab has a programme.

The data these models need is video at enormous scale, often paired with action or control signals. Which is where the publishing gets thin.

A diagram repeated over three time steps: a game frame feeds a trapezoid V that outputs z; z feeds a box M whose hidden state h passes to the next step; z and h feed a small box C that outputs an action a. Text on the left explains observation, vision model, memory RNN, controller and actions.
Ha and Schmidhuber's agent in three parts: a vision model (V) compresses each observed frame into a small code z, a memory network (M) carries the history forward and learns to predict what comes next, and a small controller (C) picks actions from both. V and M together are the world model, which is why it needs frames paired with the actions taken. Image: the interactive article's agent diagram · CC BY 4.0 · from Ha & Schmidhuber 2018, “World Models”, arXiv:1803.10122

What each programme publishes

Compiled from each programme's own primary source. 'Not published' means the source does not state it, which is a finding rather than an omission on our part.

ProgrammeTraining data as publishedAvailability
Cosmos (WFM 1)a 20M hour video pool curated to ~100M clips of 2–60 seconds; content-category mix published (e.g. nature dynamics 20%, hand motion and object manipulation 16%); NVIDIA's launch blog cites 9,000 trillion training tokensmodels under NVIDIA Open Model License
Cosmos Predict 2.5“trained on 200M curated video clips”; Transfer 2.5's own data not publishedweights on Hugging Face; repo now in limited maintenance, superseded by Cosmos 3
Cosmos 3no hours or clip count; NVIDIA says only billions of samples across text, image, video, sound and action trajectoriesSuper and Nano weights on Hugging Face since May 2026
V-JEPA 2“over 1 million hours of internet video”; action post-training on “less than 62 hours” of DROID videoweights released by Meta
Geniepool of “over 200,000 hours” of gaming video; filtered training set 6.8M clips / ~30k hours; 11B parametersno weights, no data
Genie 2no data or resolution figures — only “a large-scale video dataset”; consistent worlds “for up to a minute”no release
Genie 3training data not published; 720p, 24fps, consistency over “a few minutes”no weights; Project Genie prototype for Google AI Ultra subscribers since January 2026 (US first)
Genie 4training data not published; announced late October 2026, after this post was first publishedresearch preview for trusted testers; Project Genie access announced as coming soon
AgiBot Genie Envisioner~3,000 hours / ~1M episodes, entirely from AgiBot-World-BetaGE-Base weights on Hugging Face under the LTX-Video 2B v0.9 licence; other code and data CC BY-NC-SA 4.0
1X World Modelno exact figure — “thousands of hours of data on EVE humanoids”; over 100 hours released for its World Model Challengeover 100 hours of tokenised video (Apache 2.0) and baseline model weights released
A pipeline diagram. Real-world video domains (robotics, driving, object manipulation, egocentric, human dynamics, nature scenes) pass through shot-aware video splitting, GPU-based transcoding and video cropping into a video clip database; then through a filtering block of seven filters (aesthetic quality, motion, OCR detection, perceptual quality, semantic artefacts, VLM filter, content type classifier); then video captioning, semantic deduplication (clustering plus deduplication) and sharding into training datasets.
NVIDIA's documented curation path for world-model video: split, transcode, crop, filter on seven criteria, caption, deduplicate, shard. Every stage drops footage, which is why an hours figure means little until you know whether it was counted before or after these steps. Image: nvidia-cosmos/cosmos-cookbook · Apache-2.0 repository

The Genie figure everyone misreports

Genie is a good cautionary example of reading a paper rather than its coverage.

The source pool is “over 200,000 hours of publicly available Internet gaming videos”, with the unfiltered set given as around 244k hours and 55M videos. But the actual training set is “6.8M 16s video clips (30k hours)” — “our final dataset is 6.8M videos for a total of over 30k hours.”

Those are different pipeline stages: 200k+ hours collected, 30k hours trained on. Press coverage routinely conflates them and reports the larger number as the training set. The model is 11B parameters, of which the paper itemises 10.1B as the dynamics model, with a latent action vocabulary of just 8.

The lesson generalises: in this literature, always check whether a published hours figure is the pool, the filtered set, or the set actually trained on.

V-JEPA 2's striking result

V-JEPA 2 publishes the most useful number in this whole area for anyone doing robotics.

It pretrains on over a million hours of internet video. Then, to produce an action-conditioned model capable of robot control, it post-trains on “less than 62 hours of unlabeled robot videos from the Droid dataset”.

Sixty-two hours. And the resulting model was deployed on Franka arms in two labs with no robot data collected in either, performing pick-and-place by planning to image goals “without any task-specific training or reward.”

Its benchmark figures: Something-Something v2 77.3 top-1, Epic-Kitchens-100 action anticipation 39.7 recall-at-5, PerceptionTest 84.0, TempCompass 76.9.

If that approach holds up, it reframes the data problem substantially: the expensive scarce resource becomes passive video, which is abundant, rather than teleoperation, which is not.

A two-stage flow chart. Stage one takes over a million hours of internet video and images into actionless self-supervised pre-training of a video encoder. Stage two takes a much smaller block of robot interaction data, around sixty-two hours, into action-conditioned post-training, producing a model used for understanding, prediction and planning.
The two data pools behind one world model, at wildly different scales: a million hours of unlabelled video against sixty-two hours of robot interaction. The small pool is the robot data, which V-JEPA 2 took from the existing DROID dataset. Image: facebookresearch/vjepa2 · MIT repository

What this means practically

Three conclusions worth carrying away.

You are not going to train one of these. Cosmos's 100M clips and V-JEPA 2's million hours are industrial-scale efforts. The realistic engagement is fine-tuning or conditioning a released model — Cosmos and V-JEPA 2 have released weights, DeepMind's Genie models have not.

Check the licence on released weights. Cosmos ships under NVIDIA's own Open Model License rather than a standard open-source licence, which has its own terms to read.

The data asymmetry is a real signal. When a programme publishes clip counts and curation pipelines, you can assess it. When it publishes capability demos and nothing about inputs, you are evaluating a product rather than a result. Both can be useful; they warrant different levels of confidence.

A block diagram. On the left, a text prompt and a noise video feed a 'Diffusion Backbone'; depth, edge, segmentation and blur videos each feed their own control block, and these join an 'Adaptive Spatiotemporal Control' block together with a 'Spatiotemporal Control Weight Video'. That block feeds the backbone, whose output on the right is 'De-noised Generative Video'.
How Cosmos Transfer 2.5 is steered: depth, edge, segmentation and blur videos each enter through their own control branch, a weight video sets where and when each applies, and a text prompt guides the diffusion backbone. NVIDIA positions it for turning simulator output into realistic video: conditioning a released model, not training one. Image: nvidia-cosmos/cosmos-transfer2.5 · Apache-2.0 repository

Questions people ask

Can I use a world model to generate robot training data?

That is one of the stated motivations, and Cosmos is positioned for it. The practical caveat is that a policy trained on generated rollouts inherits the generator's physical inaccuracies, so the sim-to-real gap becomes a model-to-real gap. Treat generated data as augmentation around real data rather than as a replacement for it.

What is the difference between a world model and a video generator?

Action conditioning. A video generator produces plausible video from a prompt; a world model predicts the next observation given a specific action or perturbation, which is what makes it usable for planning. The architectures overlap heavily and the labels are applied loosely in marketing.

Why do these need so much more data than language models?

Video is far denser per sample and the models must learn physical dynamics rather than symbolic structure — and crucially there is no equivalent of the instruction-tuning shortcut, where a thousand examples select among existing behaviours. V-JEPA 2's 62-hour action post-training is notable precisely because it looks like such a shortcut.

Which released world model should I start from?

Of those with public weights, Cosmos is the one explicitly built for Physical AI and has variants for different conditioning modes. V-JEPA 2 is the stronger choice if you want a representation for downstream control and planning rather than generation. Read both licences before committing.

Stop hunting. Start searching.

Tens of thousands of curated datasets, searchable in plain language — with the licence and size checked before you download anything.

Search Dataset Finder →