FLUX.1-Kontext-dev
nvidia/flux-1-kontext-devBy NVIDIA · released 2025-08-12
Prices in USD per 1M tokens. Unknown means the provider does not publish per-token pricing.
Capabilities
Model fit scores
0–100 · higher is betterThese scores reward declared capabilities, context size, price and provider availability — they are not benchmark results. Use them as a directional signal alongside your own evaluation.
Coding1
- Tool calling0/40
- Structured output0/20
- Reasoning0/10
- Context window (100K → 1M)0/20
- Provider availability1/10
Agents16
- Tool calling0/35
- Structured output0/25
- Reasoning0/15
- Output token limit15/15
- Provider availability1/10
JSON / structured output0
- Structured output / JSON mode0/50
- Tool calling0/20
- Temperature control0/10
- Price-friendly for high-volume0/20
Cost efficiency0
- Has published price0/100
Long context0
- Context ≥ 100K0/100
Vision60
- Accepts image input50/50
- Context window (10K → 1M)9/30
- Has published price0/10
- Provider availability1/10
Production-readiness45
- Number of independent providers5/40
- Has published per-token price0/20
- Context window ≥ 8K15/15
- No data inconsistencies across providers10/10
- Official model (not derivative)15/15
Cost Efficiency Index
Open full calculator →Estimated cost using the recommended provider's headline rate. Each scenario fixes average input/output tokens — the assumptions are shown in the third column.
This model has no published per-token price, so we can't compute a cost estimate. See the provider's official pricing page for current rates.
Available on 1 providers
| Provider | Provider model id | Input / 1M | Output / 1M | Context | Released |
|---|---|---|---|---|---|
| Nvidia nvidia | black-forest-labs/flux_1-kontext-dev | Unknown | Unknown | 41K | 2025-08-12 |
Frequently asked questions
How much does FLUX.1-Kontext-dev cost?
FLUX.1-Kontext-dev does not have a publicly published per-token price in our data source. This usually means it is gated behind enterprise sales or invite access. Check NVIDIA's official pricing page for the most current rates.
What is the context window of FLUX.1-Kontext-dev?
FLUX.1-Kontext-dev has a context window of 41K tokens, with a max output of 41K tokens per reply. This is the total combined size of prompt + completion.
Does FLUX.1-Kontext-dev support tool calling?
No. FLUX.1-Kontext-dev does not support tool calling (function calling). If your workflow requires it, look at the /capabilities/tool-calling list for alternatives.
Does FLUX.1-Kontext-dev support structured output / JSON mode?
Support for structured output / JSON-schema-constrained decoding is not reported for FLUX.1-Kontext-dev in our data source. Verify with NVIDIA's official documentation before relying on it in production.
Can FLUX.1-Kontext-dev accept image input?
Yes. FLUX.1-Kontext-dev accepts both text and image input. Vision pricing per image is usually billed on top of the regular token rate — check NVIDIA's docs for the exact rule.
Is FLUX.1-Kontext-dev open-weight?
Yes. FLUX.1-Kontext-dev's weights are publicly available, so you can self-host or fine-tune. Note that open weights ≠ open source — the training data and code are typically not released.
What are the best alternatives to FLUX.1-Kontext-dev?
If FLUX.1-Kontext-dev doesn't fit, consider Nemotron 3 Super, nemotron-3-nano-30b-a3b, nvidia-nemotron-nano-9b-v2. Each one targets the same use case — see the Related links below for direct head-to-head pages.
Where does this data come from?
All numbers come from the public models.dev API and are normalised into a single canonical model record. We re-pull daily and write any changes (price, context, capability) to the /changelog page.
Explore more
More NVIDIA models
- Nemotron 3 Super$0.20 in / $0.80 out
- nemotron-3-nano-30b-a3b$0.05 in / $0.20 out
- nvidia-nemotron-nano-9b-v2$0.04 in / $0.16 out
- Llama 3.3 Nemotron Super 49B v1.5$0.05 in / $0.25 out
- Llama 3.3 Nemotron Super 49B v1$0.15 in / $0.15 out
Capability lists this model is in
Last updated:
Data is sourced from models.dev and normalized for comparison. Prices and capabilities may change. Always verify critical production decisions with the provider's official documentation.