Skip to content
ProviderBench home

Black Forest Labs: FLUX.2 Flex provider comparison

black-forest-labs/flux.2-flex

FLUX.2 [flex] excels at rendering complex text, typography, and fine details, and supports multi-reference editing in the same unified architecture. Pricing is as follows, [per the docs](https://bfl.ai/pricing?category=flux.2): We charge $0.06...

Endpoints:
1
Context:
67.3K
Input:
text, image
Output:
image

Visual comparison

Endpoint pricing chart

Compare published endpoint pricing visually.

Effective price by endpoint

USD per megapixel for input image. Lower is better.

Only directly comparable published units are charted.

Server-rendered comparison

Provider endpoints

Image prices use OpenRouter’s dedicated endpoint billing records and retain their published units. Missing speed data never removes an endpoint.

Endpoint comparison for Black Forest Labs: FLUX.2 Flex
Provider / routeCurrent pricingSpeed measurementsEndpoint details
Provider / route
Black Forest Labsblack-forest-labs
Current pricing
  • $0.06 per megapixel (input image)
  • $0.06 per megapixel (output image)
Speed measurements
500-token response
Not applicable
Response starts
Insufficient recent data
Output speed
Insufficient recent data
Endpoint details
Uptime (30 min)
Insufficient recent data
Context
67.3K
Model format
N/a
Max output
N/a
4 parameters

input_references, n, output_format, seed

Endpoint data fetched .

FLUX.2 Flex deployment guide

How to choose a FLUX.2 Flex inference provider

FLUX.2 Flex is indexed here as a image model by Black Forest Labs, with 1 provider endpoint from Black Forest Labs. The comparison preserves each exact OpenRouter routing tag so pricing and performance observations can be connected to the route an application would actually request.

Match the endpoint to the workload

The model publishes a 67.3K-token context window. It accepts text, image input and returns image output. 4 distinct supported parameters appear across the listed routes. Confirm limits on the specific endpoint rather than assuming every host exposes the same configuration.

Compare image billing units directly

At least one megapixel is published consistently across the listed endpoints, allowing a direct price chart for input image. Other charges remain in the table using OpenRouter’s exact billing labels.

Verify route format and availability

No model-format or quantization labels are currently published. Availability, rate limits, and regional support can change independently of catalog pricing, so confirm the selected routing tag before production deployment.