Output parameters — the output stage is part of the production contract
The final image is not the end of engineering. You need to know which branch is actually saved, which branch merely exists in the graph, which branch is bypassed, and what LQ/HQ output means in the current state.
Two output levels
Direct JPG after main FLUX decode. This is the first verification point for the saved configuration.
Save nodes exist, but their upscale / overlay upstream is stored in mode 4.
Prefix, format and route state
- upstream
- 53
- folder
- ph\[time(%Y-%m-%d)]
- prefix
- ph01_archviz_sdxl2flux_LQ1
- file
- JPG · 72 dpi · Q100
- upstream
- 833
- folder
- ph\[time(%Y-%m-%d)]
- prefix
- ph01_archviz_sdxl2flux_HQ
- file
- PNG · 300 dpi · Q100
- upstream
- 849
- folder
- ph\[time(%Y-%m-%d)]
- prefix
- ph01_archviz_sdxl2flux_LQ2
- file
- JPG · 72 dpi · Q100
Confirmed segment and full template
ph\[time(%Y-%m-%d)]ph01_archviz_sdxl2flux_LQ1not stored in the workflow JSON<ACTIVE_COMFYUI_ROOT>\output\ph\<YYYY-MM-DD>\ph01_archviz_sdxl2flux_LQ1_....jpgThe value stays in this browser and does not modify the workflow.
Six visual checkpoints
A · 79B · 779A · 53B · 779A · 53B · 833A · 451B · 459A · 509B · 552A · 25B · 833Show the full PreviewImage index
39 ← 38 · 167 ← 165 · 233 ← 232 · 581 ← 583
113 ← 550 · 340 ← 339 · 341 ← 346 · 342 ← 347 · 343 ← 350 · 344 ← 349 · 345 ← 348 · 351 ← 352 · 353 ← 354
409 ← 829 · 507 ← 503 · 508 ← 522
15 ← 849
Previously created images
01File paths
- Source path
- Generated neutral placeholder · 2026-09-27
- Static project
- /assets/output/atlas-neutral-01.jpg
02File paths
- Source path
- Generated neutral placeholder · 2026-09-27
- Static project
- /assets/output/atlas-neutral-02.jpg
03File paths
- Source path
- Generated neutral placeholder · 2026-09-27
- Static project
- /assets/output/atlas-neutral-03.jpg
04File paths
- Source path
- Generated neutral placeholder · 2026-09-27
- Static project
- /assets/output/atlas-neutral-04.jpg
The original path is shown for provenance. The site uses only the stable copy from public/assets/output; the TEMP file may be removed by the system.
Fan-out reference image
NOT CONFIRMED The semantics of the external receiver UUID are not proven by the serialized graph.
In the saved state, the provably active output is node 730
| Output | Upstream | State |
|---|---|---|
| 730 · LQ1 JPG | Decode 53 | Active route |
| 531 · HQ PNG | Upscale 833 | Save node exists; upstream bypassed |
| 293 · LQ2 JPG | Overlay 849 | Save node exists; upstream bypassed |
| 15 · Final Preview | Overlay 849 | Preview exists; upstream bypassed |
OUTPUT = format + size + branch + filename + state
It is not enough to say “the workflow saves PNG.” You need to know which branch supplies the image, whether it passed through upscale, whether overlays were applied, and the execution state of upstream nodes.
Upscale is a separate module, not a mandatory part of generation
The graph contains Ultimate Upscale 833 with model 4x-UltraSharp, tile logic and optional detail transfer 834. This module can be bypassed without changing the logic of previous stages.
This is an important production lesson: delivery-resolution processing should be detachable from content-generation processing.
You should be able to answer: what exactly will be saved right now?
If the answer comes only from the name of a Save node, the output contract is not yet understood. Trace its upstream route to the last active processing checkpoint.