Flowchart Symbol Shapes and Their Uses Explained

If you've ever opened a flowchart template and stared at a dozen shapes with no idea which one to use, you're not alone. Each shape in a flowchart carries a specific meaning. Pick the wrong one, and your diagram sends the wrong signal to anyone reading it. Understanding flowchart symbol shapes and their uses is the difference between a diagram that communicates clearly and one that just looks like a mess of boxes and arrows.

What do the basic flowchart shapes actually mean?

Flowcharts use standardized shapes defined by ISO 5807 and long-standing industry practice. Each shape tells the reader what kind of action or decision is happening. Here's a breakdown of the most common ones:

Oval (Terminator) Marks the start or end of a process. Every flowchart needs at least one.
Rectangle (Process) Represents an action, step, or operation. This is the shape you'll use most.
Diamond (Decision) Indicates a yes/no or true/false branch. It always has at least two exit paths.
Parallelogram (Input/Output) Shows data entering or leaving the process, like user input or printed results.
Arrow (Flow Line) Connects shapes and shows the direction of the process flow.
Rectangle with rounded corners (Predefined Process) Points to a process defined elsewhere, like a subroutine or another flowchart.

If you want a deeper look at what each symbol represents, we covered what flowchart symbols mean in more detail in another article.

Why does the shape I pick actually matter?

A rectangle and a diamond might both look like "boxes" to a beginner, but they carry completely different instructions. A rectangle says "do this." A diamond says "decide this." If you swap them, someone following your flowchart could execute an action when they should be making a decision, or vice versa.

This matters most when you're building flowcharts for:

Software development Developers rely on accurate symbols to plan logic and code structure.
Business process documentation Teams use flowcharts to map workflows, onboarding steps, and approval chains.
Troubleshooting guides Support teams build decision trees using diamond shapes to walk through problems.
Presentations and proposals Stakeholders expect diagrams that follow recognized conventions so they can read them without explanation.

In each case, the shape is the signal. Get it right, and your diagram works on its own without a legend or verbal explanation.

What about the connector symbol?

One shape that trips people up is the connector symbol a small circle (sometimes labeled with a letter or number) used to link parts of a flowchart that span across pages or break across a large diagram. Instead of drawing a long arrow that snakes across your layout, you place matching connectors at the exit and entry points.

Connectors keep your diagrams clean and readable, especially when processes get long or complex. We have a separate guide that explains the flowchart connector symbol in more detail.

When should I use specialized shapes instead of basic ones?

Beyond the core set, there are specialized symbols for specific industries and situations:

Document symbol (rectangle with a wavy bottom) Use this when a step produces a physical or digital document, like an invoice or report.
Multiple documents (stacked wavy-bottom rectangles) Same as above, but for batches of documents.
Database symbol (cylinder) Indicates data storage, common in system design and IT flowcharts.
Manual input symbol (rectangle with a sloped top) Shows a step where a user enters data manually, like typing into a form.
Delay symbol (D-shape) Represents a waiting period, like a pause in a manufacturing process.
Preparation symbol (hexagon) Signals a setup or initialization step before the main process begins.

You won't need all of these for every flowchart. Most business and software flowcharts work fine with five or six core shapes. But when your diagram describes a process with documents, databases, or manual steps, these specialized shapes make the meaning immediately clear.

What are the most common mistakes people make with flowchart shapes?

Here are the errors I see most often:

Using rectangles for decisions. A decision must use a diamond shape. If your process has a yes/no branch inside a rectangle, readers won't immediately recognize the branching point.
Skipping the terminator shape. Every flowchart needs a clear start and end. Without ovals, it's unclear where the process begins and stops.
Inconsistent shape usage. If you use a parallelogram for input in one place and a rectangle for the same thing in another, your diagram becomes confusing fast.
Overcomplicating the diagram. You don't need every specialized symbol. Stick to what makes the process easier to follow.
Missing flow direction arrows. Without arrows, readers can't tell the order of steps, especially in flowcharts with branches.

How do I choose the right shape for each step?

Ask yourself one question about each step in your process:

"Is this the start or end?" → Oval
"Am I doing something?" → Rectangle
"Am I deciding something with two or more outcomes?" → Diamond
"Is data coming in or going out?" → Parallelogram
"Does this refer to another process or document?" → Rounded rectangle or document symbol

That simple checklist covers the vast majority of flowcharting situations. If you can categorize each step with one of those questions, you'll pick the right shape every time.

Do different industries use different symbol sets?

Yes, to some degree. The standard flowchart symbols are universal, but some fields use variations:

Programming Tends to stick closely to ISO 5807 symbols. Diamonds for conditionals, rectangles for processes, parallelograms for I/O.
Engineering and manufacturing Often uses ANSI standards, which are nearly identical but have minor differences in shape proportions.
UML and software architecture Uses its own diagram types (activity diagrams, sequence diagrams) with overlapping but distinct symbol sets.
Business process modeling (BPMN) Has its own notation with circles, rounded rectangles, and gateways that look different from traditional flowcharts.

For most business and educational purposes, the standard flowchart symbols will serve you well. If you're working within a specific framework like BPMN, check that team's conventions first.

What tools should I use to build flowcharts with proper symbols?

You don't need expensive software. Here are practical options:

Lucidchart Web-based, has built-in symbol libraries that follow standard conventions.
Draw.io (diagrams.net) Free, works in the browser, includes flowchart shape libraries.
Microsoft Visio Industry standard for Windows users, extensive shape stencils.
Google Slides or PowerPoint Simple shapes work for basic flowcharts if you use the right ones intentionally.
Paper and pen Seriously. Sketching a flowchart by hand helps you think through the logic before you commit to a digital version.

Whichever tool you use, look for a "flowchart" or "standard shapes" library in the shape menu. That gives you properly named and proportioned symbols rather than generic rectangles and circles.

Quick reference: flowchart shape cheat sheet

Oval → Start / End
Rectangle → Process / Action
Diamond → Decision / Branch
Parallelogram → Input / Output
Rounded rectangle → Predefined process / Subprocess
Arrow → Flow direction
Small circle → Connector (off-page or on-page)
Document shape → Document output
Cylinder → Database / Storage

For a full overview of how all these symbols work together, see our article on flowchart symbol shapes and their uses.

Practical next step

Take a process you know well something like your morning routine, a customer support ticket workflow, or a recipe. Sketch it out using only these four shapes: oval for start/end, rectangle for actions, diamond for decisions, and arrows for flow. This simple exercise builds the habit of matching shapes to meaning. Once that feels natural, layer in the specialized shapes for input, output, documents, and connectors as needed. You'll find the full reference at the Wikipedia article on flowcharts if you want to explore the history and formal standards further.