Can You Use FLUX or Stable Diffusion Output Commercially? Which License Pages to Read (2026)

Short answer: The vendor pages read for this page do not answer the commercial-use question in plain text. They name licence and terms documents instead. For FLUX, the Black Forest Labs homepage lists a Non-Commercial License Terms document beside several other terms. For Stable Diffusion, Stability AI’s page lists a Self-Hosted License beside its Platform API. Read the document that matches your intended use before you publish anything made with either route.

What the FLUX page names

The Black Forest Labs homepage contains an open-weights section. It says FLUX models can run on your own infrastructure, and it offers a “Get a License” link there. Its enterprise block says larger organizations can add “the FLUX API and open weights license” to their products and services. That is the most direct licence reference on the captured page.

The footer then lists several documents by name. These include a Self-Hosted Terms of Service, a Non-Commercial License Terms, a Developer Terms of Service, a FLUX API Service Terms, a Usage Policy and a Responsible AI Development Policy. The page does not explain which document covers which product, model or use. That mapping is the piece a buyer needs, and it is not on the captured text.

What the Stability page names

Stability AI’s page lists two deployment routes: a Self-Hosted License and a Platform API. It does not expand on the terms of either one in the captured text. A buyer who reads only that page can see that the self-hosted route is licensed, but cannot see what the licence allows.

Side by side

Both rows labelled “not named” or “not stated” mean the captured page does not say. They do not mean the vendor has no such document.

Reading order

Start with the document named for the route you plan to use. If the hosted API is your route, the footer places the FLUX API Service Terms and the Developer Terms of Service next to each other. If you plan to self-host, the Self-Hosted Terms of Service is the named document, and the open-weights section is where the page sends you for a licence. Keep a dated copy of whichever document you read, since vendor pages are revised over time and a copy from 2026-10-14 will not show later changes.

Questions to answer from the documents

Before you rely on either route, use the vendor’s documents to answer these questions. The list is about what to look for, not a prediction of the answer.

• Does the document cover the model you intend to use, or a different model in the same family?
• Does it cover hosted output, self-hosted output, or both?
• Does it describe any restriction on commercial use, or on the kind of customer-facing product you plan to build?
• Does it mention a separate agreement for larger organizations, and what triggers it?
• Does it cover the terms of the platform you use to generate the image, as well as the model licence?

Who this matters for

• Teams that will ship images inside a paid product, where a licence mismatch is hard to undo.
• Agencies that deliver images to clients and need to say what the client may do with the output.
• Anyone who plans to self-host, because the self-hosted route has its own named documents on both pages.

Where this reading stops

This page does not give legal advice and does not interpret any licence. It cannot say whether a given image is safe to publish, whether a particular use counts as commercial, or whether a document has changed since 2026-10-14. It also does not know how a court would read any term. Read the document named for your route, check the date on the vendor page, and ask a qualified adviser before you publish.