Two-tier library
A per-space library ('Space images'. 'View images that have been uploaded to this space') and one site-wide library ('Global images'. 'View images that have been uploaded to the global space'), plus a read-only 'Stock images' section backed by Unsplash.
#Where you do it
Task | Where |
|---|---|
Open the image library | Confluence space or global apps menu → 'Capable Images' (standalone) or 'Capable' (Suite) |
Create a folder | Images library → Space images or Global images → new folder control |
Rename or delete a folder | Folder context menu in the library navigation |
#Settings that affect this
Setting | Where | What it does |
|---|---|---|
Global settings → Indexing | Capable settings → Indexing | - |
Global image library space | Confluence space with the key CAPABLEASSETSTORE, named 'Capable Asset Store' | - |
Upload permission | Confluence space permissions | - |
#Worth knowing
An Image reference macro pointing at another Capable app's library will not export on a published site. The exporter reads library images with the publishing app's own credentials, so a reference left behind by a different app id resolves to nothing and the page shows 'This image could not be exported (content not found or no longer available).'.
For an anonymous or unlicensed reader, an Image reference pointing at a plain external URL degrades to a sign-in notice rather than the picture. Library uploads, Unsplash images and Confluence attachments still render for those readers.
A freshly uploaded image can be missing from a gallery or from the library on reload. All these views are search-index queries, and Confluence indexes asynchronously. Only the folder listing hides the lag, with a live top-up limited to the last 24 hours.
Show Caption prints the library asset's own title (or description) on the page, not the Image Title stored on the macro. The published-site exporter behaves the opposite way. It prefers the macro's Image Title and falls back to the asset title.
An image picked through the shared image picker (Formatting Banner, Cards, Gallery, Compare, Background) is stored as a plain URL, not as a reference. Those macros never follow later library edits, and if the library image is deleted the macro is left pointing at a dead URL with no notice at all.
The 'Capable Images' section in the shared image picker, and the Markdown 'From library' item, are contributed by Images but consumed by Formatting and Markdown. The standalone Images app bundles neither, so both seams are Suite-only in practice.
#Related
How it actually behaves.
