Output File Naming

360 Hextile provides flexible output file naming with customizable patterns, sequence handling, and custom output directories.

Overview

Control how your rendered files are named and where they're saved:

• Naming Patterns: Choose from presets or create custom patterns
• Token System: Use dynamic tokens like {original}, {template}, {seed}
• Custom Output Directory: Save final outputs to any location
• Sequence Support: Automatic index padding for image sequences
• Conflict Resolution: Handle existing files intelligently

Output Location Structure

Render Folder (Working Directory)

All processing happens in the render folder:

output/{render-id}/
├── {original-input}.png         ← Original input (preserved)
├── config.hextile.json          ← Complete render configuration
├── tiles/                       ← Extracted tiles
│   ├── Hextile_01.png
│   ├── Hextile_02.png
│   └── ...
├── tiles_diffused/              ← AI-processed tiles
│   ├── Hextile_01.png
│   ├── Hextile_02.png
│   └── ...
├── preview.jpg                  ← Live progress preview
├── render.log                   ← Processing logs
└── {pattern-based-name}.png     ← Final output (named by pattern)

Purpose: Complete record of the render with all intermediate files.

Custom Output Directory (Optional)

When specified, the final output is copied to your custom location:

C:/MyProject/Renders/
└── {pattern-based-name}.png     ← Copy of final output

Purpose: Clean output folder with just your final renders.

Naming Patterns

Available Presets

1. Auto (Original + Settings)

Pattern: {original}_{template}_{model}_s{seed}

Example: - Input: mountain.jpg - Output: mountain_Hextile20-2K_sdxl-base_s42.png

Best for: General use, maximum information in filename

2. Original Filename

Pattern: {original}

Example: - Input: mountain.jpg - Output: mountain.png

Best for: Keeping original naming, simple workflows

3. Template + Timestamp

Pattern: {template}_{timestamp}

Example: - Output: Hextile20-2K_20260103_143522.png

Best for: Time-series work, multiple versions tracking

4. Custom Pattern

Pattern: User-defined

Example: - Pattern: {date}_project_{original}_v{index} - Output: 20260103_project_mountain_v001.png

Best for: Project-specific naming conventions

Token Reference

Available Tokens

Token Examples

# Project workflow
{date}_{original}_v{index}
→ 20260103_mountain_v001.png

# Client deliverables
Client-{original}-{template}-final
→ Client-mountain-Hextile20-2K-final.png

# Archive system
archive/{date}/{original}_{time}
→ archive/20260103/mountain_143522.png

# Simple timestamp
{original}_{timestamp}
→ mountain_20260103_143522.png

Sequence Handling

When processing image sequences (folders with multiple images):

Index Padding

Choose how many digits for frame numbers:

Recommendation: Use 3-4 digits for most sequences

Start Index

Choose where numbering begins: - 0: 000, 001, 002, ... (programmer convention) - 1: 001, 002, 003, ... (standard convention)

Recommendation: Use 1 for general use, 0 for technical workflows

Example Sequence Output

Input Folder:
frame_01.jpg, frame_02.jpg, frame_03.jpg

Pattern: {original}_enhanced_{index}
Padding: 3 digits
Start: 1

Output:
frame_01_enhanced_001.png
frame_02_enhanced_002.png
frame_03_enhanced_003.png

Conflict Resolution

Handle existing files with three strategies:

Auto-rename (Default)

Behavior: Adds unique hash if file exists

Example:

mountain.png exists
→ Save as: mountain-a3f29c.png

Best for: Never overwriting, keeping all versions

Overwrite

Behavior: Replaces existing file

Example:

mountain.png exists
→ Replace it with new render

Best for: Iterative work, don't need old versions

Skip

Behavior: Don't save if file exists

Example:

mountain.png exists
→ Don't save to custom directory
→ Still available in render folder

Best for: Avoiding duplicates, selective saves

Configuration in UI

Output Tab Settings

1. Custom Output Directory

┌─────────────────────────────────────────┐
│ Output Directory (Optional):            │
│ ┌─────────────────────┐  ┌────────────┐ │
│ │ C:\MyProject\Renders│  │  Browse    │ │
│ └─────────────────────┘  └────────────┘ │
│ ℹ️ Leave empty to keep in render folder │
└─────────────────────────────────────────┘

2. File Naming Pattern

┌─────────────────────────────────────────┐
│ Naming Pattern:                         │
│ [▼ Auto (Original + Settings)]          │
│                                         │
│ Preview: mountain_Hextile20-2K_sdxl_... │
└─────────────────────────────────────────┘

3. Sequence Options (shown when input mode is sequence)

