How to Import draw.io (.drawio) Files

The .drawio format is one of the most common ways diagrams are saved and shared, so being able to import a .drawio file is a basic test of whether a diagramming tool respects your existing work. A good import brings the whole diagram across - shapes in their positions, connectors and their endpoints, labels, colors, and styles - so you continue editing rather than rebuilding. A poor import loses connections, mangles styles, or flattens the diagram to an image, which defeats the point of importing at all.

This guide covers how .drawio import works, what carries over cleanly, what to check after importing, and how to keep round-trip editing lossless if you move between tools. The reference tool is Atlas Diagram Studio at /diagrams, which imports both .drawio and Mermaid, offers 1000-plus shapes, and exports back to .drawio along with PNG, SVG, PDF, PPTX, JSON, and Mermaid. Because .drawio is an editable, structured format, importing it should give you a live diagram you can immediately change, not a picture of one.

What the .drawio format contains

A .drawio file is not an image; it is a structured document describing the diagram. Under the hood it is XML that lists every shape with its position and size, every connector with its source and target and routing, and the styles applied to each - fill color, stroke, font, and so on. This is exactly why importing it can be lossless: the source already contains all the information needed to reconstruct the diagram as real, editable elements. There is nothing to guess, unlike converting from a flat image, where a tool must infer structure from pixels.

Because the format is structured, a good importer reads that XML and rebuilds the diagram natively: your boxes become the tool's boxes, your arrows become its connectors, your pages become its pages. The fidelity depends on how well the two tools' shape libraries and style models line up. Standard shapes and connections map almost perfectly across tools; the edges of fidelity are highly tool-specific custom shapes or effects that the target tool may not have an exact match for. Knowing this tells you where to look when you check an import.

Importing step by step

Importing a .drawio file is usually a matter of opening or importing the file and letting the tool parse it. The steps below keep the process smooth and make problems easy to catch early.

• Locate the .drawio file itself, not a PNG or PDF export of it, since only the source file carries the editable structure.
• Use the tool's open or import command and select the .drawio file; a structured importer reads the XML directly.
• If the diagram has multiple pages, confirm all pages came across, not just the first.
• Check connectors first - verify they still attach to the right shapes, since endpoints are the most common thing to review.
• Scan for custom or specialized shapes that may have been substituted, and swap in the target tool's equivalent if needed.
• Spot-check styling - colors, fonts, and line styles - and reapply anything that did not map exactly.
• Save in the new tool's native format once satisfied, keeping the original .drawio as a backup until you have verified the result.

What to check after import

Most of a .drawio import comes across cleanly, so your review can focus on the few things most likely to shift. Connectors top the list: confirm each line still connects the shapes it should and points the right direction, because endpoint mapping is where structured imports most often need a nudge. Next, look at any non-standard shapes - a tool-specific stencil may have been replaced with a generic equivalent, which is easy to swap but easy to miss. Finally, glance over styling for colors or fonts that did not translate perfectly.

The goal of the check is not suspicion but a quick pass to catch the predictable edges, after which you have a fully editable diagram in the new tool. Because Atlas Diagram Studio imports .drawio into the same editor as any native diagram at /diagrams, once imported the diagram behaves like any other: you can restyle it, extend it, collaborate on it, and export it. If the source was authored as Mermaid rather than .drawio, the Mermaid editor at /diagram-tools/mermaid-editor and the diagram-as-code guide at /guides/diagram-as-code-guide cover that path.

Keeping round-trips lossless

If you move between tools regularly, you want round-tripping to lose as little as possible each way. The reliable strategy is to stay on standard shapes and common styling, which map cleanly in both directions, and to avoid leaning on one tool's exotic, proprietary features when you know the diagram will travel. A diagram built from widely supported shapes and plain connectors survives a round trip almost perfectly; one built from a single tool's unique effects will degrade at the boundary.

The other half is exporting back out in a structured format rather than an image. Because Atlas Diagram Studio exports to .drawio as well as importing it, you can bring a diagram in, edit it, and send it back out as .drawio for someone else's tool, keeping the whole chain editable. When you need the diagram as a fixed picture instead - for a slide or a doc - export to PNG, SVG, or PDF, but keep a structured copy as the source of truth. The export guide at /guides/how-to-export-diagrams-to-png-svg-pdf covers those format trade-offs, and the broader interoperability story lives across the tools at /diagram-tools.