FLUX Licensing in Plain Terms: A Practical Guide

Summary (TL;DR)

• FLUX.1-schnell: Apache 2.0 license — commercial use allowed with attribution. Sell generated images, integrate into paid products.
• FLUX.1-dev: Non-commercial license — free for research/personal use. Paid BFL commercial license required for business use (since June 2025).
• FLUX.1-pro: Closed model — API-only, enterprise pricing, no public standalone license document.
• LoRAs: Derivatives of dev models inherit the same non-commercial restrictions unless you hold a BFL commercial license.
• Key ambiguity: Selling images created under the dev license is legally untested — the license permits commercial use of outputs but prohibits commercial generation with the model.

Introduction

The FLUX family of AI models offers multiple licensing tiers that affect commercial viability. Understanding these differences matters for businesses evaluating AI image generation. This article breaks down what FLUX.1-schnell, FLUX.1-dev, and FLUX.1-pro each permit — whether you can sell the output, how LoRAs trained on dev are treated, and where the ambiguity remains.

For additional context on training workflows, see our FLUX LoRA Training Parameters guide. For more details on specific license tiers, see Apache 2.0 license reference.

FLUX.1-schnell: The Apache 2.0 License

Apache 2.0 is the permissive open-source standard. It grants comprehensive rights, including commercial use, while requiring attribution. The FLUX.1-schnell model card on GitHub explicitly states it is "Released under the apache-2.0 licence, the model can be used for personal, scientific, and commercial purposes." [^1] The HuggingFace API confirms the license tag as apache-2.0. [^2]

What Apache 2.0 Allows

• Personal projects
• Scientific research
• Commercial use
• Sale of generated images
• Integration into paid products
• No royalty requirements (with attribution)

Using FLUX.1-schnell Commercially

Businesses can deploy FLUX.1-schnell in production environments without additional licensing fees. The model supports revenue-generating applications. Developers can modify and distribute the model as long as they maintain Apache license compliance, which primarily means preserving the copyright notice and license text in distributions.

The GitHub repo explicitly lists FLUX.1-schnell with apache-2.0 as the license for the weights and inference code. [^1]

FLUX.1-dev: The Non-Commercial License

The FLUX.1-dev license is a custom non-commercial license. The full text is available on GitHub as "FLUX.1 [dev] Non-Commercial License v1.1.1." [^3] The GitHub repo lists FLUX.1 Fill, Depth, Canny, Redux, Kontext, and Krea — all sharing this same non-commercial license. [^1] On HuggingFace, the FLUX.1-dev model is tagged license:other. [^4]

Defining Non-Commercial Use

The license restricts use to "Non-Commercial Purposes." The license defines this as uses where you do not receive any direct or indirect payment from the model's use. [^3]

Acceptable non-commercial uses include:

• Personal research and experimentation
• Private hobby projects
• Academic testing in non-production environments
• Commercial entity testing and evaluation (non-production only)

Prohibited uses include any activity generating direct or indirect payment, including:

• Revenue-generating applications
• Products sold to end users
• Using outputs to train competitive models
• Production deployments in business contexts

The June 2025 Commercial License Update

Previously, FLUX.1-dev had no official commercial self-hosting pathway. In June 2025, Black Forest Labs introduced the "Self-Hosted Commercial License Terms," which was "Last Revised on June 26, 2025." [^5] This paid license creates a legal mechanism for businesses to use FLUX.1-dev commercially, adding fees based on usage. The base model itself remains under the non-commercial license unless you purchase the commercial license separately.

The self-hosted commercial license permits "creating and hosting FLUX [dev] Models and Derivatives... solely for the purpose of integrating them into a Customer Application," but prohibits redistribution via API endpoints and reselling. [^5]

Testing and Evaluation Exception

The non-commercial license explicitly allows commercial entities to use FLUX.1-dev for "testing, evaluation, or non-commercial research and development in a non-production environment." [^3] This exception enables evaluation without purchasing a license, as long as the testing does not generate revenue or serve end users.

FLUX.1-pro: The Closed Commercial Model

FLUX.1-pro sits outside the open-weights ecosystem entirely. The official GitHub repo describes it as a "Pro tier non-open weight model." [^1] It is available through the BFL API (currently at bfl.ml), Replicate.com, and Fal.ai. [^1]

Pricing and Licensing

BFL's commercial licensing page outlines tiers — Builder, Platform, Professional, and Enterprise — with the Enterprise tier offering "All models + new releases" and "permissive commercial use." [^6] The exact standalone licensing terms for FLUX.1-pro are not publicly documented on a separate page.

What We Know and What Remains Unverified

FLUX.1-pro is not available for self-hosting or local deployment. It is API-only. The specific license governing FLUX.1-pro has not been published publicly, and no public license document was found during this research — this is a gap that should be checked with BFL directly before making licensing decisions.

Commercial Output: Selling Generated Images

The License Text

The FLUX.1-dev license explicitly states: "We claim no ownership rights in and to the Outputs. You are solely responsible for the Outputs you generate and their subsequent uses in accordance with this License. You may use Output for any purpose (including for commercial purposes)." [^3]

