Published Capable Sites
Images you add with the Image reference macro publish with your site. The file is copied into the site, and its alignment, caption, corner radius, shadow and border carry across. Width, height and aspect ratio do not.
The Image folder gallery shows an explanatory note on a published site, and the Image library placeholder shows nothing. Any Capable image link elsewhere on a published page, such as inside another macro's image field, is picked up and copied too, so it works on private sites as well. Raster images are converted to .webp so your pages load quickly.
#Where you do it
Task | Where |
|---|---|
Open the image library | Confluence space or global apps menu → 'Capable Images' (standalone) or 'Capable' (Suite) |
Put a single library image on a page | Editor → type / → 'Image reference (Capable)' (Suite) or 'Image reference macro (Capable)' (standalone) |
Put a library image on a page by pasting a link | Editor → paste the image's Capable asset URL |
#Settings that affect this
Setting | Where | What it does |
|---|---|---|
Global settings → Capabilities | Confluence admin → Apps → Capable → Settings → Capabilities | - |
Global settings → Asset access (Permissi | Capable settings → Asset access | - |
Global settings → Egress | Capable settings → Egress | - |
#Limits that apply here
Limit | Value | What happens |
|---|---|---|
Attached images sweep. Accepted file extensi | Jpg, jpeg, png, gif, bmp, svg, webp, tif | AVIF, HEIC, ICO and JFIF attachments are left out. So are images in the Capable Asset Store space, generated thumbnails and Capable's own library images. |
#Worth knowing
A migration dry run reports 'no node' for spaces that have never held a Capable image. That is expected, because nothing is created during a dry run. The real migration creates it.
#Related
Better with company.
