# Blocks

> Build a processing chain with block previews and parameter controls, inspect its history, and keep the same underlying graph available for editing.

Source: https://kaitoi.io/docs/studio/blocks/
Section: Kaitoi Studio / Graphs, nodes and blocks
Written for: Anyone who prefers a sequential workflow interface.
Last reviewed: 2026-10-24

---

Blocks presents graph nodes as a chain. Switching between **Blocks** and
**Graph** changes how you work with the same nodes; it does not create a second
workflow to keep synchronized.

## See the same nodes in two views


The illustration follows the same three nodes: A loads an image, B desaturates it, and C saves it. Blocks emphasizes their previews; Graph exposes their pins and branches. Switching views creates no copy and performs no execution. Adjacent automatic connections still need compatible pins.

The same authored plant image appears in color at A and grayscale at B and C. Graph view exposes anchored input/output ports and wires; Blocks keeps the media-led chain.

*Figure: Keep node identity and connections when switching views.*

## Add and configure a block

1. Open **Blocks** from the view dock.
2. Use the **+** card to add an operation, or an insertion control between blocks.
3. Select the block to open its parameters.
4. Set its inputs and run the work, then inspect the central preview.

Adjacent blocks connect through compatible output and input pins. If there is
no compatible pair, the interface shows a gap to resolve rather than converting
the data silently. Open Graph when you need to inspect the exact wiring.

## Work in more than one chain

Stripes group blocks into separate horizontal chains. Use them to compare
variations or keep independent processes organized. A block can also take an
input from a non-adjacent block: select the relevant blocks and use the link
icon in the parameter panel where a compatible connection is offered. Its
tooltip describes the output it will connect.

## Inspect an output or earlier result

Select which output to preview when a block has several. The history panel
shows earlier generation snapshots for the selected block. Check the displayed
result before using **Send to Timeline** or another destination action.

Use the context menu to duplicate selected blocks into another stripe when you
want a separate variation. Changes to a block still change its underlying node,
including when that node is also visible in Graph.

## When to switch to Graph

Use Graph for branching, detailed pin connections, containers, and subgraphs.
Return to Blocks for a clearer view of a mostly sequential chain. Provider
requirements, execution costs, and save behavior are the same in both views.

## Keep the chain and graph consistent

**Chain:** adjacent compatible block pins can connect automatically; a gap
needs attention. **Stripes:** organize separate chains or variations. **Graph:**
inspect exact pins and branches. These views refer to the same underlying
nodes, not separate synchronized workflows. Selecting a historical preview
does not undo every setting or downstream result.

## Checks and next steps

After inserting or reordering blocks, inspect any visible connection gap.
Supported aliases can be normalized during automatic wiring, but that does
not invent a missing transformation. Use Graph to inspect an unexpected
source or a branch that does not fit the linear presentation.

Separate stripes organize variations, while each block still references its
underlying node. Review the selected output and generation snapshot before
transferring media. A history selection is not an automatic undo of all node
settings or downstream work.