Decision Flowchart Builder

Draw a labeled directed flow from entered nodes and edges, with a readable outline and supported loops.

On-device No sign-up Free to use

Build flowchart controls

?

A JSON array of up to 24 objects, each with "id", "label" and "type". The type is start, process, decision or end. The id starts with a letter and uses letters, numbers, underscores or hyphens; labels are limited to 80 characters.

?

A JSON array of up to 48 objects, each with "from" and "to" node ids and an optional "label" of up to 40 characters. Every id must match a node.

?

Leave on to permit an edge that returns to a node already reached, such as a rework step. Turn it off to reject any cycle and name the edge that closes it.

?

Prints every labelled edge as a numbered legend entry instead of beside the connector. Useful for a dense or looping chart where a connector label would be hard to read.

Processed in your browser. Your inputs stay on this device.

Showing an example. Change the fields, then use build flowchart to update it.

Result

Showing an example.

Map an incoming order through an In stock? decision. Yes leads to packing and shipping, No to a backorder, and both paths finish at Order complete.

Laid out 5 nodes and 5 edges.

Loading the tool. Your result will appear here.

https://usefreetools.net/decision-flowchart-builder · 20 November 2026

Was this helpful?

How to use Decision Flowchart Builder

  1. Add rows under Flow steps. Give every step a unique ID, a label and a start, process, decision or end type.
  2. Add Connections using those IDs. Label decision branches such as Yes and No when needed; unknown IDs and direct self-connections are refused.
  3. Choose whether to allow loops across different steps. Turn loops off if you want any cycle rejected.
  4. Inspect the preview and text outline. Steps keep their entered vertical order; connector numbers refer to the complete connection key below the chart. Advanced raw data edits the same nodes and edges as JSON.
  5. Download decision-flowchart.svg, decision-flowchart-outline.txt or decision-flowchart-project.json after checking the flow. The diagram records your rules without running them.

Example: Decision Flowchart Builder

Map an incoming order through an In stock? decision. Yes leads to packing and shipping, No to a backorder, and both paths finish at Order complete.

You add
Nodes (JSON): [ { "id": "start", "label": "Order arrives", "type": "start" }, { "id": "check", "label": "In stock?", "type": "decision" }, { "id": "ship", "label": "Pack and ship", "type": "process" }, { "id": "backorder", "label": "Place backorder", "type": "process" }, { "id": "done", "label": "Order complete", "type": "end" } ] Edges (JSON): [ { "from": "start", "to": "check" }, { "from": "check", "to": "ship", "label": "Yes" }, { "from": "check", "to": "backorder", "label": "No" }, { "from": "ship", "to": "done" }, { "from": "backorder", "to": "done" } ] Allow loops: on List branch labels in a legend: off
You get
Laid out 5 nodes and 5 edges.

Options

Node IDs
IDs connect edges to nodes and must remain distinct. Nodes keep their entered order in a vertical column.
Branches and loops
Connector numbers refer to the full connection key. The legend switch removes nearby branch labels; long labels, more than eight nodes or a cycle also move them to the key automatically. A drawn loop does not establish that a process terminates.

Supported inputs and limits

  • 1 to 24 nodes and up to 48 edges.
  • Node labels allow 80 characters and edge labels 40.
  • IDs start with a letter and use letters, digits, underscores or hyphens.
  • Advanced JSON refuses unknown properties and references.
  • Direct self-connections are refused.
More details

Cycles across distinct nodes require Allow loops.

Large diagrams can be tall because nodes keep their input order in one vertical column.

There is no workflow execution, automatic rule validation or optimal-layout guarantee.

Where your input is processed

This tool does not upload your inputs. See the limits for anything saved on your device.

A clear drawing can still contain an unclear decision

Check that each decision has enough labeled outcomes for the actual task and that every destination is intended. The outline helps inspect connections when the drawing gets dense. The page lays out declared data rather than executing a workflow or deciding what its rules should be.

Questions about Decision Flowchart Builder

Can edges refer to missing nodes?

Unknown node IDs are refused.

Are loops allowed?

Loops across distinct nodes can be drawn when enabled. A direct connection from a node to itself is refused.

Does it execute decisions?

No. It renders your declared flow.

Page updated · Project managed by Tony Hines · Report a problem with Decision Flowchart Builder