DEVELOPER REFERENCE · VERIFIED MODEL EVIDENCE

Compare 5 source-verified model records, repository licenses, published weight formats and dated evidence. No overall model ranking.

Evidence statusSource-first verified
Latest record check2026-11-13
Latest record full verification2026-10-29

DIRECT ANSWER · SOURCE-OBSERVED REGISTRY

What Black Forest Labs model evidence is available?

Open Model Weights currently tracks 5 field-verified Black Forest Labs model records. In this indexed sample, the recorded modalities are 3 Image → image; 2 Text → image. The published repository license labels include 2 apache-2.0; 2 other; 1 FLUX Non-Commercial License v2.1. The listed weight formats include Safetensors (5).

Coverage describes the model repositories indexed here, not every model released by the publisher. A checked source, an unknown field and an unchanged source revision are different states. No missing value is treated as a negative answer.

5verified model records
2recorded modalities
3distinct license labels
5model repository links

SOURCE-BACKED PUBLISHER PROFILE

Black Forest Labs: models, research and access

Black Forest Labs describes itself as a visual-intelligence research laboratory. Its official About page refers to labs in Freiburg and San Francisco. These are publisher-level locations, not evidence of the model's training, inference or data residency.

The indexed FLUX repository records span text-to-image generation and image editing. BFL also offers API products and additional variants; the records below are a verified sample, not its complete commercial catalog.

01

What does Black Forest Labs build?

The publisher develops visual AI systems under the FLUX name, including image generation and editing. Its public pages distinguish API products from certain downloadable weight checkpoints. OMW's five indexed entries are individually checked repositories, not an exhaustive list of product releases.

02

FLUX.1 and FLUX.2 in the checked registry

Here, FLUX.1-dev and FLUX.1-schnell are classified as text-to-image records. FLUX.1-Kontext-dev, FLUX.2-dev and FLUX.2-klein-4B appear as image-to-image records. This describes model-record metadata, not universal capabilities of every deployment or hosted endpoint.

03

Download weights or access a hosted API?

BFL provides both hosted APIs and downloadable checkpoint options for different FLUX products. The publisher's FLUX.2 [klein] information distinguishes Apache-2.0 4B variants from 9B variants with non-commercial terms. API availability does not imply a right to self-host or redistribute every checkpoint.

04

What should commercial adopters verify?

The publisher's FLUX [dev] Non-Commercial License describes research, evaluation and other non-commercial rights; uses outside the permitted scope require separate authorization. Independently licensed models such as FLUX.1-schnell and FLUX.2-klein-4B have Apache-2.0 labels in our registry. Review the exact repository license and revision rather than transferring terms between models.

Publisher background is attributed to official sources. Model counts and license classifications come from OMW repository evidence; no model benchmark or processing location is inferred.

MODEL-BY-MODEL REFERENCE

Which Black Forest Labs model should I inspect?

Browse by published modality and licensing evidence. These are navigation cues, not quality, speed or suitability rankings.

Text → imageother

FLUX.1-dev

Text-to-image generation

Open the original FLUX.1-dev checkpoint and read the individual non-commercial license before any production use.

Commercial use: unknownLicense evidence →
Text → imageapache-2.0

FLUX.1-schnell

Text-to-image; Apache-2.0 label

Inspect the separate Apache-2.0-labeled FLUX.1-schnell repository if permissive weight licensing matters.

Commercial use: allowedLicense evidence →
Image → imageother

FLUX.1-Kontext-dev

Editing and reference images

Inspect the FLUX.1-Kontext-dev image-to-image record and its own [dev] license restrictions.

Commercial use: unknownLicense evidence →
Image → imageFLUX Non-Commercial License v2.1

FLUX.2-dev

FLUX.2 image editing

Review the FLUX.2-dev record for published weight artifacts, source history and the applicable custom terms.

Commercial use: not-allowedLicense evidence →
Image → imageapache-2.0

FLUX.2-klein-4B

Compact FLUX.2; Apache-2.0 label

Review the recorded 4B image-editing checkpoint and its license; parameter count alone does not establish speed.

Commercial use: allowedLicense evidence →

RELATED RESEARCH & RELEASES

