A hard cap on Free and Standard
Free sites get 2 GB of file storage and Standard sites 250 GB. At the limit, some Jira actions are restricted.

Reclaim Jira storage without a bigger plan.
Jira Cloud Standard caps file storage at 250 GB, and the only way to raise the cap is a plan upgrade. Storage Saver moves large, old attachments out of Jira's storage into the app's storage in Atlassian cloud. Each file stays with its work item, ready to download or restore.
Attachments pile up for years, and Jira leaves two ways out: pay for a bigger plan, or delete files.
Free sites get 2 GB of file storage and Standard sites 250 GB. At the limit, some Jira actions are restricted.
Upgrading is the only way to raise the cap, and Premium is priced by the number of users, so the whole site pays more for room.
Atlassian’s advice for freeing space is to delete content, and each deleted attachment is gone from its work item.
A moved attachment leaves Jira’s storage, not the work item. Add the Storage Saver panel to see its moved files and the space saved. Anyone who can see the work item can download a file; people allowed to add attachments can restore it as a new attachment.
The Move files tab lists the ten projects with the most to move. Confirm one, and the move carries on by itself until the project is done, with every file checked again before it goes. Stop at any time: files already queued still finish.
Project admins get a Storage Saver page in project settings, listing every moved file, searchable by name and work item. A + tile opens a picker of files still in Jira, largest first. Files that cannot move show why.
The first scan starts after install. The Overview tab shows what can be moved now, what is in use in work item text, and what needs checking, then forecasts when the site reaches its limit, before and after moving.
Add the app to your Jira Cloud site. The first storage scan starts on its own.
Open Jira settings → Apps → Storage Saver to see what can be moved now and when you reach your limit.
Move a whole project from the Move files tab, or pick files on a project page or a work item.
Every file takes the same path: checked, copied, the copy verified, and only then removed from Jira.

An error at any step before the last leaves the file in Jira. The worst a failure can cost you is space, never a file.
Moved files live in app storage hosted by Atlassian. The app talks to no server outside Atlassian and needs no external account.
Moving a file needs permission to delete attachments, restoring needs permission to add them, and downloading needs access to the work item.
A moved file is no longer a Jira attachment: the REST API, JQL attachment search, exports, backups, and automation rules don't see it.
Move the files your team no longer needs in Jira, keep each one with its work item, and stay on the plan you have.
Start free trial on Marketplace