Flowchart Symbols and Their Meanings: a Complete Visual Guide

If you've ever opened a flowchart template and stared at shapes you didn't recognize, you're not alone. Flowchart symbols have specific meanings, and using the wrong one can confuse your audience or break the logic of your diagram. Knowing what each flowchart symbol means helps you communicate processes clearly whether you're mapping out a business workflow, writing pseudocode for a program, or explaining a decision to your team.

Why do flowchart symbols have standardized meanings?

Flowcharts became a common tool in the 1920s and 1930s, and by the 1960s, organizations like ISO and ANSI had created standard symbol sets. The reason is simple: if everyone uses the same shapes with the same meanings, anyone can read the diagram without a legend. A rectangle always means a process. A diamond always means a decision. This consistency removes guesswork and makes flowcharts useful across industries and languages.

What does each basic flowchart symbol mean?

Here's a breakdown of the most common flowchart symbols you'll encounter, starting with the ones you'll use most often:

Oval (Terminator)

The oval (or rounded rectangle) marks the start or end of a process. Every flowchart needs at least one start oval and one end oval. Think of it as the entry and exit doors of your diagram.

Rectangle (Process)

This is the workhorse of any flowchart. The rectangle represents an action, task, or operation. When you see this shape, something is being done calculating a total, sending an email, updating a record. You'll use more rectangles than any other shape in most flowcharts.

Diamond (Decision)

The diamond asks a yes/no question or presents a condition with two (sometimes more) possible outcomes. From the diamond, paths branch in different directions depending on the answer. Common examples include "Is the order approved?" or "Is the balance greater than zero?"

Parallelogram (Input/Output)

This slanted rectangle represents data entering or leaving the system things like user input, displaying a result on screen, reading from a file, or printing a report. If data is moving in or out, use a parallelogram.

Arrow (Flow Line)

Arrows connect the shapes and show the direction of flow. They tell you which step comes next. Without arrows, a flowchart is just a collection of disconnected shapes. Always make sure arrows point in one clear direction to avoid confusion.

Circle (Connector)

A small circle is used to connect different parts of a flowchart when the diagram spans multiple pages or sections. You'll often see matching letters or numbers inside circles for example, an "A" in one circle links to an "A" in another. This avoids messy, crossing lines across a large diagram.

Rectangle with Double Vertical Lines (Predefined Process)

This looks like a regular rectangle but has extra vertical lines on each side. It means the process is defined elsewhere usually in another flowchart or a separate document. Use it when you're referencing a subroutine, a function, or a standard procedure without spelling out every step inside it.

Diamond with a Wavy Base or the Document Shape (Document)

This shape resembles a piece of paper with a wavy bottom edge. It represents a document or report that the process creates or reads. If your flowchart involves generating an invoice, signing a form, or reading a file, this is the shape to use.

Trapezoid (Manual Operation)

A trapezoid indicates a step done manually rather than by a computer. This matters in process mapping because manual steps often take more time and introduce more errors than automated ones.

Hexagon (Preparation / Initialization)

The hexagon is less common but shows up in some technical flowcharts to represent a setup or initialization step something that prepares the system before the main process runs.

For a deeper dive into how these shapes apply specifically in technical contexts, see our guide on flowchart shape meanings in software engineering.

What are the less common flowchart symbols?

Beyond the basics, you may see these shapes in more detailed diagrams:

Storage symbol (cylinder) represents a database or physical storage location
Display symbol (curved bottom rectangle) indicates output shown to a user, like on a screen
Merge symbol where multiple flow lines combine into one path
Sort symbol a rectangle with a triangle inside, meaning data is being sorted
Delay symbol (half-rounded rectangle) a waiting period in the process

Most people won't need all of these, but if you're creating detailed process maps or system documentation, knowing them helps. Our standard flowchart symbol reference guide covers these in more detail.

When would you actually need to know flowchart symbols?

You don't need to memorize every symbol to sketch a quick diagram on a whiteboard. But these situations benefit from using the correct shapes:

Writing documentation for your team or a client who expects professional diagrams
Programming and algorithm design, where instructors or reviewers expect standard notation
Business process mapping, especially in industries like finance, healthcare, or manufacturing where compliance documentation is required
Troubleshooting workflows, where a clear visual helps pinpoint where something goes wrong
Onboarding new team members who need to understand a procedure quickly

What happens if you use the wrong flowchart symbol?

Using a rectangle where you should use a diamond might seem minor, but it can cause real problems:

Confused readers If a decision point looks like a regular step, someone might skip over the branching logic entirely
Broken logic Misplaced symbols can make a flowchart impossible to follow or even contradictory
Miscommunication in teams A developer reading your flowchart might implement the wrong behavior if the diagram doesn't accurately show where decisions happen
Failed audits or reviews In regulated industries, inaccurate process documentation can lead to compliance issues

Do you need to memorize all the symbols?

No. Even experienced professionals keep a reference handy. What matters is:

You know the core five or six shapes (terminator, process, decision, input/output, arrow, connector)
You know where to look up the rest when you need them
You're consistent within a single diagram don't switch meanings halfway through

A quick reference like the one in our detailed flowchart symbol meanings guide can sit beside you while you work.

Common mistakes people make with flowchart shapes

Here are patterns I've seen repeatedly:

Mixing up diamonds and rectangles Anywhere there's a yes/no answer, it needs to be a diamond, not a rectangle
Forgetting start and end ovals Without terminators, readers don't know where the process begins or ends
Overusing connectors If your flowchart fits on one page, you probably don't need connector circles. Keep it simple.
Creating flowcharts that only you can read Test your diagram by showing it to someone unfamiliar with the process. If they can follow it, it's clear.
Ignoring flow direction Flowcharts should generally read top-to-bottom or left-to-right. Arrows that bounce around in every direction make diagrams hard to follow.

Tips for using flowchart symbols correctly

Start with the basic shapes and add complexity only when needed. A simple, correct flowchart beats a detailed, confusing one.
Label every decision diamond with a clear question, not a vague statement like "check status."
Keep one consistent direction of flow (top-to-bottom is most common).
Use color sparingly to group related steps not to replace proper shapes.
Save a template with the correct symbols so you're not starting from scratch every time.

What should you do next?

If you're building your first flowchart, start by drawing the five basic shapes on paper. Sketch the process from start to end, using ovals for the start/end points, rectangles for actions, diamonds for decisions, parallelograms for any input or output, and arrows to connect everything. Then compare your sketch against a reference to check for accuracy.

Quick checklist before you share any flowchart:

☐ Does it have a clear start (oval) and end (oval)?
☐ Are all decisions shown as diamonds with labeled questions?
☐ Are all actions/tasks shown as rectangles?
☐ Are input/output steps shown as parallelograms?
☐ Do all arrows point in a logical direction with no dead ends (unless it's a true end point)?
☐ Could someone unfamiliar with the process follow it without your explanation?

Get those six things right, and your flowchart will be clear, correct, and useful to anyone who reads it.