# Diagrams in PDF and Word exports Page exports are how diagrams reach people who will never open Confluence. It is worth knowing what survives. --- ## What survives ![A page of an exported PDF titled Export Testing containing a Mermaid user journey chart of a working day and a PlantUML use case diagram with a user, a main admin and three yellow notes.](https://help.gocapable.com/images/034b3345-4a1e-47db-baf8-786e9a8c286c.webp) Both diagrams come through the PDF at full size with their labels, notes and colours intact. | **Export** | **Diagrams** | **Notes** | | ------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------- | | **Confluence PDF** | Rendered as images | Uses the stored rendering, so it works offline | | **Confluence Word** | Rendered as images | Same rendering, embedded in the document | | **Capable Sites** | Rendered properly, and links still work. See [Integrations](https://help.gocapable.com/diagrams/integrations.html). | The best option for documentation you publish | ⚠️ **Clickable areas do not survive PDF and Word.** A diagram whose shapes link to pages exports as a flat picture. If the links matter, publish to a site instead. --- ## A few things that catch people out * A diagram edited seconds before export may export its previous rendering. * Very wide diagrams are scaled to the page and can become unreadable; consider splitting them. * Dark mode is never applied to exports. --- ## Related [Export a diagramSingle diagrams.](https://help.gocapable.com/diagrams/export.html) [IntegrationsPublishing to a site.](https://help.gocapable.com/diagrams/integrations.html) [Clickable diagramsWhat is lost in a flat export.](https://help.gocapable.com/diagrams/clickable-diagrams.html) --- _It still works for people without Confluence._