WordPress Revisions Restore Page — Practical Guide for SA Businesses

The wordpress revisions restore page feature is WordPress's built-in safety net — on each save, WordPress writes a copy to its database so you can roll back to any earlier version without touching a backup plugin. It works for accidental overwrites, copy-and-paste disasters and mid-edit reformats.

For South African site owners managing their own WordPress websites, understanding exactly what revisions can and cannot recover — and how to stop them from bloating a shared-hosting database — saves both content and server resources.

This guide covers the step-by-step restore process for the block editor (WordPress 7.0+), the classic revisions screen (WordPress 6.9 and earlier), and Elementor's separate history panel. It also shows you the two wp-config.php constants that control revision storage, with a clear decision table for knowing when to rely on revisions and when you actually need a full backup restore.

How WordPress Revisions Work Under the Hood

WordPress revisions are stored as rows in the same database table as your posts and pages (wp_posts), each assigned a post_type of revision and linked back to the parent page via a post_parent pointer. Each click of Save draft, Update or Publish writes a full copy of the title, content and excerpt to a new revision row.

Separately, WordPress autosaves your work every 60 seconds while you're editing, using a background Ajax call. Autosaves behave differently from regular revisions: there is only ever one autosave stored per user, per page. New autosaves overwrite old ones, so the database does not grow by one row every minute — it stays at one autosave row per user regardless of how long the editing session runs. Autosaves appear in the revision timeline labelled "Autosave" and are separate from regular revision entries.

This distinction matters for South African site owners. During load-shedding, if your browser session dies mid-edit, the 60-second autosave means you lose at most a minute's worth of changes. On your next visit to the editor, WordPress shows a prompt offering to restore the autosave — accept it if the power cut happened before you could save manually. The simplest approach to undo changes WordPress page editors make in a rush is always the revisions panel — no plugin or backup restore required.

WordPress Revisions Restore Page or Post: Step-by-Step

The wordpress revisions restore page process varies slightly depending on your WordPress version. According to the official WordPress revisions documentation, WordPress 7.0 introduced a redesigned revisions screen; earlier versions use the classic two-pane comparison layout. Both are accessible from the same place in the editor.

Block Editor — WordPress 7.0 and Later

