Is FLUX 3 Image Open Source? Weights and Local Access

FLUX 3 Image has a documented commercial weights offer, but we did not find an official public Image checkpoint in the catalogs checked on October 9, 2026. BFL says companies can license the model to fine-tune and deploy on their own infrastructure. That establishes a commercial self-hosting route; it does not establish a freely downloadable open-source release.^[1]^[2]

The distinction is easy to miss because Black Forest Labs also publishes open-weight models, inference repositories, and API tools. This guide separates the Image product from those neighboring releases and identifies what you can verify before planning local deployment. Its catalog audit covers BFL's public Hugging Face listings and all repositories shown by its official GitHub organization.^[2]^[3]

TL;DR

Commercial FLUX 3 Image weights are an explicit offer. BFL's product page invites companies to discuss fine-tuning and deployment on their own infrastructure.^[1]
No official public Image download was found in this check. The complete Hugging Face model catalog contained no FLUX 3 Image or FLUX 3 Dev checkpoint on October 9.^[2]
FLUX 3 Action is a different model. Its public base checkpoint is a 7B world action model for actions and predicted video frames, with its own model license.^[4]
The Dev roadmap is separate. BFL's original announcement distinguished Image API/private-weight access from a planned FLUX 3 Dev open-weight backbone.^[5]
A hosted launch does not imply a checkpoint release. The October 1 Image release note describes an endpoint for generation and editing.^[6]

What the FLUX 3 Image weights offer actually says

The current Image product page has a Commercial weights section. It says FLUX 3 Image is available under a commercial weights license for companies running image generation at scale, and explicitly mentions fine-tuning and deployment on the customer's infrastructure. Its next step is contact with BFL.^[1]

This is stronger evidence than guessing that self-hosting must be impossible because no public checkpoint appears. It is also narrower than claiming that anyone can download the model, redistribute it, or run it under a familiar license from another FLUX release.

The public statement does not identify a downloadable Image package or provide the model-specific commercial agreement. A team evaluating that route needs to establish what it would receive and what its agreement would permit. The product page alone cannot answer every deployment or redistribution question.

Treat “commercial weights available” as a specific procurement option. Treat “public weights released” as a different claim that needs an official model repository, actual model files, and the applicable terms. The same product can have a licensed deployment route without a general public download.

For the FLUX 3 Image launch date itself, see the release timeline. The October date answers when the hosted product launched; it does not resolve every form of local access.

What we found in the official public catalogs

On October 9, we read both pages of Black Forest Labs' Hugging Face model catalog. It showed 38 models. The FLUX 3 entries were Action base, SO-101, and DROID; the remaining entries belonged to earlier FLUX model families and their variants. No FLUX 3 Image or FLUX 3 Dev checkpoint appeared.^[2]

We also checked the official GitHub organization, which displayed all nine public repositories. Its descriptions included FLUX.1 and FLUX.2 inference code, FLUX 3 Action, a Python cloud client, an MCP server, and agent skills. None was presented as a FLUX 3 Image inference repository.^[3]

Evidence checked	What it establishes	What it does not establish
Official Image product page	A commercial weights offer	A public checkpoint download or a specific open-source license
Both pages of BFL's Hugging Face catalog	The public model listings visible on the inspection date	The contents of private customer deliveries
Complete BFL GitHub repository list	Public code projects and their stated purposes	That every code project includes model weights
FLUX 3 Action model card	A downloadable Action component with its own scope	An Image-generation checkpoint

This is a dated audit, not a prediction. An official checkpoint added after October 9 would change the download answer. Until that evidence appears, an installation guide should not invent a repository name or ask readers to substitute an unrelated model.

A FLUX 3 Image community article hosted on Hugging Face is also not the same thing as a model repository published by Black Forest Labs. Check the author, model card, file list, and declared task. A familiar hosting domain does not establish which model the page contains.

Why FLUX 3 Action and FLUX 3 Dev cause confusion

The public flux-3-action-base model card describes a 7B world action model. It takes camera frames, robot state, and a text instruction, then predicts a chunk of actions together with future video frames. The base repository is an adaptation component rather than a complete robot policy.^[4]

That is useful evidence about Action. It is not a basis for calling FLUX 3 Image a 7B model, publishing its memory requirements, or telling image creators to download the Action base. Shared family naming does not make the checkpoints interchangeable.

The Action card also distinguishes licenses: the model falls under the FLUX Kommunity License, the included text encoder has its own license, and the inference/training code has a separate license. Even within that one release, a code license should not automatically be assigned to every component.^[4]

FLUX 3 Dev is another separate name. In the July announcement, BFL listed an open-weight multimodal backbone under that label after the stages for Video, Action partners, and Image API/private-weight access. The announcement did not supply a firm Dev release date.^[5]

The accurate reading is that BFL described a planned open-weight route and later released specific products. The Image launch alone does not prove the Dev stage has happened. A current official Dev model card and files would provide more direct evidence than repeating the original roadmap.

Choose between hosted use and a licensing conversation

The current licensing page separates standard tiers and a bespoke Enterprise offer. Its named standard-model inclusions concern FLUX.2 variants, while the Image product has its own commercial-weights invitation. Do not assume a standard purchase includes FLUX 3 Image simply because both pages use the FLUX brand.^[7]^[1]

BFL's public licensing help also distinguishes API use from a self-hosted weights license. It says direct API usage includes commercial rights without a separate commercial-weights purchase. That is a statement about BFL's API offering; a weights agreement answers a different deployment question.^[8]

