Library images are real Confluence content

Updated
View as text
Open in Confluence
Open in ChatGPT Open in Claude

Each library image is a Confluence custom-content record of type 'Capable Image Content'. Indexed, storage-bodied, duplicate-title-protected, and able to live under a space, page or blogpost with attachments and comments as children. It is granted unlicensed and anonymous access, which is why a logged-out reader can resolve a referenced image at all.

Update screen for a library image with title and description fields, a Global container label, a version history panel showing three versions, and an editing tool rail beside the photograph.
Every image carries a title, a description, a container and its own version history because it is stored as a Confluence content record.

#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 → Capabilities

Confluence admin → Apps → Capable → Settings → Capabilities

-

Global settings → Asset access (Permissi

Capable settings → Asset access

-

Global settings → Egress

Capable settings → Egress

-

#Worth knowing

  • Deleting a folder does not delete or relocate the images inside it. One delete is issued for the folder record and nothing else. No cascade, no orphan sweep, no warning.

  • There is no images-only permission setting. All Capable global assets share one Confluence custom-content type in one space, so the Asset access tab governs them together, and only by editing CAPABLEASSETSTORE space permissions in Confluence.

  • Capable cannot change who may edit global images.

  • The Global images section disappears entirely if the CAPABLEASSETSTORE space is missing or unreadable, and a failed creation is remembered for the rest of the session rather than retried.

  • The 'Attached images' sweep misses several formats and is index-dependent. It is restricted to jpg, jpeg, png, gif, bmp, svg, webp, tiff and tif. Avif, heic, ico and jfif attachments never appear. And it excludes the CAPABLEASSETSTORE space, thumbnail files, and Capable's own library images.

  • Attachment images fetched for the editor are hard-capped at 3 MB. Larger files are resized server-side first, and if that still will not fit the request errors with 'Image too large for editor (N MB). Max 3MB.'.

How it actually behaves.