Your Cart
WordPress autosave and post revisions

WordPress Autosave and Post Revisions: Configuration Options for Safer Content Management

WordPress autosave and post revisions are often treated as one feature, but they protect different parts of the editing process. Autosave is designed to preserve work while content is being edited. Revisions preserve earlier saved versions of posts and pages, making it possible to return to a previous version when an editorial change needs to be undone.

That distinction matters when you configure a WordPress website. The AUTOSAVE_INTERVAL constant controls how often editing data is autosaved, while WP_POST_REVISIONS controls whether revisions are disabled, unlimited or retained up to a defined maximum. This article explains both settings, the practical trade-offs involved and the precautions to take before editing wp-config.php. Autosave and revisions can support content recovery, but neither replaces independent backups or a tested recovery process.

Autosave vs. Post Revisions: What Each Feature Protects

Autosave as editing-session protection

WordPress uses Ajax during editing to send content data periodically. This autosave process is intended to preserve work during an active editing session. If a browser problem, interruption or other editing issue occurs, the saved data may help recover recent work that had not yet been saved manually.

Autosave is therefore best understood as short-term editing protection. It does not represent a complete archive of every version created over the life of a post. The exact way the data is stored can depend on the state of the content, the editing context and the user involved.

Revisions as rollback history

Post revisions serve a different purpose. They preserve copies of earlier saved edits to posts and pages, allowing an editor to review or restore an earlier version. This makes revisions useful when content was saved successfully but a later change needs to be reversed.

The two mechanisms can be related because autosaved content may be stored as a special post revision, but they should not be treated as interchangeable. Autosave focuses on preserving current editing work, whereas ordinary revisions provide a history of saved content. Neither feature protects a site from hosting failure, database corruption, malware or complete site deletion.

How WordPress Autosave Works

Draft state, locks and autosave revisions

While a post is being edited, WordPress periodically sends editing data through Ajax. For drafts and auto-drafts that are not locked, the current user’s autosave can overwrite the existing draft. In other situations, WordPress can create or update a user-specific autosave revision.

This distinction explains why autosave behavior should not be reduced to the idea that WordPress simply creates a new permanent revision at every interval. The post state, lock status and user context affect whether the existing draft is updated or separate autosave data is used. Autosave is primarily a recovery aid for the active editing session, not a substitute for an intentional saved-version archive.

Behavior can also vary for custom post types and products that register their own content types. Standard posts and pages should not automatically be used as a reference for every page builder, WooCommerce-related content type or third-party editor. Check the behavior of the specific content type before assuming that autosave operates in exactly the same way.

Changing the WordPress Autosave Interval

The AUTOSAVE_INTERVAL setting

The documented way to change the WordPress autosave interval is to define AUTOSAVE_INTERVAL in wp-config.php. The value is expressed in seconds. When the constant is not set, the documented default interval is 60 seconds.

For example, a value of 180 represents three minutes because the setting uses seconds. The configuration should be edited carefully and only after taking a current backup and ensuring that you have suitable administrator or hosting-level access. Retain a rollback copy of the original configuration before making the change.

An incorrect change to wp-config.php can affect site loading or configuration. Do not treat this file as an ordinary content setting. Make one deliberate change, check the syntax and confirm that the site and editing screen continue to work as expected.

Balancing request frequency and unsaved work

Changing the interval is an operational trade-off rather than a guaranteed performance solution. A longer interval may mean that autosave requests occur less frequently, but it can also leave more editing work unsaved between autosaves. If an interruption happens during that period, more recent changes may not be present in the autosaved data.

A shorter interval may preserve editing changes more frequently, but it also changes how often the site sends autosave requests. The appropriate choice depends on the editing workflow and the amount of work editors can reasonably recreate after an interruption. Do not assume that one interval is correct for every site, hosting environment or editorial team.

Choosing a WordPress Revision Limit

Unlimited retention versus a numeric maximum

WordPress enables revisions by default unless WP_POST_REVISIONS is configured otherwise. When the setting remains true, the documented behavior is to treat the number of revisions to retain as unlimited by default.

