NVIDIA Cosmos™ is a world foundation model platform designed to accelerate the development of Physical AI by enabling machines to understand, simulate, and interact with the physical world across robotics, autonomous driving, and smart space environments, including industrial and factory-scale applications.
Model Overview: Cosmos3-Super-Image2Video
Description
Cosmos3 is a collection of Omnimodal world models capable of generating dynamic, high-quality video, image, audio, and action commands from combinations of text, image, video, and action trajectory inputs. It serves as a foundational building block for a broad range of Physical AI applications and research spanning world understanding, world generation, simulation, and embodied policy learning.
This model is ready for commercial and non-commercial use.
Model Developer: NVIDIA
Model Versions
Cosmos3-Nano:
Given multimodal inputs including text, images, video, audio, and action trajectories, generate coherent text, images, video, audio, and action outputs for multimodal understanding, world simulation, future prediction, action reasoning, and Physical AI applications.
Cosmos3-Super:
Given multimodal inputs including text, images, video, audio, and action trajectories, generate coherent text, images, video, audio, and action outputs for multimodal understanding, world simulation, future prediction, action reasoning, and Physical AI applications.
Cosmos3-Nano-Policy-DROID:
Given language instructions and visual observations from the DROID robot platform, generate robot action trajectories for manipulation and control tasks.
Cosmos3-Super-Image2Video:
Given one input image and text instructions, generate temporally coherent video sequences that are consistent with the provided visual content.
Cosmos3-Super-Text2Image:
Given text input, generate high-fidelity images that are consistent with the provided description.
Cosmos3 is an Omni-modal foundation model built on a Mixture-of-Transformers (MoT) architecture consisting of two complementary transformer towers: an autoregressive transformer for discrete token generation and a diffusion transformer for continuous multimodal generation. During inference, text is generated through standard next-token autoregressive decoding, while non-text modalities, such as images, video, audio, and actions, are synthesized through iterative denoising. This unified architecture enables Cosmos3 to model heterogeneous modalities within a single framework while preserving generation mechanisms best suited to each modality.
Input Type(s): Text, Image, Video (with audio or without audio), Action Trajectory
Input Format(s):
Text: String
Image: jpg, png, jpeg, webp
Video (with or without audio): mp4
Action: json (1D list)
Input Parameters:
Text: One-dimensional (1D)
Image: Two-dimensional (2D)
Video: Three-dimensional (3D)
Audio: One-dimensional (1D)
Action trajectory: One-dimensional (1D)
Other Properties Related to Input:
For video inputs, we accept various resolutions, including 720p, 480p, and 256p.
When using input video with audio muxed into the video MP4 file, the audio should have 2 channels (stereo) and a 48 kHz sample rate.
Image and video inputs are RGB color (8 bits per channel, sRGB color space); grayscale inputs are not supported.
Action input is a per-frame sequence of robot/agent state or control values (e.g., joint positions, gripper state, camera pose). The full input is a 2D array shaped (T, D), where T is the number of frames and D is the embodiment-specific dimensionality listed below.
Input action is only supported for compatible embodiments, including general camera motion (9D), autonomous vehicle (9D), egocentric motion (57D), single Franka Panda arm with RobotiQ gripper (10D), dual Franka Panda arm with RobotiQ gripper (20D), Agibot (29D), UR (10D), Google robot (10D), WidowX 250 (10D), UMI (9D).
Input Size and Length limits:
Text: 4096 tokens
Image: 256p, 480p, and 720p resolution at one of these aspect ratios (16:9, 4:3, 1:1, 3:4, 9:16)
Video: 256p, 480p, and 720p resolution at one of these aspect ratios (16:9, 4:3, 1:1, 3:4, 9:16). Max number of frames = 5.
Audio: Max 0.5 second
Action: 16 – 400 video frames
Generator Output
Output Type(s): Image, video, audio, action, text
Output Format(s):
Image: JPG
Video: MP4
Audio: Advanced Audio Coding (AAC) stream (muxed within the MP4)
Action: 1D list (.json)
Text: string
Output Parameters:
Image: Two-dimensional (2D)
Video: Three-dimensional (3D)
Audio: One-dimensional (1D)
Action: One-dimensional (1D)
Text: One-dimensional (1D)
Other Properties Related to Output:
The generated video is an MP4 file, with the resolution, frame rate, and duration specified in the input. The generated audio is encoded in AAC format, muxed into the video MP4 file with 2 channels (stereo) and a 48 kHz sample rate.
Video generation supports durations from 5 to 400 frames, with 189 frames as the default generation duration.
The generated action is only supported for compatible embodiments, including general camera motion (9D), autonomous vehicle (9D), egocentric motion (57D), single Franka Panda arm with RobotiQ gripper (10D), dual Franka Panda arm with RobotiQ gripper (20D), Agibot (29D), UR (10D), Google robot (10D), WidowX 250 (10D), UMI (9D).
Audio: 48 kHz stereo AAC stream muxed into video mp4
Video: mp4 at the FPS specified in input
Image: JPEG
Reasoner Input
Input Type(s): Text, Text+Image, Text+Video
Input Format(s):
Text: String
Image: jpg, png, jpeg, webp
Video: mp4
Input Parameters:
Text: One-dimensional (1D)
Image: Two-dimensional (2D)
Video: Three-dimensional (3D)
Other Properties Related to Input:
Video inputs are recommended at a frame rate of 4 fps.
Long-context inputs supported up to 256K tokens.
Input Size and Length limits:
Text: Up to 256K tokens (context window).
Image: Standard input image formats; passed as file or URL.
Video: mp4 at the recommended 4 fps.
Reasoner Output
Output Type(s): Text
Output Format(s):
Text: string
Output Parameters:
Text: One-dimensional (1D)
Other Properties Related to Output:
Default max_tokens=4096+ is recommended for reasoning outputs; longer outputs may be requested.
Reasoning outputs may include structured chain-of-thought, 2D/3D point localization, and bounding-box coordinates for vision-based tasks.
The video content visualizes the input text description as a short animated scene, capturing key elements within the specified time constraints.
Our AI models are designed and/or optimized to run on NVIDIA GPU-accelerated systems. By leveraging NVIDIA's hardware (e.g., GPU cores) and software frameworks (e.g., CUDA libraries), the model achieves faster training and inference times compared to CPU-only solutions.
Linux (We have not tested on other operating systems.)
Note: Only BF16 precision is tested. Other precisions like FP4, FP8, and FP16 are not officially supported.
The integration of foundation and fine-tuned models into AI systems requires additional testing using use-case-specific data to ensure safe and effective deployment. Following the V-model methodology, iterative testing and validation at both unit and system levels are essential to mitigate risks, meet technical and functional requirements, and ensure compliance with safety and ethical standards before deployment.
Training, Testing, and Evaluation Datasets
Dataset Overview
Total Size: 1.3B data points
Total Number of Datasets: 393 dataset entries
Dataset partition: Training [100%], Testing [N/A — evaluation benchmarks used separately], Validation [N/A — evaluation benchmarks used separately]
Time period for training data collection: 2024–2026
Time period for testing data collection: N/A (standard public benchmarks)
Time period for validation data collection: N/A (standard public benchmarks)
Raw data from internal and external sources is transformed into training-ready data through multiple stages of curation, filtering, and quality review. Data acquisition spans diverse multimodal sources — robotics, autonomous driving, industrial environments, indoor and outdoor scenes, varied lighting and weather conditions, camera viewpoints, object categories, and human activities — to broaden coverage across Physical AI operating environments. Automated filtering pipelines remove corrupted, duplicate, low-quality, and restricted content. Metadata analysis, heuristic rules, and model-assisted classifiers are applied during preprocessing to flag anomalous distributions and low-diversity subsets. Human review supplements automated filtering for selected datasets, benchmark construction, and targeted quality analysis. Datasets are balanced across modalities and task categories — visual reasoning, text-to-image, text-to-video, image-to-video, audio generation, video transfer, action-conditioned generation, and action command generation — to reduce overrepresentation of narrow domains. Synthetic and simulation-based augmentation supplements coverage of rare physical interactions and edge-case scenarios. Deduplication and provenance tracking are applied across the corpus. The resulting processed data is converted into model-ready tokenized or encoded representations through modality-specific preprocessors before training begins.
Training datasets passed through multiple layers of automated and manual safeguards designed to reduce the presence of harmful or policy-violating content across categories including weapons and weapons-related instructional content, criminal planning, child sexual abuse material (CSAM), non-consensual intimate imagery (NCII), sexual content involving minors, harassment, hate speech, profanity, threats and incitement to violence, self-harm or suicide-related content, and graphic violence. Data sources are reviewed for licensing compatibility, provenance, and alignment with internal data governance and safety policies before admission into training corpora. Automated filtering pipelines combine multiple detection strategies: hash-matching against known CSAM and NCII reference databases; classifier-based moderation models trained for explicit sexual content, hate speech, violence, weapons imagery, and other restricted categories; keyword and regex-based screening for criminal-planning, threats, and self-harm phrases in text data; metadata and provenance heuristics for source-level risk signals; and embedding-based anomaly detection to surface samples that fall outside expected distributions. Human review and targeted audits supplement automated filtering for selected datasets, benchmark construction, and safety-sensitive evaluation. For multimodal Physical AI data (robotics, autonomous driving, industrial scenes), additional filtering targets invalid action trajectories, physically implausible interactions, and unsafe control sequences. Synthetic and simulation-generated data are evaluated through internal validation before inclusion. Benchmark evaluations and red-team testing are applied post-training to surface remaining safety gaps across world generation, reasoning, audio, and action tasks. No large-scale data-filtering process can guarantee complete removal of all harmful content; residual risks may remain, particularly in rare edge cases or open-world deployment settings. Ongoing monitoring and dataset review continue post-release.
Data Modality and Training Data Size
Modality
Reasoning Data Sample Count
Generation Data Sample Count
Text
22M
Not Applicable
Image
19M
767M
Video
1M
348M
Audio
Not Applicable
139M
Action
Not Applicable
8M
Data Collection Method by dataset
Hybrid: Automatic/Sensors, Synthetic, Automated
Labeling Method by dataset
Hybrid: Human, Automated
Properties: The training, testing, and evaluation datasets consist of diverse multimodal video, image, audio, action, synthetic, and sensor-conditioned data sourced from NVIDIA-owned data and publicly available, commercially permissive datasets. These datasets are curated to exclude known restricted content and to support building an Omni model that learns to generate and reason about dynamic physical environments across world reasoning and generation tasks.
Public Datasets
Dataset
Samples
OpenImage
1.2M
Coyo700M
100M
YouTube Video
340M
UMI
4.5M
Private Datasets
Dataset
Samples
Egocentric
7M
Nexar
0.6M
AgiBot
0.2M
HOI
0.3M
Synthetic Datasets
Dataset
Samples
synthetic images generated using HiDream-I1
15M
synthetic images generated using Qwen-Image-2512
14M
synthetic captions generated using Qwen3-VL
1115M
Evaluation Datasets
Data Collection Method by dataset
Hybrid: Automatic/Sensors, Synthetic, Automated
Labeling Method by dataset
Hybrid: Human, Automated
Properties: The training, testing, and evaluation datasets consist of diverse multimodal video, image, audio, action, synthetic, and sensor-conditioned data sourced from NVIDIA-owned data and publicly available, commercially permissive datasets. These datasets are curated to exclude known restricted content and to support building an Omni model that learns to generate and reason about dynamic physical environments across world reasoning and generation tasks.
Benchmarks
Please see our technical paper for detailed evaluations of the base model.
Artificial Analysis Leaderboard
Open-Source Models [2026/05/28/]
Artificial Analysis Image-to-Video leaderboard (no audio) — open-source models
All Models [2026/05/28/] (Including Closed-Source)
Artificial Analysis Image-to-Video leaderboard (no audio) — all models including closed-source
The JSON-upsampled version of assets/example_original_prompt.txt is saved in assets/example_prompt.json for convenience, and is used for the video generation examples below.
vLLM-Omni
Container
docker pull vllm/vllm-omni:cosmos3
General Invocation
You can use the release-tested vllm-omni package for deploying an OpenAI-compatible API inference endpoint.
The recommended vLLM-Omni serving configuration for nvidia/Cosmos3-Super-Image2Video on 8xH200, 8xH100, or 8xA100 is:
With this configuration, video generation with 50 steps should take approximately 55 seconds on H200 GPUs. For 2xH200, one can simply use --cfg-parallel-size 2 --use-hsdp --hsdp-shard-size 2, and a video should take approximately 3 minutes to generate. Tensor parallelism is also supported by setting --tensor-parallel-size. Setting --enable-layerwise-offload can help reduce memory usage on GPUs with less available memory.
Download example prompts and scripts
The inference scripts (scripts/) and example inputs (assets/) live in this model repo. Download just those folders with the Hugging Face CLI:
1import json
2import requests
34# 1. Read JSON-upsampled prompt (prompt + negative_prompt)5json_prompt = json.load(open("assets/example_prompt.json"))67# 2. Build your API payload8payload ={9"prompt": json_prompt["prompt"],10"negative_prompt": json_prompt["negative_prompt"],11"size":"832x480",12"num_frames":189,13"fps":24,14"num_inference_steps":50,15"guidance_scale":6.0,16"flow_shift":5.0,17"extra_params": json.dumps(18{19"use_resolution_template":False,20"use_duration_template":False,21"guardrails":True,22}23),24}25files ={"input_reference":("input.png",open("assets/example_first_frame.png","rb"),"image/png")}2627# 3. Send the POST request28url ="http://localhost:8000/v1/videos/sync"29print("Sending request to server...")30response = requests.post(url, data=payload, files=files, headers={"Accept":"video/mp4"})31response.raise_for_status()3233# 4. Save the returned MP4 bytes34withopen("/tmp/cosmos3_i2v.mp4","wb")as video_file:35 video_file.write(response.content)36print("Saved video to /tmp/cosmos3_i2v.mp4")
Example output generated from assets/example_first_frame.png:
Inferencing with custom prompts
Cosmos3-Super-Image2Video uses JSON-format prompts for optimal quality. The recommended way is to utilize cosmos-framework. Here we provide a simple proof-of-concept script for convenience. It requires an OpenAI-compatible VLM model like claude-opus-4.7 and gpt-5.5.
bash
1exportPROMPT_UPSAMPLER_API_KEY="..."2python scripts/upsample_prompt.py \3 --model-name <model>\4 --base-url <VLM-endpoint-url>\5 --image-path assets/example_first_frame.png \6 --user-prompt "The ice cream melts and gradually disappears. The camera moves around."\7 --output-path scripts/upsampled.json
SGLang
SGLang Diffusion can serve nvidia/Cosmos3-Super-Image2Video through OpenAI-compatible video generation endpoints. Install SGLang from the main branch with diffusion dependencies, then start the server:
Cosmos 3 support in SGLang Diffusion currently requires the SGLang main branch. Switch to a stable SGLang release once Cosmos 3 support is included there.
Cosmos3 is fully supported within the popular HuggingFace Diffusers package. This integration makes it a supported inference backend, allowing developers to easily incorporate Cosmos3's capabilities - such as text-to-image generation - into their pipelines using the Cosmos3OmniPipeline class, as demonstrated by the provided code examples (see examples for other modalities on the HuggingFace Cosmos3 page).
Cosmos3 may produce imperfect outputs in challenging scenarios. Generation artifacts include temporal inconsistency, unstable camera or object motion, imprecise physical interactions, inaccurate audio-video synchronization, and action-state drift — especially in long-horizon or high-resolution outputs. Reasoning may also be incorrect: object states, causal relationships, spatial geometry, temporal ordering, agent intent, and future outcomes can be misinferred, and complex or long-context inputs may yield hallucinated entities, inconsistent interpretations, or implausible predictions. Because the model lacks an explicit physics simulator, 3D geometry, 4D space-time evolution, object permanence, contact dynamics, and physical laws are only approximated — producing artifacts such as disappearing or morphing objects, unrealistic collisions, and physically implausible motions. Quality further degrades in out-of-distribution environments, safety-critical edge cases, and domains underrepresented in training.
Cosmos3 outputs should not be treated as physically accurate simulation, reliable ground-truth reasoning, or safety-certified decision making. Applications involving robotics control, autonomous systems, scientific simulation, or safety-critical planning require additional validation, external constraints, system-level safety analysis, and domain-specific guardrails before deployment.
NVIDIA believes Trustworthy AI is a shared responsibility and we have established policies and practices to enable development for a wide array of AI applications. Developers should work with their internal model team to ensure this model meets requirements for the relevant industry and use case and addresses unforeseen product misuse.
Please make sure you have proper rights and permissions for all input image and video content; if image or video includes people, personal health information, or intellectual property, the image or video generated will not blur or maintain proportions of image subjects included.
Users are responsible for model inputs and outputs. Users are responsible for ensuring safe integration of this model, including implementing guardrails as well as other safety mechanisms, prior to deployment.
For more detailed information on ethical considerations for this model, please see the Model Card++ Explainability, Bias, Safety & Security, and Privacy subcards. Please report model quality, risk, security vulnerabilities or NVIDIA AI Concerns here.
