Skip to main content
Nemotron is NVIDIA’s family of open-weight reasoning models, built on nemotron_h — a hybrid Mamba-2/transformer architecture that mixes state-space layers with a handful of attention layers instead of using attention everywhere. That hybrid design is what lets Nemotron 3 models natively support very long context (up to 1M tokens on the largest checkpoints) without the usual attention-only memory blowup. The family spans a local-friendly Nano tier up through multi-GPU Super and Ultra models, all tuned for agentic use: reasoning traces, tool-calling, and instruction-following are trained in, not bolted on. Run the size that fits your hardware locally, then pair the Tokios connector to call it from any machine, teammate, or hosted agent through https://api.tokios.com — no inbound ports, no VPN.
Nemotron 3 weights are released under the NVIDIA Nemotron Open Model License (Hugging Face tags it other), not Apache or MIT. It’s an open-weights license that allows commercial use under its terms — read them before you redistribute or fine-tune on top of these weights.

Run it locally with Ollama

Two Nemotron 3 Nano-tier builds are in the Ollama library — Nano is the local-friendly tier:
  • nemotron3 is the Nano Omni multimodal build (text + image input). ollama run nemotron3 pulls the default nemotron3:33b (~28 GB), served at 128K context.
  • nemotron-3-nano is the text-only Nano reasoning model, served at its full 1M context. ollama run nemotron-3-nano pulls the 30B-A3B MoE (~24 GB at q4_K_M, only ~3.5B active per token); ollama run nemotron-3-nano:4b is a ~2.8 GB dense model for laptops and edge boxes.
The bigger tiers are on Ollama too: nemotron-3-super:120b (~87 GB, multi-GPU) and nemotron-3-ultra (cloud-only — no downloadable local-weights tag). NVIDIA’s older tuned Llama, nemotron (Llama-3.1-Nemotron-70B), is a separate, earlier line. See the nemotron-3-nano library page for the current tag list — this page covers connecting it, not every runtime detail.
Ollama’s default context window is small (2048 tokens) — far below Nemotron 3 Nano’s 1M. Raise num_ctx in your Modelfile or client request to use more of its context. The nemotron3 (Nano Omni) tag is served at up to 128K.

Variants & tags

Every value below is from Hugging Face model cards and the Ollama library. Tags and download sizes change as new quantizations ship — confirm against ollama.com/library/nemotron3 before you standardize on one. Sources: ollama.com/library/nemotron-3-nano, ollama.com/library/nemotron3, NVIDIA-Nemotron-3-Nano-30B-A3B-BF16 model card, NVIDIA-Nemotron-3-Super-120B-A12B-BF16 model card, NVIDIA-Nemotron-3-Ultra-550B-A55B-NVFP4 model card.
Two Nano builds, two Ollama tags: nemotron3 is Nano Omni (multimodal, 128K as served), while nemotron-3-nano is the text-only Nano with the full 1M context. Both are mixture-of-experts — see how inference works for why the full parameter count still has to fit in memory even though only the ~3.5B active slice runs per token. For the documented vLLM/SGLang tool-call and reasoning parsers, serve the Hugging Face checkpoint directly (see the tabs below).

Quantization & formats

Ollama’s nemotron3 tags are GGUF at q4_K, q8, and bf16. On Hugging Face, NVIDIA also publishes NVFP4 builds of the larger tiers — the Ultra-550B-A55B-NVFP4 checkpoint is trained natively in NVFP4, and Super and Nano Omni both have NVFP4 variants alongside their BF16 originals. NVFP4 is NVIDIA’s 4-bit format built specifically for Blackwell Tensor Cores (RTX 50 series and Blackwell-generation datacenter GPUs) — it won’t run natively on older NVIDIA cards. See Quantization formats and the hardware they need for the full format×hardware matrix, and what quantization is for how to read quant names like Q4_K_M.

Hardware fit

Treat every entry as an estimate — the ground truth is the actual download size plus the KV cache for your context. See what size model fits your GPU? for the sizing math. Super (nemotron-3-super:120b, ~87 GB) and Ultra are datacenter/multi-GPU tiers — Ultra is cloud-only on Ollama. If you’re running local on a single workstation, Nano (nemotron-3-nano) or Nano Omni (nemotron3) is the realistic pick. See Quantization & hardware for the NVFP4/Blackwell requirement in more detail.

