Flowchart symbols are the standardized shapes used to represent each kind of step in a flowchart. Every common symbol — oval, rectangle, diamond, parallelogram, arrow — has a specific meaning that tells the reader what's happening at that point, so anyone who knows flowchart shapes and their meanings can recognize the intended roles; unfamiliar domain rules still need explanation.
This guide is a complete flowchart symbols guide: every common shape defined with examples, including the four basic symbols most flowcharts actually need (terminator, process, decision, flow line), plus less common symbols like the parallelogram (data), cylinder (database), and off-page connector. If you also want an overview of flowcharts including types and use cases, see What Is a Flowchart?.
Flowchart Symbols Quick Reference: 15 Shapes
| Symbol | Shape | Meaning and example |
|---|---|---|
| Start / end | Oval or capsule | Enter or finish: Request received |
| Process | Rectangle | Perform an action: Validate request |
| Decision | Diamond | Choose a path: Required fields complete? |
| Input / output | Parallelogram | Read or return data: Read form values |
| Flow line | Arrow | Connect steps; label a decision exit Yes or No |
| Predefined process | Rectangle with two vertical side lines | Call a separately defined routine: Verify identity |
| Document | Wavy-bottom rectangle | Use or produce a document: Confirmation receipt |
| Database | Cylinder | Persist data: Request records |
| Manual input | Slanted-top rectangle | A person enters data: Type reference number |
| Display | Screen-like shape | Show information: Confirmation screen |
| Manual operation | Trapezoid | A person performs a task: Inspect package |
| On-page connector | Small labeled circle | Continue at matching A on this page |
| Off-page connector | Pentagon | Continue at B on another page |
| Preparation | Hexagon | Set up: Initialize retry count |
| Delay | D shape | Wait: Await response |
This list counts on-page and off-page connectors separately. Stacked documents are a variant of Document, rather than a sixteenth symbol. A tool's shape names can vary; use a legend when a local convention differs.
The Core Symbols
The first five cover many everyday workflows. The sixth, predefined process, helps when a detailed routine is documented elsewhere.
Terminator Symbol (Oval): Start and End

Shape: Rounded rectangle or oval
Meaning: Start or end of the process
Usage: A simple chart often uses one entry and one ending. Multiple exits are valid when each outcome is explicit; multiple entries need clear scope and labels. Label these clearly — "Start", "End", or something more specific like "Process Complete" or "User Exits."
Process Symbol (Rectangle): A Single Action or Step

Shape: Plain rectangle
Meaning: An action or step being performed
Usage: This is the workhorse of flowcharts. Use it for any step where something is being done: "Send confirmation email", "Calculate total price", "Update database record." Keep the label short and action-oriented — start with a verb.
Decision Symbol (Diamond): A Yes / No Branch

Shape: Diamond (rotated square)
Meaning: A decision point with two or more possible outcomes
Usage: A decision diamond always has a question or condition inside it, and at least two exits — typically labeled "Yes / No" or "True / False." The flow branches based on the answer. If you have more than two outcomes, you can add additional exit arrows, but diagrams with many branches become hard to read quickly.
Parallelogram Symbol: Input or Output (Data) in a Flowchart

Shape: Parallelogram (slanted rectangle)
Meaning: Input or output of data
Usage: Use this when the process involves receiving input from a user or external source, or when it produces output. In software flowcharts, this often represents reading from or writing to a file, database, or user interface.
Flow Line (Arrow): Direction Between Steps
Shape: Line with an arrowhead
Meaning: Direction of flow between steps
Usage: Arrows connect all other shapes and show which step comes next. They should always point in one direction — ambiguous arrows (no arrowhead, or double-headed) create confusion. Label arrows when the direction isn't obvious, or when a decision diamond needs more context than "Yes/No."
Predefined Process: A Referenced Subroutine

A predefined process uses a rectangle with an additional vertical line near each side. It calls a routine whose details are defined elsewhere, such as “Verify identity.” A rounded rectangle alone does not identify a subroutine and may instead be used as a terminator. Use an ordinary process rectangle for an action fully described at this level.
Additional Symbols
These shapes are used in more complex or specialized flowcharts.
Document

Shape: Rectangle with a wavy bottom edge
Meaning: A document or report produced or used in the process
Usage: When a step involves generating or consuming a physical or digital document — a contract, an invoice, a printed report. Often used in business process diagrams where paper trails matter.
Document Variant: Multiple Documents
Shape: Stacked document shapes
Meaning: Multiple documents
Usage: Used when a step involves several documents at once — processing a batch of invoices, for example.
Database / Cylinder

Shape: Cylinder
Meaning: Stored data — typically a database
Usage: In system architecture and data flow diagrams, the cylinder represents a persistent data store. In flowcharts, use it when the process reads from or writes to a database.
Manual Input

Shape: Rectangle with a slanted top edge
Meaning: Data entered manually by a person
Usage: When a user physically types or enters data — a form field, a keyboard entry, a manual override. Helps distinguish automated steps from human interactions.
Display
Shape: Shape that looks like a monitor or screen
Meaning: Information shown to the user
Usage: When a step involves displaying something on a screen — a dashboard, a confirmation message, a report view.
Manual Operation
Shape: Trapezoid (wide top, narrow bottom)
Meaning: A step performed manually, not automated
Usage: In diagrams that mix automated and manual steps, this shape flags the manual ones. Useful for process improvement work where the goal is to identify and reduce manual steps.
Connector Symbol: Linking Across or Off-Page in Flowcharts

