Skip to main content
Every Partner Node request produces data that is stored on our platform: inputs (images, videos, 3D assets, audio), and outputs produced by the model. This page explains how long each kind of data is retained. Where each provider processes that data by default is tracked separately on the Model Providers.

What gets stored

When you run a Partner Node, two kinds of files are stored:
  • Input files: reference images, audio, and other media you provide to a node. Inputs are uploaded to your account’s storage space.
  • Output files: the images, videos, audio, and other media a node generates. Outputs are written to Comfy-managed storage and returned to you as download URLs.
Both input and output files are stored in Comfy-managed cloud storage buckets.

How long files are kept

All Partner Node media files are automatically deleted 24 hours after they are created. The deletion applies to both input and output files.
The 24-hour deletion window is a platform default and applies to all Partner Node calls. If you need to keep files longer, download them to your own storage before they expire.

What happens after deletion

Once a file is deleted, its download URL returns an error. Deleted files cannot be recovered, and the same media must be re-uploaded or regenerated if you need it again. Deleting an input file also removes the corresponding file record from your account storage, so the input cannot be reused by later calls.

Provider task records

A few Partner Nodes send the provider a task ID rather than a media file, and the provider works from the record behind that ID. Tripo’s follow-up nodes work this way: Tripo: Texture model, Tripo: Rig model, Tripo: Retarget rigged model, Tripo: Convert model, Tripo: Edit Multiview, Tripo: Segment Model, Tripo: Retopology, and Tripo: Complete Mesh Parts all take an input such as model_task_id or multiview_task_id. The generated model file is not affected. It is downloaded as soon as the task finishes and saved to your output directory. Provider task records follow the provider’s own retention, not the 24-hour window above. Tripo keeps a task record for 7 days after the task completes (effective December 1, 2026). A task ID older than that can no longer be resolved, so rerunning a saved workflow with an expired model_task_id fails at the follow-up node. To recover, re-import the model file you already downloaded with Tripo: Import Model. It returns a new model_task_id that the texture, rig, and convert nodes accept, so you do not pay for the base model again.

Keeping files longer

If your workflow needs an input file to remain available for longer than 24 hours, re-upload the file before each job. For long-running pipelines, re-upload right before the call that needs it. For outputs you want to keep, download them to your own storage within the 24-hour window.

Reference

For general information about how Comfy handles customer data, see Data Retention.