Image upload and paste
Uploading or pasting an image attaches the file to the page that renders the document (as a draft attachment, retried as current if the page is already published) and inserts . Accepted drop types in the macro config: bmp, gif, ico, jfif, jpeg, jpg, png, svg, tiff, webp.
#Where you do it
Task | Where |
|---|---|
Point a macro at a README on GitHub, GitLab or Bitbuck | Configure Markdown → Markdown from URL |
Import a markdown file from your computer | Configure Markdown → Markdown from scratch → 'Upload file', or drop the file on the editor |
Insert an image or diagram from the Capable library | Editor toolbar → + → Image 'From library' or Diagram 'From library' |
#Settings that affect this
Setting | Where | What it does |
|---|---|---|
Global settings → Permissions | - | Controls edit access to the GLOBAL asset store. Which is what governs who may create Global markdown templates. It is shared with diagrams, images, calendar and search because they all use one Confluence custom content t |
Global settings → Egress domains | - | Customer-approved domains are fetched and loaded directly by the reader's browser instead of going through the Capable proxy, which also makes their images loadable without a Capable token. Customer-managed egress is ena |
#Worth knowing
Diagram fences and proxied images degrade to code blocks and alt text for logged-out readers. This is a deliberate degrade, not a failure.
Images written into a document attach to the page that renders it, not to the document, so moving or referencing the document elsewhere can break them.
Every admin control that affects markdown is a shared Capable settings surface; the Permissions tab in particular governs the whole global asset store shared with diagrams, images, calendar and search.
#Limits that apply here
Image load timeout
#Related
How it actually behaves.
