Skip to main content

Document library

OfficeIMO.Visio

Create Visio diagrams with builders, stencils, graph layouts, shapes, connectors, and pages. No Visio installation required.

MIT licensed No Office required Cross-platform .NET
Install dotnet add package OfficeIMO.Visio
Generated output · OfficeIMO.Visio
GENERATED OUTPUT

Ready for your workflow

Build, inspect, and transform documents through a focused API.

C#
using var document = CreateDocument();
document.Save();

Why OfficeIMO.Visio?

OfficeIMO.Visio lets you generate and modify .vsdx diagrams from pure .NET code. Build network topologies, org charts, flowcharts, timelines, swimlanes, dependency graphs, and architecture diagrams without requiring Visio on the machine. Builder APIs keep common diagrams concise, while lower-level pages, shapes, connectors, masters, and stencil catalogs remain available when you need precision.

Features

  • Create, load, and save VSDX files — round-trip the Visio Open XML format
  • Diagram builders — create flowcharts, architecture diagrams, networks, dependencies, swimlanes, org charts, timelines, sequences, and generic graphs
  • Stencils and catalogs — use generated catalogs, installed Visio stencils, or external .vssx and .vstx packs while retaining caller-supplied license, attribution, and unsupported-master state
  • Connectors with metadata — connect shapes with labels, hyperlinks, Shape Data, waypoints, and routing hints
  • Fluent and low-level APIs — chain common diagrams or edit individual pages, shapes, connectors, and masters
  • Headless image export — render SVG, PNG, JPEG, TIFF, and WebP previews without Microsoft Visio
  • Validation — inspect generated and loaded diagrams for package, model, overlap, routing, and connector-label issues

Diagram types you can automate

Diagram typeTypical source dataOutcome
Infrastructure topologyInventory exports, deployment metadata, cloud resourcesRepeatable architecture diagrams that stay in sync with real systems
Process and approval flowsWorkflow definitions, queue stages, or policy stepsClear step-by-step diagrams for operations and compliance teams
Org and service mapsHR systems, ownership registries, service catalogsDiagrams that show teams, responsibilities, and platform boundaries
Release and runbook visualsCI pipelines, deployment targets, or support proceduresSupporting diagrams that travel with Word reports and PowerPoint decks

Where Visio fits in the suite

Pair it withUse the combination for
OfficeIMO.WordArchitecture reports, runbooks, and handoff documents that include generated diagrams.
OfficeIMO.PowerPointStakeholder decks where the same topology or workflow data becomes presentation material.
OfficeIMO.CSVInventory-driven diagrams where nodes, owners, environments, or dependencies start in flat files.
OfficeIMO.ReaderIndexing generated diagram metadata alongside related documents for search or review workflows.

Quick start

using OfficeIMO.Visio;
using OfficeIMO.Visio.Diagrams;

VisioDocument.Create("Architecture.vsdx")
    .ArchitectureDiagram("System Overview", diagram => diagram
        .Title()
        .Legend()
        .Theme(VisioStyleTheme.Technical())
        .Region("vnet", "Virtual Network", 1, 0, 3, 2)
        .Actor("users", "Users", 0, 1)
        .Gateway("gateway", "Gateway", 1, 1)
        .Service("api", "API", 2, 1)
        .Database("database", "Database", 3, 1)
        .DataFlow("users", "gateway", "HTTPS")
        .ControlFlow("gateway", "api", "route")
        .DataFlow("api", "database", "SQL"))
    .Save();

Repeatable modeling flow

  1. Start from the system, process, or ownership data you already have instead of hand-placing every shape.
  2. Map each entity to a stable shape type, label, and color so regenerated diagrams stay easy to compare.
  3. Use connectors to represent traffic, dependency, or approval flow, then reserve shape text for the labels people need to scan quickly.
  4. Generate the .vsdx file as part of a report build, architecture export, or operational handoff package.
  5. Pair the diagram with OfficeIMO.Word or OfficeIMO.PowerPoint when the same workflow also needs narrative or presentation output.

Compatibility

Target FrameworkSupported
.NET 10.0Yes
.NET 8.0Yes
.NET Standard 2.0Yes
.NET Framework 4.7.2Yes

OfficeIMO.Visio runs on Windows, Linux, and macOS. Generated files open in Microsoft Visio and other VSDX-compatible viewers.

GuideDescription
Visio documentationChoose a creation, editing, stencil, validation, or image-export workflow.
Diagram buildersGenerate architecture, network, flow, sequence, timeline, and graph diagrams.
Editing and validationUpdate loaded VSDX files and validate the result.
Stencils and catalogsWork with generated, installed, and external stencil packs.
Image exportRender SVG, PNG, JPEG, TIFF, and WebP previews.
Visio API referenceBrowse diagram, shape, connector, and fluent builder types.
Getting StartedSet up the package and validate your first generated diagram.
OfficeIMO.WordPair diagrams with generated reports, architecture notes, or implementation docs.
OfficeIMO.PowerPointTurn the same topology or process data into stakeholder-ready slide decks.
DownloadsInstall the Visio package and compare it with the rest of the OfficeIMO family.

Next step

Turn the package into a working document.

Follow a focused guide, inspect the generated API reference, or try a browser-safe conversion.