Draw.io Review 2026

Key takeaways

• Completely free for the web app and desktop versions — no account, no credit card, no paywall for core features
• Open source under Apache 2.0, with the full codebase on GitHub (jgraph/drawio), so there's no vendor lock-in risk
• Privacy-first by design — your diagram data is stored wherever you choose (local disk, Google Drive, GitHub, OneDrive), and draw.io itself cannot access it
• Excellent integration coverage across Google Workspace, Microsoft 365, Atlassian Confluence/Jira, GitHub, VS Code, and Notion
• Not a Promptwatch competitor — this is a diagramming tool with no overlap in AI search visibility or GEO

Draw.io (also known as diagrams.net) is one of the most widely used diagramming tools in the world, with over 100 million users and a history stretching back to 2005. Built and maintained by JGraph Ltd., a small independent software company, it covers the full range of diagram types that technical and business teams need: flowcharts, UML diagrams, entity-relationship diagrams, network topology maps, org charts, BPMN process flows, and more. The core product is free, open source (Apache 2.0), and runs entirely in the browser without requiring an account.

The target audience is broad by design. Individual developers, architects, and engineers use it for technical documentation. Business analysts and product managers use it for process flows and wireframes. IT teams use it for network diagrams. What ties these users together is that they want a capable, no-nonsense diagramming tool that doesn't require a corporate procurement process or a monthly subscription to unlock basic features. Draw.io is the anti-Lucidchart in that sense: no artificial feature gating, no "upgrade to share" friction.

JGraph has been building this since 2005, which is genuinely unusual in a software market where tools get acquired, pivoted, or shut down constantly. The company is not VC-funded, which means it isn't optimizing for growth metrics at the expense of product quality or user privacy. That independence shows in the product decisions: SSO isn't locked behind an enterprise tier, the file format is open XML, and diagrams created two decades ago still open correctly today.

Key features

Browser-based editor with no account required

The web app at app.diagrams.net opens immediately without any sign-up. You pick where to save your file (local disk, Google Drive, OneDrive, GitHub, GitLab, Dropbox, or a device) and start diagramming. The editor is full-featured: drag-and-drop shape libraries, connection routing, multi-page diagrams, layers, custom styles, and a search-based shape picker. This zero-friction entry point is one of the biggest practical advantages over tools like Lucidchart or Miro, where the free tier is limited and the sign-up wall appears immediately.

Desktop application

Draw.io ships a cross-platform desktop app for Windows, macOS, and Linux, built on Electron. It works fully offline, which matters for teams in air-gapped environments or anyone who doesn't want their diagram data touching any cloud service. The desktop app is functionally identical to the web version, and files are interchangeable between the two.

Extensive shape libraries

The shape library covers a lot of ground:

• General shapes (flowchart, basic, arrows)
• Network and infrastructure (Cisco, AWS, Azure, GCP icon sets)
• UML (class diagrams, sequence diagrams, use case)
• BPMN 2.0 process notation
• Entity-relationship and database schema shapes
• Mockup/wireframe components
• Floorplan and technical drawing shapes

You can also import custom shape libraries in XML format, which is useful for teams that want to maintain consistent visual standards across diagrams.

Real-time collaboration

Draw.io supports shared cursors and simultaneous editing when files are stored in a supported cloud location (Google Drive, OneDrive, etc.). This is comparable to what Lucidchart and Miro offer, though draw.io's collaboration is mediated through the underlying storage platform rather than a proprietary sync layer. In practice, this means collaboration works well but requires everyone to have access to the same storage location.

Confluence and Jira integration

The Atlassian integration is one of draw.io's strongest selling points for enterprise teams. The draw.io app for Confluence (available on the Atlassian Marketplace) embeds diagrams directly in Confluence pages, with full editing capability inside the Confluence interface. Diagrams are stored as page attachments, so they follow Confluence's existing permission model. The Jira integration lets you attach diagrams to issues. For teams already living in Atlassian tools, this is significantly smoother than exporting PNGs and pasting them into pages.

GitHub and GitLab integration

Diagrams can be stored directly in Git repositories as .drawio XML files. The GitHub integration includes the ability to edit diagrams via github.dev (the browser-based VS Code environment), which means you can update architecture diagrams in the same workflow as code changes. This is genuinely useful for engineering teams that want diagrams to live alongside the code they document.

VS Code extension

The draw.io VS Code extension lets you open and edit .drawio files directly inside VS Code. For developers who spend most of their day in the editor, this removes the context switch of opening a browser tab. The extension renders diagrams in a panel and supports the full editor feature set.

Export and embed options

Diagrams export to SVG, PNG, PDF, HTML (as an interactive embedded viewer), and XML. The SVG export preserves editability metadata, so you can re-import an exported SVG back into draw.io. For embedding in documentation or web pages, draw.io provides an iframe-based viewer that renders diagrams interactively without requiring the viewer to have a draw.io account.

XML-based file format

The .drawio file format is plain XML, which means it's human-readable, version-control-friendly, and not dependent on draw.io's continued existence to open. This is a meaningful advantage over proprietary formats used by tools like Visio (.vsdx is technically open but practically opaque) or Lucidchart (cloud-only).

Who is it for

Draw.io fits best for individual contributors and small-to-medium teams who need capable diagramming without the overhead of an enterprise tool. A software engineer documenting a microservices architecture, a business analyst mapping out a customer journey, or a network engineer drawing a topology diagram are all natural users. The tool handles all of these use cases without requiring any configuration or licensing conversation.