┌─────────────────────────────────────────┐
│ Sequence Options                        │
│ Index Padding: [3 digits ▼]            │
│ Start Index:   [1      ]                │
└─────────────────────────────────────────┘

4. Conflict Resolution

┌─────────────────────────────────────────┐
│ If file exists: [Auto-rename ▼]        │
└─────────────────────────────────────────┘

Best Practices

For Single Images

Simple workflow:

Pattern: {original}
Directory: Keep in render folder
Conflict: Auto-rename

Professional workflow:

Pattern: {date}_{original}_{template}
Directory: C:\Projects\Client\Deliverables
Conflict: Overwrite

For Image Sequences

Animation frames:

Pattern: {original}_{index}
Padding: 4 digits
Start: 0
Directory: C:\Animation\Frames
Conflict: Overwrite

Batch processing:

Pattern: {original}_enhanced
Padding: 3 digits
Start: 1
Directory: Same as input (or custom)
Conflict: Skip

For Production Work

Time-tracked outputs:

Pattern: {original}_{timestamp}
Directory: C:\Archive\{date}
Conflict: Auto-rename

Version control:

Pattern: {original}_v{index}
Directory: C:\Project\Versions
Conflict: Auto-rename

Configuration File

Output naming is stored in the render's config.hextile.json:

{
  "output": {
    "width": 8192,
    "height": 4096,
    "file_format": "PNG",
    "quality": 95,
    "naming": {
      "pattern_preset": "auto",
      "custom_pattern": "{original}_{template}_{model}_s{seed}",
      "sequence_index_padding": 3,
      "sequence_start_index": 1,
      "conflict_resolution": "auto_rename"
    },
    "custom_output_directory": "C:/MyProject/Renders"
  }
}

Loading Saved Configurations

1. Go to Renders tab
2. Find previous render
3. Click "Load Config"
4. Output naming settings restored
5. Modify as needed

Examples by Use Case

Photography Enhancement

Pattern: {original}_{template}
Directory: Leave empty (keep with project)
Conflict: Auto-rename

Result: DSC_1234_Hextile44-4K.png in render folder

Client Deliverables

Pattern: {date}_Client_{original}_final
Directory: C:\Clients\ProjectX\Finals
Conflict: Overwrite

Result: 20260103_Client_hero_final.png in client folder

Animation Production

Pattern: shot01_{index}
Padding: 5 digits
Start: 1
Directory: C:\Animation\Shot01\Renders
Conflict: Overwrite

Result: shot01_00001.png, shot01_00002.png, etc.

Archive System

Pattern: {timestamp}_{original}
Directory: D:\Archive\360Renders\{date}
Conflict: Auto-rename

Result: 20260103_143522_mountain.png in dated archive folder

Research/Testing

Pattern: test_{template}_{model}_s{seed}
Directory: C:\Research\Results
Conflict: Skip

Result: test_Hextile20-2K_sdxl-base_s42.png (unique tests only)

Troubleshooting

Output Not Appearing in Custom Directory

Check: - Directory path exists and is writable - Sufficient disk space - No permission issues - Path doesn't contain invalid characters

Solution: - Check render logs for copy errors - File still available in render folder - Verify directory in Settings

Files Being Renamed Unexpectedly

Cause: Auto-rename conflict resolution + file exists

Solution: - Use "Overwrite" to replace existing files - Or choose different naming pattern - Or clear output directory first

Sequence Numbers Not Working

Check: - Input mode set to "Sequence" not "Single" - Using {index} token in pattern - Sequence options visible in UI

Solution: - Verify input mode is correct - Check pattern includes {index} - Review sequence padding settings

Invalid Filename Characters

Special characters are automatically removed:

Pattern: {original}@{date}!
→ Actual: original20260103

Invalid: \ / : * ? " < > |
Valid: Letters, numbers, - _ .

Advanced Tips

Organize by Date

Create folder structure with dates:

Directory: C:\Renders\{date}
Pattern: {time}_{original}

Result:
C:\Renders\20260103\143522_mountain.png
C:\Renders\20260103\151234_ocean.png
C:\Renders\20260104\090000_city.png

Client-Ready Naming

Professional naming for deliverables:

Pattern: {original}_4K_360VR
Directory: C:\Deliverables

Result: HeroShot_4K_360VR.png

Version Iterations

Track multiple versions:

Pattern: {original}_v{index}_{date}
Conflict: Auto-rename

Result:
mountain_v001_20260103.png
mountain_v002_20260103.png
mountain_v003_20260104.png

Next Steps

• 📊 Output Settings - Format and quality options
• ⚙️ Settings - Save and load configs
• 🔧 Troubleshooting - Solve problems

Questions? Check the FAQ or Troubleshooting →