# FLUX.1 License Guide: Schnell, Dev, Outputs, and API Use > Published 2026-04-06, updated 2026-09-05 · https://www.promptzone.com/zuzanna_choi/flux-ai-license-key-insights-2g8d --- title: "FLUX.1 License Guide: Schnell, Dev, Outputs, and API Use" published: true description: "Understand FLUX.1 licensing by separating schnell weights, dev model permissions, generated outputs, and commercial API access." tags: ai,imagegeneration,opensource,models --- FLUX.1 licensing depends on the model and access route: schnell weights use Apache 2.0, dev weights have non-commercial model terms with separate commercial licensing, and hosted access uses API service terms. Black Forest Labs publishes these options for its image-generation models; generated-output permissions are distinct from permission to operate dev weights. [1], [2], [5], [6] Record the exact model identifier before deciding whether a particular permission applies to your project. ## What are the key facts about FLUX.1 licensing? | Fact | Verified detail | | --- | --- | | Developer | Black Forest Labs. [1] | | Released | The original FLUX.1 family launched August 1, 2024. [1] | | Type | Image-generation models, offered as local weights and hosted inference. [1], [2] | | Size or parameters | Schnell and dev each have 12 billion parameters. [3], [4] | | License and access | Schnell: Apache 2.0; dev: non-commercial model terms or separate commercial licensing; API: service terms. [2], [5], [6] | | Where it runs | Open weights run through local inference software; pro models are accessed through hosted APIs and have no open weights. [2] | ## Which FLUX.1 access routes allow commercial use? The FLUX.1 release offers several access choices for image generation. Schnell's model card explicitly permits personal, scientific, and commercial use under Apache 2.0. [3] Apache 2.0 grants rights to use, modify, and distribute the licensed work subject to its conditions. Redistribution includes obligations concerning the license, notices, and identification of modifications. [7] That gives a project using schnell a concrete license to review. Keep the license file with the exact downloaded artifact, especially if you later distribute a modified package. BFL also offers a commercial licensing route for self-hosted models and describes its API as including commercial usage rights without a separate weight license. These are alternative ways to obtain the required access. [8] For the practical installation side, the [local FLUX.1 guide](/shreya_alvarez/easy-flux-ai-local-installation-guide-5ai4) distinguishes schnell and dev configurations. Its setup steps should be paired with the license for the selected checkpoint. ## What restrictions apply to FLUX.1 dev models and outputs? The dev agreement separates the model from its generated outputs. Its current version grants non-commercial model rights, defines that category, and provides a separate output-use clause. [5] That output clause permits commercial output uses subject to restrictions, including a restriction on training a competitive model. It does not replace the separate conditions governing operation of the weights. [5] The dev terms also cover derivatives. A fine-tuned checkpoint is not simply an output image, so inspect the derivative and distribution provisions when evaluating a modification. [5] BFL's June 2025 license update explains requirements for content filtering or manual review and compliance with applicable content-provenance rules. Those requirements belong in an implementation using the affected dev license. [9] A repository's software license should also be distinguished from its model-weight licenses. BFL's inference repository lists schnell and the various dev models separately even though the repository itself carries an Apache license. [2] Read the table and the linked agreements together. Do not record “Apache” in a project's dependency notes solely because that label appears at the top of an inference-code repository. Hosted inference has its own contract. BFL publishes separate API terms for EU and non-EU use; the EU terms also cover access through an EU establishment. Follow the applicable agreement for service access, permitted use, and responsibilities for inputs and outputs. [6], [13] ## How do you check the license for your FLUX.1 project? ### Identify the checkpoint and license Begin with BFL's official repository table. Select schnell, dev, Krea dev, or Kontext dev by its full name, then follow its model-card and license links. [2] For a local copy of schnell's model card and license identifier, Hugging Face's CLI can download its README. Authenticate and complete any displayed repository access conditions first. [3], [10] ```bash python -m pip install -U huggingface_hub hf auth login hf download black-forest-labs/FLUX.1-schnell README.md \ --local-dir ./flux-license-review ``` Read that model card alongside the full Apache license. The command retrieves model documentation; it does not install the image-generation pipeline or choose a commercial arrangement for another model. [7] ### Describe what the project will do Write a short deployment note stating the exact checkpoint, where inference runs, who uses the results, and whether you distribute model files. Include any planned fine-tuning or hosted access. Separate those activities into clear sentences. This makes it possible to compare your plan with the license's model-use, derivative, output, and distribution provisions without conflating them. For dev, consult the agreement supplied with your artifact and BFL's current licensing documentation. The website's non-commercial terms identify their revision date and covered model families. [5] If a term does not cover the planned use, use BFL's licensing page to identify the applicable commercial option. Its support documentation directs self-hosting customers to that route. [8], [11] ### Choose self-hosted or API access BFL's licensing documentation distinguishes self-hosted model licensing from API usage. The API route includes commercial usage rights under the service arrangement, while self-hosting uses the relevant weight permissions. [8] For an API trial, follow the official quick start: create a dashboard account, add credits, and create a project API key. Keep that credential in the server environment used for requests. [12] Before committing to either route, list the controls your application requires. Include checkpoint selection, inference configuration, integration effort, and whether model redistribution is actually necessary. ## How do schnell, dev, and hosted FLUX licenses compare? | Choice | Licensing distinction | | --- | --- | | FLUX.1 schnell | Apache 2.0 model weights, with that license's conditions. [3], [7] | | FLUX.1 dev | Non-commercial weight access; commercial model operation requires appropriate additional rights. [5] | | Hosted FLUX API | Commercial service access governed by API terms rather than delivery of pro weights. [2], [6], [8] | For an alternative local ecosystem, consult the [SDXL models pillar](/tara_suzuki/best-sdxl-models-in-2026-realistic-anime-and-all-purpose-checkpoints-116). Check each selected checkpoint's own model card before comparing its permissions. ## What should you know before using FLUX.1 commercially? ### Is every FLUX model Apache 2.0? FLUX models have different licenses: FLUX.1 schnell uses Apache 2.0, while dev weights use non-commercial model terms. Hosted pro access is also separate. [2] ### Can dev outputs be used commercially? The FLUX dev terms permit commercial uses of generated outputs subject to their restrictions. Operation of the model itself remains subject to separate model-use conditions. [5] ### Does fine-tuning remove the dev restrictions? The FLUX dev license covers fine-tuned derivatives as well as the original model. Review those provisions for the specific adaptation you intend to create or distribute. [5] ### Do API users need a separate self-hosting license? BFL says FLUX API usage includes commercial rights without a separate self-hosting license. The API service terms still govern that access. [6], [8] ## Sources - [Original FLUX.1 release][1] - [Official inference repository and model-license table][2] - [FLUX.1 schnell model card][3] - [FLUX.1 dev model card][4] - [Current FLUX dev non-commercial terms][5] - [BFL API service terms][6] - [Apache License 2.0][7] - [BFL licensing support documentation][8] - [BFL's June 2025 license update][9] - [Hugging Face CLI documentation][10] - [BFL open-weight licensing options][11] - [BFL API quick start][12] - [BFL EU API service terms][13] [1]: https://bfl.ai/blog/24-08-01-bfl [2]: https://github.com/black-forest-labs/flux [3]: https://huggingface.co/black-forest-labs/FLUX.1-schnell [4]: https://huggingface.co/black-forest-labs/FLUX.1-dev [5]: https://bfl.ai/legal/non-commercial-license-terms [6]: https://bfl.ai/legal/flux-api-service-terms [7]: https://www.apache.org/licenses/LICENSE-2.0 [8]: https://help.bfl.ai/articles/9272590838-self-serve-dev-license-overview-pricing [9]: https://bfl.ai/blog/flux-1-kontext-dev [10]: https://huggingface.co/docs/huggingface_hub/guides/cli [11]: https://bfl.ai/licensing [12]: https://docs.bfl.ai/quick_start/get_started [13]: https://bfl.ai/legal/eu-api-service-terms ## Related guides on PromptZone - [Realistic Photos with FLUX](/stabletom/realistic-photos-with-flux-57aa) - [Best SDXL Models in 2026](/tara_suzuki/best-sdxl-models-in-2026-realistic-anime-and-all-purpose-checkpoints-116)