Flowchart symbols and their meanings
Use start/end, process, decision, input/output, and connector symbols to make a flowchart readable. Learn when to use each shape with programming examples.
Start with four basic symbols
Most simple programming flowcharts need a terminal for Start and End, rectangles for actions, diamonds for conditions, and parallelograms for input or output. Arrows connect the symbols in the order the algorithm follows.
Choose shapes by the role of the step. “Read age” is input, “age = age + 1” is a process, and “Is age ≥ 18?” is a decision. Use short labels that say what happens or what is being tested.
Common flowchart shapes
| Symbol | Meaning | Example label |
|---|---|---|
| Start / EndRounded terminal | The beginning or end of a flow. | Start; End; Return result |
| ProcessRectangle | An action, calculation, or assignment. | total = price × quantity |
| DecisionDiamond | A condition that selects the next route. | Is total ≥ 100? |
| Input / OutputParallelogram | Data entering or leaving the algorithm. | Read quantity; Show total |
| FunctionRectangle with side lines | A named routine whose internal steps are described elsewhere. | calculateTax(total) |
| DatabaseCylinder | Stored data, such as records read from a database. | Customer records |
| ConnectorSmall circle | A labeled continuation elsewhere on the same page. | A, paired with another A |
A database symbol names a store of data; an action such as “Save customer record” can be a process connected to that store. Keep the distinction between data and the operation that reads or changes it.
Arrows show the direction of control
An arrow means “continue here.” Draw the main sequence in a consistent direction, usually from top to bottom. Give each arrow a visible destination. A line crossing another line should not imply that the two routes join.
For long routes, a pair of connectors with the same label can replace a line that would otherwise cross the page. Use a different label for each continuation pair. An off-page connector indicates a continuation on another page; include a page or destination reference so the reader can find it.
Decision symbols need clear outcomes
A decision should contain a test with distinct outcomes. For a two-way branch, write “Is password valid?” in the diamond and label the outgoing arrows “Yes” and “No.” The Yes route might open the account page; the No route might show an error.
Place actions on the branches, outside the diamond. If a decision has more than two outcomes, label every route with its case, such as “Card,” “Cash,” and “Other.” When a class or team specifies a particular notation, use its conventions consistently.
Loops use decisions and return arrows
A loop does not need a special shape. A decision checks whether to continue, a sequence of processes does the work, and an arrow returns to the check. One branch must lead to the next part of the program when the repetition is finished.
For example, “Is i ≤ 3?” can send Yes to “Print i,” then “i = i + 1,” then back to the decision. No goes to End. The drawing guide shows this complete loop and explains how to trace its values.
Choose extra symbols when they add meaning
Flowchart Studio includes 32 shapes. Beyond the basics, the palette includes documents, multiple documents, preparation, manual input, manual operation, storage, delay, display, annotations, and routing symbols.
Use a document for a report or page, a display for screen output when that distinction matters, and a note or annotation for an explanation beside the flow. Use a function symbol when the reader can understand the main sequence without seeing every step of the routine.
Specialized symbols are useful when they clarify the diagram for its audience. If a shape may be unfamiliar, label it clearly or add a legend. A small set of consistent symbols is enough for many algorithms.