All posts
Allen
Author, Content Operations Manager·Originally published Feb 20, 2026 · Updated Oct 31, 2026
Data flow diagram with a Customer entity sending order details to a Take order process that writes to an Orders data store and sends a pick list to a Warehouse

Data Flow Diagram Maker: 10 Free DFD Tools Compared (2026)

A data flow diagram maker is any tool that lets you draw processes, external entities, data stores and labelled data flows, then share or export the result. For a free, no-account option, use draw.io. To generate a first draft from a text prompt, try Eraser. For a threat model, use OWASP Threat Dragon or the Microsoft Threat Modeling Tool. To keep the diagram next to the spec that explains it, use AFFiNE. The rest of this guide compares ten free tools, explains the symbols and levels, and walks through one complete example, including the mistakes we see most often and Mermaid code you can paste into any renderer.

How we compared these tools: We read each vendor's current pricing page and documentation on October 28, 2026, rechecked them on October 31, 2026, and drew one fictional online store as the shared example. The Mermaid example was rendered with Mermaid CLI 11.17.1. We did not run benchmarks or long-term trials. AFFiNE publishes this blog, so we apply the same criteria to it and list its limits.

Quick answer: which DFD maker fits your task?

If you need to...Start withWhyWatch out for
Draw a DFD for free with no accountdraw.ioFree, open source, web and desktop appsYou build DFD symbols from general shapes
Generate a first draft from a promptEraserDiagramGPT turns text into a DFDFree plan: 3 files and 3 AI credits
Threat-model a system with STRIDEOWASP Threat Dragon or Microsoft Threat Modeling ToolDFD elements with trust boundaries and threat listsBuilt for security reviews, not general diagrams
Use polished templates with a teamLucidchart or CreatelyDFD shape libraries and templatesFree plans cap documents or shapes
Make a quick, presentable diagramCanvaWhiteboard templates and easy stylingNo DFD rules or numbering
Keep the DFD next to specs and decisionsAFFiNEWhiteboard and documents in one workspaceNo DFD-specific shapes or validation

Free data flow diagram makers compared

"Free" means a plan you can keep using without paying, not a trial. Details checked against each vendor's pages on October 28, 2026 and rechecked on October 31, 2026.

ToolFree plan limit worth knowingAI generationGood for
draw.ioNo account; free web and desktop appsYes (Generate tool; prompts go to third-party AI models)General DFDs, offline work
Eraser3 files, 3 AI creditsYes (DiagramGPT)Developer teams who want a prompt-to-diagram draft
Lucidchart3 editable documents, 75 shapes eachLucid AI on the free planTeams already using Lucid
Creately45 shapes per diagramAI tools on all plansTemplates and visual workspaces
Miro3 editable boardsYes; the free plan includes AI diagram generation, paid plans add monthly AI creditsWorkshops that start on a whiteboard
CanvaFree plan with limited AI usesGeneral AI toolsPresentation-ready visuals
Visual Paradigm OnlineFree edition is for non-commercial use; exports carry a watermark40+ AI apps on the free plan; the dedicated AI diagram chatbot is on the Deluxe planStudents and classic Yourdon/Gane-Sarson shape sets
OWASP Threat DragonFree and open sourceNoThreat models built on DFDs
Microsoft Threat Modeling ToolFree Windows downloadNoSTRIDE-per-element security reviews
AFFiNELocal use free; free cloud: 10 GB, 3 members per workspaceAFFiNE AI is a paid add-onDFD plus written spec in one place

SmartDraw also includes DFD templates, but it offers a trial rather than a permanent free plan. If you are replacing a desktop diagramming suite, these Microsoft Visio alternatives cover the wider category.

Which one would we pick?

  • One-off DFD for a class or a design doc: draw.io. It has no account wall, and the files are plain XML you can keep in Git.
  • Many DFDs that a team maintains: Lucidchart or Creately. Their DFD shape libraries save time, but count the free-plan caps before you build a whole set of levels.
  • A draft from a written spec: Eraser or draw.io's Generate tool. Then check the draft against the rules below. The AI gives you a starting point, not a finished diagram.
  • Security review: OWASP Threat Dragon (cross-platform) or the Microsoft Threat Modeling Tool (Windows). Both turn DFD elements into a threat list.
  • The DFD has to live with the spec, data dictionary and decisions: AFFiNE, accepting that you draw the shapes yourself.

