Presets
Save a full Workflow recipe, or reuse a Preset fragment
Last updated: 2026-09-19
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… is a separate header item; it is not the save door.
Share the .hextile.json file. The recipient still needs the same pipeline weights installed locally. The input image is not inside the recipe.
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 a prompt fragment, not a Workflow. This page does not teach Worlds.
Related
- Creating Renders
- Pipelines
- Agent Mode — agents load the same
.hextile.jsonrecipe