Guides
Assets and Storage

Assets and Storage

Assets collects recorded generations across projects and workflows. It keeps media details and available generation-time workflow snapshots. Imported project results can open their project but have no historical workflow snapshot. A snapshot records the workflow as it was when that result was made. Recent generations shows the current tab's recent results; Assets provides the full library.

Find and reuse a result

  1. Select Nb → Assets, or press A outside a text field.
  2. Search the library or choose filters in its side panel.
  3. Open a result to inspect its media and details.
  4. Open its context menu for project, download, and organization actions.

You can filter by media type, project, workflow, model, tags, and date. The side panel also has Favorites, Missing files, and Trash. Tags and favorites help you collect results without moving their files.

ActionResult
Open projectOpens the result's current project
Open as it was when madeOpens the saved generation-time workflow snapshot
Open workflowOpens the available workflow for a result without a project action
Copy promptCopies the recorded prompt
RevealOpens the file's location where supported
Save copy or downloadCreates a separate copy of the media

Available actions depend on the result's recorded origin and files. Opening a snapshot does not repeat generation requests. Check models, keys, and inputs before you run it again. For Assets keyboard shortcuts, see Keyboard Shortcuts.

Choose the Node Banana folder

Settings → Storage shows the shared Node Banana folder. New projects use this folder by default. Generations from unsaved workflows go in its Generations subfolder. Existing projects can stay in other folders and still appear in Open and Assets.

The usual default is Documents/Node Banana under your user folder. On Windows with OneDrive-redirected Documents, the app uses Node Banana directly under your user folder. It also falls back to that location if the Documents default is not writable. NODE_BANANA_ASSET_LIBRARY can override the location for a source installation.

The shared folder is separate from the desktop profile that holds preferences and encrypted keys. See Desktop app for profile locations.

Change the folder

  1. Open Settings → Storage.
  2. Choose the new folder.
  3. Read the folder-change dialog.
  4. Choose the action that matches your intent.
ChoiceEffect
Move everything thereMoves the library and eligible project folders to the new location
Use that folderSwitches the active folder without moving existing files

The move checks for conflicts and folders that contain unrelated files. If a move is refused, read the report before you change or delete anything. Keep the original files until the app reports a successful move.

Project files and auto-save

Your workflows are JSON files that store the canvas and node settings. JSON is a text format for structured data. Media can live beside the workflow file or inside it.

Auto-save is enabled by default under Settings → Project → Save automatically. After the first save, it waits about three seconds after your last edit. During continuous edits, it attempts a save within 30 seconds of the first edit. That limit waits while a run, another save, or a media write is active. Leaving the window or hiding its tab also requests a save. If saving fails repeatedly, the app backs off and shows an error. Use Cmd/Ctrl + S to save important changes and inspect any error.

New projects default to the shared Node Banana folder. The Project tab controls whether images use external files or embedded base64 data. Base64 encodes binary media as text and makes the workflow file larger. External media lives beside the workflow, including the generations/ and outputs/ folders. Keep these folders together when you move a project.

Workflow tabs track separate canvases and warn about unsaved changes before discard. The desktop app also keeps crash-recovery checkpoints.

Bring in existing projects

  1. Open Settings → Storage.
  2. Under Bring in projects from another folder, select Choose folder….
  3. Choose the folder that contains your existing Node Banana projects.
  4. Wait for the search of that folder and its subfolders.
  5. Review the discovered projects and choose an action.

If no projects are known yet, the Welcome screen also offers Bring in your projects.

ChoiceEffect
Make this my Node Banana folderUses this folder for new projects and unsaved generations; nothing moves
Move them into the current folderMoves the discovered project folders into the active Node Banana folder
Leave them where they areAdds projects to Open and Assets without moving them

Open project lists the projects the app knows about, including projects elsewhere. A custom parent directory remains available under Settings → Project. Project directories need absolute paths.

Trash, missing files, and permanent deletion

Moving a result to Trash keeps it available for restoration for 30 days. A missing file still has a record with its prompt and settings under Missing files. Restore the original file location to make that media available again.

Permanent deletion removes the library record and sends library files to your operating system's trash. You cannot undo that action within Node Banana. The confirmation has a separate checkbox for files inside project folders. If you leave it unchecked, those project files remain available to their workflows.

Removing a missing-file record deletes its saved details without restoring its media. Read the confirmation before you remove records or project files.

Maintain the library

Settings → Storage also provides cleanup for unused workflow data and the thumbnail cache. A thumbnail is the small preview shown in the library. Read each cleanup action's description before you run it. Use normal project saves as well as the generation snapshots. See save troubleshooting if a project cannot save.

Next steps

AgentComfyUI