SVG vs PNG for Confluence

Confluence blocks inline SVG rendering for security — shaping a PNG-plus-draw.io strategy for documentation graphics.

The SVG Rendering Block

Confluence Cloud shows uploaded SVGs as attachment links, not inline images — an XSS-protection choice. That makes PNG the default for static doc images: export at 2x display width from vector masters and pages stay sharp. Marketplace apps can re-enable sandboxed SVG rendering where teams need it.

Uploaded SVGs become download links by design
2x PNG exports are the practical static-image default
Marketplace apps exist for sandboxed SVG display

draw.io for Living Diagrams

Architecture and process diagrams belong in the draw.io integration: it imports SVG sources, renders sharply, and — critically — stays editable by the whole team on the page. Docs with draw.io diagrams don't rot the way attached-image docs do, because updating them takes one click, not a re-export cycle.

draw.io imports SVGs into editable diagram blocks
In-page editing keeps documentation current
Vector rendering without the attachment security block

Frequently Asked Questions

Can admins enable inline SVG attachments?

Not in standard Confluence Cloud — the block is by design. Marketplace apps provide sandboxed rendering; Data Center offers more configurability.

What export size for PNG documentation images?

2x the display width (typically 1400-1600px for full-width page images). Confluence's renderer downsamples cleanly and retina screens stay sharp.

Ready to Convert Your Image to SVG?

Free online converter — no sign-up, no watermarks, results in under 3 seconds.

Convert Image to SVG — Free