Data flow diagram symbols in Gane-Sarson and Yourdon-DeMarco notation: process, external entity, data store and labelled data flow

Data flow diagram symbols

Every DFD uses four elements. Only the shapes change between notations.

ElementGane-SarsonYourdon-DeMarcoRule of thumb
ProcessRounded rectangle with an ID bandCircleName it verb + noun, such as "Take payment"
External entityRectangleRectangleA person, team or system outside your boundary
Data storeOpen rectangle with an ID such as D1Two parallel linesData at rest, such as a table or file
Data flowLabelled arrowLabelled arrowName it with a noun, such as "Order details"

Gane-Sarson is common in business and information systems analysis; Yourdon-DeMarco circles are common in textbooks. Pick one and use it across every level.

Data flow diagram levels, with one example

The example below is a fictional online store called BookNook. Each level zooms in on the one above it.

Level 0: the context diagram

Level 0 shows the whole system as a single process and the external entities it exchanges data with. It sets the scope. There are no data stores at this level.

Level 0 context data flow diagram for a fictional online store: Customer, Payment provider and Warehouse exchange order, payment and shipment data with one BookNook order system process

If you only need the boundary, a system context diagram covers the same view with more detail on actors.

Level 1: the main processes

Level 1 splits the single process into the system's main functions and adds the data stores they share. In the example, order taking, payment, fulfilment and notification each become a numbered process, with Orders (D1) and Inventory (D2) as stores.

Level 1 data flow diagram for a fictional online store with four numbered processes, Orders and Inventory data stores, and flows to Customer, Payment provider and Warehouse

Level 2 and below

Split a Level 1 process again only when it is still too complex to describe in a few sentences. Number children after their parent: process 2.0 becomes 2.1, 2.2 and 2.3. Most systems are clear at Level 2.

A useful stopping test: if a process can be described in about five lines of plain text or pseudocode, stop splitting it. Going deeper usually turns a DFD into a flowchart.

Logical vs. physical data flow diagrams

A logical DFD describes what the business does with data, using technology-free names such as "Take order" and "Orders". A physical DFD shows how the same flow is built: the actual systems, protocols and tables.

Logical and physical data flow diagrams for the same fictional order flow: Customer, Take order, Orders store and Payment provider on the left; Web browser, Checkout API, Postgres orders table and Stripe API on the right

Logical DFDPhysical DFD
AnswersWhat happens to the data?Which system, file or table handles it?
Names"Take order", "Orders""Checkout API", "Postgres: orders"
Flow labelsBusiness data ("Order details")Transport and format ("HTTPS POST /orders")
Best forScope, requirements, stakeholder reviewsBuild, migration and security work

Draw the logical version first. It changes less often and is easier for non-engineers to review. Add the physical version when you need to show vendors, protocols or where personal data is stored.

Rules that keep a DFD correct

  • Balance every level. The flows into and out of a parent process must appear on its child diagram. In the example, every Level 0 flow (order details, order confirmation, payment request, payment result, pick list, shipment status) appears again at Level 1.
  • No black holes or miracles. A process with inputs but no outputs is a black hole; one with outputs but no inputs is a miracle. Both are errors.
  • Data moves through a process. An entity cannot write straight to a data store, and two stores cannot exchange data without a process between them.
  • No decisions or timing. Diamonds and "if/then" belong in a flowchart. A DFD shows what data moves, not when.
  • Label every flow with a noun. "Data" or "Info" is not a label. If you cannot name the data, you do not yet understand the flow.

Common DFD mistakes, before and after

The left panel below breaks three of these rules. The right panel shows the same data drawn correctly.

Before-and-after data flow diagram: on the left a Customer writes straight to an Orders store, a Check stock process has an input but no output, and a Send receipt process has an output but no input; on the right each flow passes through a process

MistakeHow to spot itFix
Entity writes straight to a storeAn arrow joins a rectangle to a data store with no process between themAdd the process that validates and writes the data, such as "Take order"
Black holeA process has arrows in but none outAdd the output it produces, or delete the process
MiracleA process has arrows out but none inAdd the input it reads, such as the paid order from D1
Unbalanced levelsA Level 1 diagram has a new external flow that is missing from Level 0Add the flow to the parent, or remove it from the child

