You have a portrait working, close ComfyUI, and later discover that the downloaded graph still contains the original settings. The usual confusion is between saving a working workflow, exporting a JSON copy, and saving an output image. Treat them as three separate actions.
Import a workflow JSON
Use Workflows → Open and select the JSON file. ComfyUI also supports recovering graphs from compatible images containing workflow metadata. These are documented in the official first-generation guide. A normal screenshot or an image whose metadata was removed cannot supply the missing graph.
- Keep a copy of the downloaded original.
- Open it in ComfyUI and inspect missing-node and missing-model messages.
- Locate the inputs, including any reference images.
- Run a small diagnostic generation.
- Save your working copy with a new, descriptive name.
Importing a JSON does not install everything it references. If the graph expects a model your machine lacks, follow the author’s documented dependencies. See the missing-node guide for extensions and the installation guide for model placement.
Where does ComfyUI save workflows?
A common local user-workflow location is ComfyUI/user/default/workflows, discussed in the project’s workflow storage thread. This is not a universal absolute path: the installation directory, user profile and configured storage can change it. An exported JSON normally follows your browser or desktop save destination instead.
| What you saved | Where to investigate |
|---|---|
| Named user workflow | The Workflows sidebar and the active installation’s user directory |
| Exported JSON | The chosen save location or browser Downloads folder |
| Generated media | The save node’s configured output location |
| Original download | The location used before importing; it may still be unchanged |
Save a portable copy you can verify
After naming and saving the workflow, export a JSON with a version suffix. Then open that exported file in a separate workflow tab and inspect two settings you intentionally changed, such as the prompt and output dimensions. This round trip catches the common mistake of backing up an old download instead of the current graph.
Use a filename such as host-portrait-sdxl-v03.json. Put a short companion note beside it containing the model names, extension versions and input filenames. Avoid naming every iteration “final”; the next adjustment immediately makes that label misleading.
Recover a graph from an image
ComfyUI’s built-in save nodes can embed workflow information in supported outputs, as explained in its workflow documentation. Try the original generated file. A copy downloaded from social media, an edited export, or a screenshot may have lost that information.
If recovery fails, return to your exported JSON and source assets. Do not assume every visually identical copy contains identical metadata. For a client handoff, provide a deliberately prepared production archive and a separate clean delivery export.
A reusable handoff checklist
- Workflow JSON opens without an unexplained missing dependency.
- Reference files are included when you have permission to share them.
- Model names and licenses are recorded; large model files are not silently assumed to be inside the JSON.
- A small example output and acceptance note show what “working” means.
- Private paths, prompts and reference information have been reviewed before sharing.
For an ongoing character series, keep the workflow version beside each approved asset. That lets you return to the configuration that produced a good face instead of guessing through dozens of settings. The workflow guide explains how to organize that production process.
If you want to spend less time managing local graphs, create your AI creator in Clout and build the next photo or video concept around the saved persona.
