NVIDIA Cosmos 3 Edge: A 4B World Action Model Running at 15 Hz on Jetson
Source: NVIDIA / Hugging Face Date: 2026-07-20
- Announcement: https://huggingface.co/blog/nvidia/cosmos3edge
- Model card: https://huggingface.co/nvidia/Cosmos3-Edge
- Model collection: https://huggingface.co/collections/nvidia/cosmos3
- An autoregressive tower processes visual and text tokens for understanding, reasoning, and text output;
- A diffusion tower processes visual, audio, and action tokens for prediction, generation, and neural simulation.
Yesterday's Cosmos news was a robotics alliance of 22 Japanese companies. Today NVIDIA has released the model those partners will use: Cosmos 3 Edge, a 4-billion-parameter model aimed at robotics, smart cameras, and edge devices.
Its goal goes beyond recognizing scenes. Given the current visual state and a task, the model can produce reasoning text, generate action tokens, and predict the visual consequences of those actions. NVIDIA calls it a *world action model* — one model that answers both "what is happening" and "what should I do next, and what happens after?"
Two Transformers, One Shared World Representation
Cosmos 3 Edge is not a shrunken VLM. It contains two Transformer towers:
A practical benefit of this design: the same model supports forward prediction — give an action, see the future frame — and inverse inference — give a change, infer the action that caused it. Policy mode ties the two together, generating expected visual consequences alongside action output.
NVIDIA also released Cosmos3-Edge-Policy-DROID, post-trained on DROID robot data for grasping and placement tasks, with training scripts published. Developers can fine-tune on a small H100 cluster or DGX Station, then deploy to Jetson, GeForce RTX, RTX PRO, or data center GPUs.
The Edge Numbers Look Great — But Check the Measurement
The headline numbers from the announcement: 640×360 robot-control observations, 32 actions generated per inference, and a 15 Hz control frequency on Jetson Thor. NVIDIA also claims first place among same-size 4B models on VANTAGE-Bench visual analysis and SOTA on robot policy learning.
The model card's detailed tables are more complicated. It lists Jetson AGX Thor T5000/T3000/T2000, H100, B200, and RTX PRO 6000 hardware. The Reasoner shows 239ms time-to-first-token at single concurrency on RTX PRO 6000, with ~639ms latency for a 100-token output request. Meanwhile, the DROID Policy generation latency table shows 6.32 seconds on Jetson AGX Thor T5000.
The 15 Hz figure and 6.32 seconds seem to conflict, but they likely use different inference backends, action chunking, and timing conventions: the former emphasizes maintaining control frequency after generating a 32-action chunk per inference, the latter a full Policy generation call. NVIDIA does not clarify this relationship in the announcement. Before deploying to a real robot, don't just quote 15 Hz for marketing — re-test the end-to-end closed loop on your target hardware.
The license is OpenMDW 1.1, usable commercially and non-commercially, but it is not Apache-2.0. Official testing currently covers only Linux and BF16; Windows, FP4, FP8, and FP16 are outside the supported/verified scope.
Why This Roadmap Is Worth Following
MiniCPM-Robot, LingBot-VA, and Cosmos 3 Edge represent three distinct strategies: MiniCPM-Robot bets on small models and streaming memory, LingBot on complete embodied infrastructure, and NVIDIA on a vertical loop of "world model + action model + Jetson hardware."
NVIDIA's advantage is concrete. A robotics team gets not just weights but an entire chain: training framework, post-training scripts, edge inference, a reference robot policy, and the GPU/Jetson deployment platform. Even a modest model-quality lead, combined with this engineering loop, could decide who reaches factories and warehouses first.
The Model Card Pours Cold Water
Don't read this as "general-purpose robotics is solved." The model card is explicit: Cosmos 3 has no explicit physics simulator; it only approximates 3D geometry, contact dynamics, and object permanence from data. Long-horizon tasks exhibit state drift, out-of-distribution environments can produce implausible actions, and objects may vanish, deform, or clip through each other. NVIDIA states outright that outputs must not be treated as physically accurate simulation or used directly for safety-certified decisions.
What matters next is real-robot data: how many new trajectories cross-robot transfer requires, whether 15 Hz holds under occlusion, deformable objects, and contact tasks, and whether viable deployment paths exist on non-NVIDIA hardware. Cosmos 3 Edge has already pushed world models from the data center to the edge. The next milestone isn't another polished demo video — it's keeping actions running continuously on real machines for hours without failure.