Basic · Attachment source
The file already on your page becomes the table, diagram or document
With the Attachment source the file someone attached - a name in a list at the bottom of the page - becomes the table, the diagram or the document itself. Your readers learn what it says without downloading it, and nothing is moved or copied anywhere.
You administer nothing new
No connection to configure, no credential to hand out, no admin involved. If someone can see the page, they can see the attachment, because the permissions are the ones Confluence already applies. The picker lists what is attached to the current page and, when the file lives elsewhere, searches the whole site by name. It is your shortest path from "here is the file" to "here is what the file says", and it is available to 29 of the 31 macros - everything except Miro and Redirect, which have nothing to attach.
You get version history without building it
Attachments are versioned by Confluence, so replacing the file leaves the old one recoverable, and every macro pointing at it reads the current version. Your page becomes the current view of the artefact rather than a snapshot of the day it was uploaded - and where a download is the point, the File macro presents the attachment as a card with its name, size and date rather than a bare link.
You present one file however each page needs it
One attachment feeds more than one macro. The same .csv is a table on
the summary page and a download on the handover page; a .puml renders
as a diagram here and as highlighted source there. You choose how to present a file
without committing it to one format.
Your Jira attachments too
In Macro Pack for Jira the same source lists the files attached to the issues a macro is linked to, grouped by issue, so the log excerpt, the screenshot or the exported dataset on a ticket is shown right there instead of downloaded. A Confluence page that needs a file from a Jira issue uses the Atlassian source instead - either way, nobody re-uploads the file and leaves two copies to drift apart.
Attachment is one of 13 places Macro Pack reads from
One app, one licence, one connection your admin sets up - and 12 more places a page can pull content from, whether that is a page attachment, a Git repository, an S3 bucket or your database.
See every source compared