NVIDIANemotronDoryForCausalLM

NVIDIA Nemotron Labs Dory1.0 4B BF16 — Hardware Requirements & GPU Compatibility

ChatFunctions

NVIDIA-Nemotron-Labs-Dory1.0-4B-BF16 is a 4 billion parameter looped model from NVIDIA Labs, built for general-purpose reasoning on a small footprint. It applies a shared block of layers repeatedly, so one checkpoint can trade inference compute for accuracy by changing the loop count, and it mixes sliding-window and full-attention layers. NVIDIA recommends two loops as the default. A Q4 build needs roughly 2.5 GB of memory, so it fits almost any GPU and many CPU-only machines. The context window is up to 256K tokens, and the model supports English. It is released under the OpenMDW-1.1 license and was published on October 16, 2026. Its card says last-loop KV caching avoids extra cache memory as loops are added, and that it was pre-trained natively in NVFP4 before continuing in BF16. It also lists BF16, MXFP8, NVFP4, and Q5_K_M formats. vLLM support is still in a pull request, and llama.cpp support requires building from a Dory-enabled source tree.

4.0B params · dense262K contextOtherOct 20263.8K downloads178 likes2.6K quant downloads

Your hardware

Verdicts below are for the reference RTX 4090. Set yours to personalise the page.

Detection reads your browser's GPU name with no data sent anywhere.

Runs great on a 24 GB GPU

Runs from 8 GB (Q4_K_M · 16K)Best on 24 GB (Q4_K_M · ~214 tok/s · 64K)Macs from 8 GB (Q4_K_M · ~23 tok/s)

Other

Reference GPU · RTX 4090 24 GB

Estimates, ±20% · how we estimate

Run NVIDIA Nemotron Labs Dory1.0 4B BF16

One recommended way. Every other method, OS and quant is in the step-by-step guide.

Other ways

each opens step-by-step

Run in cloud

Fits on RTX 3060 12GB (6 GB headroom) · Q4_K_M

Generation speed: ~77 tok/s; generation speed
Cost per 1M output tokens: $0.26; per 1M output tokens

Deployon Vast.aiBest optionfrom $0.071/hr

Compare GPUs →

Run NVIDIA Nemotron Labs Dory1.0 4B BF16

5.7 GB VRAM at 16K context · fits the RTX 4090 (18.3 GB free)

Works on macOS, Windows and Linux.

Install Ollama (Linux)
$curl -fsSL https://ollama.com/install.sh | sh
Install Ollama (macOS / Windows)
Download and run the app; it installs the ollama command.
Download Ollama ↗
Run Q4_K_M
$ollama run hf.co/cloudnathan5/Dory1.0-4B-GGUF:Q4_K_M
Raise the context window
Type it inside the chat. For the API server instead, start it with OLLAMA_CONTEXT_LENGTH=16384 ollama serve.
$/set parameter num_ctx 16384
A larger context needs more memory than the weights alone.
Use the API
Ollama serves its API on http://localhost:11434.

Works on macOS, Windows and Linux.

Install LM Studio
Desktop app for macOS (Apple silicon), Windows and Linux.
lmstudio.ai ↗
Download the model
In the app press Ctrl/Cmd + Shift + M and paste https://huggingface.co/cloudnathan5/Dory1.0-4B-GGUF, then pick Q4_K_M. Or use the CLI (run LM Studio once first):
$lms get https://huggingface.co/cloudnathan5/Dory1.0-4B-GGUF@Q4_K_M
Open on Hugging Face ↗
Load and chat
Open the model loader, select the model and set Context Length to 16384. Leave GPU offload at maximum if it fits.
Start the local server (optional)
$lms server start

Works on macOS, Windows and Linux.

Install llama.cpp (macOS)
MacPorts, Nix and conda-forge also work.
$brew install llama.cpp
Install options ↗
Install llama.cpp (Windows)
$winget install llama.cpp
Install llama.cpp (Linux)
Download the prebuilt llama-*-bin-ubuntu-* archive for your GPU backend (CPU, Vulkan) from the releases page, unpack it and run the binaries from that folder. Homebrew (brew install llama.cpp) and conda-forge also work on Linux.
llama.cpp releases ↗
Start the server
Downloads the model on first run. The chat UI and an OpenAI-compatible API are at http://localhost:8080.
$llama-server -hf cloudnathan5/Dory1.0-4B-GGUF:Q4_K_M -c 16384 -ngl 99 --port 8080

