comfyui-frontend-package is not installed in ComfyUI
Fix comfyui-frontend-package is not installed, outdated, or failed frontend version errors by updating the correct ComfyUI Python environment.
Start with Wonderful Launcher if this issue touches your real ComfyUI environment. Use the docs to understand the fix, and use the app to inspect the machine you already have.
Download Wonderful LauncherIf ComfyUI says comfyui-frontend-package is not installed or Failed to check frontend version, update the Python environment that actually starts ComfyUI.
comfyui-frontend-package is the Python package that provides ComfyUI's browser interface.
If it is missing, outdated, or installed into the wrong Python environment, ComfyUI may start with frontend warnings, fall back to an older UI, or fail before the web interface loads.
In a real Windows portable repair, this appeared after the first missing core dependency was fixed. That means the frontend package error can be the second blocker in a damaged portable environment, not just a cosmetic UI warning.
Quick Diagnosis
| What You See | Likely Cause | First Fix |
|---|---|---|
comfyui-frontend-package is not installed | Required package missing | Install from ComfyUI's requirements.txt |
Failed to check frontend version | Python package metadata problem | Check the active Python environment |
New UI features are missing after git pull | Code updated but dependencies did not | Run pip install -r requirements.txt |
| Portable install still uses old frontend | Used system Python by accident | Run the bundled Python from the portable root |
| Error mentions workflow templates too | More core packages are missing | Update all core requirements together |
The Real Log We Hit
After fixing ModuleNotFoundError: No module named 'sqlalchemy', the next startup attempt failed with:
Failed to check frontend version: No package metadata was found for comfyui-frontend-package
********** ERROR ***********
comfyui-frontend-package is not installed.That log is clear: the Python environment starting ComfyUI cannot find the package metadata. Installing the package into system Python will not help if ComfyUI is launched by python_embeded\python.exe.
What This Package Does
Older ComfyUI versions shipped more frontend files directly inside the main repository. Current ComfyUI loads the frontend from a package instead.
In the ComfyUI source, the default frontend path imports comfyui_frontend_package and serves its static directory. When the import fails, ComfyUI logs that comfyui-frontend-package is not installed.
The package is not a random plugin. It is part of the core ComfyUI runtime.
Why It Breaks After Updating
Many update problems happen because only one part of ComfyUI was updated.
For a manual install, this is incomplete:
git pullYou also need to update the packages required by that new code.
Do not run pip install -r requirements.txt blindly.
- Confirm which Python environment is active (
where pythonorwhich python) - Inspect
requirements.txt— check if it pins torch, numpy, or opencv versions - Install only the missing package when possible:
pip install <package-name> - Run
pip checkafter installation to verify no conflicts were introduced
The official ComfyUI update guide lists comfyui-frontend-package, comfyui-workflow-templates, comfyui-embedded-docs, comfy-kitchen, and comfy-aimdo as core dependencies that may need to move with the code.
Step 1: Check the Required Version
Open:
ComfyUI/requirements.txtLook for:
comfyui-frontend-package==...That is the version your local ComfyUI code expects. Do not blindly install the latest frontend package if your ComfyUI code expects a specific version.
Step 2: Check the Installed Version
Run this in the same Python environment used to start ComfyUI:
python -m pip show comfyui-frontend-packageIf it says the package is not found, install the specific missing package:
python -m pip install comfyui-frontend-packageDo not run pip install -r requirements.txt blindly.
- Confirm which Python environment is active (
where pythonorwhich python) - Inspect
requirements.txt— check if it pins torch, numpy, or opencv versions - Install only the missing package when possible:
pip install <package-name> - Run
pip checkafter installation to verify no conflicts were introduced
If it shows a version lower than the one in requirements.txt, update from requirements instead of guessing a version.
Portable Windows Fix
For the GitHub Windows portable package, run from the extracted portable root: the folder that contains the run_*.bat files, python_embeded, and ComfyUI.
.\python_embeded\python.exe -s -m pip show comfyui-frontend-packageThen check the versions requested by your local ComfyUI code:
Get-Content ComfyUI\requirements.txt | Select-String "comfyui-frontend-package|comfyui-workflow-templates|comfyui-embedded-docs"In the repaired lab environment, the matching fix was:
.\python_embeded\python.exe -s -m pip install "comfyui-frontend-package==1.42.15" "comfyui-workflow-templates==0.9.63" "comfyui-embedded-docs==0.4.4"Use the versions from your own ComfyUI\requirements.txt if they differ.
Do not run pip install from a random system terminal unless you know it points at the portable Python. Installing into the wrong Python is the most common reason the error keeps coming back.
If the frontend package error appears after other core missing-package errors, read Repair Broken ComfyUI Portable Dependencies Without Reinstalling Torch before running broad package updates.
For ComfyUI Desktop or another managed launcher, use the app's own terminal, updater, or environment tools instead of copying the portable python_embeded path.
Manual Install Fix
Activate your virtual environment first:
.\venv\Scripts\activateThen update from the ComfyUI folder:
cd ComfyUI
git pull
python main.pyDo not run pip install -r requirements.txt blindly.
- Confirm which Python environment is active (
where pythonorwhich python) - Inspect
requirements.txt— check if it pins torch, numpy, or opencv versions - Install only the missing package when possible:
pip install <package-name> - Run
pip checkafter installation to verify no conflicts were introduced
If you use Conda, activate the Conda environment before installing requirements.
What Not to Do
Avoid these shortcuts:
- do not install frontend packages into system Python while ComfyUI uses a venv
- do not upgrade only
comfyui-frontend-packagewhile ignoring other core packages - do not run every custom node
requirements.txtafter fixing the frontend - do not delete ComfyUI before reading the first error in the log
- do not mix stable and nightly update paths without knowing which one you want
If It Says "Not Found in requirements.txt"
If a tool says comfyui-frontend-package not found in requirements.txt, check three things:
- You are looking at the correct
ComfyUI/requirements.txt. - The ComfyUI code was actually updated.
- You are not running from an old fork, old zip, or partial copy.
For a Git install:
git status
git pullIf Git says the folder is not a repository, use ComfyUI Won't Update.
How Wonderful Launcher Helps
Frontend package errors are usually environment errors, not workflow errors. Wonderful Launcher helps when you need to:
- keep several ComfyUI environments separate
- preserve a working environment before updating packages
- collect startup logs that show the active frontend version
- recover from custom node installs that changed core dependencies
If your environment breaks every time you update, read ComfyUI Dependency Conflicts before installing more packages.
Related Guides
- Repair Broken ComfyUI Portable Dependencies Without Reinstalling Torch
- ModuleNotFoundError: No module named 'sqlalchemy' in ComfyUI
- ComfyUI Won't Update
- ComfyUI Dependency Conflicts
- ComfyUI Startup Failed
- Install ComfyUI Custom Nodes
Source References
- Official ComfyUI update guide
- ComfyUI frontend management source
- ComfyUI command-line arguments
- Windows portable repair lab, May 18, 2026:
comfyui-frontend-package is not installedwas resolved by installing the package versions requested in localComfyUI\requirements.txt
Start with Wonderful Launcher if this issue touches your real ComfyUI environment. Use the docs to understand the fix, and use the app to inspect the machine you already have.
Download Wonderful LauncherStart with Wonderful Launcher if this issue touches your real ComfyUI environment. Use the docs to understand the fix, and use the app to inspect the machine you already have.
Download Wonderful LauncherDid this fix your issue?
Your answer helps prioritize verified ComfyUI repairs.