Our recommendation is to start from the requirement that actually matters. If you need to create and edit images through a service, evaluate the documented hosted interface. If the model must run on infrastructure you control, ask BFL about the Image package and agreement before planning the deployment.

For the hosted model's behavior, BFL documents text generation, image editing, up to ten references, and asynchronous results. This establishes the described interface, not a performance comparison against a self-hosted configuration we have not inspected.^[9]

The FLUX 3 Image model page and reAPI documentation describe the reAPI interface. The editing guide covers reference roles and prompt-based boxes. Neither kind of guide needs to imply that public model files are available.

Resolve the missing deployment facts before choosing hardware

The official sources reviewed here do not provide a public FLUX 3 Image checkpoint package with a corresponding local installation procedure. We therefore cannot derive a verified local GPU requirement, memory budget, quantization choice, or inference command from them.

For a commercial-weights evaluation, ask for the facts specific to the package you would receive:

Question to resolve	Why it matters to the decision
Which Image checkpoint and version are included?	Identifies the model being evaluated and the update path
What runtime, dependencies, and hardware are supported?	Provides a basis for infrastructure planning
Which uses and deployment arrangements are covered?	Distinguishes your proposed use from an assumed generic license
What fine-tuning, derivative, and distribution rights apply?	Determines which planned changes and delivery methods are permitted
Which generation controls are supported in the delivered package?	Allows comparison with the hosted workflow you are evaluating
What support and update arrangements are included?	Clarifies who handles changes after deployment

These are procurement questions, not assertions about unpublished terms. The publicly linked self-hosted terms refer to selected FLUX [dev] models; that text should not be used to invent conditions for an Image agreement that has not been supplied.^[10]

The same restraint applies to performance. A memory figure for an earlier FLUX model or the Action checkpoint is not an Image specification. A proposed hardware plan becomes meaningful when it matches the exact model package and a measured workload.

Questions about FLUX 3 Image and open source

Is FLUX 3 Image open source right now?

As checked October 9, 2026, the verified offer is hosted access plus a commercial weights license. We found no official public Image checkpoint in BFL's complete public model catalog. Describe that observed status rather than promising a free download or claiming private self-hosting is impossible.^[1]^[2]

Can a company self-host FLUX 3 Image?

BFL's product page explicitly offers commercial weights for fine-tuning and deployment on a company's infrastructure. The next step is to confirm the exact package and agreement with BFL. The page does not by itself grant a license to a particular reader.^[1]

Can I download it from BFL's Hugging Face account?

No public Image checkpoint was found in either catalog page checked on October 9. FLUX 3 Action files were present, but they are a different product. Re-check the official catalog when making a new download decision because listings can change.^[2]^[4]

Is the FLUX 3 Action download the image model?

No. Its model card identifies an action model that works with camera frames, robot state, and instructions. It is not presented as the commercial Image checkpoint, and its size, license, or runtime requirements should not be assigned to Image.^[4]

Does open-source client code let me run the model locally?

Client code and model weights serve different purposes. BFL's public organization includes a cloud client, MCP tooling, and agent skills; their existence does not establish local Image inference. Look for the actual Image checkpoint and its runtime documentation before treating a repository as a local deployment path.^[3]

When will public FLUX 3 Image or Dev weights arrive?

The July roadmap described a separate Dev open-weight backbone, but the sources checked do not establish a firm public download date for it or the Image product. Use a future official release and model card to update that answer. For FLUX 3 Image today, evaluate the verified hosted or commercial-weights route against your actual needs.^[5]^[1]

Choose the access route you can verify

For FLUX 3 Image, make the next decision from evidence you can inspect: the hosted request contract, or the exact model package and agreement offered for your infrastructure. If a public download is essential, wait for an official checkpoint and its terms before writing an installation plan. Save the model name, version, source link, and date with the decision so a future release can be assessed without inheriting today's assumptions.

References

Black Forest Labs. FLUX 3 Image: Commercial weights. Retrieved October 9, 2026 from bfl.ai/models/flux-3-image.
Black Forest Labs on Hugging Face. Official model catalog, both pages. Observed October 9, 2026 at huggingface.co/black-forest-labs/models and page 2.
Black Forest Labs on GitHub. Official public repository list. Observed October 9, 2026 at github.com/black-forest-labs.
Black Forest Labs. FLUX 3 Action Base model card. Retrieved October 9, 2026 from huggingface.co/black-forest-labs/flux-3-action-base.
Black Forest Labs. FLUX 3 — Real World Models: Launch Plan. July 23, 2026; retrieved October 9, 2026 from bfl.ai/blog/flux-3.
Black Forest Labs. Release Notes: October 1, 2026. Retrieved October 9, 2026 from docs.bfl.ai/release-notes.
Black Forest Labs. Licensing. Retrieved October 9, 2026 from bfl.ai/licensing.
Black Forest Labs Help Center. How does FLUX licensing work? Retrieved October 9, 2026 from help.bfl.ai/articles/9272590838-self-serve-dev-license-overview-pricing.
Black Forest Labs. FLUX 3 Image overview. Retrieved October 9, 2026 from docs.bfl.ai/flux_3/flux3_image_overview.
Black Forest Labs. Self-Hosted Commercial License Terms. Last revised August 4, 2026; retrieved October 9, 2026 from bfl.ai/legal/self-hosted-commercial-license-terms.