Storage and Backup

Locate work, clear disposable caches and preserve editable projects and assets

Last updated: 2026-11-11

A delivery PNG or Workflow recipe preserves only part of your work. A useful backup includes editable project/output folders, their referenced assets and shared authored resources. Make a separate copy before moving or deleting work.

Find the Actual Locations

Open Settings > Storage and record:

  • Data Storage Location, including any warning that the configured drive is unavailable and a fallback location is active.
  • Renders save to, plus the active Project's output root when a Project is open. A Project overrides the global output selection.
  • The paths shown for storage classes/cache buckets. Use their folder actions to inspect actual locations rather than assuming everything is beside the app.

Also record the Project root (not only its output subfolder), registered custom output locations, and any external images/assets you imported or referenced. A missing drive/fallback warning can explain an apparently empty library; do not replace or delete the original data because it is temporarily unavailable.

What to Preserve

Work Keep
Editable Project/render history Whole Project root, including hidden app metadata, configs, render folders, saved history, channels, layers, Shots and associated assets. Preserve separately located outputs too.
Sequences Sequence records plus referenced source frames and completed outputs, including external/borrowed files. Frame exports alone do not preserve the editable job.
Shader and Fractal work Saved scenes/shelves, revisions, authored inputs and camera bookmarks; export editable scenes where their own guides provide that action. A rendered image is not the scene.
Custom resources User LUTs, Worlds, workflows, templates, Pattern presets, custom LoRA files and other authored media in their actual storage locations.
App setup Record data/output roots and model choices. Shared preferences and downloaded models are not all Project-local; protect any private configuration backup.

Keep a manifest of external paths alongside the backup. Copying a Project does not automatically collect every external input, model or preference. A Workflow contains settings/references; it is not a bundle of source images or model weights. Never share a full private configuration/data backup as a public recipe.

Make a Backup

  1. Let rendering, downloads, migrations and other writes settle. Save named Shader/Fractal scenes and commit image edits you intend to keep.
  2. Close the app normally before a filesystem backup so files are not changing while they are copied. Wait for it to finish shutting down.
  3. Copy the whole relevant Project/data folders and external assets to a separate backup location using your normal file-backup tool. Include hidden files. Do not manually rearrange individual managed history files.
  4. Check that the copy completed, compare its size/file count where useful and open representative exported images. Keep the original until an editable restore has also been checked.

For selective transfer between Projects, use the supported Copy/Move migration. It is not a complete backup: items can fail individually, and external references/tag assignments have limits. Check the results before deleting any source.

Free Space Safely

In Settings > Storage, expand cache usage. Use a disposable bucket's Clear or Clear Disposable Caches after active work settles. Read any per-bucket error; clearing can be partial and busy buckets can refuse. Previews and thumbnails may need to regenerate, so the next view can be slower.

Shaders is disposable. Clear on that bucket, or Clear Disposable Caches, can remove it. That clear stays outside the Shader Library shelves, so saved Shaders stay. It also leaves Shader Output Receipts and Recovery in place. If Shader output is still running, the clear refuses with "Shader output is active; try clearing its cache after it finishes."

Shader Output Receipts and Recovery is protected. It has no Clear action, and Clear Disposable Caches never removes it. The row tooltip is "Contains your work — cannot be cleared from the application". It holds Shader output receipts and recovery inputs.

Protected creative items do not have bulk-clear permission. Do not recursively delete a folder just because it is named cache: authored camera bookmarks and output-recovery evidence can share broader storage areas. Remove work through its own Library/tool controls only when you intend that deletion. Trash, sequence unregister and Project deletion have different file-retention rules; see Projects and Sequence.

Change Locations

Change Location... changes the data-root setting; it does not move existing data. Plan a backup/copy first and restart normally afterward so all components use the new root. Retain the old folder until you have verified the work and resources you need at the new location.

The global Renders save to > Browse... changes where new renders go; old renders remain where they were. Reset to Default follows the data root again. Close the active Project before changing the global output override. Use Project opening/migration for Project work rather than treating the global setting as a Project relocation tool.

Restore or Reopen a Backup

There is no universal one-click restore of every root and external dependency. Keep the original backup intact and restore a working copy while the app is closed. For a Project backup, preserve its folder structure and use the Dashboard/File menu's Project opening action to open that restored root. Reconnect external drives and inspect representative renders, history, sequences and named scenes before accepting the restore. Do not combine parts of different backups or hand-edit metadata to force discovery.

Shared resources restored outside a Project need their corresponding data-root location or supported import action. Reinstall downloadable models through Model Manager when needed; check custom assets against your manifest. If work is missing, check the active root/fallback warning and original paths first. Keep both copies and use safe troubleshooting if the app refuses the restored data. Reopening one image does not prove that all external dependencies or recovery state are intact.

Esc
Searching...
No results found.
Type to search the documentation
↑↓ Navigate ↵ Select Esc Close

We use cookies for analytics to understand how visitors use our site. Privacy Policy