
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.
| If you need to... | Start with | Why | Watch out for |
|---|---|---|---|
| Draw a DFD for free with no account | draw.io | Free, open source, web and desktop apps | You build DFD symbols from general shapes |
| Generate a first draft from a prompt | Eraser | DiagramGPT turns text into a DFD | Free plan: 3 files and 3 AI credits |
| Threat-model a system with STRIDE | OWASP Threat Dragon or Microsoft Threat Modeling Tool | DFD elements with trust boundaries and threat lists | Built for security reviews, not general diagrams |
| Use polished templates with a team | Lucidchart or Creately | DFD shape libraries and templates | Free plans cap documents or shapes |
| Make a quick, presentable diagram | Canva | Whiteboard templates and easy styling | No DFD rules or numbering |
| Keep the DFD next to specs and decisions | AFFiNE | Whiteboard and documents in one workspace | No DFD-specific shapes or validation |
"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.
| Tool | Free plan limit worth knowing | AI generation | Good for |
|---|---|---|---|
| draw.io | No account; free web and desktop apps | Yes (Generate tool; prompts go to third-party AI models) | General DFDs, offline work |
| Eraser | 3 files, 3 AI credits | Yes (DiagramGPT) | Developer teams who want a prompt-to-diagram draft |
| Lucidchart | 3 editable documents, 75 shapes each | Lucid AI on the free plan | Teams already using Lucid |
| Creately | 45 shapes per diagram | AI tools on all plans | Templates and visual workspaces |
| Miro | 3 editable boards | Yes; the free plan includes AI diagram generation, paid plans add monthly AI credits | Workshops that start on a whiteboard |
| Canva | Free plan with limited AI uses | General AI tools | Presentation-ready visuals |
| Visual Paradigm Online | Free edition is for non-commercial use; exports carry a watermark | 40+ AI apps on the free plan; the dedicated AI diagram chatbot is on the Deluxe plan | Students and classic Yourdon/Gane-Sarson shape sets |
| OWASP Threat Dragon | Free and open source | No | Threat models built on DFDs |
| Microsoft Threat Modeling Tool | Free Windows download | No | STRIDE-per-element security reviews |
| AFFiNE | Local use free; free cloud: 10 GB, 3 members per workspace | AFFiNE AI is a paid add-on | DFD 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.

Every DFD uses four elements. Only the shapes change between notations.
| Element | Gane-Sarson | Yourdon-DeMarco | Rule of thumb |
|---|---|---|---|
| Process | Rounded rectangle with an ID band | Circle | Name it verb + noun, such as "Take payment" |
| External entity | Rectangle | Rectangle | A person, team or system outside your boundary |
| Data store | Open rectangle with an ID such as D1 | Two parallel lines | Data at rest, such as a table or file |
| Data flow | Labelled arrow | Labelled arrow | Name 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.
The example below is a fictional online store called BookNook. Each level zooms in on the one above it.
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.

If you only need the boundary, a system context diagram covers the same view with more detail on actors.
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.

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.
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 DFD | Physical DFD | |
|---|---|---|
| Answers | What happens to the data? | Which system, file or table handles it? |
| Names | "Take order", "Orders" | "Checkout API", "Postgres: orders" |
| Flow labels | Business data ("Order details") | Transport and format ("HTTPS POST /orders") |
| Best for | Scope, requirements, stakeholder reviews | Build, 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.
The left panel below breaks three of these rules. The right panel shows the same data drawn correctly.

| Mistake | How to spot it | Fix |
|---|---|---|
| Entity writes straight to a store | An arrow joins a rectangle to a data store with no process between them | Add the process that validates and writes the data, such as "Take order" |
| Black hole | A process has arrows in but none out | Add the output it produces, or delete the process |
| Miracle | A process has arrows out but none in | Add the input it reads, such as the paid order from D1 |
| Unbalanced levels | A Level 1 diagram has a new external flow that is missing from Level 0 | Add the flow to the parent, or remove it from the child |
| Data flow diagram | Flowchart or BPMN | UML (activity, sequence) | |
|---|---|---|---|
| Shows | What data moves and where it is stored | The order of steps and decisions | Behaviour and messages between objects or services |
| Decisions | None | Diamond decision symbols | Guards and fragments (alt, loop) |
| Storage | Explicit data stores | Rarely shown | Usually not shown; use a class or ER diagram |
| Time order | Not shown | Top to bottom | Explicit on a sequence diagram |
| Structure | Levels (0, 1, 2) | Usually one flat diagram | Many 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.
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.

| Element or flow | STRIDE threat | Example | Mitigation |
|---|---|---|---|
| Order details (Customer to 1.0) | Spoofing | Someone places orders as another customer | Require sign-in; rate-limit checkout |
| Payment result (provider to 2.0) | Tampering | A forged "paid" webhook | Verify the provider's webhook signature |
| D1 Orders | Information disclosure | Addresses and emails leak from the table | Encrypt at rest; least-privilege access |
| Shipment status (Warehouse to 3.0) | Repudiation | The warehouse disputes that it shipped | Signed, 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.
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.
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:
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.
A data dictionary for BookNook starts like this:
| Flow | From | To | Fields |
|---|---|---|---|
| Order details | Customer | 1.0 Take order | customer_id, items[], shipping_address |
| Payment request | 2.0 Take payment | Payment provider | order_id, amount, currency |
| Pick list | 3.0 Fulfil order | Warehouse | order_id, sku[], quantity[] |
| Shipment status | Warehouse | 3.0 Fulfil order | order_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.
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.
Process, external entity, data store and data flow. Gane-Sarson draws processes as rounded rectangles; Yourdon-DeMarco draws them as circles.
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.
No. Decisions and sequence belong in a flowchart or sequence diagram. A DFD only shows how data moves and where it rests.
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.
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.
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.
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.
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.
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.