Works on macOS, Windows and Linux.

Option A: Docker Model Runner
Docker Desktop: Settings > AI > Enable Docker Model Runner. Docker Engine on Linux: install the docker-model-plugin package.
$docker model run hf.co/cloudnathan5/Dory1.0-4B-GGUF:Q4_K_M
Model Runner docs ↗
The quant tag after the repo is how Hugging Face cards write it; if your Docker version rejects it, drop the tag and pick the quant by repo.
Option B: llama.cpp server image (NVIDIA)
Needs the NVIDIA Container Toolkit. Models are cached in the llama-cache volume. Open http://localhost:8080.
$docker run --gpus all -p 8080:8080 -v llama-cache:/root/.cache ghcr.io/ggml-org/llama.cpp:server-cuda -hf cloudnathan5/Dory1.0-4B-GGUF:Q4_K_M -c 16384 -ngl 99 --host 0.0.0.0 --port 8080
Image tags (cuda13, vulkan, rocm) ↗
Cache path inside the image is not in the docs; remove the -v flag if the volume complains.

Linux only.

Install vLLM
Linux only; on Windows run it inside WSL2. NVIDIA GPU shown; AMD ROCm, Intel and CPU builds have their own install pages.
$uv venv --python 3.12 --seed
$source .venv/bin/activate
$uv pip install vllm --torch-backend=auto
vLLM installation ↗
Serve the model
OpenAI-compatible API at http://localhost:8000/v1.
$vllm serve nvidia/NVIDIA-Nemotron-Labs-Dory1.0-4B-BF16 --max-model-len 16384
Runs the original weights, not the Q4_K_M GGUF; needs ~9 GB of GPU memory.

macOS only.

MLX supports only macOS, so follow these steps for that setup.

Install mlx-lm
$pip install mlx-lm
Chat in the terminal
$mlx_lm.chat --model netprojects/nemotron-dory1.0-4b-mlx-bf16
Downloads the model on first run. The MLX repo has its own quantisation; it may not match the quant selected above.
Or start a local server
Listens on http://localhost:8080.
$mlx_lm.server --model netprojects/nemotron-dory1.0-4b-mlx-bf16

Works on macOS, Windows and Linux.

Install Jan
jan.ai ↗
Find the model
Open the Hub tab, paste this model ID in Search, and choose Q4_K_M if offered.
$cloudnathan5/Dory1.0-4B-GGUF
Use the local API (optional)
Settings > Local API Server > Start Server. It listens on http://127.0.0.1:1337.

Rent GPUs hourly to run Q4_K_M right there. Pricing comes from partner marketplaces and varies.

Available GPU rentals for Q4_K_M, prioritized by value
GPU	Speed	$/1M tokens	Rent
RTX 3060 12GBCheapestCheapest6 GB free	~77 tok/s	$0.26	Deploy on Vast.aifrom $0.071/hr (opens in new tab)	6 GB free · ~77 tok/s · $0.26 / 1M tokens
RTX 4060 (8 GB)2 GB free	~58 tok/s	$0.49	Deploy on Vast.aifrom $0.10/hr (opens in new tab)	8 GB · 2 GB free · ~58 tok/s · $0.49 / 1M tokens
RTX A4000 (16 GB)10 GB free	~95 tok/s	$0.32	Deploy on Vast.aifrom $0.11/hr (opens in new tab)	16 GB · 10 GB free · ~95 tok/s · $0.32 / 1M tokens
RTX 3070 (8 GB)2 GB free	~95 tok/s	$0.36	Deploy on Vast.aifrom $0.12/hr (opens in new tab)	8 GB · 2 GB free · ~95 tok/s · $0.36 / 1M tokens
RTX A5000 (24 GB)18 GB free	~163 tok/s	$0.27	Deploy on RunPodfrom $0.16/hr (opens in new tab)	24 GB · 18 GB free · ~163 tok/s · $0.27 / 1M tokens
RTX 3080 Ti (12 GB)6 GB free	~194 tok/s	$0.26	Deploy on RunPodfrom $0.18/hr (opens in new tab)	12 GB · 6 GB free · ~194 tok/s · $0.26 / 1M tokens
RTX 4000 Ada (20 GB)14 GB free	~77 tok/s	$0.73	Deploy on RunPodfrom $0.20/hr (opens in new tab)	20 GB · 14 GB free · ~77 tok/s · $0.73 / 1M tokens
RTX 3090 (24 GB)18 GB free	~199 tok/s	$0.31	Deploy on RunPodfrom $0.22/hr (opens in new tab)	24 GB · 18 GB free · ~199 tok/s · $0.31 / 1M tokens

