# ComfyUI in the cloud: keeping models, workflows and outputs

Preserve ComfyUI cloud models, node versions, workflows, inputs and outputs with an explicit storage map and a tested replacement-instance restore.

Author: Retrivium team
Updated: 2026-11-01
Canonical URL: https://retrivium.ai/journal/comfyui-cloud-persistence/
Language: en

ComfyUI in the cloud needs a preservation plan for models, workflows, custom nodes, inputs and outputs after the environment stops. Saving a JSON graph is useful, but it does not restore the entire process on a replacement instance. Map the full environment and test recovery before deleting the only working copy.

## Inventory the environment recipe

Record the ComfyUI version, node versions, model filenames and revisions, launch settings and user-file locations. A workflow can reference weights or nodes absent from a new environment. Preserve the recipe separately from the temporary compute resource so another operator can rebuild it.

Distinguish recoverable model caches from unique inputs and results. A public weight file may be downloadable again, while an output or annotation might exist only in the project. Recovery time still matters even for data that can be regenerated or downloaded.

## Map each object to storage

| Object | Description to retain | Restore check |
| --- | --- | --- |
| Models | Durable location and version | Files are readable |
| Workflow | Saved graph and date | Graph opens |
| Custom nodes | Version inventory | Dependencies load |
| Inputs | Owner and retention period | Permitted sample exists |
| Outputs | Separate result directory | Control file is readable |
| Temporary files | Cleanup rule | Not mistaken for an archive |

Folder names alone do not establish durability. Match application paths to actual mounted resources and the cloud product's lifecycle rules. A familiar workspace directory can use a different storage type in another template.

## Verify paths and deletion behavior

ComfyUI startup settings can define model, input, output and temporary directories. Compare those settings with attached disks or volumes. Docker volumes have a lifecycle distinct from containers, but a cloud template may use a different mechanism with its own deletion responsibility.

Record what happens on process restart, instance stop and instance deletion. Persistent storage is not an automatic substitute for an independent backup of irreplaceable data. Keep the storage inventory outside the environment and assign an owner for retained resources and charges.

## Rehearse recovery and closure

Generate a small control output, preserve the recipe and recreate the test environment through the intended route. Confirm model availability, graph loading, node dependencies and reading the saved result. Where appropriate, compare checksums and inspect the output itself.

At the end of a pilot, retain only agreed data and remove unnecessary resources after verifying recovery. This supports a practical discussion of local placement and operations without assuming the cloud environment survives every lifecycle action.

Official references: [github.com — ComfyUI](https://github.com/Comfy-Org/ComfyUI), [docs.comfy.org — startup flags](https://docs.comfy.org/development/comfyui-server/startup-flags), [docs.docker.com — volumes](https://docs.docker.com/engine/storage/volumes/).

Related guides: [Multiple GPUs for ComfyUI: one workflow or separate queues?](/journal/comfyui-multi-gpu/), [Stable Diffusion GPU requirements: resolution, batch and weights](/journal/stable-diffusion-gpu-requirements/).