Shape: Small circle (on-page connector) or pentagon (off-page connector)
Meaning: The flow continues elsewhere
Usage: When a flowchart gets too large to fit on one page or canvas, use connectors to link sections. Label both connectors with the same letter or number so the reader knows where to pick up.
Preparation / Initialization

Shape: Hexagon
Meaning: A setup step before the main process begins
Usage: Used in technical diagrams to show initialization steps — setting variables, loading configuration, preparing a loop. Not commonly used in business process diagrams.
Delay

Shape: D-shape (rectangle with a rounded right side)
Meaning: A waiting period or delay in the process
Usage: When the process must pause and wait — for an approval, a delivery, a timer, or an external event.
The Only Symbols Most Teams Actually Need
If you're drawing a normal business or software flowchart today, you probably do not need the full symbol list above. In practice, a useful starter set is these five:
- Start / End for entry and exit points
- Process for action steps
- Decision for branches
- Arrow for flow direction
- Input / Output only when data entering or leaving the process matters
That means you can start drawing without overthinking notation. To try those symbols immediately, open the flowchart maker template and choose “Use this template.”
How to Read a Flowchart
When you encounter a flowchart drawn by someone else, here's a simple approach:
- Find the Start — the oval or terminator labeled "Start." If there isn't one, look for the shape with no incoming arrows.
- Follow the arrows — always in the direction they point, never backward unless a loop is explicitly shown.
- At every decision diamond, understand the condition being tested and which path each outcome follows.
- At connectors, find the matching label on another part of the diagram to continue.
- Find the End — confirm you've reached a terminal state, not a dead end where an arrow simply stops.
Common Mistakes
Using the wrong shape for convenience. If a diamond means "decision," don't use it for a regular step just because it looks good in that position. Readers will expect a branch.
Missing labels on decision arrows. Every exit from a diamond needs a label. "Yes/No" is fine; unlabeled arrows force the reader to guess.
Too many crossing arrows. When arrows cross frequently, the chart becomes hard to follow. Reorganize the layout so the main flow runs in one direction (usually top-to-bottom or left-to-right).
No terminator. A flowchart without a clear Start and End is ambiguous. Even if the process is cyclical, show where it begins and define the exit condition.
Overloading a single shape. If a process rectangle needs five lines of explanation, it's probably doing too much. Break it into multiple steps.
Worked Example: A Request Form with a Correction Loop
Here is an illustrative workflow you can draw using the symbols above. It describes a request form, not a measured production system. The key distinction is between an action, a decision, and data that persists after the action ends.
| Step | Label | Symbol | Next step |
|---|---|---|---|
| 1 | Request started | Terminator | Read form values |
| 2 | Read form values | Input / output | Required fields complete? |
| 3 | Required fields complete? | Decision | Yes: save request; No: show missing fields |
| 4 | Show missing fields | Display | Return to Read form values after correction |
| 5 | Save request | Process | Request records |
| 6 | Request records | Database | Generate receipt |
| 7 | Generate receipt | Process | Confirmation receipt |
| 8 | Confirmation receipt | Document | Request accepted |
| 9 | Request accepted | Terminator | End |
Trace the Yes path once, then trace the No path back to input. The return arrow must target the input step rather than the Start symbol: correcting a field should not create a new request. A cylinder denotes the stored records; the rectangle says what the system does to those records. A document represents the receipt itself, while “Generate receipt” remains an action.
If the team does not need that data-level detail, combine steps 5–6 into one rectangle labeled “Save request to database.” Simplification is useful when it preserves the question the diagram must answer. Do not add a database symbol merely because the application uses one somewhere.
Open the flowchart example below and replace its labels with this sequence. Add and label the correction branch, then follow both routes before sharing. The template is a starting layout, not an implementation of the form.
Process vs. Predefined Process vs. Terminator
These three shapes are easy to confuse in a symbol picker. “Validate request” is a normal process rectangle when its work is contained in the current chart. “Verify identity” can be a predefined process with two side lines when its detailed steps live in another diagram or procedure. “Request accepted” is a terminator because the current workflow stops there.
A rounded corner alone does not mean “subroutine.” Reusing the same rounded shape for both actions and endpoints makes readers depend on the text to recover the intended meaning. Keep the shape convention consistent and link to the detailed procedure when a predefined process needs explanation.
How to Check a Flowchart Before Sharing
Read labels without looking at colors first. A reader should still be able to distinguish an action from a condition and an endpoint in a grayscale export. Then inspect every decision: the outgoing labels should cover the outcomes the current scope allows, without two labels describing the same case.
Next, follow every connector. Matching letters need matching destinations; an off-page connector should identify the page or section as well as the label. Finally, read each ending aloud. “Request accepted” and “Request canceled” explain more than two identical End labels, especially when both outcomes appear in the same diagram.
Related Reading
- Flowchart Examples — real-world layouts you can copy
- How to Make a Flowchart — step-by-step tutorial
- Free Flowchart Makers — tool comparison
- Open the flowchart maker template — choose the template, then enter the editor



