NVIDIA's latest answer to "small models, small memory" shipped on October 23: Nemotron 3.5 Bolt E4B 4GB, an open small language model post-trained on Google's Gemma-4-E4B-it. It packs 8B total parameters (4B effective) into roughly 4GB of memory in its target workloads, and it is not aimed at data centers — the named targets are Jetson Orin Nano 8GB, RTX 5070 12GB-class edge hardware, voice assistants, in-game NPCs, and robot human-machine interfaces.
What fits in 4GB
Per the official model card, Bolt E4B ships primarily as a Q4_K_M quantized release: ~4GB memory in target workloads, 64K context, 35 languages supported (the base was pre-trained on 140+). Every feature is built around interactive agents: multi-turn tool use with asynchronous-call integration guidance, a toggleable conversational mode that encourages concise speech-ready replies, and configurable reasoning — thinking on for hard requests, off for fast ones, with a cap option to meet latency targets.
Official measured numbers (Q4_K_M, batch size 1, llama.cpp) tell the positioning story: 3.5GB VRAM, 548ms time to first token and 133.4 tokens/s on an RTX 5070 12GB; 4.2GB and 15.5 tokens/s on a Jetson Orin Nano 8GB. The blog also demos a Reachy Mini robot on Jetson Orin Nano 8GB, where Cosmos 3 Edge supplies real-time visual understanding while Bolt E4B drives animation scripts and spoken responses.
Talks less, does more
Two vendor numbers stand out: roughly 40% higher average quality than the prior Nemotron 3 Nano 4B on conversational-agent benchmarks (about 10% over other peers evaluated), and up to ~80% fewer output tokens than peers in reasoning-enabled comparisons. On edge devices, generating fewer tokens is not just cost math — decoding work maps directly to latency and power, which is why brevity is a feature here.
The post-training recipe behind that brevity is documented: RLVR plus RLHF via NeMo-RL and NeMo-Gym, with every training sample used in both reasoning and non-reasoning modes at a 2:1 non-reasoning-to-reasoning ratio per batch. As answers grew longer during training, the team increased group-relative length penalties in the GenRM environment to control verbosity.
Wins on its home field, loses on general benchmarks
Read the official benchmark tables row by row and the direction is more honest than the headline. The wins cluster in conversation and persona: MultiChallenge 53.1 (vs Qwen3.5-4B 51.8, Gemma-4-E4B 42.1), RoleBench 67.0, RoleMRC 80.6, instruction-hierarchy IHEval 84.8, When2Call-MT 63.4 and LongMemEval 72.1 — all best among the four compared models. But it does not sweep general agent benchmarks: Tau2-Bench 55.1 clearly trails Qwen3.5-4B's 75.1, BFCL-v3 68.5 sits below Qwen's 70.9, RULER 64K at 87.0 ranks behind Qwen's 95.1 and even Nano's 91.5, and EQ-Bench 39.4 is slightly below the original Gemma-4-E4B's 41.1. NVIDIA itself concedes the benchmarks were chosen to reflect customer workloads — "choosing a model is not as simple as picking the highest leaderboard score." Read the trade-offs before deploying.
Quantization and speed: the recipe ships too
The BF16 checkpoint was quantized to Q4_K_M with llama.cpp importance-matrix (imatrix) calibration, using roughly 1M tokens of RL rollouts from the same training step as the selected checkpoint — calibration data that tracks the training run is a reusable engineering detail. The release also includes a DFlash parallel drafter that proposes all draft tokens in one forward pass; NVIDIA reports up to 21% higher throughput versus Gemma-4-E4B's original MTP drafter. Four checkpoints (GGUF, DFlash, BF16, BF16-DFlash-NVFP4) are out, available day-one on Ollama, LM Studio, Unsloth and the Jetson AI Lab, under the OpenMDW-1.1 license.
So what
Edge-model competition is shifting from "who scores highest" to intelligence per GB and tokens per second. Bolt E4B's play: take Google's base, specialize with NVIDIA's post-training recipe at the 4GB tier, then open-source the recipe itself — models age, reproducible recipes and quantization details are what stay. And the benchmarks it loses to Qwen are a useful reminder: vendor charts always grow on their home field; your workload is the only referee.
Refs: research.nvidia.com/labs/nemotron/NVIDIA-Nemotron-3.5-Bolt-E4B-4GB/ ; huggingface.co/nvidia/NVIDIA-Nemotron-3.5-Bolt-E4B-4GB