Where Does SwarmUI Install SD 3.5 Models? Default Paths and What Affects Them

If you've just downloaded Stable Diffusion 3.5 through SwarmUI and can't find where it landed, you're not alone. SwarmUI has a specific directory structure that differs from other frontends like AUTOMATIC1111 or ComfyUI standalone installs — and once you understand the logic behind it, navigating those paths becomes much easier.

How SwarmUI Organizes Its File Structure

SwarmUI is a launcher and management layer that wraps around backend engines — most commonly ComfyUI as its primary inference backend. This layered architecture is the core reason its file paths can feel unintuitive at first.

When you install SwarmUI, it creates its own root directory (typically named SwarmUI or StableSwarmUI depending on the version). Inside that root, it maintains two distinct areas:

• Its own model folders — used directly by the SwarmUI layer
• Backend-specific folders — passed through to whichever inference engine is running underneath

This distinction matters when you're hunting for a freshly downloaded SD 3.5 checkpoint.

The Default SD 3.5 Model Install Path

When SwarmUI downloads a model like Stable Diffusion 3.5 Large or SD 3.5 Medium through its built-in model downloader, it places the file here by default:

SwarmUI/Models/Stable-Diffusion/ 

So a typical path on Windows might look like:

C:SwarmUIModelsStable-Diffusionsd3.5_large.safetensors 

And on Linux:

/home/username/SwarmUI/Models/Stable-Diffusion/sd3.5_large.safetensors 

This is the SwarmUI-native model directory — the location SwarmUI reads from when populating its model selector in the UI.

What About the ComfyUI Backend Folder?

Here's where things get slightly more complex. When SwarmUI installs ComfyUI as a backend (which happens automatically in most fresh installs), it places ComfyUI inside a subfolder:

SwarmUI/dlbackend/ComfyUI/ 

ComfyUI has its own model directory structure at:

SwarmUI/dlbackend/ComfyUI/models/checkpoints/ 

SwarmUI handles the bridge between these two locations through symbolic links or direct path configuration, depending on your OS and version. In many setups, SwarmUI points the ComfyUI backend to its own Models/ folder rather than duplicating files. This means you generally don't need to copy SD 3.5 files into the ComfyUI subfolder manually — but this behavior can vary.

🗂️ Quick Reference: Common Paths by Scenario

Factors That Change Where Models End Up

The path above is the default — but several variables can shift where SD 3.5 actually lands on your machine.

Installation method and custom paths. During SwarmUI's initial setup wizard, you can specify a custom data directory. If you changed this during install, your Models/ folder lives wherever you pointed it — not in the default location.

Operating system. Windows, Linux, and macOS handle paths differently. Linux installs following a Docker-based setup may place the SwarmUI root under /opt/ or a home directory subfolder. Windows installs often go directly to C:SwarmUI unless you chose otherwise.

Symlink behavior on Windows. Symbolic links on Windows require elevated permissions in some configurations. If symlinks failed silently during setup, SwarmUI may have fallen back to a different resolution method for backend model paths — meaning ComfyUI might look in its own local checkpoints/ folder instead of the shared SwarmUI Models/ directory.

SwarmUI version. The project is under active development. Path conventions have shifted between versions, particularly around how backend model directories are handled. A setup from six months ago may organize files differently than a fresh install today.

Manual model placement. If you dropped SD 3.5 files manually rather than using the built-in downloader, they'll be wherever you put them — and SwarmUI will only find them if that folder is registered in its model paths configuration.

How to Confirm Where SwarmUI Is Looking

Rather than hunting by hand, SwarmUI gives you a direct way to check. Inside the interface:

1. Navigate to Server → Server Configuration
2. Look for Model Root or Models Folder settings
3. This shows the exact path SwarmUI is reading from

You can also check the Data/Settings/ folder inside your SwarmUI root for configuration files that list registered model directories explicitly.

For the ComfyUI backend specifically, the file SwarmUI/dlbackend/ComfyUI/extra_model_paths.yaml (if it exists) will show which external directories ComfyUI has been told to scan — including whether it's pointing to SwarmUI's shared Models folder.

SD 3.5-Specific Considerations

SD 3.5 models use the .safetensors format and are significantly larger than earlier SD versions. The Large variant is in the 8–9 GB range, while the Medium sits closer to 4–5 GB — so confirming your target drive has enough space before downloading is worth checking.

SD 3.5 also requires specific text encoder models (the T5-XXL and CLIP encoders) to function correctly. These are typically placed in:

SwarmUI/Models/clip/ 

or passed through to:

SwarmUI/dlbackend/ComfyUI/models/clip/ 

If SD 3.5 appears in your model list but fails to generate, missing text encoders in the expected subfolder is a common cause — separate from where the main checkpoint file landed.

The Part Only Your Setup Can Answer

The default paths described here cover the most common SwarmUI configurations — but your actual install reflects choices made during setup, your OS environment, whether symlinks resolved correctly, and which version of SwarmUI you're running. Two people can follow the same general install process and end up with models resolving from meaningfully different locations. Checking the model root in Server Configuration and cross-referencing with what the ComfyUI backend is actually scanning will give you the definitive answer for your specific machine.