For teams already using Confluence, draw.io is close to a default choice. The Confluence app is mature, widely deployed, and avoids the awkward workflow of maintaining diagrams as separate files that get out of sync with documentation. Engineering teams using GitHub for documentation (README files, architecture decision records, wikis) also benefit from the Git-native storage model.

The tool is less suited for teams that need advanced presentation-layer features, complex data-linked diagrams (where shapes update based on live data sources), or highly polished visual output for client-facing deliverables. Miro is better for collaborative whiteboarding and workshop facilitation. Lucidchart has stronger data linking and more polished templates. Figma is the right tool if the output needs to look like a designed artifact rather than a technical diagram.

Organizations with strict data residency requirements will find draw.io's storage model appealing: because diagrams are stored in your own cloud storage or on-premises systems, there's no third-party data processor to worry about. This matters in regulated industries like finance and healthcare where data governance is a real concern.

Integrations and ecosystem

Draw.io's integration story is one of its strongest points. Native integrations include:

• Google Workspace: Store and open diagrams from Google Drive; embed in Google Docs and Slides via the draw.io add-on
• Microsoft 365: Integration with SharePoint, OneDrive, and Teams; diagrams stored in OneDrive can be opened and edited collaboratively
• Atlassian: Confluence app (available on Marketplace) and Jira attachment support; widely used in enterprise Atlassian deployments
• GitHub and GitLab: Store .drawio files in repos; edit via github.dev or the VS Code extension
• VS Code: Full editor embedded in the IDE via the official extension
• Notion: Chrome extension for embedding draw.io diagrams in Notion pages
• Dropbox: File storage option in the web app

The GitHub repository (jgraph/drawio) is public and actively maintained. JGraph also maintains jgraph/drawio-desktop for the Electron app and jgraph/mxgraph, the underlying graph library. Developers can self-host the web application, embed the viewer in their own apps, or use the XML format to generate diagrams programmatically.

There's no official Zapier or Make integration, which limits automation possibilities for non-developers. The API surface is primarily the file format itself: if you can generate valid draw.io XML, you can create diagrams programmatically.

Pricing and value

Draw.io's pricing structure is unusual because the core product is free and open source. The paid tiers are primarily for the Confluence and Jira apps on the Atlassian Marketplace, which are priced per user per month based on the number of Confluence/Jira users.

• Web app and desktop app: Free, no account required, no feature limits
• Confluence app: Paid, priced through the Atlassian Marketplace. Pricing scales with the number of Confluence users; small teams (up to 10 users) pay around $10/month, with pricing increasing for larger deployments. The full pricing table is on the Atlassian Marketplace listing.
• Jira app: Similarly priced through the Marketplace

The web app has no premium tier -- every feature is available for free. This is a meaningful contrast to Lucidchart, which limits free users to 3 editable documents and restricts shape libraries, or Miro, which limits free users to 3 boards. Draw.io's free tier is the full product.

For teams evaluating draw.io against Lucidchart or Microsoft Visio, the cost comparison is stark. Lucidchart's Team plan runs around $9/user/month. Visio Plan 2 is around $15/user/month. Draw.io's web app is $0/user/month. Even the Confluence app pricing is competitive with what you'd pay for Lucidchart at scale.

Strengths and limitations

What draw.io does well:

• Zero cost for the core product. No other diagramming tool at this feature level is completely free without a sign-up wall or feature restrictions. This makes it genuinely accessible for individual contributors, open source projects, and small teams.
• Data privacy and storage flexibility. The model of storing diagrams in your own storage (Google Drive, GitHub, local disk) rather than on draw.io's servers is rare and valuable. Most SaaS diagramming tools hold your data on their infrastructure.
• Longevity and format stability. Files from 2005 still open correctly. The XML format is stable and human-readable. For teams that care about long-term accessibility of their documentation, this matters.
• Confluence integration quality. The draw.io Confluence app is one of the best-maintained third-party Confluence apps available. It's been around long enough to be considered a de facto standard for technical diagramming in Confluence.
• Open source with active maintenance. The Apache 2.0 license means you can self-host, fork, or build on top of draw.io without licensing concerns. The GitHub repo is actively maintained.

Honest limitations:

• Collaboration UX lags behind dedicated tools. Real-time collaboration works, but it's not as smooth as Miro or Figma. There's no built-in commenting system, no cursor presence indicators in the standalone web app (only when using shared cloud storage), and no facilitation features like voting or timers.
• Template library is functional but not beautiful. The built-in templates cover the technical bases but look dated compared to what Lucidchart or Miro offer. Teams that need polished, client-ready diagrams will spend more time on styling.
• No native data linking. Lucidchart's data linking feature lets shapes update based on spreadsheet or database data. Draw.io has no equivalent. For diagrams that need to reflect live data (org charts from HR systems, infrastructure maps from cloud APIs), you'd need to build custom tooling.
• Mobile experience is limited. The web app works on mobile browsers but isn't optimized for touch input. There's no dedicated mobile app.

Bottom line

Draw.io is the right choice for any team or individual that needs capable, full-featured diagramming without paying for it or compromising on data privacy. It's particularly strong for engineering teams using Confluence, GitHub, or VS Code as part of their documentation workflow. The Atlassian Marketplace app alone justifies the tool's reputation in enterprise environments.

If you need advanced collaboration features, polished templates, or live data linking, Lucidchart or Miro will serve you better -- but you'll pay for it. For the vast majority of technical diagramming use cases, draw.io is the most practical choice available.

Best for: Engineering and IT teams that need reliable, privacy-respecting diagramming integrated into their existing Confluence, GitHub, or Google Workspace environment.