Import a page attachment
Drag a result from 'Attached images' onto a library section or folder. This imports a copy. It does not move or link the attachment. The bytes are fetched server-side because the browser cannot read attachment binaries cross-origin, and anything over 3 MB is downscaled during the import.
#Where you do it
Task | Where |
|---|---|
Upload images | Images library → pick a section or folder → Upload button, or drag files onto the section |
Add a page attachment to the library | Images library → Attached images → drag a result onto a Space images or Global images folder |
Add a stock photo to the library | Images library → Stock images → search → drag a result onto a library folder |
#Settings that affect this
Setting | Where | What it does |
|---|---|---|
Upload permission (derived, not a Capabl | Confluence space permissions | - |
Per-image actions | Image context menu | - |
#Worth knowing
A referenced image that has neither a stored full-resolution attachment nor a thumbnail cannot be published or exported: the page gets an explanatory note instead of the picture.
Page attachments and stock photos cannot be referenced. Only library images resolve through the asset lookup, so the reference picker hides them and 'Insert N references' is disabled if one is selected.
Upload permission is inferred from two unrelated Confluence permissions. Create-attachment AND create-page-or-blogpost. A user with attachment rights but no page-create right is silently told they cannot upload images.
If the attachment step of an upload fails, the record just created is deleted again so nothing partial is left behind; a mixed batch reports 'Successfully uploaded N files, failed to upload M files'.
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.'.
#Limits that apply here
Editor / attachment-import fetch ceiling
Rovo / chat attachment ceiling
#Related
How it actually behaves.
