Model comparisons
At 1K, FLUX 3 Klein Base costs 10% less than FLUX 3 Klein Base LoRA. Tier prices, request fields and limits side by side.
FLUX 3 Klein Base image editing changes or combines one to three images from a written instruction on Black Forest Labs' undistilled FLUX 3 Image Klein. Refer to sources as image 1, image 2 and image 3; fifteen shapes or auto, 1k or 2k.
View model details →View sample outputs →FLUX 3 Klein Base LoRA image editing changes or combines one to three images on Black Forest Labs' undistilled FLUX 3 Image Klein, with up to three of your own LoRA files. Refer to sources as image 1, image 2 and image 3.
View model details →View sample outputs →Compare
Start with the input you have, the result you want and your budget. These are the differences that affect that choice.
Compare the published examples, then try the same input on both models with matching settings.
The Spicy Index and Freedom Score for both models, from the same daily calculation as the leaderboards.
| Measure | FLUX 3 Klein Base | FLUX 3 Klein Base LoRA |
|---|---|---|
| Spicy Index | 52.1 | 78.5 |
| Freedom Score | 13.5 | Not enough evidence yet |
| Evidence | Tested 3 of 6 probe types · 5 runs | Tested 1 of 6 probe types · 1 run |
| Range if the rest pass | 13.5–77.5 | 6.0–90.0 |
| Price | $0.036 per image | $0.042 per image |
| Reviews | Read the FLUX 3 Klein Base review | Read the FLUX 3 Klein Base LoRA review |
Preliminary · freedom evidence pending
See both on the leaderboard →Current price
A start price answers a different question than the one you have. These are the tiers both models publish, matched setting for setting, in US dollars per billed unit with no conversion step in between.
Swipe horizontally to compare all fields.
| Tier | FLUX 3 Klein Base | FLUX 3 Klein Base LoRA | Difference |
|---|---|---|---|
| 1K | $0.054 / output images | $0.06 / output images | FLUX 3 Klein Base −10% |
| 2K | $0.216 / output images | $0.222 / output images | FLUX 3 Klein Base −2% |
Arithmetic on the published rates at each model's own default setting, not a quote. The console prices your actual settings before a request is accepted.
About this comparison
Every row here is read from the JSON Schema the endpoint validates against, so it matches what the API will really accept rather than a feature list written by hand.
Swipe horizontally to compare all fields.
| Controls and limits | FLUX 3 Klein Base | FLUX 3 Klein Base LoRA |
|---|---|---|
| Supported tasks | image-to-image | image-to-image |
| Resolution tiers | 1K · 2K | 1K · 2K |
| Aspect ratios | auto · 1:1 · 16:9 · 9:16 · 4:3 · 3:4 · 3:2 · 2:3 · 4:5 · 5:4 · 21:9 · 9:21 · 2:1 · 1:2 · 3:1 · 1:3 | auto · 1:1 · 16:9 · 9:16 · 4:3 · 3:4 · 3:2 · 2:3 · 4:5 · 5:4 · 21:9 · 9:21 · 2:1 · 1:2 · 3:1 · 1:3 |
| Reference material | Up to 3 files | Up to 3 files |
| High-resolution tier | Yes | Yes |
| Seed | Yes | Yes |
| Execution | Submit, then poll or take the callback | Submit, then poll or take the callback |
| Request timeout | 30 minutes | 30 minutes |
| Availability | Live | Live |
Do low-filter models allow every request?
Two separate facts sit behind these labels. The first is what we do, which is nothing: no platform content filter, and no maturity flag to set on a request. The second is what each model does on its own, and that is the only part that varies between these two.
FLUX 3 Klein Base
This model returns a result instead of an error, but requests beyond its own limits come back toned down. The call still succeeds and is still billed, so check the output rather than the status code.
FLUX 3 Klein Base LoRA
This model returns a result instead of an error, but requests beyond its own limits come back toned down. The call still succeeds and is still billed, so check the output rather than the status code.
Use these content labels to shortlist models, then open each model page for available examples and content-test details.
The label never changes your obligations. Age, consent, real-person likeness and the law where you operate stay with you, and SpicyAPI does not inspect each request.
Can I swap the model ID without changing the request body?
The task lifecycle is shared; the body is not. Each endpoint publishes its own JSON Schema and the API validates against that, so this is the list to reconcile before a switch.
Compare
The model identifiers are black-forest-labs/flux-3-klein-base/edit and black-forest-labs/flux-3-klein-base-lora/edit, and both go in the same field of the same request.
Both run the same way: submit the task, then poll it or take the callback. Queueing and retry logic carry over unchanged.
Both use the same submit-and-track flow, but their required inputs may differ. Check each model page before switching.
One key, one balance, one set of spend caps. Both bill to the same account in US dollars, and the per-key daily, monthly and lifetime limits apply to whichever one you call.
Questions developers ask
FLUX 3 Klein Base is 10% cheaper at 1K, the closest like-for-like setting the two publish. Prices may change; check the estimate shown for your actual settings before submitting.
FLUX 3 Klein Base allows 30 minutes per task and FLUX 3 Klein Base LoRA allows 30. Those are ceilings rather than typical times — most requests finish far sooner — but they are what your own client timeout has to survive.
Prices and capabilities shown here come from the current public model catalogue. Check each model page for its latest inputs and examples.