Nemotron 3.5 Super VL: NVIDIA's 120B model in NVFP4 for text, image and video
NVIDIA has released Nemotron 3.5 Super VL in a 4-bit variant (NVFP4). The model has 120 billion parameters but uses only 12 billion per token, understands text, images and video, and handles up to 1 million tokens of context. NVIDIA says it runs on a single DGX Spark or an H200.

What this is about
NVIDIA has released the quantized version of Nemotron 3.5 Super VL on Hugging Face, specifically NVIDIA-Nemotron-3.5-Super-VL-120B-A12B-NVFP4. It is a vision-language model, meaning it can understand text, images and video and outputs text. It's intended for reasoning, coding, tool use, document understanding and video analysis. This variant uses NVFP4, a 4-bit number format, to cut memory requirements. The quantization was retrained from the BF16 model (the 16-bit variant) with "Quantization-Aware Distillation."
Architecture
The model has 120 billion parameters (roughly, the knobs adjusted during training), of which only 12 billion are active per token. That comes from the Mixture-of-Experts (MoE) principle: there are many specialized sub-networks ("experts"), here 512 per MoE layer, and only a small share is selected for each token. This saves compute.
The layers alternate between Mamba-2, MoE and attention. Mamba-2 is an alternative to classic attention that needs less memory on long texts. For images, a C-RADIO vision encoder with a connector is used, which translates image information into a form the language model can process. Context extends to 1 million tokens. The prompt, images, history, tool results and response all share this window. Individual deployment recipes often use less for memory reasons.
A Multi-Token Prediction (MTP) head predicts several future tokens, which enables speculative decoding: the main model checks a fast draft, and several tokens can be accepted per step. For DGX Spark there's also the "LiLiCorr" drafter, which NVIDIA recommends there in all scenarios.
Thinking can be controlled via the chat template: off, on (medium), or on. "Medium" generates fewer tokens but can reduce accuracy.
Training
According to NVIDIA, training ran in seven stages:
- The language backbone starts from Nemotron 3 Super Base; the MTP head is trained on 100B tokens, followed by 1 trillion tokens of distillation from Nemotron 3 Ultra Base.
- Continued pre-training (100B Indic tokens), extension to 1M context (35B tokens) and 67B tokens of software-engineering mid-training, using things like repositories, commit diffs, CI logs and agent trajectories.
- Vision-language training with images, document pages and video frames.
- Supervised fine-tuning with sequences of up to 524,288 tokens.
- Reinforcement learning (verifiable rewards, human feedback) and multi-teacher distillation.
- MTP boosting for better acceptance rates.
- Quantization with NVIDIA Model Optimizer. The vision encoder, connector, Mamba convolutions and embeddings stay in BF16, and the MoE router in FP32. Inference uses W4A4 on Blackwell and W4A16 on other platforms.
Benchmarks
NVIDIA compares BF16 and NVFP4 with identical settings. A selection (vendor figures):
| Benchmark | BF16 | NVFP4 |
|---|---|---|
| GPQA-Diamond | 89.52 | 89.90 |
| LiveCodeBench v6 | 88.22 | 87.41 |
| SWE-bench Verified | 71.10 | 71.07 |
| SWE-bench Pro | 51.78 | 51.30 |
| Terminal-Bench 2.1 | 60.67 | 62.78 |
| MMLU-ProX | 76.91 | 73.76 |
| OSWorld-Verified | 51.14 | 52.3 |
| CharXiv reasoning | 80.82 | 79.88 |
| WebVoyager [offline] | 77.72 | 66.31 |
| DeepSWE [offline] | 24.65 | 18.2 |
Quantization costs little on most tests, and NVFP4 even edges ahead in some. MMLU-ProX, WebVoyager and DeepSWE show clear drops. If you plan to run agentic tasks like these, keep that in mind. According to NVIDIA, the results come from NeMo Gym; some benchmarks used official implementations or internal, unreleased harnesses. The model card, at least in the text we have, includes no comparisons with competing models.
What you need to try it
The model is built for NVIDIA hardware (Blackwell and Hopper, Linux). NVIDIA lists 1× DGX Spark, 1× H200, 2× H100 or 1× GB200 as target systems. A normal gaming graphics card generally isn't enough for a model this size; the card also mentions local runs on RTX Spark and RTX Pro 6000 via llama.cpp (ggml-org collection) and Unsloth. According to the source, it isn't intended for Mac, CPU-only setups or Google Colab. Expect to need more than 60 GB of memory for the weights, so be generous with disk space too. For video, these limits apply: up to 2 minutes of MP4, at 1080p 1 FPS and max. 128 frames, at 720p 2 FPS and 256 frames. One image and one video per request are possible. Recommended sampling values: temperature 1.0 for text and 0.6 for vision, each with top_p 0.95.
For production, NVIDIA offers NIM containers and the Dynamo framework.
Our take
The model shows how large MoE models with 4-bit quantization can fit on a few GPUs or even a compact desktop supercomputer. The benchmarks show that quality mostly holds up, with a few exceptions. NVIDIA calls the Nemotron family open, with weights, training data and recipes. According to the card, the OpenMDW-1.1 license allows commercial use. What remains open is how the model stacks up directly against other open models, and the numbers are vendor claims. The source is also truncated (the training data section is missing), and the model card gives the release date as 10/15/2026.
Sources
- Hugging Face Trending huggingface.co
- Ollama-Bibliothek ollama.com
- NVIDIA Blog blogs.nvidia.com
Try it yourself: NVIDIA-Nemotron-3.5-Super-VL-120B-A12B-NVFP4
Explained step by step, no prior knowledge needed – on your own computer or free in your browser.
What can I do with it?
The model answers questions about text, images, document pages and short videos, writes and fixes code, and can call tools. Thinking can be switched on and off. It works well as a foundation for local agents.
Who is it worth it for?
For developers with NVIDIA data-center hardware or a DGX Spark who want to run agents or document and video analysis. It's too big for ordinary home PCs.
What your computer needs
Values estimated from the model size – the Model Card may have more precise figures.
Which variant is right for me?
Many models come in several sizes or "quantizations." These are compressed versions: smaller and faster, but slightly less accurate. Rule of thumb: pick the largest variant whose memory requirement fits in your VRAM (video memory). The scripts below choose this for you automatically.
| Variant | Download | Needs approx. | Compatible graphics cards |
|---|---|---|---|
4-bit (Q4) Default |
72 GB | 80 GB | e.g. multiple professional GPUs (2× A6000, H100) or DGX Spark |
8-bit (Q8) |
128 GB | 142 GB | servers only, with multiple data-center GPUs (e.g. 8× H100) |
16-bit (Original) |
240 GB | 265 GB | servers only, with multiple data-center GPUs (e.g. 8× H100) |
This NVFP4 variant is meant for DGX Spark, H200, 2× H100 or GB200. There's also a BF16 version with higher memory requirements. For local runs, NVIDIA lists llama.cpp and Unsloth variants.
- Target hardware according to NVIDIA: 1× DGX Spark, 1× H200, 2× H100 or 1× GB200 on Linux.
- The full 1M context costs a lot of memory; some recipes use smaller windows (e.g. 131072 with TensorRT-LLM on DGX Spark).
- On DGX Spark, the LiLiCorr drafter is recommended, and the configuration runs with one concurrent request.
- Video: 1080p at 1 FPS and up to 128 frames, 720p at 2 FPS and 256 frames.
- The source lists no support for Mac, CPU-only or Colab.
Groß (120 B parameters, MoE): running entirely on the GPU takes a lot of VRAM (video memory). With MoE offloading, a regular graphics card plus plenty of RAM is enough (see table). Colab Free isn't enough.
How do I find out what my computer has?
- Windows: Press Ctrl + Shift + Esc → Task Manager → Performance tab → click GPU on the left. At the bottom you'll see Dedicated GPU memory (that's your VRAM). You'll find system memory under Memory.
- Mac: Apple menu at the top left → About This Mac. You'll see your chip (e.g. M2) and memory (e.g. 16 GB). On Apple chips, graphics and processor share this memory.
- Linux: Type
nvidia-smiin the terminal (shows your graphics card and its memory) andfree -hfor system memory.
Guide
Google Colab (in your browser, no installation)
Google Colab is a free service from Google. It gives you a computer with a graphics card in your browser for a few hours. All you need is a Google account. For this model: too big for Colab – even the largest Colab GPUs aren't enough.
- Download the notebook. Click the button and save the file.
- Open Colab. Go to colab.research.google.com and sign in with your Google account.
- Upload the notebook. In the window that appears, click Upload on the left (or choose File → Upload notebook at the top) and select the file
colab.ipynb. - Turn on the GPU. In the top menu, go to Runtime → Change runtime type → under Hardware accelerator, select T4 GPU (with Colab Pro: L4 or A100) → Save.
- Start everything. Runtime → Run all (keyboard shortcut Ctrl + F9). If you see the warning “This notebook was not authored by Google,” click Run anyway.
- Wait. The cells run one after another. A green checkmark appears to the left of each cell when it's done. Installation and download take about 28 minutes here.
- Try it out. The result appears below the last cell. To test something else, change the text in the cell and run it again with Shift + Enter. The last cell starts a proper chat with an input field.
- Clean up. When you're done: Runtime → Disconnect and delete runtime. This saves your free quota.
Good to know: The free GPU is limited (usually a few hours per day). After about 90 minutes of inactivity, Colab disconnects, and you'll have to start everything over.
Windows 10 / 11
The easiest way is Ollama, a free program that launches AI models with a single command.
- Update your graphics driver (NVIDIA cards only): Install the NVIDIA app or the latest driver. For AMD cards, use the latest Adrenalin driver.
- Install Ollama. Download the file OllamaSetup.exe from ollama.com/download/windows, double-click it, and choose Install. Afterward, a small llama icon appears in the taskbar at the bottom right.
- Open a terminal window. Press the Windows key, type PowerShell and press Enter. A blue or black window opens.
- Start the model. Copy this command ("Copy" button), paste it into the window with a right-click, and press Enter:
The first time, Ollama downloads the model (72 GB (about 1.6 hr at 100 Mbit/s)). After that, it's instant.ollama run hf.co/lmstudio-community/NVIDIA-Nemotron-3.5-Super-VL-120B-A12B-NVFP4-LiLiCorr-GGUF - Start typing. Once
>>> Send a messageappears, type your question and press Enter. Type/byeto end the chat.
Not enough memory? Pick a smaller variant from the table above, e.g. ollama run hf.co/lmstudio-community/NVIDIA-Nemotron-3.5-Super-VL-120B-A12B-NVFP4-LiLiCorr-GGUF.
Prefer automatic? A script that picks the right variant for you
- Download both files into the same folder: try_windows.ps1 demo.py
- Open the folder in File Explorer, right-click an empty spot and choose Open in Terminal.
- Paste this command and press Enter:
powershell -ExecutionPolicy Bypass -File try_windows.ps1
If needed, the script installs Ollama via winget, measures your VRAM (video memory) and downloads the matching variant.
macOS
Macs with an Apple chip (M1 to M5) are ideal. Older Intel Macs are very slow.
- Install Ollama. Download it from ollama.com/download/mac, open the file, and drag Ollama into your Applications folder. Launch Ollama once – a llama appears in the menu bar at the top.
- Open Terminal. Press Cmd + Space, type Terminal, and press Enter.
- Start the model. Paste the command (Cmd + V) and press Enter:
The first time, the model is downloaded (72 GB (about 1.6 hr at 100 Mbit/s)).ollama run hf.co/lmstudio-community/NVIDIA-Nemotron-3.5-Super-VL-120B-A12B-NVFP4-LiLiCorr-GGUF - Start typing. Type your question and press Enter. Quit with
/bye.
Linux
- Check your GPU.
nvidia-smishould show your card. If it doesn't, install the driver on Ubuntu and restart:sudo ubuntu-drivers install - Install Ollama:
curl -fsSL https://ollama.com/install.sh | sh - Start the model:
Exit withollama run hf.co/lmstudio-community/NVIDIA-Nemotron-3.5-Super-VL-120B-A12B-NVFP4-LiLiCorr-GGUF/bye. Useollama psto check whether the model is running on the GPU. - Or let it pick the right variant automatically:
bash try_linux.sh # mit Python/transformers statt Ollama: MODE=hf bash try_linux.sh
Try it
Explain why binary search has logarithmic running time.Describe this image and read out all visible text.Summarize the events in this video in the correct order.
If something goes wrong
You need --trust-remote-code because the model ships with its own code.
Use the specified vLLM image (v0.32.0 or the nightly build mentioned), otherwise Mamba options may be missing.
Reasoning tokens and the answer share max_tokens; if the value is too small, the answer gets cut off.
Set HF_TOKEN if needed, in case the repo requires a login.
In NVFP4, quality on some agentic benchmarks (e.g. WebVoyager) is clearly below BF16.
“out of memory,” a crash, or your computer freezes
The model is too big for your VRAM (video memory). Pick a smaller variant from the table above and close other programs, especially games and browsers with lots of tabs.
It runs, but extremely slowly
Your CPU is probably doing the work instead of your graphics card. In Ollama, the PROCESSOR column of ollama ps shows how much runs on the GPU. If it says "100% CPU", update your graphics driver or pick a smaller variant that fits entirely into VRAM (video memory).
“ollama” or “python” is not found
Close the terminal window and open it again so it recognizes the newly installed program. For Python on Windows: reinstall it and check Add python.exe to PATH.
Windows: "Running scripts is disabled on this system"
Run the script with exactly the command above: powershell -ExecutionPolicy Bypass -File try_windows.ps1. This allows execution for this one time only.
Error message when loading the model (version, "trust_remote_code", unknown architecture)
Brand-new models often need the latest software version. With Ollama: update Ollama. With Python: pip install -U transformers in the activated environment. The Model Card usually lists the exact version.
Tokenstrom generates the scripts and notebook automatically. Please take a quick look before running them – they're plain, readable text. Mind the model's license: OpenMDW-1.1.
Ask the AI assistant
Questions about this article, installation or background? Our assistant knows this page and runs on our own machine, not in someone else's cloud.
The Assistant is an AI (Gemma 4) and can make mistakes – please check important details against the source. Questions are used only to generate an answer and are deleted after one hour. Please don't enter any personal data.
Comments
What do you think? Already tried it? Write it here, no sign-up needed.
Comments are public. Links aren't allowed, and we delete abusive posts. You can delete your own comment at any time in this browser. Learn more in the Privacy Policy.