Skip to content

EN Project Management

FuryNocturnTV (Tare Fernandez) edited this page Feb 12, 2026 · 2 revisions

πŸ—‚οΈ Project and File Management

Studio Fury eliminates the chaos of ComfyUI's default output folder. Instead, the system automatically creates a professional hierarchical structure to organize your digital assets.


πŸ—οΈ Directory Structure

When you initialize a project with the Project Manager node (for example, with the name "Cyber_City"), the system generates the following architecture on your hard drive:

ComfyUI/
   └── output/
      └── StudioFury/          <-- Suite Root Folder
         └── Cyber_City/       <-- Your Current Project
            β”œβ”€β”€ Characters/    # Saved characters (.fury + .png)
            β”œβ”€β”€ Scenes/        # Backgrounds and environments (.fury + .png)
            β”œβ”€β”€ Renders/       # Final compositions and tests
            └── Cache/         # Temporary session data

Behavior Automatic Detection: If folders don't exist, the Project Manager node creates them instantly.

Routing: The Smart Saver node automatically detects whether you're saving a Character or a Scene based on bus information and sends the file to the correct subfolder.

πŸ’Ž The .fury Format

Most AI workflows save a PNG image with embedded metadata. This is useful for sharing, but insufficient for professional production.

Studio Fury introduces the .fury file as the exchange standard.

What does a .fury file contain?

It's a serialized container (based on torch.save) that stores the technical "DNA" of your generation. It's not a flat image; it's a living object:

Latent Space: The exact tensors before VAE decoding.

Benefit: Allows you to resample, enlarge, or modify the image without generating the compression artifacts caused by repeatedly saving and loading a JPG/PNG.

Image Tensors: The raw pixel data in PyTorch tensor format.

Entity Metadata: * ID: Unique name of the asset.

Prompts: The original positive and negative texts that created the image.

Aspect Ratio: The original aspect ratio settings.

Workflow: Loading and Reusing Saving to .fury ensures complete data fidelity.

Use Case: You create a character today. In three months, you use the Asset Loader node to load that .fury file. The system will recover the original latent space, allowing you to perform in-painting or variations with 100% mathematical accuracy, identical to the moment you created it.

πŸ–ΌοΈ Sidecar Files (.png)

Although the engine works with .fury files, the system always generates a visual PNG copy with the same name.

Purpose: For quick viewing in your operating system's file explorer.

Use: You can send these PNGs to clients or use them as a visual reference, while keeping the .fury file as your "digital negative."

Clone this wiki locally