Set entry history retention limits
Log in to add to favouritesPage last updated 14 August 2026
Once a content type has version history switched on, retention limits decide how many old versions of its entries are kept. There are two limits, and you can use either one, both, or neither.
Before you start
You must be a System Administrator to update project settings.
The two retention limits
- Limit version history by age. Turn this on and set Maximum age (days) to remove versions once they're older than that number of days.
- Limit the number of versions. Turn this on and set Maximum versions to keep only the most recent versions, removing anything beyond that count.
The two limits are independent, so any combination is possible:
| Limit by age | Limit by count | Result |
|---|---|---|
| Off | Off | Unlimited retention. Every version is kept. |
| On | Off | Versions are removed once they pass the maximum age. It doesn't matter how many versions that leaves. |
| Off | On | Only the most recent versions, up to the maximum, are kept. It doesn't matter how old they are. |
| On | On | Both limits apply together. A version is removed as soon as it exceeds either one. |
Set retention limits
- Select the Settings (gear) icon in the project sidebar to open Project settings.
- Select the Version history tab.
- Under Entry history retention:
- To remove versions after a set number of days, turn on Limit version history by age and enter a number in Maximum age (days).
- To keep only a set number of versions, turn on Limit the number of versions and enter a number in Maximum versions.
- Save your changes, then Publish.