Model comparisons
FLUX.1 Dev LoRA lists a 22% lower unit price than FLUX.2 Dev. Tier prices, request fields and limits side by side.
FLUX.1 Dev LoRA image editing from Black Forest Labs' FLUX.1 [dev], with up to three of your own LoRA files per request. A strength control sets how far the result moves from one source image, and a mask can limit the redraw to one area.
View model details →View sample outputs →FLUX.2 [dev] image editing from Black Forest Labs' open-weights model. It takes one to three source images and a prompt, keeps faces recognisable, and can combine people from separate photos into one scene.
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.1 Dev LoRA | FLUX.2 Dev |
|---|---|---|
| Spicy Index | 53.4 | 65.6 |
| Freedom Score | 43.5 | 84.0 |
| Evidence | Tested 6 of 6 probe types · 22 runs | Tested 6 of 6 probe types · 50 runs |
| Range if the rest pass | 43.5–87.5 | 84.0–84.0 |
| Price | $0.018 per image | $0.0116 per image |
| Reviews | Read the FLUX.1 Dev LoRA review | Read the FLUX.2 Dev review |
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.1 Dev LoRA | FLUX.2 Dev | Difference |
|---|---|---|---|
| Current price | $0.018 / output images | $0.023 / output images | FLUX.1 Dev LoRA −22% |
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.1 Dev LoRA | FLUX.2 Dev |
|---|---|---|
| Supported tasks | image-to-image | image-to-image |
| Resolution tiers | Not offered | 1K · 2K |
| Aspect ratios | Not offered | auto · 1:1 · 16:9 · 9:16 · 4:3 · 3:4 · 3:2 · 2:3 · 21:9 · 9:21 |
| Reference material | Not offered | Up to 3 files |
| High-resolution tier | No | 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.1 Dev LoRA
This model declares no content filter. SpicyAPI forwards the request without adding a platform content scan; legal and consent duties remain with the customer.
FLUX.2 Dev
This model declares no content filter. SpicyAPI forwards the request without adding a platform content scan; legal and consent duties remain with the customer.
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.
How to choose
FLUX.2 Dev supports a high-resolution option.
Compare
The model identifiers are black-forest-labs/flux-1-dev-lora/edit and black-forest-labs/flux-2-dev/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.1 Dev LoRA has the lower listed unit price by 22%. Prices may change; check the estimate shown for your actual settings before submitting.
FLUX.1 Dev LoRA allows 30 minutes per task and FLUX.2 Dev 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.
Related comparisons