Dragging an image does not restore a workflow: verify that metadata survived
A displayed result, screenshot or resaved image may not contain recoverable workflow data. This alone does not indicate a broken import function.
Symptoms and scope
A displayed result, screenshot or resaved image may not contain recoverable workflow data. This alone does not indicate a broken import function.
Error fragments for search; IDs, values and filenames may vary:
No workflow found
workflow metadata
Source-supported context
Official examples load images that contain workflow JSON. Current ComfyUI PNG saving can write separate prompt and extra workflow information, but --disable-metadata suppresses it; a prompt record alone is not proof that a UI graph is recoverable. VideoHelperSuite's save_metadata is a separate video-output option. Check the exact file and its supported metadata before diagnosing the import. Text-to-image ControlNet ComfyUI save source VHS README VHS node source
Cases to distinguish
1. The saved file is a thumbnail, screenshot or platform-recompressed image.
2. The original save omitted workflow metadata, including when metadata saving was disabled; some files may still carry a prompt without a recoverable UI graph.
3. Workflow data is present but malformed or unsupported by the current importer. A graph that loads with missing nodes or models is a separate dependency problem.
Diagnostic sequence
The sequence below is an editorial procedure based on the cited context, not a diagnosis already confirmed for your environment.
Step 1. Prefer the author's original attachment or standalone workflow JSON rather than a displayed thumbnail.
Step 2. Inspect a local copy with a metadata-aware tool appropriate to its actual image or video format. Look specifically for a parseable workflow graph rather than assuming any prompt or metadata field is sufficient. This site's JSON-only tool cannot extract media metadata; its rejection proves nothing about that file.
Step 3. If the original file lacks a recoverable graph, use the author's standalone UI workflow JSON or request it. Pixels, a thumbnail or a prompt payload alone do not guarantee exact graph recovery.
Step 4. If workflow data is present but import fails, retain the exact importer error and verify its format and frontend support. Once the graph loads, check missing nodes, models and versions as separate dependency steps.
Completion check
The original file or standalone UI JSON supplies a parseable graph that the target frontend loads with plausible nodes and connections. This does not establish that the graph can execute with the available dependencies.
Limitations and cautions
Metadata may expose prompts, paths and other information. Inspect it before public sharing; pixels alone cannot guarantee recovery of the original seed and full settings.
Original sources
- Text-to-image workflow — checked 2026-09-26.
- ComfyUI ControlNet example — checked 2026-09-26.
- VideoHelperSuite README — checked 2026-09-26.
- ComfyUI image metadata source — checked 2026-09-26.
- VideoHelperSuite node source — checked 2026-09-26.
Source and English-language review: 2026-09-26. No site-run media import, ComfyUI workflow or GPU test is claimed.
Related troubleshooting and guides
Was this page helpful?
Anonymous. Only a yes/no counter is stored; no account, IP address or device details.
Sources & references
2026-09-26 reviewed current ComfyUI image metadata saving, official workflow examples, VHS metadata behavior and English wording. Prompt metadata is not equated with a recoverable UI workflow. No media import or GPU test was run.
01Text-to-image workflowSource checked: 2026-09-2602ComfyUI ControlNet exampleSource checked: 2026-09-2603VideoHelperSuite READMESource checked: 2026-09-2604ComfyUI image metadata sourceSource checked: 2026-09-2605VideoHelperSuite node sourceSource checked: 2026-09-26