Which Python does ComfyUI Portable use? Keep startup and package installation aligned

Purpose and scope

Portable contains its own Python and ComfyUI directories. Installing into system Python does not automatically make those packages available to its embedded interpreter.

Source-supported context

Official Portable documentation uses the literal directory spelling python_embeded and distribution-specific launch scripts. One script name is not a standard for every GPU and platform. Source 1 Source 2

Before you start

1. Identify the actual extracted directory and avoid ambiguity from duplicate packages or old shortcuts.

2. Check the official source and the build's intended hardware/platform rather than trusting a universal repack.

3. Back up workflows, configuration and model mappings before repairs; deleting the whole Portable installation is not the first diagnostic step.

Steps and checks

The sequence below is an editorial procedure based on the cited context, not a diagnosis already confirmed for your environment.

Step 1. Locate the active package from process/startup paths rather than browser history.

Step 2. Invoke that package's python_embeded/python.exe for dependencies, using requirements from the same ComfyUI instance.

Step 3. Restart the backend and review IMPORT FAILED and dependency messages. Browser refresh is not a Python restart.

Step 4. When copying or updating, retain the original environment and model mapping until a small regression workflow passes and shortcuts can be switched safely.

Commands and request examples

Use the environment and shell identified above. Paths and variables are examples to adapt; these commands/snippets were not executed for your machine. Portable examples run from the package root. A virtual environment or managed launcher can use a different executable layout.

.\python_embeded\python.exe -c "import sys; print(sys.executable); print(sys.version)"
.\python_embeded\python.exe -m pip --version
.\python_embeded\python.exe -m pip check

Completion check

Startup, installation and diagnostics all use the same interpreter and ComfyUI directory.

Limitations and cautions

Do not copy system site-packages directly into embedded Python. Binaries built for another Python/platform can create an unrecoverable mixed environment.

Original sources

• ComfyUI Portable Windows — original record checked 2026-09-21.
• Install custom nodes — original record checked 2026-09-21.

Localization prepared: 2026-09-22. The source-check dates above were inherited from the existing article; this translation does not claim they were all rechecked today. No GPU run, minimum-memory measurement or runtime guarantee is supplied.

Related troubleshooting and guides

• ModuleNotFoundError in ComfyUI even though the package is installed
• ComfyUI Manager button missing: distinguish UI changes from load failures
• Share ComfyUI model storage without mixing up instances or resource categories