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, SDXL, or Qwen-Image
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 / video references
FLUX.1YesYesNo
SDXLYesYesOne IP-Adapter image prompt, alongside img2img
SD 1.5YesYesOne IP-Adapter image prompt, alongside img2img
SD 3.5YesYesNo
Z-ImageYesYesNo
Flux.2 KleinYesYesNo
Flux.2 DevNoNoUp to 4 ordered native references
Wuerstchen v2YesYesNo
Qwen-ImageYesYesNo
Qwen-Image-EditNoNoYes
LTX VideoNot yetNot yetNot yet
LTX-2YesNoKeyframes
Wan VideoN/AN/AFirst/last frame on capable checkpoints
MiniMax H3N/AN/ARequired first frame (FL2VA) or ordered refs (Ref2VA)
Hunyuan3DN/AN/ARequired source image — the only conditioning it has

Control and Adapters

FamilyInternal familyControlNetLoRA
FLUX.1fluxNoYes
Flux.2 Kleinflux2NoYes
Flux.2 Devflux2NoNo
LTX-2ltx2NoYes
SD 1.5sd15YesYes
SD 3.5sd3NoYes
SDXLsdxlNoYes
Qwen-Imageqwen-imageNoYes
Qwen-Image-Editqwen-image-editNoYes
Z-Imagez-imageNoYes
Wuerstchen v2wuerstchenNoNo
LTX Videoltx-videoNoNo
Wan VideowanNoYes
MiniMax H3minimax-h3NoNo¹
Hunyuan3Dhunyuan3dNoNo

¹ H3 Turbo model tags contain manifest-pinned, reviewed distillation adapters. They do not enable arbitrary request-time LoRA stacks.

Prompt Conditioning

FamilyNegative PromptsScheduler Override
FLUX.1NoNo
SDXLYesYes
SD 1.5YesYes
SD 3.5YesNo
Z-ImageNoNo
Flux.2 KleinNoNo
Flux.2 DevNoNo
Wuerstchen v2YesNo
Qwen-ImageYesNo
Qwen-Image-EditYesNo
LTX VideoNoNo
Wan VideoYesYes¹
MiniMax H3NoNo
Hunyuan3DN/A²No

² Hunyuan3D has no text encoder at all, so neither a prompt nor a negative prompt is read. The source image is the entire conditioning.

¹ Wan's solver set is disjoint from the UNet schedulers: it takes --sample-solver unipc|euler|dpm++, which travels in the same scheduler wire slot. See Wan.

Video Generation

Familytxt2vidimg2vidaudio2vidkeyframeretakelip dubIC-LoRAaudio track
LTX VideoYesNot yetNoNoNoNoNoNo
LTX-2YesYesYesYesYesYesYesYes
Wan VideoYesYesNoFirst/lastNoNoNoNo
MiniMax H3No¹YesRef2VAFirstNoNoNoRequired
All othersNoNoNoNoNoNoNoNo

¹ The currently advertised compact FL2VA profile requires a first frame. Ref2VA instead requires an ordered set of image, video, or audio references.

LTX Video, LTX-2, and Wan all default to MP4. This lets LTX-2 preserve synchronized audio when requested. Wan renders video only and has no audio path. A build compiled without the mp4 feature falls back to APNG. GIF and APNG remain available for all three families, plus feature-gated WebP. Use --format apng|gif|webp|mp4. Wan keyframing is first/last-frame interpolation only (--image + --last-image); other keyframe layouts are refused at admission. Frame grids are per family: LTX Video and LTX-2 take 8n+1 frame counts (9, 17, 25, 33, ...) with dimensions in multiples of 32; 64 for LTX-2 lip dub, which always renders in two stages and takes its frame count and rate from the reference clip. Wan takes 4n+1 frame counts (49, 53, 81, ...) with dimensions in multiples of 16, except wan22-ti2v-5b, whose 2.2 VAE requires multiples of 32.

The --output extension outranks those family defaults: mold run … -o clip.gif writes a real GIF even where the family would have picked MP4. An extension this binary cannot encode; .mp4 without the mp4 feature, .webp without webp; is refused before any weight is read rather than filled with another container's bytes, and an explicit --format that disagrees with the filename is reported instead of silently overriding it. --output - writes to stdout and claims no extension, so it keeps whatever container the family resolved.