The same constant can be assigned an integer to define a maximum number of revisions retained per post or page. A value such as 3 or 12 represents a defined retention limit. This gives the site a controlled amount of rollback history without removing the revision feature entirely.

WordPress documentation does not establish one universally correct revision count for every website. A numeric value should therefore be treated as a site-specific operational choice, not an official WordPress requirement. Avoid claiming that a particular limit guarantees a certain database size or performance result; the available documentation does not establish such an outcome for specific hosting plans.

Factors for a site-specific decision

Choose a revision approach by considering how the website is edited and recovered:

  • Editing frequency: content that changes often can create a stronger need for a usable rollback history.
  • Rollback value: consider how important it is for editors to restore an earlier saved version.
  • Maintenance practices: consider whether the site has an established backup and recovery process.
  • Content types: confirm whether the relevant post type supports revisions before interpreting the setting.

These factors support a reasoned configuration, but they do not produce one universal number. A limit can be a practical starting point when the team wants defined history and a clearer retention policy. Review the result in the actual editorial workflow rather than assuming that the setting behaves identically for every product or custom content type.

When Limiting Revisions Is Better Than Disabling Them

A defined history versus no revision history

A numeric limit is generally the more cautious choice when editors still need content recovery but unrestricted revision retention is undesirable. It preserves a defined number of earlier versions for each post or page, so the built-in rollback workflow remains available within that limit.

Setting WP_POST_REVISIONS to false disables revisions for the affected content. That removes the built-in history that editors might otherwise use to compare or restore earlier saved versions. Disabling revisions should therefore be a workflow decision, not an automatic response to concerns about database growth.

Consider disabling revisions only when the site has a documented alternative recovery workflow and the team understands what will be lost. Even then, an alternative process does not remove the need for independent backups. A revision limit is often more appropriate when the goal is to control retention while preserving some rollback capability.

Compatibility and Recovery Cautions

Custom post types and third-party editors

Revision retention depends on whether the post type supports revisions. WordPress also exposes separate support concepts for revisions and autosave. As a result, a custom post type may not behave like a standard post or page, and support for one feature should not automatically be assumed to include the other.

This is relevant when working with WooCommerce-related content, page builders, themes or other third-party products. The reviewed documentation does not verify how every product handles autosave and revisions. Check product-specific behavior before changing configuration or promising that a particular editing workflow will be preserved.

If a content type does not support revisions, a configured revision limit cannot create that support by itself. Similarly, changing the autosave interval does not establish that every editor or custom content type will use autosave in the same way as standard WordPress content.

Configuration safety and independent recovery

Before editing wp-config.php, take a current backup and retain a rollback copy of the file. Ensure that you can access the site through an appropriate administrator or hosting-level channel. Make changes carefully, because an incorrect configuration edit can affect site loading or other site behavior.

After changing AUTOSAVE_INTERVAL or WP_POST_REVISIONS, check the relevant editing workflow. Confirm that the expected content type behaves as intended and that editors understand whether they are relying on autosave, revisions or another recovery process.

Autosave and revisions are content-management features, not a complete disaster-recovery strategy. They should not be presented as protection against hosting failure, database corruption, malware or accidental deletion of the entire site. Independent backups and tested recovery procedures remain separate operational safeguards.

WordPress autosave protects active editing work, while post revisions provide saved-version rollback. AUTOSAVE_INTERVAL changes the autosave timing in seconds, with a documented default of 60 seconds when it is not set. WP_POST_REVISIONS can leave revisions unlimited, define a numeric maximum or disable them, but the right retention choice is site-specific rather than universal. When editors need recovery history, a defined limit generally preserves more capability than disabling revisions. Before changing either setting, check custom post types and third-party editors, back up the site and keep a rollback copy of the configuration. Explore our WordPress plugins, WooCommerce extensions, themes and membership plans to find the right tools for your website.

One comment

  1. uZ8rlF0ykP7dzW5kxD3zdJ6ng_soobshenie

Comments are closed.

Free Worldwide shipping

You can download the products right away at wpbetterplugins.com

Immediate delivery

After the payment is credited, the product is ready for download

International Warranty

Offered in the country of usage

100% Secure Checkout

Stripe / Apple Pay / Google Pay / MasterCard / Visa

Zadzwoń