1. Open the page or post you want to roll back in the WordPress editor.
2. Open the Settings sidebar (top-right gear icon if it's not already visible).
3. Click the Page or Post tab in the sidebar.
4. Click the number next to Revisions (e.g. "12 Revisions") — this opens the new revisions screen.
5. Use the slider at the top to move through saved versions, or click directly in the Revision panel list to jump to a specific date and time.
6. Review the colour-coded changes: solid green = blocks added, red diagonal stripes = blocks removed, yellow diagonal stripes = blocks modified.
7. When you find the version you want, click Restore.

Restoring does not delete your current version. WordPress saves the restored content as a brand-new revision at the top of the history, so if you change your mind you can restore forward again.

Classic Revisions Screen — WordPress 6.9 and Earlier

1. Open the post or page for editing.
2. In the sidebar panel, click Revisions to open the classic revisions screen.
3. Use the slider or the Previous / Next buttons to step through versions. The left pane shows the older version; the right pane shows the newer one.
4. Enable Compare any two revisions mode (checkbox at the top) if you want to compare non-adjacent versions — this adds a second slider handle.
5. Click Restore This Revision when you find the right version.

Restoring Revisions in Elementor

If you build pages with Elementor, revision history is handled inside the Elementor editor rather than in the standard WordPress revisions screen. Elementor maintains two separate logs: Actions (changes made in the current session only) and Revisions (saved versions that persist when you close and reopen the editor).

To restore a previous Elementor design:

1. Open the page in Elementor (Edit with Elementor).
2. In the left toolbar, click the History icon (clock/history symbol).
3. Select the Revisions tab at the top of the panel.
4. Browse the timestamped entries and click the version you want to preview.
5. Click Apply to restore that version instantly.

Elementor-hosted sites store the 25 most recent revisions per page. For self-hosted WordPress with Elementor installed, the number of revisions available depends on your WordPress revision settings and how frequently you saved.

Controlling Revision Storage in wp-config.php

On a self-hosted WordPress site, revisions accumulate without limit by default. On shared SA hosting plans with capped database storage, a site with dozens of frequently edited pages and no revision limit can quietly exhaust its database allocation over months. Two constants in wp-config.php give you precise control.

Limit the Number of Revisions

Add this line to your wp-config.php file (before the line that reads "That's all, stop editing!"):

define( 'WP_POST_REVISIONS', 5 );

This keeps the five most recent revisions per post or page. When a new save pushes the count past five, WordPress automatically removes the oldest revision. A working rule of thumb for a content site is to keep enough revisions to cover a day's editing — five is a reasonable starting point, three is fine for rarely-edited service pages, and ten is appropriate for frequently updated news or blog posts.

If the limit appears to have no effect after saving, try moving the define() call to the very top of wp-config.php, immediately after the opening <?php tag — some server configurations require the constant to load before the rest of the file processes it.

Disable Revisions Entirely

define( 'WP_POST_REVISIONS', false );

Disabling revisions completely is an option for very low-resource environments, but it removes your ability to roll back any content change — use with caution, and only alongside a robust daily backup.

Adjust the Autosave Interval

define( 'AUTOSAVE_INTERVAL', 120 ); // seconds

The default is 60 seconds. Increasing the interval reduces database write frequency on slow shared servers; decreasing it below 60 seconds is possible on fast managed hosting — there is no documented minimum, so test any custom value and monitor server load before applying it to a live site. Since there is only one autosave row per user per post, this setting affects write frequency — not storage size.

WordPress.com users cannot access wp-config.php — the platform manages revision storage on your behalf according to your plan tier. If revision limits are a concern on WordPress.com, Jetpack's revisions guide reports that upgrading to a Business or eCommerce plan raises the ceiling to 100 revisions per page; verify current tier limits on WordPress.com's plan page before upgrading. For self-hosted sites, you can always restore page from WordPress revisions as long as the limit you set is large enough to include the version you need.

For broader questions about WordPress site maintenance in South Africa, including scheduled backups and update management, that guide covers the recurring tasks that sit alongside revision control.

When Revisions Cannot Help: Recovery Decision Table

Revisions recover content changes made inside the editor — they cannot reach data that was never stored as a revision row. Before spending time scrolling through revision history, check the table below to confirm revisions are the right tool for your situation.

If your loss falls in the "No" column, revisit your WordPress hosting setup and backup schedule. Most SA shared hosts include automatic daily backups — check your cPanel or hosting control panel before assuming the content is unrecoverable.

Why South African Businesses Choose Growth Pulse Media for WordPress

Our web design service is built around WordPress sites that operators can actually manage day-to-day — including understanding which native tools, like the revision system, are worth using and which gaps need a plugin or hosting-level solution.

Dirk van Greuning founded Growth Pulse Media after building and scaling a large South African ecommerce business, so the advice comes from someone who has navigated local hosting constraints, load-shedding-driven data loss risks and the practical limits of budget shared hosting — not from a textbook. All work is executed in-house; client load is kept limited so that senior attention remains on every project. We are a registered Shopify Partner and Omnisend Certified Partner.

When we configure a WordPress site for an SA operator, revision limits, autosave intervals and backup cadence are part of the initial setup conversation — not an afterthought left to the client to figure out. If your current site has never had that conversation, a WordPress activity log is a good starting point for understanding what's actually changing on your site over time.

Who WordPress Revisions Are NOT the Right Tool For

Three categories of WordPress site owner will find that revisions cannot solve their core problem: those running sites with no dedicated backup strategy, teams that need a structured content approval workflow, and operators on minimal shared hosting with uncapped database storage and no access to wp-config.php.

Frequently Asked Questions

How many revisions does WordPress keep by default?

By default, self-hosted WordPress stores an unlimited number of revisions for every post and page. There is no built-in cap unless you set one yourself in wp-config.php using define( 'WP_POST_REVISIONS', 5 ); or equivalent. Separately, only one autosave is stored per user per post at any time — autosaves overwrite themselves and do not contribute to revision accumulation. Jetpack's WordPress revisions guide reports that WordPress.com's hosted service limits revisions by plan: 25 for Free, Personal and Premium; 100 for Business and eCommerce — verify current limits on WordPress.com's plan page before upgrading.

Can I use WordPress revisions to restore a page I accidentally deleted?

Not with the revisions system alone. WordPress stores revisions as child rows of the parent post; when you delete a page, its revision rows are also removed. Check the Trash (Pages → Trash) first — pages sit in Trash for 30 days before permanent deletion. If the page is not in Trash, you need a database-level backup restore from your hosting control panel or a backup plugin.

What is the difference between an autosave and a WordPress revision?

A revision is saved each time you manually save (draft, update or publish) and accumulates indefinitely unless limited. An autosave happens every 60 seconds while you are actively editing; there is only ever one autosave stored per user per page, and it overwrites itself with each cycle. Autosaves are labelled separately in the revision timeline and appear as a recovery prompt the next time you open that page for editing. On save, the autosave is replaced by the new revision.

Do WordPress revisions slow down my website?

Unlimited revisions can inflate the wp_posts database table significantly on sites with many pages and frequent edits, which may slow database queries over time — particularly on shared SA hosting where database performance is shared across accounts. Setting a sensible limit in wp-config.php (typically three to ten revisions depending on edit frequency) and running a one-time database cleanup removes the accumulated rows. A well-sized revision limit has no measurable impact on front-end load time for visitors.

Can I restore a revision in Elementor without going through the WordPress revisions screen?

Yes. Elementor maintains its own revision history inside the editor, separate from the standard WordPress revisions screen. Open the page in Elementor, click the History icon in the left toolbar, select the Revisions tab, choose the version you want, and click Apply. Use the WordPress revisions screen when you need to recover content or metadata edited outside the Elementor editor — such as content changed in the block editor directly.

Dirk van Greuning Founder, Growth Pulse Media

Founder of Growth Pulse Media and a specialist in South African search dominance. Dirk translates his experience in scaling South African businesses into high-velocity digital strategies for B2B and retail leaders. He writes about SEO, lead generation, and paid media from an operator's perspective — prioritising pipeline value over impressions.

Connect on LinkedIn