Network diagram, four tabs
- Input
- 238,720-byte .vsdx with Structural, Physical, Logical and Rack pages.
- Output
- 306,237-byte ZIP of four SVGs in 0.3 s after the PDF step; the rack page alone is about 1 MB uncompressed.
VSDX → SVG gives a diagram that stays sharp at any zoom in a web page or documentation site, at the price of labels that are shapes rather than text.
From real runs
| Element | Result | What happens |
|---|---|---|
| One SVG per page | Kept | The four-tab network diagram became a ZIP of four SVG files; each opens on its own in a browser, Inkscape or Illustrator. |
| Lines, connectors and fills | Kept | Connectors, box outlines and fills are SVG paths, so a 4K screen or a zoomed browser shows them as sharp as the original. |
| Labels | Changed | Text is converted to glyph outlines in the substitute font. It looks right everywhere without fonts installed, but you cannot select it or fix a typo in a text editor. |
| File size of dense pages | Changed | The rack elevation page, with hundreds of small slots, became a 997,297-byte SVG on its own; simple pages were 21,241 bytes. |
| Page background | Changed | Each SVG includes the white page rectangle, so it will not sit transparently on a dark-themed site without editing. |
| Visio shape data | Lost | Shape data fields, layers and hyperlinks are not written to the SVG; it carries geometry and colour only. |
The four-tab network diagram became a ZIP of four SVG files; each opens on its own in a browser, Inkscape or Illustrator.
Connectors, box outlines and fills are SVG paths, so a 4K screen or a zoomed browser shows them as sharp as the original.
Text is converted to glyph outlines in the substitute font. It looks right everywhere without fonts installed, but you cannot select it or fix a typo in a text editor.
The rack elevation page, with hundreds of small slots, became a 997,297-byte SVG on its own; simple pages were 21,241 bytes.
Each SVG includes the white page rectangle, so it will not sit transparently on a dark-themed site without editing.
Shape data fields, layers and hyperlinks are not written to the SVG; it carries geometry and colour only.
We converted our Microsoft Visio sample (233 KB) with Office engine → Image engine on 2026-10-20. It took 2.4 s and produced a 299 KB SVG file, 1.3× larger than the input. The engine raised 3 warnings, listed below.
Input · sample.vsdx · 233 KB
ZIP with 64 parts
Output · sample.zip · 299 KB
ZIP with 4 page images (sample-page-1.svg … sample-page-4.svg)
LibreOffice and PyMuPDF
soffice --headless --convert-to pdf map.vsdx && python -c "import fitz; d=fitz.open('map.pdf'); open('page1.svg','w').write(d[0].get_svg_image())"soffice can also write SVG directly, but for a multi-page drawing it packs every page into one file that most viewers show as overlapping pages.
The HTTP API and the MCP server run the exact engine this page uses (Office engine → Image engine); the response carries the same warnings the web converter shows. Check support first with GET /api/v1/pairs?from=vsdx&to=svg.
curl -X POST https://filetypeconverters.com/api/v1/convert \
-H "Authorization: Bearer $FTC_API_KEY" \
-F "file=@input.vsdx" -F "from=vsdx" -F "to=svg" \
-F 'options={"width":0}' \
--output output.svg| Key | Applies to | Type | Default |
|---|---|---|---|
| width | Writing SVG | number | 0 |
| height | Writing SVG | number | 0 |
| fit | Writing SVG | contain · cover · fill | contain |
| quality | Writing SVG | number | 90 |
| background | Writing SVG | string | #ffffff |
| stripMetadata | Writing SVG | boolean | true |
Not as text. Labels are converted to outlines so the SVG looks the same on machines without the fonts. Edit the label in Visio or draw.io and export again.
Pages with many small shapes, such as rack layouts or floor plans, turn into thousands of paths. Gzip on the web server shrinks them a lot; otherwise use PNG for that page.
No. Layers are flattened during conversion, and shapes on layers set not to print are left out of the SVG entirely.