English | 中文说明

Portable package for ComfyUI on Windows

Similar to the ComfyUI official standalone portable, but preloaded with numerous custom nodes and Python packages, with all dependencies resolved and ready to use.

Features

• Pre-installed 40+ commonly-used custom nodes. [Full List]

  • With all the model files that need to be downloaded on the first run (which may cause freezing for users with a poor Internet connection).

• Pre-installed 300+ mutually compatible Python packages, including:

  • Performance optimization libraries such as SageAttention, FlashAttention, xFormers and Nunchaku.

  • Packages that require native compilation during installation (e.g., insightface, dlib, etc.), already built and ready to use.

• Only a few functional models are pre-installed; users please prepare model files of your favorite.

• This repository uses the GitHub pipeline for packaging, making it easy for DIY. No need to configure CI/CD, simply fork this repository on GitHub to run the packaging script. See Creating Your Own All-In-One Package.

How to Use

1. Only NVIDIA GPUs (2018 or newer) are supported. Installing the latest driver is strongly recommended.

2. Download the package files from the release page.

   • Or you can download them directly:

     • ComfyUI_Windows_portable_cu130.7z.001

     • ComfyUI_Windows_portable_cu130.7z.002

     • models.zip (If you are upgrading from a previous release, you don’t need this file.)

3. After downloading the files, place them in the same directory, then open and extract the 001 file.

   • Extract to a shallow directory path, such as C:\AI\, to avoid errors caused by long paths (exceeding the MAX_PATH limit of 260 characters).

   • You do not need to open the 002 file. The extraction software will automatically handle it when decompressing the 001 file. They are two parts of a single large archive created using "split compression".

   • You can use 7-Zip for extraction.

4. Open the models.zip and extract it to the same place.

5. Place your model files under ComfyUI\models\.

6. Run RUN_Launcher.bat to start.

• After launching, the program will automatically open a browser. You can also manually access: http://localhost:8188/.

• Close the window to exit the program.

Tips

1. Take full advantage of ComfyUI-Manager (the Manager button in the top-right of the ComfyUI page) to manage Custom Nodes: install, update, disable, and uninstall.

   • You can click the "Update ComfyUI" button daily to get the latest workflow templates and related updates. This feature does not affect your installed Custom Nodes.

   • Be cautious when using "Update All"; there’s no need to update unused nodes to avoid Python package conflicts.

Pre-installed Custom Node List

Workspace
ComfyUI Manager	Crystools	ComfyUI-to-Python-Extension
Performance
Nunchaku	GGUF	RadialAttention
General
Comfyroll Studio	ComfyUI Essentials by cubiq	Custom Scripts by pythongosssss
Efficiency Nodes by jags111	KJNodes	Mikey Nodes
Mira Nodes	rgthree Nodes	smZ(shiimizu) Nodes
Use Everywhere	WAS Node Suite	ComfyUI-Easy-Use
Control
Advanced ControlNet	ControlNet Auxiliary Preprocessors	Detail Daemon
IC-Light Native	Impact Pack	Impact Subpack
Inspire Pack	IPAdapter plus	Layer Style
LayerDiffuse	Portrait Master	SD Dynamic Thresholding
SDXL Prompt Styler
Video
AnimateDiff Evolved	FizzNodes	Frame Interpolation (VFI)
MTB Nodes	Video Helper Suite
More
Depth Anything V2 by kijai	DepthCrafter by akatz	Florence-2 by kijai
Image Selector	ProPost	Ultimate SD Upscale
WD 1.4 Tagger

If compatibility issues arise, you can try disabling conflicting nodes in ComfyUI-Manager.

Advanced Information

1. The ExtraScripts folder contains command-line launch scripts, which are equivalent to the launcher.

2. For power users, consider using Sandboxie to limit cache files while isolating the environment.

   • For better I/O performance when using Sandboxie, it is recommended to configure the program’s main directory (ComfyUI_Windows_portable) as "Open Access" in "Sandbox Options" → "Resource Access".

3. External Model Directory

If you place model files on different partitions or share a set of model files across multiple ComfyUI instances, you can configure ComfyUI to load external model directories:

• Rename extra_model_paths.yaml.example in the ComfyUI directory, removing the .example suffix.

• Edit extra_model_paths.yaml, where lines starting with # are comments.

Reference file (click to expand)

comfyui:
    base_path: D:\models\
    animatediff_models: animatediff_models
    animatediff_motion_lora: animatediff_motion_lora
    bert-base-uncased: bert-base-uncased
    checkpoints: checkpoints
    clip: clip
    clip_vision: clip_vision
    configs: configs
    controlnet: controlnet
    depthfm: depthfm
    diffusers: diffusers
    diffusion_models: |
        diffusion_models
        unet
    embeddings: embeddings
    facerestore_models: facerestore_models
    gligen: gligen
    grounding-dino: grounding-dino
    hypernetworks: hypernetworks
    insightface: insightface
    instantid: instantid
    ipadapter: ipadapter
    loras: loras
    mmdets: mmdets
    onnx: onnx
    photomaker: photomaker
    reactor: reactor
    rembg: rembg
    sams: sams
    style_models: style_models
    text_encoders: text_encoders
    ultralytics: ultralytics
    unet: unet
    upscale_models: upscale_models
    vae: vae
    vae_approx: vae_approx

4. More External Model Directories

ComfyUI has five common locations for saving model files:

• The built-in ComfyUI\models directory.

• External model directories configured via extra_model_paths.yaml.

• Model files downloaded via HuggingFace Hub (HF official downloader).

• Model files downloaded via PyTorch.

• Files downloaded in-place by nodes in ComfyUI\custom_nodes.

Among these:

• HF Hub defaults to downloading files to C:\Users\UserName\.cache\huggingface\hub.

• PyTorch defaults to downloading files to C:\Users\UserName\.cache\torch\hub.

This package modifies the launch script to redirect these to the program’s root directory, under HuggingFaceHub and TorchHome folders, respectively, for easier management. If needed, you can edit the launch script to change these paths.

Creating Your Own All-In-One Package

This repository utilizes a pipeline to build the package, and the codebase doesn’t contain specific configurations or require additional access permissions. Hence, you can directly fork this repository to start executing the GitHub Workflow.

1. After forking, go to Actions on the page.

2. Locate Build & Upload Package.

   • For example, the page in my repository looks like this.

3. Click Run Workflow.

4. Wait about 20~40 minutes until the workflow run complete.

5. Go to the releases page of your repository, where you will find the newly generated draft, ready for download or editing.

Development Idea

Originally, the code was copied from ComfyUI’s GitHub workflow, but I found it difficult to debug, so I rewrote the script.

However, the packaging concept is similar: providing a self-contained, portable, and fully equipped environment with a pre-installed Python Embedded (now migrated to Python Standalone).

The difference is that I didn’t download wheels first and then install them in bulk like Comfy did. Because dependency relationships are too tricky, I went straight to pip install for dependency solving.

As a note, a common issue with Python Embedded in such pre-installed packages is that most of the executables in the Scripts directory cannot run properly. This is because these executables are often Python command wrappers that invoke python.exe through an absolute path. Once the directory changes (or is relocated), they naturally fail to execute. Fortunately, this does not affect the current project significantly.

See Also

• Development Memo - Version Upgrades

• How To: Manually Setup ComfyUI

Thanks

Thanks to the ComfyUI GitHub workflow, from which I drew inspiration.