Compare GPUs →

How Much VRAM Does NVIDIA Nemotron Labs Dory1.0 4B BF16 Need?

Select a quantization level; the listed hardware adheres to it.

VRAM	+32K	+128K	File	Quality	On RTX 4090 (reference)
1.8 GB	7.4 GB	25.6 GB	1.2 GB	2-bit · i-quant extreme compression — Importance-weighted 2-bit, extreme compression — significant quality loss	Fits: 64K context · ~370 tok/s
1.9 GB	7.5 GB	25.7 GB	1.3 GB	2-bit · i-quant extra small — Importance-weighted 2-bit, extra small	Fits: 64K context · ~350 tok/s
1.9 GB	7.6 GB	25.7 GB	1.4 GB	2-bit · i-quant small — Importance-weighted 2-bit, small	Fits: 64K context · ~341 tok/s
2.0 GB	7.7 GB	25.8 GB	1.5 GB	2-bit · i-quant medium — Importance-weighted 2-bit, medium	Fits: 64K context · ~324 tok/s
2.2 GB	7.9 GB	26 GB	1.7 GB	3-bit · i-quant — Importance-weighted 3-bit	Fits: 64K context · ~295 tok/s
2.3 GB	7.9 GB	26.1 GB	1.5 GB	2-bit · small K-quant — 2-bit small K-quant	Fits: 64K context · ~289 tok/s
2.3 GB	8 GB	26.1 GB	1.8 GB	3-bit · i-quant extra small — Importance-weighted 3-bit, extra small	Fits: 64K context · ~282 tok/s
2.4 GB	8 GB	26.2 GB	1.9 GB	3-bit · i-quant small — Importance-weighted 3-bit, small	Fits: 64K context · ~277 tok/s
2.4 GB	8 GB	26.2 GB	1.6 GB	2-bit · K-quant — 2-bit quantization with K-quant improvements	Fits: 64K context · ~277 tok/s
2.4 GB	8.1 GB	26.2 GB	1.9 GB	3-bit small — 3-bit small quantization	Fits: 64K context · ~271 tok/s
2.5 GB	8.1 GB	26.3 GB	1.9 GB	3-bit · i-quant medium — Importance-weighted 3-bit, medium	Fits: 64K context · ~265 tok/s
2.6 GB	8.3 GB	26.4 GB	2 GB	3-bit medium — 3-bit medium quantization	Fits: 64K context · ~250 tok/s
2.7 GB	8.4 GB	26.5 GB	2.1 GB	3-bit large — 3-bit large quantization	Fits: 64K context · ~242 tok/s
2.8 GB	8.5 GB	26.6 GB	2.2 GB	4-bit · i-quant compact — Importance-weighted 4-bit, compact	Fits: 64K context · ~233 tok/s
2.9 GB	8.6 GB	26.7 GB	2.3 GB	4-bit small — 4-bit small quantization	Fits: 64K context · ~225 tok/s
2.9 GB	8.6 GB	26.7 GB	2.3 GB	4-bit · i-quant non-linear — Importance-weighted 4-bit, non-linear	Fits: 64K context · ~225 tok/s
3.1 GB	8.7 GB	26.8 GB	2.4 GB	4-bit medium — 4-bit medium quantization — most popular sweet spot	Fits: 64K context · ~214 tok/s
3.1 GB	8.8 GB	26.9 GB	2.7 GB	4-bit large — 4-bit large quantization	Fits: 64K context · ~211 tok/s
3.4 GB	9.1 GB	27.2 GB	2.8 GB	5-bit small — 5-bit small quantization	Fits: 64K context · ~192 tok/s
3.5 GB	9.2 GB	27.3 GB	2.8 GB	5-bit medium — 5-bit medium quantization — good quality/size tradeoff	Fits: 64K context · ~187 tok/s
3.6 GB	9.2 GB	27.3 GB	3 GB	5-bit large — 5-bit large quantization	Fits: 64K context · ~184 tok/s
4.0 GB	9.6 GB	27.7 GB	3.3 GB	6-bit, very good — 6-bit quantization, very good quality	Fits: 64K context · ~166 tok/s
4.7 GB	10.3 GB	28.4 GB	4.2 GB	8-bit, near-lossless — 8-bit quantization, near-lossless	Fits: 64K context · ~141 tok/s
8.6 GB	14.3 GB	32.4 GB	8 GB	16-bit · bfloat — Brain floating point 16 — preferred for training	Fits: 64K context · ~76 tok/s

