Export network maps and diagrams
You can download any network map, documented diagram, or rack as a file, to send to a client, attach to a ticket or an audit, or keep editing in another tool. Exports are drawn with your map style and carry its drawing sheet: the title block, the legend, and, for documented diagrams, the revision table.
Before you begin
Section titled “Before you begin”- You need
discovery:read. - An export uses the whole map for the view and filters you chose under View, Site, Network, and VLAN. Narrow the drawing does not apply to exports.
Export the live map
Section titled “Export the live map”- On Endpoints > Network map, choose the View and filters you want.
- Select Export.
- Choose a format:
- Under This view, any of the eight formats in the table below.
- Under Every view, one page each, draw.io, L1 to L3 (.drawio), Visio, L1 to L3 (.vsdx), or PDF drawing set (.pdf). Each holds the Physical (L1), Data link (L2), and Network (L3) views as separate pages.
The file is named for the client and the date, such as
network-acme-2026-10-23.drawio.
Export a documented diagram or a rack
Section titled “Export a documented diagram or a rack”- A documented diagram. Open it from the Diagrams tab and select Export: draw.io (.drawio), Image (.png), Vector image (.svg), Visio (.vsdx), or PDF (.pdf). The export is the current revision.
- A rack. Open it from Racks on the Diagrams tab and select Export: draw.io (.drawio), Image (.png), Vector image (.svg), or Visio (.vsdx). Racks have no PDF export.
- A Pioneer AI drawing. Select Download on its card. It offers the same eight formats as the live map.
Formats
Section titled “Formats”| Menu label | Opens in | What it keeps |
|---|---|---|
| draw.io (.drawio) | draw.io, and the Outpost diagram editor | Everything. The layout and routes as drawn, link styles, and each device’s and link’s details as shape data. Outpost reads it back with its links to devices intact, so it is the best format to edit and upload again. |
| Visio (.vsdx) | Microsoft Visio, and draw.io | Devices as shapes with Shape Data for IP address, MAC address, vendor, model, serial number, and VLAN. Sites, subnets, and VLANs as containers. Links as connectors glued to both devices, with their color, weight, and line pattern. Layers for devices, links, labels, and the sheet. From a documented diagram, draw.io library shapes become labeled rectangles. |
| PDF (.pdf) | Any PDF reader | A picture of the drawing on the paper size and orientation in your map style, one page per view. The drawing is an image at twice screen resolution, so its text cannot be selected or searched. |
| Image (.png) | Any image viewer, and draw.io | A picture at twice screen resolution, up to 8,000 pixels a side, on a white background. It carries the .drawio drawing inside it, so draw.io opens it as an editable diagram. |
| Vector image (.svg) | A browser or vector editor, and draw.io | A drawing that scales without blurring, drawn as the console draws the map. Like the PNG, it carries the .drawio drawing, so draw.io opens it as an editable diagram. |
| yEd GraphML (.graphml) | yEd and other GraphML tools | Devices, groups, and links at their positions, with every detail Outpost knows as data on each one. |
| Mermaid (.mmd) | Anything that renders Mermaid, such as a Markdown editor or a wiki | A flowchart in text, with a subgraph for each group. The tool that renders it does its own layout. |
| D2 (.d2) | The D2 tools | A diagram in text, with groups, colors, and line styles. D2 does its own layout. |
PNG, SVG, and PDF exports of a documented diagram are the pictures saved with its revision. A revision without one, such as an uploaded .drawio file or one made by accepting proposals, cannot be exported in those formats until you open it in the editor and save it. The .drawio and .vsdx exports always work.
Export with the API
Section titled “Export with the API”The same exports are available from the API, with format set to drawio,
vsdx, pdf, png, svg, graphml, mermaid, d2, or json:
| Export | Request |
|---|---|
| The live map | GET /api/v1/topology/export?format=<format>&view=<view>, with view one of l1, l2, or l3, or left out for the combined map. Add pages=l1,l2,l3 for every view, one page each. |
| A daily snapshot | GET /api/v1/topology/snapshots/<snapshot-id>/export?format=<format> |
| A documented diagram | GET /api/v1/network-diagrams/<diagram-id>/export?format=<format>, with revision=<number> for an earlier revision. |
| A rack | GET /api/v1/racks/<rack-id>/export?format=<format> |
On the MSP plan, prefix each path with /api/v1/clients/<client-id> in place
of /api/v1. The json format, for the live map and snapshots only, is the
map’s data as Outpost builds it. See API.
If something goes wrong
Section titled “If something goes wrong”| Message | Fix |
|---|---|
| An export is in progress | Wait for the current export to finish. |
| The map has not loaded | Wait for the map to load, or select Refresh. |
| A PNG, SVG, or PDF export of a diagram fails | The revision has no picture. Open it in the editor and select Save. |
Next steps
Section titled “Next steps”Content is licensed CC BY 4.0. Code samples are MIT. Outpost and the Outpost mark are trademarks of Outpost Business Solutions, PBC and are not covered by either license.