ComfyUI Failed to Save Workflow Draft: Save It Safely

If you searched for failed to save workflow draft, save workflow comfyui, or where is my workflow saved, the safe move is this:

save the workflow JSON immediately while the graph is still visible. Treat PNG metadata as a useful backup, not your only copy.

Saving a ComfyUI workflow is not the same as saving an image. The image is your output. The workflow is the node graph that made it: nodes, links, prompts, model choices, and UI state.

Quick Answer

If you only remember one rule, remember this one: when a workflow matters, save both the JSON and the output PNG.

Emergency Fix for Failed to Save Workflow Draft

If this error appears while the graph is still visible, protect the workflow before debugging:

1. Use Save As or export workflow JSON immediately.
2. Save one output PNG with metadata if the workflow can still run.
3. Copy the browser error text or screenshot the canvas before refreshing.

Then diagnose the draft-save error:

The Three Workflow Formats Users Confuse

1. Normal workflow JSON

This is the main format for reopening a workflow in the ComfyUI interface. It stores the graph layout, nodes, links, widgets, groups, and related UI information.

Use this when you want to:

• reopen the workflow later
• send the graph to another user
• keep a versioned backup
• debug missing custom nodes
• preserve a working state before changing plugins

2. API format JSON

API format is different. It is designed for programmatic execution through APIs, scripts, and cloud systems.

Use API format when you want to:

• submit workflows through an API
• automate generation
• build tooling around ComfyUI
• feed a workflow into a service that expects prompt JSON

Do not use API format as your only human-readable backup unless you know the workflow will never be reopened in the normal ComfyUI UI.

3. PNG metadata

The SaveImage node saves images to ComfyUI/output/. It can embed prompt and workflow metadata inside PNG files.

This is convenient because you can often drag a generated PNG back into ComfyUI to recover the workflow that created it.

But PNG metadata is not a complete backup strategy:

• metadata can be stripped by image optimizers
• screenshots usually do not preserve workflow metadata
• some sharing platforms remove metadata
• video workflows and non-PNG outputs may behave differently

For important work, keep the JSON too.

If You See "Failed to Save Workflow Draft"

That wording usually points to browser-side state, permissions, or a broken frontend session, not to a missing model.

This specific diagnosis is practical troubleshooting guidance based on how the ComfyUI frontend stores workflow state. The official ComfyUI docs directly document workflow JSON, PNG metadata, and the user directory, but they do not publish a formal error taxonomy for every draft-save failure.

Check these in order:

1. Save the workflow manually as JSON first, so you do not lose the graph.
2. Refresh the page and confirm ComfyUI is still connected.
3. Test in http://127.0.0.1:8188 with browser extensions disabled.
4. Check whether the browser is blocking local storage or file access.
5. If ComfyUI keeps reconnecting or other UI actions fail too, continue with ComfyUI Reconnecting Error or ComfyUI Failed to Fetch Server Logs.

Do not assume a draft-save problem means the workflow itself is broken. Most of the time, the safer move is to export JSON immediately and debug the UI second.

How to Save a Workflow

Use one of these methods:

If a browser download dialog appears, choose a clear folder and name the file based on the workflow purpose.

Example:

workflows/
  flux-kontext-product-photo-v1.json
  flux-kontext-product-photo-v2.json
  wan-video-test-lowvram.json

Where ComfyUI Saves Workflows

There is no single universal answer because ComfyUI has multiple save paths.

Manual JSON export

If you explicitly save or export a workflow JSON, it goes wherever your browser or file dialog saves it. Many users accidentally leave these in Downloads.

Check:

C:\Users\<you>\Downloads

or the folder you selected in the save dialog.

ComfyUI user directory

ComfyUI also has a user directory for settings, workflow state, and user-specific data.

For GitHub Windows portable installs, the default user directory is usually under the ComfyUI folder inside your extracted portable root:

<your-portable-root>/ComfyUI/user/default

For example, if your extracted portable folder is D:\AI\ComfyUI_windows_portable, check:

D:\AI\ComfyUI_windows_portable\ComfyUI\user\default

That folder currently contains settings such as:

comfy.settings.json

Depending on your ComfyUI version and how you save from the Workflows sidebar, workflow state and saved workflow files may also appear under the user directory. Treat this directory as useful state, but do not rely on it as your only backup.

Generated images

Output images are normally saved to:

ComfyUI/output/

If workflow metadata is embedded, those images may be usable for recovery by dragging them back into ComfyUI.

How to Recover a Workflow from an Image

If you still have the generated PNG:

1. Open ComfyUI.
2. Drag the PNG onto the canvas.
3. If metadata is present, ComfyUI should load the workflow.
4. Immediately save the workflow as JSON.
5. Rename the JSON clearly and keep it with the project.