Selected Q4_K_M

4-bit medium quantization

5.7GBat 16K context

Weights: 2.4 GB
KV cache: 3.0 GB
Overhead: 0.3 GB

Fits RTX 4090 (reference) · 18.3 GB free · ~214 tok/s

≥50 tok/s needs ≥235 GB/s · RTX 5090 ~381, RTX 3090 Ti ~214

Which Hardware Can Run NVIDIA Nemotron Labs Dory1.0 4B BF16?

Q4_K_M · 3.1 GB

NVIDIA Nemotron Labs Dory1.0 4B BF16 (Q4_K_M) requires 3.1 GB of VRAM to load the model weights. For comfortable inference with headroom for KV cache and system overhead, 4+ GB is recommended. Using the full 262K context window can add up to 47.9 GB, bringing total usage to 51 GB. 52 GPUs can run it, including NVIDIA GeForce RTX 5090, NVIDIA GeForce RTX 3090 Ti. 163 devices with unified memory can run NVIDIA Nemotron Labs Dory1.0 4B BF16, including Mac Studio (M3 Ultra, 256GB), Mac Studio (M3 Ultra, 512GB), MacBook Air 13" M3 (8 GB).

By VRAM tier · typical GPUs and Macs at Q4_K_M

Typical hardwareQuantVRAMtok/sContext that fits

8 GB · RTX 4060Q4_K_M · 5.7 GB · ~58 tok/s · 16K5.7~5816K8 GB tier →

12 GB · RTX 3060 12GBQ4_K_M · 5.7 GB · ~77 tok/s · 32K5.7~7732K12 GB tier →

16 GB · RTX 5060 Ti 16GBQ4_K_M · 5.7 GB · ~95 tok/s · 64K5.7~9564K16 GB tier →

24 GB · RTX 4090referenceQ4_K_M · 5.7 GB · ~214 tok/s · 64K5.7~21464K24 GB tier →

Mac 32 GB · Mac Mini M4Q4_K_M · 5.7 GB · ~28 tok/s · 128K5.7~28128KMacs →

Mac 64 GB · Mac Studio M4 MaxQ4_K_M · 5.7 GB · ~125 tok/s · 256K5.7~125256KMacs →

Alternatives to NVIDIA Nemotron Labs Dory1.0 4B BF16

Nemotron family · 44 models →

Similar models

6tok/s on RTX 4090

Model	Score	VRAM	tok/s	Why it is similar
Granite Vision 4.1 4BIBM	—	4 GB	~228	same size
Qwen3 4B Instruct 2507Alibaba	—	4.2 GB	~226	same size
MiniCPM V 4OpenBMB	—	3.1 GB	~236	same size
Phi 4 Mini ReasoningMicrosoft	—	4.8 GB	~228	same size
Qwen2.5 VL 3B InstructAlibaba	—	3.2 GB	~249	same size
Phi 3.5 Vision InstructMicrosoft	—	9.2 GB	~183	same size

Specifications

Publisher: NVIDIA
Family: Nemotron
Parameters: 4.0B
Architecture: DoryForCausalLM
Context Length: 262,144 tokens
Vocabulary Size: 131,072
Release Date: 2026-10-16
License: Other

Resources

Frequently Asked Questions

How much VRAM does NVIDIA Nemotron Labs Dory1.0 4B BF16 need?

NVIDIA Nemotron Labs Dory1.0 4B BF16 requires 3.1 GB of VRAM at Q4_K_M, or 8.6 GB at BF16. Full 262K context adds up to 47.9 GB (51 GB total).