Data flow diagram vs. flowchart vs. UML

Data flow diagramFlowchart or BPMNUML (activity, sequence)
ShowsWhat data moves and where it is storedThe order of steps and decisionsBehaviour and messages between objects or services
DecisionsNoneDiamond decision symbolsGuards and fragments (alt, loop)
StorageExplicit data storesRarely shownUsually not shown; use a class or ER diagram
Time orderNot shownTop to bottomExplicit on a sequence diagram
StructureLevels (0, 1, 2)Usually one flat diagramMany diagram types, one model

Use a DFD when the question is "where does this data go?". Use a flowchart or a BPMN diagram when the question is "what happens next, and who decides?". For step-by-step logic, see these free online flowchart makers, or compare process mapping tools for operations work. For the order of calls between services, use a UML sequence diagram or start from the sequence diagram template.

Using a DFD for threat modeling

Security teams often start a threat model from a DFD. Draw a trust boundary wherever data crosses from one level of trust to another, such as from the internet into your API or from your service to a payment provider. Then walk each element through STRIDE: spoofing, tampering, repudiation, information disclosure, denial of service and elevation of privilege. The Microsoft Threat Modeling Tool documents this as STRIDE per element, and OWASP Threat Dragon follows the same idea.

Here is the BookNook Level 1 diagram with its trust boundary drawn in. Every arrow that crosses the dashed line is a place to ask the STRIDE questions.

Level 1 data flow diagram of a fictional online store with a dashed trust boundary around its processes and data stores, and four STRIDE examples: spoofing on order details, tampering on payment results, information disclosure on the Orders store and repudiation on shipment status

Element or flowSTRIDE threatExampleMitigation
Order details (Customer to 1.0)SpoofingSomeone places orders as another customerRequire sign-in; rate-limit checkout
Payment result (provider to 2.0)TamperingA forged "paid" webhookVerify the provider's webhook signature
D1 OrdersInformation disclosureAddresses and emails leak from the tableEncrypt at rest; least-privilege access
Shipment status (Warehouse to 3.0)RepudiationThe warehouse disputes that it shippedSigned, append-only status log

The same diagram helps privacy reviews: it shows where personal data is collected, stored and sent to third parties. A threat model is itself sensitive, because it lists your weak points. Store it where you control access. AFFiNE can run locally or be self-hosted, and these whiteboard security practices apply to any tool you choose.

Can AI generate a data flow diagram?

Yes. Eraser's DiagramGPT, Lucid AI, Creately's AI tools and Miro AI can draft a diagram from a text description. Eraser recommends describing the processes, data stores, external entities and the data passed on each connection in your prompt.

Treat the output as a draft. Check that it follows the rules above: AI drafts often include decision diamonds, unlabelled arrows, or flows straight from an entity to a database.

A prompt and Mermaid code you can reuse

If your tool has no DFD generator, ask any chatbot for Mermaid code and paste it into a Mermaid renderer. This prompt follows Eraser's advice to name processes, stores, entities and the data on each connection:

Write Mermaid flowchart code for a Level 0 data flow diagram. System: "BookNook order system" (one process, drawn as a circle, numbered 0). External entities, drawn as rectangles: Customer, Payment provider, Warehouse. Flows: Customer sends Order details and receives Order confirmation; the system sends a Payment request and receives a Payment result; the system sends a Pick list to Warehouse and receives Shipment status. Label every arrow with the data. No decisions, no data stores.

Here is the BookNook context diagram as Mermaid code. We checked that it renders with Mermaid CLI 11.17.1:

flowchart LR
  customer[Customer]
  payment[Payment provider]
  warehouse[Warehouse]
  system(("0 BookNook order system"))

  customer -- Order details --> system
  system -- Order confirmation --> customer
  system -- Payment request --> payment
  payment -- Payment result --> system
  system -- Pick list --> warehouse
  warehouse -- Shipment status --> system

