Skip to main content

Model comparisons

FLUX.2 Klein 4B vs Z-Image Turbo LoRA

Z-Image Turbo LoRA lists a 4% lower unit price than FLUX.2 Klein 4B. Tier prices, request fields and limits side by side.

Z-Image Turbo LoRA

Z-Image Turbo LoRA image-to-image restyles one source image with up to three of your own LoRAs. A strength from 0 to 1 (default 0.8) sets how far it moves from the source, and the output keeps the source's aspect ratio.

View model details →View sample outputs →

Compare

The short answer

Start with the input you have, the result you want and your budget. These are the differences that affect that choice.

  • Z-Image Turbo LoRA has the lower listed unit price by 4%.
  • Both are listed as Uncensored. Compare the examples and content-test details on each model page for the scenes you want to create.

Compare the published examples, then try the same input on both models with matching settings.

Test scores side by side

The Spicy Index and Freedom Score for both models, from the same daily calculation as the leaderboards.

Test scores side by side
MeasureFLUX.2 Klein 4BZ-Image Turbo LoRA
Spicy Index59.665.3
Freedom Score78.695.0
EvidenceTested 6 of 6 probe types · 50 runsTested 6 of 6 probe types · 38 runs
Range if the rest pass78.6–78.695.0–95.0
Price$0.0093 per image$0.012 per image
ReviewsRead the FLUX.2 Klein 4B reviewRead the Z-Image Turbo LoRA review
See both on the leaderboard →

Current price

Price at the same setting

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.

Price at the same setting
TierFLUX.2 Klein 4BZ-Image Turbo LoRADifference
Current price$0.013 / output images$0.012 / output imagesZ-Image Turbo LoRA −4%

What one ordinary job costs

  • FLUX.2 Klein 4B: $1.26 for one hundred images.
  • Z-Image Turbo LoRA: $1.2 for one hundred images.

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

Controls and limits

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.

FLUX.2 Klein 4B vs Z-Image Turbo LoRA
Controls and limitsFLUX.2 Klein 4BZ-Image Turbo LoRA
Supported tasksimage-to-imageimage-to-image
Resolution tiers1K · 2K1K · 1.5k
Aspect ratiosauto · 1:1 · 16:9 · 9:16 · 4:3 · 3:4 · 3:2 · 2:3 · 21:9 · 9:21Not offered
Reference materialUp to 3 filesNot offered
High-resolution tierYesNo
SeedYesYes
ExecutionSubmit, then poll or take the callbackSubmit, then poll or take the callback
Request timeout30 minutes30 minutes
AvailabilityLiveLive

Do low-filter models allow every request?

Content policy, side by side

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.2 Klein 4B

Uncensored

This model declares no content filter. SpicyAPI forwards the request without adding a platform content scan; legal and consent duties remain with the customer.

Z-Image Turbo LoRA

Uncensored

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?

Request body, field by field

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.

  • 3 fields appear in both request bodies under the same names. prompt, resolution, seed
  • Only FLUX.2 Klein 4B accepts: aspect_ratio, image_urls.
  • Only Z-Image Turbo LoRA accepts: image_url, loras, output_format, strength.
  • FLUX.2 Klein 4B requires image_urls, prompt.
  • Z-Image Turbo LoRA requires image_url, prompt.
  • Both reject unknown fields outright, so a parameter left over from the other model comes back as a validation error instead of being quietly ignored.

How to choose

How to choose

High-resolution delivery

FLUX.2 Klein 4B supports a high-resolution option.

Compare

Moving from one to the other

The model identifiers are black-forest-labs/flux-2-klein-4b/edit and alibaba/z-image-turbo-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

Which is cheaper, FLUX.2 Klein 4B or Z-Image Turbo LoRA?

Which is cheaper, FLUX.2 Klein 4B or Z-Image Turbo LoRA?

Z-Image Turbo LoRA has the lower listed unit price by 4%. Prices may change; check the estimate shown for your actual settings before submitting.

How long can a single request run?

FLUX.2 Klein 4B allows 30 minutes per task and Z-Image Turbo 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.

Related comparisons