VRAM = Weights + KV Cache + Overhead

Weights = 4.0B × 4.8 bits ÷ 8 = 2.4 GB

KV Cache + Overhead ≈ 0.7 GB (at 2K context + ~0.3 GB framework)

Fit ratings and hardware model lists check this model with room for a 16K-token context, which needs a little more memory.

KV Cache + Overhead ≈ 48.6 GB (at full 262K context)

VRAM usage by quantization

Q4_K_M

3.1 GB

Q4_K_M + full context

51.0 GB

Learn more about VRAM estimation →

What's the best quantization for NVIDIA Nemotron Labs Dory1.0 4B BF16?

For NVIDIA Nemotron Labs Dory1.0 4B BF16, Q4_K_M (3.1 GB) offers the best balance of quality and VRAM usage. Q4_K_L (3.1 GB) provides better quality if you have the VRAM. The smallest option is IQ2_XXS at 1.8 GB.

VRAM requirement by quantization

IQ2_XXS

1.8 GB~53%

IQ3_XS

2.3 GB~73%

Q3_K_L

2.7 GB~86%

Q4_K_M ★

3.1 GB~89%

Q4_K_L

3.1 GB~90%

BF16

8.6 GB~100%

★ Recommended — best balance of quality and VRAM usage.

Learn more about quantization →

Can I run NVIDIA Nemotron Labs Dory1.0 4B BF16 on a Mac?

Yes — Mac Mini M2 (8 GB) and 145 other Macs can run NVIDIA Nemotron Labs Dory1.0 4B BF16. Apple Silicon uses unified memory, so the model shares RAM with the system. At Q4_K_M you need at least 3.1 GB of usable unified memory (RAM minus macOS overhead).

Can I run NVIDIA Nemotron Labs Dory1.0 4B BF16 locally?

Yes — NVIDIA Nemotron Labs Dory1.0 4B BF16 can run locally on consumer hardware. Popular tools include Ollama, LM Studio, and llama.cpp.

How fast is NVIDIA Nemotron Labs Dory1.0 4B BF16?

At Q4_K_M, NVIDIA Nemotron Labs Dory1.0 4B BF16 can reach ~1569 tok/s on AMD Instinct MI350X. On NVIDIA GeForce RTX 4090: ~214 tok/s. Speed depends mainly on GPU memory bandwidth. Real-world results typically within ±20%.

tok/s = (bandwidth GB/s ÷ model GB) × efficiency

Example: NVIDIA B200 → 8000 ÷ 3.06 × 0.65 = ~1699 tok/s

Estimated speed at Q4_K_M (3.1 GB)

NVIDIA B200

~1699 tok/s

NVIDIA GeForce RTX 4090

~214 tok/s

NVIDIA B300

~1699 tok/s

AMD Instinct MI350X

~1569 tok/s

Real-world results typically within ±20%. Speed depends on batch size, quantization kernel, and software stack.

Learn more about tok/s estimation →

What's the download size of NVIDIA Nemotron Labs Dory1.0 4B BF16?

At Q4_K_M, the download is about 2.39 GB. The full-precision BF16 version is 7.95 GB. The smallest option (IQ2_XXS) is 1.09 GB.

Which GPUs can run NVIDIA Nemotron Labs Dory1.0 4B BF16?

52 consumer GPUs can run NVIDIA Nemotron Labs Dory1.0 4B BF16 at Q4_K_M. Top options include AMD Radeon RX 6700 XT, AMD Radeon RX 6800, AMD Radeon RX 6800 XT. 52 GPUs have plenty of headroom for comfortable inference.

Which devices can run NVIDIA Nemotron Labs Dory1.0 4B BF16?

163 devices with unified memory can run NVIDIA Nemotron Labs Dory1.0 4B BF16 at Q4_K_M (3.1 GB), including AMD Ryzen AI 9 HX 370 (Strix Point) Laptop, ASUS Ascent GX10, Beelink GTR9 Pro (Ryzen AI Max+ 395, 128 GB), Framework Desktop (Ryzen AI Max+ 395, 128 GB). Apple Silicon Macs use unified memory shared between CPU and GPU, making them well-suited for local LLM inference.