NVIDIA

Nemotron 3.5 Content Safety

Generally availableOpen weights131K contextReasoning

Summary

Nemotron 3.5 Content Safety is an open-weight language model from NVIDIA, released on 2 Jun 2026. It accepts text and images and generates text, with a 131K-token context window and up to 118K output tokens per response. As of 18 Nov 2026, the lowest listed API price is $0.20 per million input tokens and $0.20 per million output tokens (OpenRouter), across 2 providers we track.

Safety model for policy screening, moderation, and risk-aware routing workflows

Last verified 18 Nov 2026. Every figure on this page links to its source.

Specifications

DeveloperNVIDIA
Release date2 Jun 2026 [models.dev]
StatusGenerally available [models.dev]
WeightsOpen weights [Hugging Face]
Licenseopenmdw-license-agreement [Hugging Face]
Parameters4.3B [Hugging Face]
Context window131K (131,072 tokens) [models.dev]
Max output118K tokens [models.dev]
InputText and images [models.dev]
OutputText [models.dev]
Reasoning modeYes [models.dev]
Tool callingNo [models.dev]
Structured outputNo [models.dev]
Hugging Facenvidia/Nemotron-3.5-Content-Safety [Hugging Face]

Nemotron 3.5 Content Safety API pricing by provider

USD per million tokens. Sorted by input price.

ProviderInputOutputCached inputContextSource
NVIDIA NIM
nvidia/nemotron-3.5-content-safety
FreeFree–128Kmodels.dev, 18 Nov 2026
OpenRouter
nvidia/nemotron-3.5-content-safety
$0.20$0.20–131KOpenRouter, 18 Nov 2026

Running Nemotron 3.5 Content Safety locally

Estimated memory, from the parameter count and the architecture in config.json on Hugging Face. Includes about 0.8 GB of runtime overhead.

QuantizationWeightsTotal, 8K contextTotal, 32K context
Q4_K_M (4-bit)2.6 GB3.7 GB4.2 GB
Q8_0 (8-bit)4.6 GB5.7 GB6.2 GB
FP16 / BF16 (16-bit)8.6 GB9.7 GB10 GB

At 4-bit with an 8K conversation, Nemotron 3.5 Content Safety needs about 3.7 GB, so it fits on a graphics card with 8 GB or more, such as the NVIDIA GeForce RTX 4060 8 GB. Check your own hardware, or see Running local LLMs on an 8 GB GPU on our sister site AIPCs.

Frequently asked questions

What is the context window of Nemotron 3.5 Content Safety?

Nemotron 3.5 Content Safety has a context window of 131,072 tokens (131K) and can generate up to 117,964 tokens in a single response, according to models.dev.

How much does the Nemotron 3.5 Content Safety API cost?

Nemotron 3.5 Content Safety is listed from $0.20 per million input tokens and $0.20 per million output tokens (OpenRouter). Prices last verified 18 Nov 2026.

Is Nemotron 3.5 Content Safety open source?

Nemotron 3.5 Content Safety is an open-weight model: its weights are published on Hugging Face as nvidia/Nemotron-3.5-Content-Safety under the openmdw-license-agreement license. Check the license terms before commercial use.

When was Nemotron 3.5 Content Safety released?

NVIDIA released Nemotron 3.5 Content Safety on 2 Jun 2026, according to models.dev.

Which providers offer Nemotron 3.5 Content Safety?

We track Nemotron 3.5 Content Safety on 2 providers: NVIDIA NIM, OpenRouter.

How much VRAM does Nemotron 3.5 Content Safety need?

About 3.7 GB at 4-bit (Q4_K_M) with an 8K-token conversation, and about 5.7 GB at 8-bit. The 4-bit model fits on a graphics card with 8 GB or more, such as the NVIDIA GeForce RTX 4060 8 GB. These are estimates from the model's published parameter count and architecture.

Similar models from other labs

Comparable on output type, weights, release date, price and context window. Prices are the lowest listed, USD per million tokens.

ModelLabReleasedContextInput $/1MOutput $/1MWeights
Gemma 4 12B ITGoogle DeepMind9 Jun 2026262K$0.10$0.30Open
Granite 4.2 8BIBM25 Aug 2026131K$0.06$0.15Open
Gemma 4 26B A4B ITGoogle DeepMind2 Apr 2026262K$0.07$0.30Open
GLM-4.7-FlashXZhipu AI (Z.ai)19 Jan 2026200K$0.06$0.40Open
GLM-4.7-FlashZhipu AI (Z.ai)19 Jan 2026200K$0.06$0.40Open
Hy3Tencent (Hunyuan)6 Jul 2026262K$0.13$0.53Open

Change history

  • Max output changed from 8K to 118K
  • Context window changed from 128K to 131K
  • Max output changed from 118K to 8K
  • Context window changed from 131K to 128K
  • Context window changed from 128K to 131K
  • Max output changed from 8K to 118K
  • Max output changed from 118K to 8K
  • Context window changed from 131K to 128K
  • Max output changed from 8K to 118K
  • Context window changed from 128K to 131K
  • Max output changed from 118K to 8K
  • Context window changed from 131K to 128K
  • Max output changed from 8K to 118K
  • Context window changed from 128K to 131K
  • Max output changed from 118K to 8K
  • Context window changed from 131K to 128K
  • Max output changed from 8K to 118K
  • Context window changed from 128K to 131K
  • Context window changed from 131K to 128K
  • Max output changed from 118K to 8K
  • Max output changed from 8K to 118K
  • Context window changed from 128K to 131K
  • Max output changed from 118K to 8K
  • Context window changed from 131K to 128K
  • Context window changed from 128K to 131K

Sources