WindowsmacOSLinux

Where Does ComfyUI Store Models and Output?

ComfyUI's models, input and output folders for portable installs and the Desktop app on each OS.

Last updated

ComfyUI splits its working tree by job. Models sort into subfolders by type under models, uploads land in input, and renders land in output. Custom nodes and user workflows sit alongside them in the same base folder.

The catch is that the base moves between install styles. Portable and manual installs use wherever you cloned or unzipped ComfyUI. The Desktop app defaults to a ComfyUI folder inside Documents instead, with an override in its Storage settings.

Where ComfyUI stores this, by platform

Windows
C:\Users\[Username]\Documents\ComfyUI\models

Desktop app default. Portable installs use [InstallDir]\ComfyUI\models with checkpoints, loras, vae and controlnet below it. Output goes to the sibling output folder. Extra paths live in %APPDATA%\ComfyUI\extra_models_config.yaml.

macOS
~/Documents/ComfyUI/models

Desktop app default with the same type subfolders. Portable installs use [InstallDir]/ComfyUI/models instead. Renders go to the sibling output folder. Extra paths live in ~/Library/Application Support/ComfyUI/extra_models_config.yaml.

Linux
~/ComfyUI/models

Portable and manual installs default to wherever you cloned, commonly ~/ComfyUI, with models/input/output/custom_nodes below it. Override output per launch with python main.py --output-directory /your/custom/path.

Frequently asked questions

Where do I put a checkpoint or LoRA so ComfyUI sees it?

Under models in the matching subfolder: checkpoints for base models, loras for LoRAs, vae for VAEs. Refresh the node picker or restart and the file appears in the loader dropdown.

Where did my rendered image go?

The sibling output folder next to models and input. If you set a custom --output-directory flag or Desktop Storage override, that replaces the default, so check there first.

Notice an outdated path? Let us know.