Skip to content

Feature Support

This page answers the practical question: which model families support which features today?

Quick Picks

NeedBest Starting Point
LoRA adaptersFLUX.1
ControlNetSD 1.5
img2img at 1024 outputFLUX.1 or SDXL
broadest feature surfaceSD 1.5 or SDXL
best prompt-following qualityFLUX.1 or SD 3.5

Source Image Workflows

Familyimg2imgInpaintingEdit-family refs
FLUX.1YesYesNo
SDXLYesYesNo
SD 1.5YesYesNo
SD 3.5YesYesNo
Z-ImageYesYesNo
Flux.2 KleinYesYesNo
Wuerstchen v2YesYesNo
Qwen-ImageYesYesNo
Qwen-Image-EditNoNoYes
LTX VideoNot yetNot yetNot yet
LTX-2YesNoKeyframes

Control and Adapters

FamilyControlNetLoRA
FLUX.1NoYes
SDXLNoNo
SD 1.5YesNo
SD 3.5NoNo
Z-ImageNoNo
Flux.2 KleinNoNo
Wuerstchen v2NoNo
Qwen-ImageNoNo
LTX VideoNoNo
LTX-2NoYes

Prompt Conditioning

FamilyNegative PromptsScheduler Override
FLUX.1NoNo
SDXLYesYes
SD 1.5YesYes
SD 3.5YesNo
Z-ImageNoNo
Flux.2 KleinNoNo
Wuerstchen v2YesNo
Qwen-ImageYesNo
Qwen-Image-EditYesNo
LTX VideoNoNo

Video Generation

Familytxt2vidimg2vidaudio2vidkeyframeretakeIC-LoRAaudio track
LTX VideoYesNot yetNoNoNoNoNo
LTX-2YesYesYesYesYesYesYes
All othersNoNoNoNoNoNoNo

LTX Video defaults to APNG (lossless, metadata-rich). LTX-2 defaults to MP4 so it can preserve synchronized audio when requested. Both families also support GIF, and feature-gated WebP/MP4 outputs where applicable. Use --format apng|gif|webp|mp4. Frame count must be 8n+1 (9, 17, 25, 33, ...). Dimensions must be multiples of 32.

The recommended LTX default today is ltx-video-0.9.6-distilled:bf16. The 0.9.8 family is available, pulls its spatial upscaler asset, and now runs the full multiscale refinement path.

Backend Support

FamilyCUDAMetalCPU
FLUX.1 / FLUX.2YesYesYes (slow)
SDXL / SD 1.5YesYesYes
SD 3.5YesYesYes
Z-ImageYesYesYes
Wuerstchen v2YesYesYes
Qwen-ImageYesYesYes
Qwen-Image-EditYesYesYes
LTX VideoYesYesYes
LTX-2YesNot yetCorrectness-only

LTX-2 is CUDA-only for real generation

LTX-2 / LTX-2.3 does not support Apple Metal in this release. The native runtime runs on CUDA; the CPU path exists for correctness-oriented coverage and can be extremely slow. On macOS you can still use every other family through the Metal backend — LTX-2 is the only family that is currently CUDA-gated.

Notes

  • ControlNet is currently available only for SD 1.5.
  • General LoRA adapters are currently available only for FLUX models; LTX-2 has its own stacked video-adapter path plus camera-control presets.
  • LTX-2 adds stacked LoRAs plus camera-control presets for the published 19B adapters.
  • --scheduler applies only to SD 1.5 and SDXL.
  • Negative prompts are meaningful for CFG-based families and ignored by FLUX, Z-Image, and Flux.2 Klein.
  • qwen-image-edit is a distinct edit family, not a standard img2img mode.
  • The CLI and API support multiple ordered input images for qwen-image-edit; the TUI keeps the edit flow to a single source image in v1.
  • qwen-image-edit can use quantized --qwen2-variant language weights while still loading the Qwen2.5-VL vision tower for image conditioning.
  • LTX-2 now wires x2 spatial upscaling across the family, x1.5 spatial upscaling for ltx-2.3-*, and x2 temporal upscaling in the native runtime.
  • LTX-2's native CUDA path is validated across text+audio-video, image-to-video, audio-to-video, keyframe, retake, public IC-LoRA, spatial upscale, and temporal upscale workflows.
  • LTX-2 is CUDA-only for real generation: CPU is correctness-only, and Metal is not supported in this release.

For model size and VRAM fit, see Models Overview. For usage examples, see Generating Images.