MiniMax H3 is separate from those fallback rules: it always emits MP4 with synchronized generated audio, runs at 24 fps, and accepts 107–345 frames on its 17n+5 grid. It renders one clip per request. See MiniMax H3 for its request and build constraints.

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-2YesYesCorrectness-only
Wan VideoYesYesCorrectness-only
MiniMax H3SM89 H3 buildsCorrectness-only, unqualifiedNo
Hunyuan3DCorrectness-onlyYesCorrectness-only

Hunyuan3D Metal qualification

Metal is qualified on real weights: hunyuan3d-mini-turbo:fp16 on an M4 Max at octree 192, 256 and 320, compared against ComfyUI on the same checkpoint, image and seed (scripts/capture-hunyuan3d-metal-uat.sh against scripts/capture-hunyuan3d-comfy-metal-reference.sh). The shape path is dense fp16 matmuls and attention with no custom kernel, so CUDA is portable by construction — but "Yes" in this table is a claim about MEASURED performance on real weights, and that campaign has not run on a CUDA card. Correctness-only is the honest answer there until it does.

LTX-2 Metal qualification

LTX-2 / LTX-2.3's Apple Metal path is performance-qualified: BF16 transformer compute, fused attention, streamed FP8 lookup-table widening, and temporal VAE chunks, measured end-to-end on the 19B and 22B distilled FP8 tiers on Apple Silicon. Metal remains slower than a comparable CUDA card; streaming trades speed for fitting the model in unified memory.

Wan Video's Metal path is performance-qualified on Apple Silicon. The measured matrix covers 1.3B BF16 text-to-video at 832x480 and 5B Q8 text-to-video plus 5B FP16 image-to-video at 1280x704, with one cold and three warm 17-frame runs per workload. The path uses family-scoped BF16 and chunked attention; fp8-scaled Wan checkpoints remain refused on Metal.

MiniMax H3's Metal route is shipped but has not completed hardware qualification; the compact stack needs a 64 GB-class Apple Silicon host. H3 generation is otherwise limited to binaries built with the H3 engine, including the Linux SM89 release. Other release targets can still download and verify the registered models and report why generation is unavailable.

Native app surfaces

Desktop and mobile apps use the family capabilities above and the same generation request contract. The table focuses on desktop and iPhone; Android uses the same remote-only Studio surface and native bridge described in the Android guide.

AreaDesktopiPhone
PlatformsmacOS, Linux, and Windows (x64 and ARM64)iPhone and iPad
EngineBuilt-in local engine (Metal on macOS, CUDA on Linux and on x64 Windows when built with a CUDA toolkit, otherwise CPU; the published Windows nightly is CPU/remote-client only) plus remote hostsRemote hosts only
CreateCapability-driven image/video controls, review-first prepared expansion batches, estimatesSame exact-N, frozen-host review lifecycle and independent siblings, full-screen Advanced sheet, optimized for touch
LibraryUnified local/remote grid with persisted top-bar thumbnail sizing, host filters, deduplication, batch provenance, a Runs/Prompts History column, and desktop file actionsMerged saved-host library with persisted pinch-to-resize thumbnail sizing, Prints/Collections/Trash scopes, favorites/tag chips, titles via the viewer Info sheet, per-host trash retention on host detail, batch/source provenance, full-screen image/video, swipe navigation, Use as prompt, and Use as source
StylesReady to use / Browse more with the Still picture · Short clip · 3-D object chips, friendly names over exact ids, kind and explicit 18+ NSFW badges, Get it onto any machine still missing the style (Repair once all have it), download progressInstalled/live union, matching kind/18+ badges and detail, same install-or-repair host picker, pull progress, cancel, load/unload/remove
MachinesThis device plus remembered/discovered remote hosts, host detail, automatic routing choicesBonjour, IP/DNS/HTTPS, or Tailscale MagicDNS; explicit generation host and detailed telemetry
QueueShared multi-host console: live progress, per-job cancel, Pause/Resume, and drag-reorder (queue.can_reorder)Per-host queue with progress and per-job cancel
SettingsA 200px jump nav beside one scrolling page of sixteen always-open sections from the shared schema (Cloud GPUs and Per-style defaults included); rows save on change; ?section= deep linksSix Mold Studio themes with Match phone, remote-host shortcut, version, and TestFlight update channel
SequencesNot authored in the apps — a clip longer than one render is chained and stitched by the machine automatically. Script one with mold run --script or the /api/chain-jobs API.Same: long clips chain automatically, no scene composer.
UpdatesSigned Stable/Nightly in-app updater on macOS; Linux and Windows are replaced manuallyInternal TestFlight builds after eligible main CI

