Can Confluence Cloud display a Visio file?

You can attach a .vsdx file, but Confluence Cloud will not render a preview of it: clicking the attachment downloads the file instead of showing it. Atlassian tracked this as CONFCLOUD-68619 and closed it in October 2023 as timed out, without a fix, stating that there is no known workaround. To show the diagram on the page you have to export it to an image format or convert it.

What is the best format to export a Visio diagram for Confluence?

SVG if the diagram has text or links, PNG only if it is small and will never change. SVG is vector, so it stays sharp at any zoom and keeps the links that were attached to shapes inside the file. PNG flattens everything to pixels: the text blurs when readers zoom, and any link on a shape is gone.

Can I keep editing the diagram after moving it to Confluence?

Yes, if you import it rather than export it. The draw.io app for Confluence imports .vsdx through File then Import, and the result is an editable diagram inside Confluence. Complex drawings may need small corrections after import.

Why do the links on my Visio shapes stop working in Confluence?

If you exported to PNG, they were discarded with everything else that was not pixels. If you exported to SVG, they are still in the file, but Confluence renders an uploaded SVG as a flat picture, so the viewer never makes them clickable.

How to put a Visio diagram into Confluence Cloud

You attach the .vsdx, click it to check, and the browser downloads the file instead of showing the drawing. That is not a permissions problem or a broken upload. Confluence Cloud simply does not preview this format, and it is not going to start.

Short answer. Attaching the file works; previewing it does not. To get the diagram visible on a page you either export it from Visio as SVG and insert that, or import the .vsdx into a diagramming app inside Confluence and keep it editable there. Export to PNG only if the picture is small and finished forever. Which one you want depends on a single question: does the diagram change, and do its shapes carry links?

Why the attachment does not show

Confluence Cloud previews a long list of formats on the page. The modern Visio format is not on it: a .vsdx attachment downloads rather than opening. Atlassian has a ticket for exactly this, CONFCLOUD-68619, and the honest part is how it ended. It was raised in 2019, it says in plain words that there is no known workaround, and in October 2023 it was closed as timed out — not fixed, just expired. The older .vsd format did preview, which is why people with long memories insist this used to work.

So the decision is not whether to convert, but into what.

The four routes, and what each costs later

Export to PNG

The fastest and the most common. File, Export, PNG, drag onto the page, done in a minute.

The cost shows up later. A PNG is pixels, so the text inside the boxes turns to mush the moment somebody zooms to read a label — and architecture diagrams exist to be zoomed into. Any hyperlink you attached to a shape in Visio is gone, because pixels cannot hold a link. And every edit means exporting and re-uploading by hand.

Export to PDF

Sharper than PNG and it survives printing, which is why audit and compliance teams like it. But a PDF is a document sitting next to the page rather than a picture on it: the reader has to open an attachment, and the diagram stops being part of what they are reading. Fine as a formal record, poor as documentation.

Export to SVG

SVG is vector: it stays sharp at any zoom, the text stays text, and, crucially, the links attached to shapes travel inside the file. For a diagram with any text at all this is the right export format.

There is a catch, and it is the thing people write to us about: Confluence renders an uploaded SVG as a flat image. The file still contains everything, but the viewer does not make it live, so your clickable boxes arrive looking perfect and behaving like a screenshot. We wrote that up in why Confluence shows your SVG as a flat picture.

Import into a diagramming app and keep it editable

If you want to stop depending on Visio altogether, import rather than export. The draw.io app for Confluence reads .vsdx: open a draw.io diagram, choose File then Import, pick the file. The result is an editable diagram living inside Confluence, so the next change is made where the documentation is, without a round trip through the desktop.

Two honest caveats. Complex drawings usually need small corrections after import, because Visio stencils and draw.io shapes are not a perfect match. And this is a swap of tools, not a conversion trick: your colleagues who live in Visio will still be working in Visio.

The arithmetic nobody does

Take one architecture diagram that gets a real edit once a month, which is modest for a system under active development.

By the export route each change is: open Visio, edit, export, find the Confluence page, delete the old attachment, upload the new one, check the page still looks right. Call it ten minutes if nothing goes wrong, and it goes wrong often enough — somebody uploads the picture but forgets the page still shows the old attachment. Two hours a year per diagram, for a file that in theory you already finished.

By the import route the edit happens on the page itself, and there is nothing to re-upload.

If the shapes have links on them

This is the case worth separating out. A Visio diagram where each box links to the runbook, the service page or the owner's documentation is not a picture: it is navigation. Flattening it to PNG destroys exactly the part that made it useful, and nobody notices until a reader clicks a box and nothing happens.

Export that diagram as SVG and the links survive in the file. Then they stop working in Confluence, for the viewer reason above.

Disclosure: I build the app that fixes this one. Clickable SVG renders the SVG as live markup rather than a flat picture, so the links your Visio shapes already carry keep working on the Confluence page: click a box, open the page behind it. Nothing leaves your site, and re-exporting after an edit does not mean redoing anything by hand.

And if your diagram is a simple drawing with no links and no small text, export it to PNG and move on. It is free, it takes a minute, and this whole article is beside the point for you.

Questions people actually ask

Is there a Visio macro in Confluence Cloud?

No. There is no built-in macro that renders Visio files. The request has been open on Atlassian's tracker for years as CONFCLOUD-27877.

Can I at least show a thumbnail of the .vsdx?

Not natively. The file downloads rather than previewing, so there is nothing to thumbnail. Some file-preview apps on the Marketplace add Visio support if you need the raw file viewable in place.

Does .vsd still preview?

The old binary format behaved differently from .vsdx, which is the source of a lot of confusion in forum threads. Do not plan around it: saving modern diagrams back to a legacy format to win a preview is a bad trade.

What about multi-page Visio files?

Export gives you one file per page, so a five-page drawing becomes five images and five uploads. The draw.io import handles multi-page .vsdx in one go, which is the main practical argument for importing when the drawing is large.

We are moving off Visio. Does that change the answer?

It simplifies it: import once, keep the diagram editable inside Confluence, and stop exporting anything. The comparison of the diagramming options is in diagrams in Confluence compared.