Rightshold™ Sign up

Answers · AI image models

Can I use FLUX or Stable Diffusion images commercially?

Last updated

TL;DR: It depends on which model checkpoint you run and who you are, not on the image. FLUX.1 [schnell] is released under Apache-2.0, so personal, scientific and commercial use is allowed. FLUX [dev] models (FLUX.1 [dev], Kontext [dev], Krea [dev], FLUX.2 [dev] and others) are under Black Forest Labs' FLUX [dev] Non-Commercial License v2.0: the model may only be used for non-commercial, non-production purposes, and although the license says outputs may be used for any purpose, it also bans using the model or data it produces for commercial or production purposes, so commercial work with [dev] should be covered by a paid BFL license. Stable Diffusion 3.5 and other Stability AI Core Models are free for commercial use under the Stability AI Community License only while you and your affiliates make under US $1,000,000 in annual revenue, and commercial users must register. Older Stable Diffusion 1.x models use CreativeML OpenRAIL-M, which allows commercial use with use restrictions.

What should I check, step by step?

1. Identify the exact checkpoint, not the family: open the model card on Hugging Face and read the license field and LICENSE file. FLUX.1 [schnell] (Apache-2.0) and FLUX.1 [dev] (non-commercial) look alike in a UI.

  1. Check fine-tunes, LoRAs and merges too: a FLUX [dev] fine-tune is a Derivative and keeps the [dev] restrictions; a Stability fine-tune or LoRA is a Derivative Work under the Community License.
  2. FLUX [dev] for anything revenue-generating, client-facing or in production: get a commercial license from Black Forest Labs (its licensing page lists self-hosted tiers with image-volume and domain limits) or switch to [schnell] or a paid API.
  3. Stability Core Models (SD 3.5 Large, Medium, Large Turbo, SD3 Medium, SDXL Turbo and others): register with Stability AI for commercial use, and track revenue: once you and your affiliates pass US $1M a year, from any source, the Community License ends and you need an Enterprise license.
  4. Distributing the model or a product that uses it: under the Stability Community License, ship the agreement, keep the Notice file text and display "Powered by Stability AI"; under FLUX [dev], include the license and its attribution notice and say you modified it.
  5. Don't train or improve competing models on outputs: FLUX [dev] bans using Output to train, fine-tune or distill a model competitive with FLUX [dev]; the Stability license bans using outputs to create or improve a foundational generative AI model.
  6. FLUX [dev] also requires content filters or human review of outputs for unlawful or infringing content, and AI disclosure where the law requires it.
  7. Separately inspect each image for real people, logos, characters and copied artworks; a model license does not clear what an image shows.
  8. Record the model ID, version, license file hash, date and your revenue tier at generation time, so you can show which terms you relied on.

Why FLUX [dev] outputs are a trap for commercial work

Section 2(d) of the FLUX [dev] Non-Commercial License v2.0 (last updated November 25, 2025) says Black Forest Labs claims no ownership of Outputs and you may use Output for any purpose, including commercial, except as expressly prohibited.

The Stability AI US $1M revenue line

The Stability AI Community License (last updated July 5, 2024) allows research, non-commercial and commercial use free of charge, but the commercial grant terminates on the date you or your affiliates, individually or together, exceed US $1,000,000 in annual revenue, whether or not that revenue comes from the model.

Using a hosted API instead

If you call FLUX or Stable Diffusion through BFL's API or a third-party host, the provider's API terms govern your use of outputs, not only the open-weights license. Read the terms of the service you actually call.

What do the license checks say?

Yes means the license grants the use, on the duties listed. Duties such as source_disclosure, share_alike and network_source_offer are the ones that conflict with keeping a product closed-source.

UseAnswerWhy
FLUX.1 [schnell] (Apache-2.0) run yourself for commercial images (Apache-2.0)YesEvery use you described is granted by Apache 2.0, and nothing you described is prohibited. Duties: attribution, license_notice, state_changes.
A Stable Diffusion 1.x model (CreativeML OpenRAIL-M) run yourself for commercial images (LicenseRef-CreativeML-OpenRAIL-M)YesEvery use you described is granted by CreativeML OpenRAIL-M, and nothing you described is prohibited. Duties: license_notice, state_changes, use_restrictions, pass_on_restrictions.

How do I ask Rightshold about this (free, no key)?

Add the MCP server https://www.rightshold.com/mcp to Claude, Cursor, ChatGPT, Grok or VS Code, then ask: “We self-host FLUX.1 [dev] to make product photos for our store. Is that allowed, and what about switching to FLUX.1 [schnell]?”

One-click setup

{
  "tool": "ask_rightshold",
  "arguments": {
    "question": "Can I use FLUX.1 [dev] or FLUX.1 [schnell] images in a commercial store?"
  }
}

Rightshold reads the model licenses and terms you point it at. It does not see your revenue, your BFL or Stability agreements, or what an image depicts. Not legal advice.

What are the sources?

Related

Not legal advice. JSON · Markdown · All answers

Get a free API key in one call

No card and no email needed. 100 free credits; the license and policy checks stay free without a key.

curl -s -X POST https://www.rightshold.com/v1/accounts/signup -H "Content-Type: application/json" -d '{"accept_terms":true}'
export RIGHTSHOLD_API_KEY=rs_...   # the api_key from the reply (shown once)
curl -s https://www.rightshold.com/v1/licenses/check -H "Authorization: Bearer $RIGHTSHOLD_API_KEY" \
  -H "Content-Type: application/json" -d '{"license":"MIT","intended_use":{"commercial_use":true}}'