Mermaid has no dedicated DFD diagram type, so this uses flowchart syntax in Yourdon style: a circle for the process and rectangles for entities. Before you share an AI or Mermaid draft, check four things:

  1. Every arrow has a noun label.
  2. There are no diamonds or "yes/no" branches.
  3. No entity connects directly to a data store.
  4. Each Level 0 flow still appears on the Level 1 diagram.

How to make a data flow diagram in AFFiNE

AFFiNE is not a dedicated DFD tool. It has no DFD-specific shapes or rule checks. It suits teams who want the diagram and the written spec in the same place.

  1. Open the data flow diagram template or a blank Edgeless canvas on the AFFiNE whiteboard.
  2. Draw the Level 0 diagram first: one process, your external entities and labelled flows.
  3. Add a frame for Level 1, number each process, and add data stores as shapes labelled D1, D2 and so on.
  4. Write a data dictionary next to the diagram that lists every flow and its fields (example below).
  5. When the data model is ready, design the stores with an ER diagram tool or the ERD template, and show the processing stages with a pipeline diagram.

A data dictionary for BookNook starts like this:

FlowFromToFields
Order detailsCustomer1.0 Take ordercustomer_id, items[], shipping_address
Payment request2.0 Take paymentPayment providerorder_id, amount, currency
Pick list3.0 Fulfil orderWarehouseorder_id, sku[], quantity[]
Shipment statusWarehouse3.0 Fulfil orderorder_id, carrier, tracking_number, status

To show the services and infrastructure that carry these flows, pair the DFD with a software architecture diagram. More starting points are in the UML, flowchart and architecture diagram templates.

Frequently asked questions

What is the best free data flow diagram maker?

For general use, draw.io is free, needs no account and runs offline. Its Generate tool can also draft a diagram from a prompt. For a prompt-to-diagram draft, Eraser's free plan includes a few AI credits. For security work, OWASP Threat Dragon and the Microsoft Threat Modeling Tool are free and built around DFDs.

What are the four symbols of a data flow diagram?

Process, external entity, data store and data flow. Gane-Sarson draws processes as rounded rectangles; Yourdon-DeMarco draws them as circles.

What is the difference between a Level 0 and a Level 1 DFD?

Level 0 shows the whole system as one process with its external entities. Level 1 splits that process into the main sub-processes and adds data stores.

Can a DFD show decisions?

No. Decisions and sequence belong in a flowchart or sequence diagram. A DFD only shows how data moves and where it rests.

What is balancing in a DFD?

Balancing means the inputs and outputs of a parent process match the flows on its child diagram, so no data appears or disappears between levels.

What is the difference between a logical and a physical DFD?

A logical DFD names business activities and data, such as "Take order" and "Orders". A physical DFD names the systems that do the work, such as "Checkout API" and "Postgres: orders". Draw the logical version first.

How detailed should a data flow diagram be?

Stop splitting a process when you can describe it in about five lines of plain text. Most systems need Level 0 and Level 1; complex processes may need Level 2.

What are the most common DFD mistakes?

An entity writing straight to a data store, black holes (inputs with no output), miracles (outputs with no input), unlabelled arrows, and decision diamonds. Each one is shown, with a fix, in the before-and-after example above.

Can ChatGPT make a data flow diagram?

A chatbot can describe a DFD or write diagram code, such as Mermaid, that another tool renders. The prompt and code in this guide show the pattern. For an editable diagram, use a tool with built-in AI generation and check the result against the DFD rules.

Start with the free template

Open the free data flow diagram template in AFFiNE or download AFFiNE to keep your DFD, data dictionary and decisions in one workspace.

Update note (October 31, 2026): We added Visual Paradigm Online, confirmed draw.io's Generate tool, corrected Miro's free-plan AI entry after rechecking every pricing page, and added logical vs. physical DFDs, a before-and-after mistakes diagram, a trust-boundary STRIDE example, a reusable Mermaid prompt and code, and a sample data dictionary.

Update note (October 28, 2026): This article was first published in February 2026 and rewritten in October 2026 to compare free DFD tools. We checked free-plan limits on official pages, added original Level 0, Level 1 and symbol diagrams, added threat-modeling and AI sections, and removed unrelated links. AI tools assisted with drafting, and the content was reviewed and edited by the AFFiNE team.