A ControlNet that treats every line art preprocessor the same

What it does MistoLine is a trained SDXL ControlNet that conditions image generation on virtually any line art input—hand-drawn sketches, outputs from different edge preprocessors, or model-generated outlines. It uses the standard ControlNet architecture paired with the SDXL base U-Net, so it drops into existing ComfyUI and AUTOMATIC1111 workflows without structural changes. The authors developed it alongside a companion preprocessor called Anyline, though the model is meant to generalize across other preprocessors too.

The interesting bit Rather than maintaining a separate ControlNet checkpoint for every line-detection algorithm, MistoLine tries to handle all of them with a single weight file. The README claims this works especially well in complex scenes, though it offers qualitative comparisons rather than reproducible benchmarks.

Key highlights

• Ships as a single checkpoint: mistoLine_rank256.safetensors is the recommended general-use weight, with an FP16 fallback that the authors explicitly note performs worse.
• Uses the standard ControlNet architecture, so it works with existing SDXL pipelines and can be stacked with LCM or other ControlNets.
• Explicitly incompatible with PlaygroundV2.5, CosXL, and possibly SDXL-Lightning.
• Commercial use requires prominent attribution to TheMisto.ai in your product documentation or about screens.
• Outputs are uncensored; the authors disclaim responsibility for generated content.

Caveats

• The README lists extensive usage restrictions (no medical advice, no exploitation, etc.) and strict commercial attribution rules that may complicate product integration.
• Performance comparisons to other ControlNets are qualitative; no quantitative benchmarks or evaluation datasets are provided in the README.
• The FP16 checkpoint is described as inferior to the rank256 version, so storage-conscious users face a quality trade-off.

Verdict Try it if you want one line-art ControlNet that accepts whatever sketch or edge map you have on hand. Avoid it if you need PlaygroundV2.5 or CosXL compatibility, or if the commercial attribution clause is a dealbreaker.