A reusable prompt preserves words. A recoverable project preserves the machinery and assets those words relied on. The difference matters when a model disappears, a node changes or the original reference image is no longer available.
This comparison uses a local ComfyUI workflow with a Stable Diffusion model as the concrete local case. It does not imply that every ComfyUI graph runs locally: the same ecosystem also supports remote partner nodes.
Decide what must survive
For an original fictional adult botanist at a greenhouse bench, the minimum creative record contains the character description, scene, composition and intended use. The technical record depends on the workflow.
A practical project folder could look like this:
greenhouse-project/
brief.txt
workflow.json
model-record.txt
environment-snapshot.json
references/
authorized-source.png
retained/
scene-01.png
revision-notes.txtThis is an editorial folder plan, not a download created by this article. Keep private account credentials and API keys out of the saved records.
A hosted preset and a workflow export have different scope
Frosting’s May announcement previewed presets. The June follow-up described saving, naming, labeling and searching prompts, plus term search across Dreams for Star tier and above. A September update says the new site is live. The documentation is therefore more substantial than an abandoned May roadmap.
Those records describe reusable prompts and retrieval of past work, not an export package containing a model, graph and environment. Individual production controls were not inspected here, so the comparison concerns documented record scope rather than a claim that no preset has shipped.
ComfyUI’s first-generation guide documents Workflows → Export for JSON and Workflows → Open for loading a workflow. It also describes opening generated images whose metadata contains the graph. Those are concrete preservation routes.
An image that has been resized, re-encoded or stripped of metadata may no longer carry that graph. Keep a separate workflow JSON rather than relying entirely on a shared preview file.
Preserve the model record separately
The same ComfyUI guide explains that base models are generally not bundled with the application and that missing models must be installed. A graph naming a checkpoint does not mean the checkpoint file is stored inside the graph.
Record the exact model filename, source, version and applicable license. For important local assets, a checksum can help distinguish two different files that share a similar name. Retain the reference images and any additional model assets the actual workflow needs.
A seed is also not a complete recipe. Without the same model, dimensions and workflow settings, matching that number alone cannot establish a matching result.
The environment is another dependency
The Comfy CLI reference documents environment snapshot and restore functions, alongside workflow dependency tools. A snapshot record can help identify what was installed when the graph worked.
That does not guarantee a model download remains available, that every custom node keeps working forever or that an old environment will run on different hardware. The snapshot complements the asset record; it does not replace it.
For a simple project, prefer a workflow you understand over an elaborate graph with unexplained nodes. Every extra dependency adds something to preserve and diagnose.
Local control has a maintenance cost
Frosting’s hosted approach can reduce the setup work a creator manages. The tradeoff is dependence on the service’s actual model and export options, which were not verified here.
A local workflow gives the user more direct responsibility for assets and environment. That can help a long-running project but also creates installation, storage and compatibility work. Neither a local program nor a desktop browser proves all processing stays on the machine.
The Comfy CLI source explicitly documents partner endpoints. If a graph uses remote services, their data handling and billing still matter. “Runs in ComfyUI” is not equivalent to “entirely offline.”
Reopen before declaring the record complete
The meaningful recovery check is modest: open the saved JSON, confirm that its model and assets resolve, and inspect whether the retained project settings are present. Do this before deleting the original working copy.
No workflow was installed or executed for this article. The supported distinction is record depth: Frosting’s dated preset announcement concerns reusable hosted choices, while ComfyUI documents a portable graph and separate dependencies. A recoverable local project needs all of those layers, not just the words that described the image.