The Flux dev license says three different things about selling your images, and they don’t agree with each other.

That one document is why I opened seven license files on October 20, 2026 and read them clause by clause.

I am not a lawyer. Below is what each license text says on the day I read it, with links so you can check it yourself.

If you want the bigger picture on selling (platform rules, which apps let you sell, real people), I covered that in Can You Sell NSFW AI Images?.

Here I stick to the license files themselves, and I go through them model by model.

The short version

ModelCommercial use of imagesClause about adult contentNote
FLUX [dev]Unclear without a paid licenseNoneGrant is non-commercial, and 4(a)(i) covers “data produced”
Wan 2.2YesNoneApache 2.0
SDXLYesNoneOpen RAIL++-M with a list of banned uses
HunyuanVideo 1.5Yes, inside its territoryNoneEU, UK and South Korea excluded
MiniMax H3Yes, inside its territoryNoneUS, EU, UK and Korea excluded
LTX-2.5Yes, under $10M revenueBans sexually explicit contentAcceptable use policy
SD 3.5Yes, under $1M revenueBans sexual actsStability acceptable use policy

So five of seven say nothing about adult content between adults, and two ban it.

Two of seven have a territory clause. And only one of them, Flux dev, makes the plain “can I sell the picture” question hard.

Flux dev: three clauses pulling in different directions

The current text is the FLUX [dev] Non-Commercial License v2.0, last revised November 25, 2025. It covers FLUX.1 [dev], Kontext dev, Krea dev and FLUX.2 [dev].

I read it top to bottom, and these are the three parts that matter for selling.

Clause 1: the license itself is non-commercial. Section 2(b) says you may only use the model “for Non-Commercial Purposes”.

Section 1(c) defines that as use where you “do not receive any direct or indirect payment arising from the use” of the model. It also excludes “revenue-generating activity” by name.

Clause 2: the outputs sound free. Section 2(d) says:

You may use Output for any purpose (including for commercial purposes), except as expressly prohibited herein.

That sentence is the one everybody quotes. The last five words are the part people skip.

Clause 3: something is expressly prohibited. Section 4(a)(i) bans using the model “(or any Derivative thereof, or any data produced by the FLUX [dev] Model)” for “any commercial or production purposes”.

An image you generate is data produced by the model.

So my honest reading is this. 2(d) sounds like a yes, but 1(c) and 4(a)(i) make selling Flux dev images a real risk if you rely on the free license alone.

The clean path is the one BFL offers. They sell commercial licenses for their open weights on bfl.ai/licensing, and FLUX.2 [dev] is in those plans.

A few more things from the same license that matter for this audience:

  • No adult clause. Section 4(a)(vii) bans unlawful content and names CSAM and non-consensual intimate images. I found nothing against consensual adult content.
  • Filtering is about illegal content. Section 2(e) asks you to filter or review output for “unlawful or infringing content”, and to label AI output where the law requires it.
  • LoRAs count as Derivatives. Selling a Flux dev LoRA falls under the non-commercial grant, so that one is a clear no.
  • No training competitors. 2(d) says you can’t use the output to train a model that competes with Flux dev.

Wan 2.2: the simple one

Wan 2.2 is Apache 2.0, on GitHub and on Hugging Face.

The model card adds that they “claim no rights” over what you generate. Apache 2.0 itself has no content clause and no revenue cap.

This is the license I’d want under a paid page, because there is very little to interpret.

SDXL: open, with a list of banned uses

SDXL uses the CreativeML Open RAIL++-M license, dated July 26, 2023.

The grant has no non-commercial limit, and Stability “claims no rights in the Output”. Attachment A lists banned uses (illegal content, harming minors, harassment, fake info), and none of them is adult content as such.

One catch. Community SDXL checkpoints carry their own license.

Illustrious is a good example, because its license changes by version on Hugging Face: v0.1 is FAIPL-1.0-SD, v1.0 uses the SDXL license, v2.0 is CreativeML OpenRAIL-M. Read the license of the exact file you run.

SD 3.5: closed for adult work

SD 3.5 runs under the Stability AI Community License (last updated July 5, 2024). Commercial use is free until you pass $1M in annual revenue.

The problem is the Acceptable Use Policy it pulls in, effective September 30, 2026. It has a section called “We Prohibit Sexually Explicit Content”, and it lists “content relating to sexual intercourse, sexual acts”.

For adult creators, that is a no.

LTX-2.5: open business terms, banned content

LTX-2.5 uses the LTX-2.x Community License, dated August 11, 2026. Commercial use is fine below $10M in annual revenue.

Attachment A then makes the Acceptable Use Policy (last updated March 30, 2026) part of the license, and it applies “when using the Outputs” too.

That policy has a section titled “Do Not Generate Sexually Explicit Content”. It names sex acts and fetish content directly.

HunyuanVideo 1.5: fine, if you’re in the right country

The Tencent Hunyuan Community License for HunyuanVideo 1.5 (released November 21, 2025) only applies inside its Territory. The Territory is the world minus the EU, the UK and South Korea.

Section 5(c) extends that to outputs, including displaying them outside the Territory. The United States is allowed.

There is no clause about sexual content. The only extra limit on business is a license request above 100 million monthly active users.

MiniMax H3: great model, US excluded

The MiniMax H3 license is dated August 2, 2026. Section I.5 lists the Excluded Territories: the EU, the UK, the Republic of Korea and the United States.

Section V.4 says you may not use or “display” the model or its Outputs outside the allowed territory. So an American audience is a problem even if you generate somewhere else.

No clause names adult content. Above $20M a year in revenue you need written authorization (IV.1).

Two clauses almost nobody mentions

AI labels. MiniMax H3 (AUP item 12), Hunyuan (AUP item 12) and LTX (Attachment A item 5) all require you to disclose that content in public is machine generated.

If you post on Fanvue or X with these models, label it.

The vague one. MiniMax and Hunyuan both ban use that violates the “social ethics and moral standards of other countries or regions” (AUP item 15).

I don’t know how anyone would enforce that. But it’s in the text, so I’m telling you.

What I check now, every time

  1. What does the license restrict: the model, the output, or both? Flux shows how much that changes the answer.
  2. Is there a territory clause? Two of seven had one, and they don’t exclude the same countries.
  3. Is the acceptable use policy a separate file? LTX and SD 3.5 look open until you open the policy.
  4. Is there a revenue cap? $1M, $10M and $20M are all in this list.

It takes me about ten minutes per model. The license is right there on the model page.

Sources (all read on October 20, 2026)

Licenses change. If you’re reading this months from now, open the link and check the date at the top.

If you make real money from this, one hour with a lawyer who knows licensing costs less than finding out the hard way.

Want new tools and tutorials when they come out? 👉 Subscribe For Free 👈

For where to actually sell, see Where to Sell NSFW AI. The tools I’ve tested are in NSFW AI Tools.