CQL search on library images

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

Library images ship nine searchable fields you can use in Confluence's CQL builder: Asset title (~), Asset description (~), Asset category (=), Asset author (=), Asset template (=), Asset capability (=), Asset type (=), Asset feature (=) and Asset tags (=). So the library is directly searchable and reportable from Confluence itself.

#Note

The Search capability is bundled in the standalone Images app as well as the Suite.

#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

-

#Limits that apply here

Limit

Value

What happens

Editor / attachment-import fetch ceiling

3 MB

An attachment loaded for editing or importing into the library is capped at 3 MB of raw bytes. Larger files are auto-resized to PNG to fit; only if that still fails does it error 'Image too large for

Rovo / chat accepted extensions

.png .jpg .jpeg .gif .webp .svg .bmp .av

PDF, AI and PSD are deliberately excluded even though the library uploader stores them. The check sniffs the file's bytes rather than trusting the filename.

Gallery page size

25 images per page

A 'Show more' button loads the next 25 while more remain.

#Worth knowing

  • Standalone Images has no space settings screen, so there is no per-space configuration surface of any kind in that app.

  • The Indexing tab is not available in standalone Images, so there is no way to force a reindex there when the search index lags.

  • The Migration tab never appears for the Images app. Standalone-to-Suite migration is started from the Suite side.

  • Customer-managed egress domains are unavailable in standalone Images. That app declares no external permissions block at all.

  • There is no Capabilities (global hide) tab in the standalone Images app, so a standalone customer cannot hide the capability instance-wide from the app either.

Better with company.