Instructions to use nvidia/Cosmos3-Nano-FP8 with libraries, inference providers, notebooks, and local apps. Follow these links to get started.
- Libraries
- Cosmos
How to use nvidia/Cosmos3-Nano-FP8 with Cosmos:
# No code snippets available yet for this library. # To use this model, check the repository files and the library's documentation. # Want to help? PRs adding snippets are welcome at: # https://github.com/huggingface/huggingface.js
- Diffusers
How to use nvidia/Cosmos3-Nano-FP8 with Diffusers:
pip install -U diffusers transformers accelerate
import torch from diffusers import DiffusionPipeline # switch to "mps" for apple devices pipe = DiffusionPipeline.from_pretrained("nvidia/Cosmos3-Nano-FP8", dtype=torch.bfloat16, device_map="cuda") prompt = "Astronaut in a jungle, cold color palette, muted colors, detailed, 8k" image = pipe(prompt).images[0] - Notebooks
- Google Colab
- Kaggle
Add enterprise GPU benchmarks and clarify FP8 model card
Populate single-GPU Generator throughput for DGX Spark, DGX Station, and RTX PRO 5000 72GB Blackwell from enterprise PBR 309485. The six FPS values use 189 frames divided by measured average generation time and carry an explicit assumption footnote; the underlying seconds and unverified denoising-step count are documented alongside the table.
Clarify Reasoner video inputs and throughput scope, correct H100/H200 hardware descriptions and action array shapes, document resolution-specific video frame limits and the configured mixed activation precision, and distinguish base-model quality plots from FP8 evaluation. Fix asset downloading, framework links, stale SGLang modality wording, and Explainability output/benchmark labels.
Validation: 14 existing Generator FPS values and 18 Reasoner values match the supplied source workbooks; six enterprise generation times match PRISM report 40954 and its workbook. Checked all six derived enterprise FPS cells, Python example syntax, example JSON, and git diff whitespace. GPU inference and backend loading were not run. Existing DROID policy values still require checkpoint/precision provenance; the GB300 policy estimate remains labeled.