The Restriction

The same license restricts using the model itself to "Non-Commercial Purposes only." [^3] This creates a paradox: the output can be used commercially, but generating that output commercially with the dev model may violate the license.

Practical Paths for Businesses

For businesses selling AI-generated images:

1. Legal path: Purchase BFL's commercial self-hosted license
2. Alternative path: Use FLUX.1-schnell (Apache 2.0) for commercial generation
3. Gray area: Using the dev model for business output generation is not explicitly tested in case law — the output-use permission and the non-commercial generation prohibition create conflicting signals

How LoRAs Trained on Dev Models Are Treated

LoRAs are fine-tuned weight adaptations derived from base models. The FLUX.1-dev license defines a "Derivative" as "any (i) modified version of the FLUX.1 [dev] Model (including but not limited to any customized or fine-tuned version thereof)." [^3] LoRAs fit this definition. The license states that any restrictions applying to FLUX.1-dev also apply to Derivatives created from it. [^3]

Community LoRAs

Popular community LoRAs like "Amateur Photography" [^7] and "iPhone Photo" [^8] on Civitai both display the FLUX.1-dev Non-Commercial License. These LoRAs derive from the FLUX.1-dev base model and carry the same non-commercial restrictions.

Commercial LoRA Rights

BFL's commercial licensing tiers include "Fine-tuning & LoRA rights." [^6] This means:

• Builder tier: LoRA creation rights within a single domain
• Platform tier: LoRA rights with expanded usage scope
• Professional tier: LoRA rights for client work (the first three clients are included) [^6]

Community-created LoRAs may carry additional restrictions imposed by their creators, which vary from LoRA to LoRA.

For related reading on community model creation, see Civitai FLUX models overview.

For implementation guidance, see our FLUX LoRA Training Parameters dossier and the commercial use FAQ.

Common Errors and Fixes

Error 1: Assuming "Non-Commercial" Means Only Non-Profit

Fix: The FLUX.1-dev license defines "Non-Commercial Purpose" by whether payment is received, not by organization type. A for-profit company can use FLUX.1-dev for testing if it receives no direct or indirect payment from the use. [^3]

Error 2: Selling Generated Images as "Personal Use"

Fix: Personal use excludes revenue-generating activity under the license. Selling prints or derivatives created with FLUX.1-dev in a commercial context violates the license, regardless of whether the output ownership is retained. [^3]

Error 3: Using Dev License for Production Deployment

Fix: Production deployment in any business context requires BFL's commercial self-hosted license. The free dev license covers testing and non-production evaluation only. [^3][^5]

Error 4: Assuming All LoRAs Allow Commercial Use

Fix: Verify each LoRA's specific license. Community-created LoRAs inherit the FLUX.1-dev non-commercial license regardless of whether you hold a commercial license for the base model. [^7][^8]

Error 5: Attempting to Self-Host FLUX.1-pro

Fix: FLUX.1-pro is API-only. Self-hosting it is not supported. Use open-weight models like FLUX.1-schnell (Apache 2.0) for local deployment, or FLUX.1-dev with a commercial license for self-hosted business use. [^1]

Frequently Asked Questions

Can I sell images generated with FLUX.1-dev?

Selling images created with FLUX.1-dev is legally untested territory. The output-use clause permits commercial use of outputs, but the non-commercial generation clause prohibits commercial use of the model itself. Purchasing BFL's commercial license or switching to FLUX.1-schnell are the paths with clear legal standing. [^3]

Do I need a commercial license to use FLUX.1-dev for business evaluation?

The non-commercial license allows commercial entities to use FLUX.1-dev for testing and evaluation in non-production environments, provided no revenue is generated. [^3] The June 2025 commercial license adds a paid pathway for production use. [^5]

Can I use community LoRAs commercially if I have the commercial license?

The BFL commercial license covers your use of FLUX.1-dev and its derivatives for commercial purposes. [^6] However, community LoRAs may have their own additional terms — check each LoRA's page for specific restrictions. [^7][^8]

Is FLUX.1-pro available for self-hosting?

No. FLUX.1-pro is strictly API access. The GitHub repo explicitly excludes it from the open-weights table. Self-hosting requires open-weight models. [^1][^6]

What changed with the June 2025 license update?

Commercial self-hosting became officially available through BFL's paid licensing tiers. Before June 2025, there was no published commercial self-hosting pathway for FLUX.1-dev. [^5]

Sources

Conclusion

The FLUX ecosystem offers three distinct paths for commercial AI image generation:

1. Apache 2.0 freedom (FLUX.1-schnell) — immediate commercial use with attribution
2. Paid commercial access (FLUX.1-dev + BFL commercial license) — controlled deployment with legal protection
3. Enterprise API access (FLUX.1-pro) — closed model usage through commercial tiers

For most commercial applications, FLUX.1-schnell provides the simplest path to market with clear licensing. Businesses requiring the capabilities of FLUX.1-dev should purchase BFL's commercial license before generating output for sale. Always verify current licensing terms with BFL directly before deploying in production environments.

JSON-LD