Source-backed publisher coverage

News about additional products is not automatically a field-verified registry addition.

FIELD-BY-FIELD COMPARISON · PRIMARY LINKS

Model evidence at a glance.

Compare the exact entries in our registry. Parameter values are taken from the source-checked record; a license label is not a legal opinion, and recognized weight files are not an inference-speed benchmark. Open each record for the underlying citations and observed history.

Model and parameter countModalityLicense evidenceFormats and filesSource and history
FLUX.1-dev11.9014B published parametersText → imageotherunknown commercial-use classificationLicense file ↗Safetensors11 filesRepository ↗Model evidence →History →
FLUX.2-klein-4B3.87554B published parametersImage → imageapache-2.0allowed commercial-use classificationLicense file ↗Safetensors6 filesRepository ↗Model evidence →History →
FLUX.2-dev32.2233B published parametersImage → imageFLUX Non-Commercial License v2.1not-allowed commercial-use classificationLicense file ↗Safetensors22 filesRepository ↗Model evidence →History →
FLUX.1-schnell11.8912B published parametersText → imageapache-2.0allowed commercial-use classificationInspect license evidence →Safetensors11 filesRepository ↗Model evidence →History →
FLUX.1-Kontext-dev11.9014B published parametersImage → imageotherunknown commercial-use classificationLicense file ↗Safetensors11 filesRepository ↗Model evidence →History →

LICENSE & COVERAGE · NOT LEGAL ADVICE

How do the recorded licenses differ?

Different models from the same developer can use different license terms. The distribution below describes the labels and field-level classifications observed in the listed repositories; it does not automatically establish permissions for a specific deployment.

License labels

  • apache-2.02 of 5
  • other2 of 5
  • FLUX Non-Commercial License v2.11 of 5

Commercial-use classifications

  • allowed2 of 5
  • unknown2 of 5
  • not-allowed1 of 5

Model modalities

  • Image → image3 of 5
  • Text → image2 of 5

A classification of unknown is not a prohibition. Even a recognized permissive license can carry conditions. Review the license for the exact model and revision. Open the license explorer →

EVIDENCE METHOD · TRANSPARENT LIMITS

How this developer profile is assembled.

We aggregate the current source-checked model records, rather than publish an unverified corporate biography. Repository metadata, model cards, license files and recognized weight artifacts supply the facts where available. The record-check date does not assert that a model or its license changed on that date.

Source-derived runtime signals are not hardware benchmarks. Weight-only memory estimates omit runtime overhead, activations and other deployment requirements. Model-specific uncertainties remain visible in the individual evidence records.

QUESTIONS · DIRECT ANSWERS

Frequently asked questions about Black Forest Labs models.

Which Black Forest Labs models are covered?

Open Model Weights currently lists 5 field-verified records for Black Forest Labs. Their recorded model modalities are: 3 Image → image; 2 Text → image. This is a registry sample, not an exhaustive publisher catalog.

Which licenses are recorded for Black Forest Labs models?

In the 5 indexed records, repository license labels are: 2 apache-2.0; 2 other; 1 FLUX Non-Commercial License v2.1. License labels do not replace the model-specific terms or establish rights for every use case.

Where can I verify Black Forest Labs model information?

Each indexed model links to its official source repository and a field-level Open Model Weights profile. The most recent record checks shown here reach 2026-11-13; checking a repository does not imply that its contents changed.

Where is Black Forest Labs based?

Black Forest Labs identifies laboratories in Freiburg, Germany, and San Francisco, United States, on its About page. That does not establish any model's processing or training data residency.

Are all Black Forest Labs FLUX weights available for unrestricted commercial use?

No blanket permission follows from weight availability. BFL publishes separate FLUX [dev] non-commercial terms, while its FLUX.2 [klein] 4B variants are described with Apache-2.0 licensing. Check each repository and license revision.

Does Black Forest Labs API access mean its weights are downloadable?

No. API access and rights to download, modify or self-host weights are distinct. BFL documents both API products and model-specific self-hosting licenses; the registry verifies only the listed repositories.

COMPLETE INDEXED SELECTION

All 5 indexed model profiles.