Copy as macro
An image or folder context-menu action that copies a Capable asset URL. Pasting an image URL into a page auto-converts into the Image reference macro; pasting a folder URL auto-converts into the Image folder gallery macro.
#Where you do it

Task | Where |
|---|---|
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 |
Style a referenced image | Image reference config panel → Style tab |
#Settings that affect this
Setting | Where | What it does |
|---|---|---|
Standalone byline off-switches (properti | App property capable-global-hidden-capabilities.hiddenCapabilities, and space property <ha | - |
Per-image actions | Image context menu | - |
#Worth knowing
Value 500 in Width or Height is ignored. It was a legacy sentinel meaning 'auto-size', so a macro saved with 500 behaves as if the field were blank.
Corner radius, Shadow and Border on the reference macro, and Columns, Image fit, Gap, Corner radius, Shadow and Border on the gallery, exist only in the custom config panel.
An anonymous or unlicensed reader can see a referenced image or a gallery, but never the library macro, the library page contents, or the settings page. The space page and global page grant unlicensed and anonymous access but fall back to a static visitor notice instead of the library; the global settings page grants none and requires being logged in.
Cancelling the auto-opened picker on an 'Image (Capable)' placeholder leaves the macro on the page showing a 'No Images Selected' card. Visible to readers, not just the author. And the picker will not reopen automatically for the rest of that browser session. Because that macro has no unlicensed access grant, an unlicensed or anonymous reader sees nothing there at all.
There is no migrator for the legacy standalone image library macro. Only three migrators exist. The library, the Image reference macro and the Image folder gallery macro.
#Related
How it actually behaves.
