Flowchart Maker — Create Flowcharts Free Online

Standard Flowchart Symbols

How to Use the Flowchart Maker

1. Open the flowchart maker.
2. Drag a Start terminal onto the canvas.
3. Add process boxes for each action step in sequence.
4. Add diamond decision boxes where yes/no choices occur. Each diamond connects to two paths labelled Yes and No (or True/False).
5. Connect shapes with arrows by dragging from the edge of one shape to another.
6. Add labels to all shapes and connector lines to clarify what each step or decision means.
7. End all paths with an End terminal.
8. Export as PNG for documents, SVG for scalable use, or share a link.

Types of Flowcharts

Flowchart Design Best Practices

Flow direction and layout

Standard flowcharts flow top-to-bottom or left-to-right. Choose one direction and stick to it throughout. Top-to-bottom is most common for processes; left-to-right is common for timelines and software sequences. Avoid diagonal connectors — they imply non-standard relationships and confuse readers.

One action per box

Each process box should contain one discrete action — not a summary of multiple steps. "Verify identity and check eligibility and send confirmation" should be three separate boxes. Single-action boxes make it clear where decisions need to be made between steps, and make the process easier to audit and update.

Decision diamonds should have exactly two outputs

A decision diamond asks a yes/no question and always has exactly two connectors leaving it: one for Yes and one for No. If there are three or more possible outcomes, use a separate decision diamond for each additional branch, or use a different diagram type (such as a flowchart with a sub-process).

All paths should terminate

Trace every path through the flowchart — every possible sequence of decisions must eventually reach an End terminal. An open-ended path indicates an incomplete process design. Common errors: forgetting to add the "No" path from a decision, or leaving error/exception paths undefined.

Consistent sizing and alignment

All process boxes should be the same size; all decision diamonds the same size. Align shapes to a grid. Consistent sizing and alignment makes the diagram significantly easier to read and looks professional. Most flowchart tools (including the PublicSoftTools maker) have snap-to-grid and auto-align features.

Creating a Process Flowchart: Step by Step

Before drawing, plan the process in text:

1. Define scope: Where does the process start? Where does it end? What triggers it?
2. List all steps: Write every action in sequence. Include what happens when something goes wrong.
3. Identify decisions: Where are yes/no branching points? What are the criteria?
4. Assign owners: Who performs each step? (For swim lane diagrams.)
5. Draw draft: Start with the main happy path, then add exception paths.
6. Validate: Walk through the flowchart with someone who performs the actual process to find missing steps or incorrect sequences.

Flowcharts in Software Development

Flowcharts are used in software development to visualise algorithm logic before coding, document system processes for onboarding, and explain decision trees for product managers or stakeholders. For complex conditional logic (nested if/else, switch statements), drawing the flowchart first often reveals logic errors that are harder to spot in code.

Common algorithm flowcharting use cases:

• Authentication flows (login, OAuth, 2FA)
• Payment processing logic (validate → charge → confirm → notify)
• Content moderation decision trees
• Error handling and fallback sequences
• Sorting and search algorithm visualisation

Swim Lane Diagrams: Adding Responsibility

A swim lane diagram divides the flowchart into horizontal (or vertical) lanes, each representing a person, team, department, or system. Steps are placed in the lane of whoever performs them. Handoffs between lanes are immediately visible as connectors crossing lane boundaries.

Swim lanes are particularly useful for identifying:

• Where handoffs occur and who is responsible at each point
• Bottlenecks — steps where work accumulates waiting for input from another lane
• Unclear ownership — steps that fall between lanes
• Redundancy — the same information being checked or entered by multiple parties

Common Questions

What is the difference between a flowchart and a process map?

The terms are often used interchangeably. In strict usage, a flowchart uses the standard set of shapes (oval, rectangle, diamond, parallelogram) defined by ISO 5807. A process map is a broader term for any visual representation of a process — it may use flowchart symbols, swim lanes, value stream maps, or simplified block diagrams. For most purposes, the tools and techniques are the same.

How many steps should a flowchart have?

A flowchart should be as long as the process requires — no more, no less. In practice, if a flowchart exceeds 15–20 steps on a single page, consider using sub-process symbols (a rectangle with a bar at the top and bottom) to collapse complex sub-sequences into single boxes that reference a separate detailed flowchart. This keeps the top-level view navigable while allowing drill-down into detail.

What is BPMN and how does it differ from a standard flowchart?

BPMN (Business Process Model and Notation) is an industry-standard notation for business processes with more symbols and rules than simple flowcharts. BPMN distinguishes between tasks, events, gateways, pools, lanes, and message flows. It is used when process models need to be implemented in workflow software (e.g., Camunda, Signavio, or enterprise BPM tools). Standard flowcharts are sufficient for most documentation, communication, and planning purposes.