Is there an existing issue for this?
What would your feature do ?
WebUI is still a top entry point, but current user demand has shifted toward multi-runtime workflows (SDXL, SD3-family, FLUX variants), stronger LoRA ergonomics, and lower-VRAM usability. A clearer compatibility and optimization layer would reduce setup friction and keep WebUI competitive for mainstream users.
Proposed workflow
- Add a runtime capability panel in settings/UI to show model-family compatibility (SD1.5/SDXL/SD3/FLUX), supported samplers, and known constraints.
- Add guided optimization profiles (Low VRAM / Balanced / Max Quality) that configure attention/memory options safely.
- Add LoRA manager improvements: conflict hints, weight presets, per-family compatibility warnings.
- Add a benchmark command/report for startup diagnostics (VRAM, backend, expected throughput).
- Publish/maintain a first-class compatibility matrix page generated from tested configs.
Additional information
Related trend signals:
- Rising adoption of FLUX-oriented and SDXL-heavy workflows
- Growing expectation for low-VRAM presets and reproducible setup paths
- Community confusion around model/runtime combinations and extension compatibility
If useful, I can help with a docs-first PR: compatibility matrix + optimization profiles draft.
Is there an existing issue for this?
What would your feature do ?
WebUI is still a top entry point, but current user demand has shifted toward multi-runtime workflows (SDXL, SD3-family, FLUX variants), stronger LoRA ergonomics, and lower-VRAM usability. A clearer compatibility and optimization layer would reduce setup friction and keep WebUI competitive for mainstream users.
Proposed workflow
Additional information
Related trend signals:
If useful, I can help with a docs-first PR: compatibility matrix + optimization profiles draft.