Published Capable Sites

Image reference exports fully. The file is copied into the site and alignment, caption, corner radius, shadow and border are reproduced (Width, Height and Aspect Ratio are not). Image folder gallery renders an explanatory note. The Image library placeholder renders nothing. Any Capable image reference URL found elsewhere on a published page. Inside another macro's image field, for instance. Is also resolved and downloaded with app authority, so it works on private sites too. Raster files are rewritten to .webp for the site optimizer.


#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 never appear. The sweep also excludes the CAPABLEASSETSTORE space, generated thumbnail files, and Capable's own library images.

Unsplash search debounce and failure ceiling

500 ms debounce; gives up after 5 consec

Search does not go to Unsplash from the browser. It calls Capable's own API with the viewer's app token.


#Worth knowing

  • A migration what-if run reports 'no node' for spaces that have never held a Capable image. Nothing is created during verification, so the Capable storage lookup returns nothing rather than inventing one. The real run creates it.



Better with company.