If dragging the image does nothing, the metadata may have been removed. Try the original file from ComfyUI/output/, not a compressed copy from chat, social media, or a website.

The Safer Workflow Habit

Many ComfyUI breakages happen right after custom node installs, updates, or model cleanup. The users who recover fastest are usually the ones who exported a clean JSON before changing anything.

Use this habit:

1. Save the working workflow as JSON.
2. Save a second copy with a date or change note in the filename.
3. Keep one output PNG that still contains metadata.
4. Write down the required model files and custom nodes.
5. Only then update custom nodes, Python packages, or ComfyUI itself.

Best Backup Habit

Before installing custom nodes, updating ComfyUI, or changing Python packages:

1. Save your current workflow as JSON.
2. Copy important JSON files to a backup folder.
3. Copy the matching output images if they contain useful metadata.
4. Keep a note of required custom nodes and models.
5. Test that the JSON opens in a clean ComfyUI environment.

A simple project folder can look like this:

project-name/
  workflows/
    workflow-v1.json
    workflow-v2-before-plugin-update.json
  outputs/
    ComfyUI_00001_.png
  notes/
    required-models.txt
    required-custom-nodes.txt

Why Workflows Fail After You Save Them

A workflow JSON stores the graph. It does not include every model file, custom node repository, or Python dependency.

Common reasons a saved workflow fails later:

• model files are missing
• checkpoint names changed
• LoRA files moved
• custom nodes are not installed
• a custom node renamed a class
• Python dependencies changed
• the workflow was saved in API format but reopened as a UI workflow

This is why saved and recoverable are not the same thing. A workflow file preserves structure, but the environment still has to match it.

If you see Invalid image file

Some workflows store a reference to an input image, mask, or uploaded file. After moving the workflow to another machine, clearing browser state, or deleting files from ComfyUI's input folder, the graph may load but fail at queue time:

Custom validation failed for node image
Invalid image file: silver_hand.png

That usually means the workflow JSON is intact, but one referenced input asset is gone or no longer readable.

Fix it in this order:

1. Reattach the missing input image in the node that names it.
2. Check ComfyUI's input/ folder if the node expects a previously uploaded file.
3. Rename or reselect the file instead of editing random JSON by hand.
4. Save a fresh workflow JSON after the missing asset is restored.

For portable installs, the relevant input folder is usually under the ComfyUI folder inside the extracted portable package. For Desktop or managed launchers, use the app's file management path instead of assuming the portable layout.

If a saved workflow opens with red or unknown nodes, use How to Fix ComfyUI Plugin Import Failed Errors.

For larger workflow setup, use Workflow Environment Setup.

Save Workflow vs Save Image

For serious projects, save both.

How Wonderful Launcher Fits

Saved workflows are only useful if the environment can still run them.

Wonderful Launcher is useful when you need to protect or recover:

• workflow JSON files
• model folders
• custom node setup
• Python dependencies
• a ComfyUI environment that broke after updates

If you have important workflows and your environment keeps breaking after custom node work, download Wonderful Launcher before rebuilding everything from scratch.

FAQ

Where is my ComfyUI workflow saved?

If you exported a JSON file, check the folder you selected or your browser Downloads folder. If you used the Workflows sidebar or auto-save behavior, check the ComfyUI user directory, commonly ComfyUI/user/default in portable installs.

Why did ComfyUI not save my workflow draft?

Usually because browser-side state failed, the frontend was partially broken, or the local session lost access to the running server. Export JSON manually first, then debug reconnecting, frontend, or permission issues.

Are ComfyUI workflows saved inside PNG images?

Sometimes. The SaveImage node can embed workflow and prompt metadata into PNG files. If the metadata is still present, dragging the PNG into ComfyUI can reload the workflow.

Why did my PNG stop loading the workflow?

The metadata may have been removed by a website, chat app, image optimizer, or screenshot tool. Use the original file from ComfyUI/output/ when possible.

Should I save workflow JSON or API format?

Save normal workflow JSON for reopening and editing in the UI. Save API format only when you need automation or API execution.

Does a workflow JSON include models?

No. It can reference model names and node settings, but it does not package checkpoint, LoRA, VAE, or custom node files.

Related Guides

• ComfyUI Interface Guide
• How to Group in ComfyUI
• ComfyUI Prompt Has No Outputs Fix
• Workflow Environment Setup
• Install Custom Nodes
• ComfyUI Plugin Import Failed

Source References

• Official ComfyUI workflow concept
• Official workflow JSON schema
• Official SaveImage node documentation
• Official ComfyUI settings documentation
• Official ComfyUI appearance and user directory documentation