Editing a WordPress post or page often involves more than one draft. A paragraph may be removed accidentally, a page may be overwritten with an unsuitable version, or several people may work on the same content. WordPress revisions and autosaves address different parts of this problem, but they are not interchangeable mechanisms and neither should be treated as a complete backup strategy.
Regular revisions let you review saved versions, compare changes and restore earlier content. Autosaves provide a separate, short-term recovery record while editing. This guide explains how to use the revisions interface, how restoration works, what distinguishes autosaves from regular revisions, and how WP_POST_REVISIONS and AUTOSAVE_INTERVAL affect storage and editing recovery. It also covers the trade-offs involved in disabling regular revisions.
What WordPress Revisions and Autosaves Do
Regular revisions as saved content history
Regular revisions preserve saved versions of posts and pages as content is updated. They create a history that can be inspected later, which is useful when you need to understand what changed or return to an earlier version. The revisions screen can show inserted, deleted and changed content, helping you select a version based on the actual differences rather than memory.
Revisions are content-history records stored in WordPress’s posts table as child records associated with the relevant post. Their retention can be controlled, but the number retained should be considered in relation to the site’s editorial workflow. A frequently edited site may have different rollback requirements from a site where content changes rarely.
Autosaves as short-term editing recovery
Autosaves are special revision records created during editing. They do not overwrite the actual published or current post content. WordPress keeps at most one autosave per user for a given post, and a newer autosave replaces the older autosave for that user and post. In a multi-user environment, each user may have one autosave for the same post.
This makes autosave primarily a short-term editing-recovery mechanism, while regular revisions provide a saved history subject to the configured retention policy. Neither mechanism is a substitute for scheduled, verified backups or a complete disaster-recovery strategy.
How to Compare WordPress Revisions
Opening the revisions screen
To inspect earlier versions, open the relevant post or page in the WordPress editor. In the Settings sidebar, select the appropriate Post or Page tab. If revisions are available, select the Revisions link or the displayed revision count. The exact controls can vary according to the WordPress version and the editing screen in use.
- Open the post or page editor.
- Open the relevant Post or Page section in the Settings sidebar.
- Select Revisions or the displayed number of revisions.
The revisions screen presents saved versions for review. The presence and presentation of revision information may depend on the content and the editing environment. Do not assume that every field, custom field or plugin-specific setting is represented in exactly the same way as standard post content.
Reading the comparison view
Use the revisions slider to move through saved versions. As you change the selected revision, review the highlighted additions, deletions and other changes. This allows you to determine whether a version contains the paragraph, title, excerpt or other standard content you are looking for.
The current revisions interface uses a slider to compare saved versions. The classic revisions screen also supports side-by-side comparison and, according to the documentation, comparison between any two revisions. Because the controls differ between interfaces, focus on the displayed version information and highlighted content before making a decision.
How to Restore an Earlier Version
Selecting the correct revision
Restoration should begin with comparison, not with an immediate click on Restore. Move through the available versions and inspect the highlighted differences. Check that the selected revision contains the intended content and that returning to it will not remove a newer change that you still need.
This is especially important when several people edit the same post or when a page has been changed repeatedly. A revision represents a saved content version, so choosing the correct point in the history is a deliberate editorial decision. The revisions interface helps you compare versions, but it does not decide which version is appropriate for your workflow.
Restoring and checking the result
After selecting the intended revision, use Restore from the revisions screen. Then inspect the restored content in the editor. Check the result before updating or republishing the live page, and confirm that the content now reflects the version you meant to recover.
Restoration should not be understood as a guarantee that every custom field or third-party setting will behave identically. The research describes WordPress revisions and standard tracked content, while the behavior of individual page builders, custom post types and plugins requires separate testing in the actual site environment.
Autosaves vs. Regular Revisions
What the autosave record does
Regular revisions are saved versions created as content is updated. They are intended for reviewing and restoring earlier content. Autosaves, by contrast, are created while editing and are stored as a special type of revision. Their purpose is to preserve a more recent editing state without overwriting the current post.
WordPress does not add an unlimited new autosave for every interval. It keeps a maximum of one autosave per user for a given post. When that user’s newer autosave is created, it replaces the older one. If multiple users edit the same post, each user may have one autosave for that post.
Why AUTOSAVE_INTERVAL is a separate setting
AUTOSAVE_INTERVAL controls the interval between autosaves in seconds. The official administration documentation identifies 60 seconds as the default. This setting affects how often editing work is saved automatically; it does not define how many regular revisions WordPress retains.
A longer interval may increase the amount of unsaved work if a browser or connection fails before the next autosave. For that reason, no interval should be presented as universally safer. Test any change with the editing workflow used on the site, and keep the distinction clear: AUTOSAVE_INTERVAL controls frequency, while WP_POST_REVISIONS controls regular revision retention.
How to Set a WordPress Revision Limit
WP_POST_REVISIONS values
The regular revision limit is configured with WP_POST_REVISIONS in wp-config.php. Before editing that file, create and verify a current backup and use a method appropriate for the hosting environment. The documented values have different effects:
| Value | Effect on regular revisions |
|---|---|
true or -1 |
Retains every regular revision. |
false or 0 |
Disables regular revision storage. |
| Positive integer | Retains that number of regular revisions per post. |
A positive integer can be used when you want a defined history without retaining every regular revision. The documentation gives values such as 3 or 12 as examples of numeric limits. These are examples of configuration values, not universal recommendations. The appropriate choice depends on how often content is edited and how far back the editorial team needs to roll back.
This setting applies to regular revisions, not to the separate autosave behavior described in the WordPress documentation. It should also not be presented as a complete database-optimization or backup strategy. The research does not quantify storage savings or guarantee a performance improvement from any particular limit.
When older revisions are removed
When a positive limit is applied, older regular revisions are automatically deleted when the post is updated again after the limit has been applied. Reducing the configured number therefore does not necessarily mean that every existing revision disappears immediately at the moment the configuration changes.
Autosaves are handled separately from the regular revision count in the documented behavior. A regular revision limit should therefore not be described as a control over the number of autosaves, nor should it be assumed to remove every revision-type record associated with editing.
What Changes When Revisions Are Disabled
The loss of regular rollback history
Setting WP_POST_REVISIONS to false or 0 disables regular revision storage. The practical result is that affected content no longer has the normal history of earlier saved versions available through the revisions workflow. Users lose the regular rollback option that would otherwise let them compare and restore a previous saved version.
This can be a reasonable site-specific operational choice only after considering the editorial process and recovery requirements. A site with frequent revisions or several editors may rely on rollback history more heavily than a site with a simpler publishing workflow. Disabling regular revisions should therefore be treated as a trade-off, not as a default optimization.
The autosave exception
Disabling regular revisions does not remove the per-post autosave described in the official documentation. The one-autosave-per-user behavior remains a separate short-term editing-recovery mechanism. However, an autosave is not a complete history of earlier saved versions and should not be presented as an equivalent replacement for regular revisions.
Autosave also does not replace a backup. If the site needs recovery beyond the editing process, revisions and autosaves alone are insufficient. Keep the decision about regular revision storage separate from the requirement for independent, scheduled and verified backups.
A Safer Maintenance Policy for Revisions
Choosing settings around real editorial needs
Start by identifying how the site is actually edited. Consider how often posts and pages change, whether several users work on the same content, and how important it is to return to an earlier saved version. Choose a retention value according to those requirements rather than applying an unsupported universal ideal.
- Use regular revisions when the team needs a reviewable history of saved content.
- Consider a positive
WP_POST_REVISIONSvalue when a defined history is appropriate. - Understand that
falseor0removes regular rollback history. - Treat
AUTOSAVE_INTERVALas a separate editing-frequency setting.
Do not measure the policy only by the number of records in the posts table. Retention settings can help control the number of stored revision records, but they are not a complete database-maintenance plan. The available research does not establish a universal limit, a quantified storage reduction or a guaranteed performance result.
Verification before and after configuration changes
Before changing wp-config.php, create and verify a current backup. Make the change through a method suitable for the hosting environment, then test the result with the real editing screens used by the site. Check both the revisions workflow and autosave behavior rather than assuming that a configuration change will appear identically in every tool.
Third-party page builders, custom post types and plugins may expose, modify or preserve content differently; their compatibility was not verified in the research. Test the specific content types and tools used on the website. After applying a positive revision limit, remember that older regular revisions are described as being removed during a later post update, not necessarily immediately when the setting is changed.
WordPress revisions provide a practical history of saved content, allowing editors to compare changes and restore an earlier version. Autosaves serve a different, shorter-term purpose: they preserve editing work without overwriting the current post, with newer autosaves replacing older ones for the same user and post. WP_POST_REVISIONS controls regular revision retention, while AUTOSAVE_INTERVAL controls autosave frequency. Disabling regular revisions removes normal rollback history but does not necessarily remove the documented autosave exception. Choose settings around the real editorial workflow, back up before editing configuration, test the actual environment and never treat revisions as a replacement for independent backups. Explore our WordPress plugins, WooCommerce extensions, themes and membership plans to find the right tools for your website.