Terminator (oval)
Start or end of the flow. Use one clear start and one or more clear ends.
A clear chart of the standard flowchart shapes and what each one means, plus free examples you can open and edit. No signup; hourly fair-use limits apply when you generate.
Free · no signup · no credit card · daily fair-use limits
Each template uses standard flowchart symbols. Open one, then edit the prompt to rename steps.
Start or end of the flow. Use one clear start and one or more clear ends.
An action or operation: send email, create account, run a check.
A branch. Label each outgoing arrow (Yes/No, Pass/Fail).
Data entering or leaving the process: form submit, report print.
Shows direction. Loops go back to an earlier step instead of duplicating boxes.
A report, ticket, or file produced by a step.
Time passing: SLA timer, approval queue, cooldown.
Who owns the step. Mention lanes in the prompt for cross-functional flows.
Each template uses standard flowchart symbols. Open one, then edit the prompt to rename steps.
Flowchart symbols are the shared visual vocabulary for processes: ovals for start/end, rectangles for work, diamonds for decisions, and arrows for order. Memorizing the shapes matters less than using them consistently so anyone can read the chart. This page lists the common symbols and meanings, then links into FreeDiagram so you can generate a full flowchart from a sentence.
One oval for the start, and clear end ovals for each exit path (success, cancel, error).
Each process box should be one action a reader can verify: “Send contract”, not “Handle paperwork”.
Ask a yes/no (or labeled) question, then draw both outcomes. Avoid diamonds with only one exit.
Describe the process in plain English on the flowchart maker, or open a template below and rename the steps.
Standard flowchart symbols come from long-standing conventions used in ISO 5807 and countless textbooks. When every team uses the same shapes, a support lead, an engineer, and a new hire can all read the same diagram without a legend.
The two mistakes that break readability are overloaded process boxes (“do everything related to onboarding”) and unlabeled decision arrows. Keep each rectangle to one verb, and write Yes/No (or Approved/Rejected) on every diamond exit.
Swimlanes add ownership: Sales, Support, Engineering. If you need stricter BPMN events and gateways, use a BPMN diagram instead. If you need equipment and instruments, use a P&ID — different symbol set entirely.
Terminator (oval), process (rectangle), decision (diamond), input/output (parallelogram), and arrows. Many teams also use document, delay, and connector symbols.
A decision. Each outgoing path should be labeled, typically Yes/No or a named outcome.
Yes. Browse the meanings with no signup. Generating diagrams uses hourly fair-use limits; downloads are SVG or PNG.
Yes. Open the flowchart maker, describe the process in a sentence, and FreeDiagram picks the shapes for you.
Flowchart maker, templates, and Boolean solvers.
Describe any process in plain English and FreeDiagram draws the flowchart instantly — decision branches, loops, and all. Free, hourly fair-use limited, no signup.
Start from a ready-made flowchart template for a real workflow, or describe your own process in a sentence. Free, no signup, download as SVG or PNG.
Type a Boolean expression and get a full truth table instantly — including minterm lists. Free, no signup; computation runs locally in your browser.
Simplify Boolean functions with a real minimizer — minimal SOP and POS, optional don’t-cares, and a K-map grid for 2–4 variables. Runs in your browser; free, no signup.