Confluence · Attachment Cleanup for Confluence

Find unused and orphaned attachments in Confluence Cloud

See every attachment across your site, flag the unused and orphaned files, and total the storage you can reclaim.

Try it free on the Atlassian Marketplace Documentation

Runs entirely on Atlassian Forge inside your own tenant. No external servers, no data egress.

Why it exists

This app answers a request that has been open on Atlassian's public tracker for years: CONFCLOUD-16577, "Detect unused attachments", with 291 votes. We wrote up the problem and the native workarounds on Atlassian Community.

The gap

Attachments pile up silently: an image removed from a page stays in storage, trashed pages keep their files, and giant uploads hide in forgotten spaces. Confluence has no site-wide attachment inventory, so "where is my storage going?" has no native answer.

What it does

Inventories every attachment site-wide, daily and on demand.
Flags unused, orphaned, and large attachments.
Totals storage and reclaimable bytes per space and site-wide.
Surfaces the biggest cleanup opportunities first.
One-click, audit-ready CSV export of the full inventory.
Opt-in bulk cleanup: preview, confirm, then soft-delete flagged attachments to the space trash. Recoverable, never a permanent purge.

The site-wide inventory: every attachment with its flag and size.

Reclaimable storage rolled up per space, biggest first.

The daily sweep classifies files and totals what you can reclaim.

60-second walkthrough

Honest about its limits

Reference detection is a textual scan of page bodies. It is deliberately conservative, and a file it cannot prove is referenced is flagged for review, not deleted.
Cleanup is soft-delete to the space trash only. Nothing is ever purged permanently by the app.
The one write path, honestly scoped: The opt-in bulk cleanup soft-deletes flagged attachments to the space trash after a preview you confirm. Everything it moves can be restored from trash.

Security & permissions

Built on Atlassian Forge: the app runs on Atlassian's own serverless platform inside your tenant, stores its data in Forge storage, and makes no external network calls. Every scope it requests, and why:

read:space:confluence / read:page:confluence	enumerating spaces, pages, and attachments
storage:app	the chunked inventory cache, in your tenant

The native feature it builds on

Atlassian's own documentation for what Confluence does out of the box, so you can see exactly where the gap is:

Manage uploaded files (support.atlassian.com)

FAQ

Does any data leave my instance?

No. The app runs on Atlassian Forge inside your own tenant with zero external egress, which makes it eligible for Atlassian's Runs on Atlassian trust marker.

How is it billed?

Through the Atlassian Marketplace, on your existing Atlassian bill, priced per user like any Cloud app. The listing has a free evaluation and the exact calculator for your tier.

Where do I get support?

Email support@llmgraph.ai or open an issue from the documentation page. You talk directly to the people who build the app.

Install Attachment Cleanup for Confluence in about a minute.

Free evaluation from the Marketplace listing. If it does not fit your workflow, tell us what would and we will build it.

Try it free Read the deep-dive