Presets
Save a full Workflow recipe, or reuse a Preset fragment
Last updated: 2026-10-27
Two different objects share this page. Do not mix them.
| Word | What it is | File |
|---|---|---|
| Workflow | The full recipe — pipeline, template, prompts, modules, effects | .hextile.json |
| Preset | A reusable fragment (quality, style, or a chunk of settings) | not the whole recipe |
The live save door is the header caret: Save as Workflow…. That writes a portable .hextile.json. There is no mounted Config Manager.
Save a Workflow
- Open a render (or finish a Create source so one exists).
- Open the header identity caret.
- Choose Save as Workflow….
- Name the file. The app writes a
.hextile.jsonrecipe.
Apply Workflow to… (same menu) needs an open render. It replaces or forks the current recipe from a saved Workflow. Batch workflows…, where available, is a separate action and may be disabled in your build; its presence does not unlock execution.
Review the chosen input, pipeline, template and modules after applying. Replacement/fork choices affect the recipe/target offered by that dialog; they are not proof that pixels were rendered. Save the current Workflow first if you want to return to it.
Batch Workflows availability
The Batch workflows… header action is conditional and disabled by default. A visible menu item or an old saved job does not establish that this build admits execution. Use only the availability and permitted actions the app actually reports; there is no supported user setting here to force it on.
Where an enabled build offers the task, preflight checks a frozen Workflow and chosen inputs/destination before Start. Pause/Cancel request a boundary stop; closing the dialog is not cancellation. Completed output files and Import to Library are separate outcomes. Inspect existing results before retrying failed work; cancelled jobs do not become resumable merely by reopening the window. Follow its offered remaining-input/new-batch action instead.
This is separate from basic image sequences, folder Format Converter and 360 LoRA Batch Watch. Do not use those names interchangeably or assume Batch Workflows processes video.
Share the .hextile.json file only after checking for private prompts and machine-specific file paths. The recipient needs compatible installed models, referenced input/resources and supported features. The input image and weights are not inside the recipe. A recipe file is not a complete Project backup. If applying reports a missing model or input, locate/install it through the app before rendering; do not substitute a similarly named file silently.
Preset fragments
A Preset is a chunk, not a whole studio setup.
- Diffusion quality fragments (for example sharp / hd / photo) and negative-prompt fragments apply at render time. They are not a substitute for Save as Workflow….
- Pattern and Fractals presets store generator parameters. See Patterns and Fractals.
- Post Process hook presets store one effect chain fragment. See Post Process.
Worlds stores reusable prompt environments (.prompt.json). That is prompt content, not a full Workflow or a saved image. Fractal scenes, Shader assets/Looks and .hexshader bundles have their own source/save/share controls.
Related
- Creating Renders
- Pipelines
- Agent Mode — agents load the same
.hextile.jsonrecipe