Can you limit how many page versions Confluence Cloud keeps?
By Kayabyte · Updated 17 November 2026
Short answer: Not with a built-in setting. Confluence Cloud keeps every version of every page and attachment, and there is no option to keep only the newest N versions; the request for one, CONFCLOUD-27701, was still Gathering Interest when checked on 1 November 2026. The native ways to cap history are to delete versions one at a time from the page history, or to script the REST API and run the script again whenever history grows back. For a standing “keep the newest N versions” rule across spaces, with a preview and an optional nightly run, Pruner: Version History Cleanup for Confluence is an app I make.
Disclosure: I make Pruner. The built-in options come first, and nothing before the Pruner section needs an app.
If your pages have hundreds of versions, you have probably looked for a “maximum versions” setting. This guide says what exists in Confluence Cloud, what a cap would have to do, and where each option stops.
What Confluence Cloud does today
- Every save adds a version of the page, and every upload of a changed file adds a version of the attachment.
- There is no site, space or page setting that limits the number of versions kept.
- On the Free and Standard plans, attachment versions count toward the storage limit. See Confluence storage almost full for what counts.
Option 1: delete versions by hand
- Open the page and open its page history.
- Select Delete next to a version you no longer need and confirm.
Deleted versions don’t go to the trash and can’t be restored, and version numbers can change after a delete. If you don’t see Delete, ask a space administrator. Deleting a specific attachment version needs the Space Administrator permission. This is one version of one page per click. Details are in How to delete old page versions in Confluence Cloud.
Option 2: a script on the REST API
A script can list the pages in a space, list each page’s versions and delete all but the newest ones with DELETE /wiki/rest/api/content/{id}/version/{versionNumber}. It is the closest thing to a cap that needs no app. Where it stops:
- No preview unless you build one. Deleting can’t be undone, so the script needs a dry run that lists what would go.
- It runs once. History grows back, so someone has to run it again, or host it and keep it working.
- Restricted pages only appear if the account running the script can see them.
- Large sites need paging, retries and a way to resume.
What a cap on versions needs
Whatever you use, decide these first:
- How many versions to keep. The newest ones, and the current content, should never be deleted.
- A minimum age, so versions from this week survive even when a page has more than N.
- Which spaces. Spaces that need their full history, for legal or policy reasons, should be left out.
- A preview with counts before the first delete, and a generous first value (for example keep 20 versions older than 180 days) that you tighten later.
- Whether it repeats, or is a one-off clean-up.
Pruner: Version History Cleanup for Confluence
Pruner applies that policy to Confluence Cloud.
- Keep the newest N versions of each page and attachment, optionally delete only versions older than a set number of days, and choose the spaces (empty means every space), with a list of spaces to leave out.
- Preview counts the old page and attachment versions the policy would delete, the storage the attachment versions use, and the pages with the most history. Nothing is deleted at that step.
- A manual clean-up is confirmed by a Confluence admin. The nightly clean-up is optional and off by default.
- The current version and the page content are never changed. Blog posts, comments and whole pages aren’t touched.
- Pages restricted to named people are not visible to apps, so the nightly run skips them. A manual clean-up by an admin who can see them includes them. Archived pages are skipped.
- It runs on Atlassian Forge and makes no calls outside Atlassian.
Limits: deleted versions can’t be restored, Confluence renumbers the remaining versions, and Confluence updates its storage figure on its own schedule, usually within a few hours. Page text versions are small, so the storage you free is mostly attachment versions.
Pruner is on the Atlassian Marketplace. Moving from Data Center? See Purge Versions for Confluence in Cloud, and for other apps, Confluence version cleanup apps compared.
Not a Confluence admin? Send this to yours
Only an admin can install apps. Copy this note and send it to yours:
Could we try Pruner? Delete old versions of Confluence pages and attachments, keep the newest ones, preview what goes first, and free up storage. Nightly clean-up is optional. It is on the Atlassian Marketplace and built on Atlassian Forge, and it makes no calls outside Atlassian. Free for up to 10 users. Listing: https://go.kayabyte.dev/atl/pruner?s=site-ask-confluence-limit-page-versions
FAQ
Is there a setting to keep only the last N versions of a Confluence Cloud page? No. Confluence Cloud keeps every version, and the request for a limit, CONFCLOUD-27701, was still Gathering Interest when checked on 1 November 2026.
Can I limit versions for one space only? Not with a setting. You can delete versions in that space by hand or with a script, or use a retention policy app that lets you choose the spaces.
Can I undo deleting a page version? No. Deleted versions aren’t restorable, so preview or dry-run first.
Does deleting old versions free storage? For attachment versions, yes, and Confluence updates the storage figure on its own schedule. Page text versions are small.
Will Pruner delete the current page? No. The current version and the page content are never changed, and the newest versions you chose to keep are always kept.
Confluence and Atlassian are trademarks of Atlassian. Kayabyte is an independent developer and is not affiliated with or endorsed by Atlassian.
More guides
- Atlassian Connect end of support: what Jira and Confluence admins should check before 31 January 2027
- Apps to make a Confluence group watch a space or page, compared
- How to make a Confluence group watch a space or page
- Onboarding in Confluence: make new hires watch the right spaces automatically
- Confluence watching but no email? 5 things to check
- How to track billable and non-billable hours in Jira
- How to calculate budget burn rate and run-out date in Jira
- Jira business days apps compared: JQL, Automation and holidays
- How to count business days between two dates in Jira
- How to see what a Jira epic costs from worklogs
- How to export Jira worklogs to Excel or CSV
- How do I make a Jira field read-only after approval?
- How to handle hourly rate changes in Jira cost reports without changing past costs
- Jira project cost and budget apps compared: Tempo Financial Manager alternatives
- How to track project cost and budgets in Jira from worklogs
- How to see project cost from Tempo worklogs in Jira
- How to set a WIP limit per person in Jira
- How to see workload per assignee in Jira
- How to invoice Jira worklogs in Fiken
- How to invoice Jira worklogs in Fortnox
- How to invoice Jira worklogs in PowerOffice Go
- How to invoice Jira worklogs in Tripletex
- JQL with business days: find Jira work due within N working days
- How can I add a whole group as request participants in JSM?
- JSM agent can’t find a customer in Request participants: what to check
- Add or remove request participants with Jira Automation
- CC a whole team on every Jira Service Management request
- Why can’t a customer see a JSM request shared with their group or organization?
- Group request participants apps for Jira Service Management compared
- How to calculate on-call pay from Jira Service Management schedules
- JSM organizations vs request participants: which to use
- Why adding request participants in bulk floods inboxes in Jira Service Management, and how to avoid it
- Stop agents or the reporter ending up as request participants
- How to add public holidays to a JSM SLA calendar
- Kanban WIP limit per person in Jira: beyond column limits
- Kayabyte apps for Jira and Confluence: what each one does
- What happens to your worklogs when you leave Tempo Timesheets (Jira Cloud)
- Opsgenie to Jira Service Management: on-call pay reports