All companies

No consumer access · Open stack · Company profile

Meta

Meta's V-JEPA 2 is an open world model for understanding, predicting, and planning in the physical world. It is included for category completeness, but it is not a consumer world-creation app.

What this company is for

Understand physical prediction and planning with V-JEPA 2.

Consumer access. No consumer access

Visitor can see. Read the official explanation, inspect open artifacts, and view demonstrations of physical prediction and robot planning.

Where the claim stops. There is no consumer prompt-to-world creator; local use is intended for researchers and developers with model-running experience.

This company's models

The model Meta ships

Physical reasoning and planning world model

V-JEPA 2

A video-trained latent world model for understanding, predicting, and planning actions in the physical world.

Official Meta explanation plus open code and model checkpoints for researchers and developers.

A latent prediction and planning model, not a consumer application that renders explorable worlds.

Open the V-JEPA 2 dossier

Why consumers should know it

V-JEPA 2 explains a world model that predicts before an agent acts.

Most consumer-facing world models show their work as pixels, video, or 3D scenes. V-JEPA 2 instead learns representations that help a system understand observations, predict change, and plan actions. That makes it useful for explaining the planner side of the category.

A visitor can read the official examples and inspect open artifacts, but there is no normal create button. The page should answer what the research means without placing V-JEPA 2 beside Marble as if both produced the same kind of output.

What it can do

Understanding, prediction, and planning are the relevant capabilities.

Meta describes V-JEPA 2 as a video-trained world model that can support physical-world prediction and zero-shot robot planning. The visible demonstrations help readers understand why internal models matter even when they do not render an explorable fantasy world.

This is not evidence that a household user can download the model and control a robot safely. Real robot deployment needs hardware integration, action definitions, safety systems, and evaluation beyond the released research examples.

Access boundary

Open artifacts serve developers, not a mainstream creation workflow.

Code and checkpoints make the work inspectable, but they do not create a C-end product. The practical consumer path is reading the dossier and official demonstrations; local experimentation belongs in the open-source guide.

Keep model claims tied to Meta's named benchmarks and examples. Do not convert research performance into claims about general physical understanding, long-horizon autonomy, or commercial robot readiness.

Keep reading

Sources