Run it — beginner to advanced

Leave Ollama listening on the default http://127.0.0.1:11434. This is the Nano Omni build (128K context as served); see the note above if you need the text-only Nano checkpoint with full context instead.

Capabilities

  • Reasoning: Nemotron 3 models are unified reasoning/non-reasoning models — they emit a reasoning trace before the final answer by default, and it’s on across the whole line (Nano, Super, and Ultra all default to enable_thinking=True). Turn it off with enable_thinking=False in the chat template if you want a direct response at a slight accuracy cost on harder prompts. Budget control (reasoning_budget) lets you cap how many tokens the reasoning trace can use.
  • Native tool-calling: Yes — the model cards document tool-calling support with the qwen3_coder tool-call parser on both vLLM and SGLang, trained in via synthetic tool-calling data during post-training. On vLLM/SGLang you must set the parser flags shown above, or tool calls won’t parse; when combining tools with reasoning, also set "chat_template_kwargs": {"enable_thinking": true, "force_nonempty_content": true} in the request.
  • Vision: The plain-text Nano/Super/Ultra checkpoints are text-only. The Ollama nemotron3 tag is Nano Omni and exposes text + image input. Broader video/audio/image/text behavior belongs to the upstream Omni model card, not to the simple Ollama tag surface documented here.
  • Long context: Up to 262,144 tokens natively on Nano/Super, extensible to 1M with VLLM_ALLOW_LONG_MAX_MODEL_LEN=1. The hybrid Mamba-2/attention architecture is what makes that context length practical — a pure-attention model this size would need far more memory for the KV cache. Ollama’s nemotron3 tag currently exposes only 128K of that range.

Connect it with Tokios

Once Nemotron is running locally, pair the Tokios connector so you can reach it as https://api.tokios.com from Claude Code, Cline, or any other compatible client — instead of only from localhost:11434.
1

Pair the Tokios connector

Sign in at tokios.com/console, open the Setup tab, and click Start pairing to get a one-time claim code (TKS-XXXX-XXXX). Install and run the connector on the machine running Ollama:
Windows
macOS
Linux
Then approve the device on the Setup or Connectors tab.
2

Point the connector at Ollama's /v1 API

Ollama exposes an OpenAI-compatible surface at /v1. For a single-model setup, the console’s Setup wizard fills this in automatically as http://127.0.0.1:11434/v1. For multiple models, set it explicitly in tokios-connector.json — see Connector config.
3

Register a deployment

In the Models tab, register the model and choose a public deployment name, for example nemotron-tunnel. This name — not Ollama’s local model id — is what clients send in the model field.
4

Create an API key

In the Keys tab, click Create key. Copy the sk-tok-… key now — it’s shown only once.

Call it from anywhere

The model field is always your registered deployment name (nemotron-tunnel above), never Ollama’s local model id. See Use Claude Code and Use Cline for full client setup.

Caveats

  • Nemotron emits a reasoning trace by default across the family. If a downstream client shows the raw thinking or you want lower latency, disable it with enable_thinking=False or set a reasoning_budget.
  • The Ollama nemotron3 tag is Nano Omni (multimodal, 128K as served). For the text-only Nano with the full 1M context, pull nemotron-3-nano instead — or serve the Hugging Face checkpoint on vLLM/SGLang for the documented tool-call and reasoning parsers.
  • Tool calling requires the qwen3_coder parser flags on vLLM/SGLang, plus force_nonempty_content when combining tools with reasoning — without them, tool calls won’t parse correctly.
  • Every Nemotron 3 tier (Nano, Super, Ultra) is a mixture-of-experts model — size your hardware off the total parameter count, not the active-parameter count. Super and Ultra are multi-GPU/datacenter tiers; don’t plan to run them on a single consumer card.
  • Nemotron 3 uses the NVIDIA Nemotron Open Model License, not Apache or MIT — commercial use is allowed under its terms, but check the exact checkpoint license before redistribution or fine-tuning.

Quickstart

Pair a connector and register your first model end to end.

What size model fits your GPU?

Match Nemotron’s Nano, Super, or Ultra tier to your available VRAM before you pull it.

Quantization & hardware

The NVFP4/Blackwell requirement behind Nemotron’s Super and Ultra quantized builds.

Which local model for which task?

See how Nemotron compares to other local models by task.