FLUX.3 Image costs 4.1 to 60.7 credits: what 1,000 credits buys

The short answer

Black Forest Labs bills FLUX.3 Image in credits, and one credit equals $0.01 (read 2026-10-09). A 1,000-credit top-up is $10, and it buys 243 images at 768sq, 208 at 1k, 100 at 2k or 16 at 4k. Sume's catalog lists FLUX.2 rows but no FLUX.3, so you cannot buy FLUX.3 images through Sume today.

Credits to images

BFL's pricing page lists FLUX.3 Image per image by output resolution. The credit counts below are the dollar prices divided by $0.01. The images per 1,000 credits are rounded down, since you cannot buy part of an image.

What Sume lists instead

The Sume catalog read on 2026-10-09 names two FLUX rows in the Image Router: flux-2-pro and flux-2-flex. Their Sume prices per image at default options are $0.0375 and $0.0625. On the same $10, that is 266 images on flux-2-pro (10 / 0.0375 = 266.7) and 160 on flux-2-flex (10 / 0.0625).

These are different models, not a cheaper way to get FLUX.3. Use them if FLUX.2 is good enough for the job, and keep FLUX.3 on BFL's own API if you need that model.

Picking a tier by budget

Work back from the number of finals you need. If you need 100 images and $10 is the cap, the 2k tier fits exactly: 100 x 10 credits = 1,000 credits. If you need 200 images for the same $10, only the 768sq tier (4.1 credits) and the 1k tier (4.8 credits) fit, at 243 and 208 images. If a client demands 4k files, 16 images use the whole 1,000 credits.

A split plan is common: explore at 768sq, which costs 4.1 credits per image, then re-render the chosen five at 4k for 5 x 60.7 = 303.5 credits. That run costs 50 x 4.1 + 303.5 = 508.5 credits, or $5.09.

Turning credits into a budget

Credits are a billing unit on BFL's side, and the pricing page sets 1 credit at $0.01, so the conversion is a move of the decimal point: 4.1 credits is $0.041, 60.7 credits is $0.607. Write the budget in credits first, then in dollars, so that a change in the credit price shows up in one place.

Because Sume does not list FLUX.3, you cannot call it through a Sume key. If you need an image model from the FLUX family there, the catalog lists FLUX.2 rows, and the Sume image docs describe how to read the model list for the current ids. Check the list on the day you plan the job rather than trusting a stored page.

BFL says the submission response includes the cost of each request, so you can confirm the credit charge on the first call. On Sume, read the usage.cost field on each response, which is the USD amount billed to your wallet. If you plan a large FLUX.3 run, price the tier you will really use: the jump from 2k ($0.100) to 4k ($0.607) is 6.07 times the price for 4 times the pixels.