Projects
Organise your work with project-based workspaces — each with its own renders, sequences, and 360 LoRA outputs
Last updated: 2026-10-27
360 Hextile uses a project-based workflow to keep your work organised. Each project is a folder on disk that contains its own renders, sequences, 360 LoRA outputs, and settings — completely separate from every other project.
Think of projects like folders in VS Code: you open one at a time, and everything you create lives inside it. This keeps related work together and makes it easy to switch between different workflows without mixing outputs.
What are Projects?
A project is a folder on your computer that 360 Hextile uses as a workspace. It is not a complete backup of your models, external source files or app settings. Every project shares the same output root directory structure — but the contents are unique to that project:
- Renders generated within a project stay in that project's output tree
- Sequences and animations are scoped to the project they were created in
- 360 LoRA outputs (panorama generation history) live inside the project folder
- Configs are stored at
<project>/configs/and are not shared between projects
Switching projects does not re-download AI models or LoRA weights — those are shared globally. Only the output tree changes.
Creating a Project
Create a project from the Dashboard:
- Click New Project and choose a folder location on your computer
- Give the project a name (defaults to the folder name)
- 360 Hextile creates a
360-project.index.jsonfile at the folder root to track its contents - The project opens immediately and becomes your active workspace
You can create as many projects as you like. Each is completely independent — renders in one project are never mixed with renders in another.
The create action is idempotent: if you point it at a folder that already has a project index, it recognises the existing project rather than overwriting it.
Opening and Switching Projects
Open a different project from the Dashboard recents list or the File menu:
- The recents list (up to 12 projects) appears on the Dashboard for quick access
- Switching projects re-roots the app's output tree to the new project's folder
- The render list, 360 LoRA history, and any open viewer surfaces refresh to reflect the new project
You cannot switch projects while a render, sequence, or 360 LoRA generation is actively running. If the app refuses the switch, finish or cancel the active work and wait for its settled status before trying again. Other operations, including migration, may also hold the project busy.
The last active project reopens automatically when you launch the app. If the project folder has moved or is missing, 360 Hextile starts in global mode and shows a warning.
What's Global vs Per-Project
Some things are shared across all projects, some are unique to each one:
Global (shared across all projects): - AI models and pipeline installations - LoRA model weights - GPU cache and VRAM state - Application preferences and settings - HuggingFace authentication token
Per-Project (unique to each project):
- Renders and render history
- Sequences and animation outputs
- 360 LoRA generation history
- Project configs (<project>/configs/)
- Project cover image
- Tags (each project maintains its own tag list)
This separation means you can switch between a landscape photography project and an interior design project without re-downloading models or re-configuring the app. Only the output context changes.
Project Index
Every project folder contains a 360-project.index.json file at its root. This file tracks:
- The project name and unique ID
- The output subfolder configuration
- Cover image reference
- Tags (each project has its own tag list, starting with the built-in "Favorite" tag)
The index is automatically maintained by 360 Hextile. You never need to edit it by hand. It uses atomic writes (temp file + rename) to prevent corruption.
If the index file becomes corrupt, 360 Hextile self-heals on next open — backing up the corrupt file to <project>/.360hextile/backups/ and creating a fresh index. A warning toast lets you know this happened.
Output Subfolder
Each project can route its output into a subfolder within the project root. This lets you keep the project folder clean or separate output by purpose:
- Default: output goes directly into the project root
- Custom: set an output subfolder name (e.g., "output" or "renders-v2") from the project settings
The output subfolder is validated to prevent unsafe paths — no absolute paths, no path traversal (..), no reserved names.
Migrating Renders
Move renders between projects using the migration tool:
- Select one or more renders in any project and choose Migrate
- Pick a target project from the list
- Choose Copy to keep the source or Move to relocate the selected work to the destination
- Successfully transferred items carry their core render files and saved history. Inspect the result for dropped tag assignments; existing destination tag definitions can take precedence. Check linked external inputs and references after migration.
- Sequences migrate after their frame renders to maintain consistency
Before migration, review the destination, dependent items and collision choices. Keep a backup before moving irreplaceable work. A multi-item migration can finish partially: inspect migrated, skipped and failed items before retrying. Cancel stops remaining work; it does not promise to undo items already transferred. Verify the destination opens correctly before removing any remaining source files. Migration does not repair every external file reference.
Deleting a Project
Remove from recents only removes the shortcut. Delete is destructive: it removes the project's permitted Hextile output folders and registry data. Make a separate backup first; this is not a Trash operation.
The root project marker, cover and backups are retained. Output-local support data may be removed along with outputs. Retained project metadata is not a backup of deleted renders or sequences.
If the project is active, use the offered close-and-delete flow after active work is settled. Deletion can be incomplete if files are locked or a disk operation fails. Read the result and inspect the folder before assuming all output bytes were erased. Do not use Project deletion as a secure-erasure tool.
Backup and recovery
Use Storage and Backup to preserve the whole Project, separately located output and external/shared assets. A Project marker, exported image or saved Workflow alone cannot restore editable history. After interruption, check Rendering and Recovery before retrying active work or changing roots.
Next: Learn about creating renders or explore the interface overview.