LoRA (Low-Rank Adaptation)
Install compatible add-ons and control their strength, trigger text and style wording
Last updated: 2026-10-27
LoRA add-ons change a compatible model's style or learned concepts. They are not interchangeable across base-model families, and a generic “LoRA” label does not prove compatibility with your selected model or precision.
360 LoRA Is An Input Source
360 LoRA generates starting panoramas from text. This guide covers the separate LoRA render module. Outpaint has its own source/model requirements.
Supported Processors
Supported families expose the LoRA module in their actual configuration. SDXL, SD 1.5, SD 2.1, SD 3.5, FLUX, Qwen, Chroma and Z-Image use family-specific add-ons; some are Alpha. TeleStyle, Real-ESRGAN, Edit, Coverage and Format Converter do not expose this ordinary module. Check Pipelines and the selected model before importing.
Adding LoRAs to Your Library
- Open the selected pipeline's LoRA catalogue or Add Custom dialog.
- Choose a supported source: catalogue entry, Hugging Face/Civitai discovery or URL, or a local file through the offered import control.
- Check the exact training base, file and license. A Civitai/Hugging Face listing is not permission to use or redistribute the model commercially.
- Set a useful name and Trigger Word where needed. Use the 360/equirectangular option only for an actual compatible panorama adapter, not to turn an ordinary style LoRA into one.
- Follow installation/readiness through Downloads. Registration is not the same as installed/verified weights. See Model Management.
Applying LoRAs to a Render
Enable the module, select installed compatible entries and adjust each strength. Start near the model author's or catalogue's recommendation, then compare one controlled change. Reduce influence if it overwhelms structure or color. There is no universal safe sum of strengths or guarantee every pair combines well.
Trigger Word and LoRA style wording are different. Edit the trigger for the chosen adapter; where offered, the style-injection switch controls its contributed style text. Custom Style pills belong to Prompt. Inspect both to avoid repeating wording or assuming disabling one removes the other.
Precision and compatibility
Base family, distilled variant, quantization and loading path can affect support. Use the app's compatible model/precision choices; do not rename a file or force an unsupported add-on into another family. Fit guidance is not proof the combined model/add-ons fit currently free VRAM.
Reuse and removal
Save a Workflow for the selected recipe, but share the model's original source/requirements separately: the Workflow does not contain weights. Preserve licensing and trigger recommendations. Use managed uninstall/removal actions and read their file effects instead of deleting a shared folder.
For reference-image conditioning, use the separate IP-Adapter, not a LoRA source field.