See the Desktop App and iPhone App guides for complete workflows.

Notes

  • ControlNet is currently available only for SD 1.5.
  • LoRA-capable families are flux, flux2, ltx2, sd15, sd3, sdxl, qwen-image, qwen-image-edit, wan, and z-image. Wuerstchen and LTX Video are not wired for LoRA yet.
  • Wan adapters cover low-rank pairs and full-weight .diff/.diff_b deltas: on bf16 safetensors they merge as the weights are read, on GGUF they apply as a parallel branch at full precision. fp8-scaled Wan checkpoints refuse adapter stacks rather than re-round their weights.
  • LTX-2 adds stacked LoRAs plus camera-control presets for the published 19B adapters.
  • --scheduler selects the UNet scheduler for SD 1.5 and SDXL (edm-dpm-pp-2m is Playground v2.5 only). Wan selects its flow solver with --sample-solver unipc|euler|dpm++, which travels in the same scheduler wire slot; the two sets are mutually exclusive and rejected off-family.
  • Negative prompts are meaningful for CFG-based families and ignored by FLUX, Z-Image, and Flux.2 Klein. Wan checkpoints were tuned against a specific negative prompt, which mold applies automatically when a request leaves it unset; /api/models advertises it per model (default_negative_prompt), every surface prefills it, and clearing the field (or --no-negative) sends an explicit empty negative instead.
  • 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, text-to-audio, image-to-video, audio-to-video, keyframe, retake, lip dub, public IC-LoRA, spatial upscale, and temporal upscale workflows.
  • LTX-2 renders audio on its own with --pipeline t2a (pipeline: "t2a"): no video, duration from frames/fps, and a 16-bit PCM stereo wav artifact that lands in the gallery with a rendered waveform tile.
  • LTX-2's multimodal guider exposes optional per-request overrides for STG scale/blocks, CFG-rescale, cross-modality scale, and the guidance skip stride on the CLI and in web, desktop, iPhone, and TUI Advanced video controls. They apply to the two-stage, two-stage-hq, keyframe, a2-vid, and t2a pipelines; unset fields keep each pipeline's own constants. The TUI uses bounded keyboard cycles for the numeric guidance values and validates comma-separated STG blocks before closing the editor; untouched values remain absent from the request. Its Video accordion also exposes the shared enable_audio contract as a checkpoint-aware default/on/off choice, family-gated spatial_upscale / temporal_upscale native modes, and the source-free one-stage, two-stage, two-stage-hq, and distilled recipes while Auto leaves pipeline absent. Conditioning-file modes, the audio-only t2a pipeline, and chain-job administration remain a separate tracked gap.
  • Completed LTX-2 videos report the runtime-resolved pipeline separately from the requested Auto/explicit choice. Server, CLI, and TUI saves preserve that response in gallery metadata, and web, desktop, iPhone, and TUI Library details show it when present; older and non-LTX prints simply omit the row.
  • LTX-2 is performance-qualified on CUDA and Apple Metal (19B/22B distilled FP8 tiers, checkpoint-backed); CPU stays correctness-only.
  • Library organization (titles, ♥ favorites, tags, collections, and a trash with per-host retention (gallery.trash_retention_days)) is stored per host in that host's mold.db and merged across hosts by every client. The web Library exposes it as the Prints | Collections | Trash scope control, the filter-chip row, the print viewer's editable aside, and the selection bar's Add to collection / Tag / Favorite / Trash actions; Settings ▸ Library and Machines ▸ host edit retention. Hosts that do not advertise gallery.organize / gallery.trash show none of it and keep permanent deletes. See Generating ▸ Browser UI.
  • Creation-time filing ("File under") lets a print arrive already organized: GenerateRequest and the chain body carry additive title, tags, and collection, seeded onto the gallery row once, as it is created. The CLI spells it mold run --title/--tag/--collection (with --no-auto-tag and the generate.auto_tag_title preference); web, desktop, and iPhone Create render a capability-gated File under group, and the TUI keeps it as the last Create ▸ Advanced section. A scripted sequence files the stitched print only, batch and prepared siblings inherit their parent's filing, and a filing the host cannot apply is dropped and reported on x-mold-request-warning rather than failing the render. See Generating ▸ File under.

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