WordPress Time Machine: Single File Restore Without a Full Rollback

One plugin file gets corrupted during a bad update, or a client accidentally overwrites their own homepage template — and the fix you actually need is one file back to how it was yesterday, not a full-site rollback that also undoes every other legitimate change made since then. WordPress single file restore exists for exactly that gap between “nothing’s wrong” and “roll back everything.”

Table of contents

• The gap a full-site restore leaves open
• How Time Machine actually works
• What’s browsable and restorable
• The real limitation worth knowing upfront
• When to reach for this instead of a full restore
• FAQ

The gap a full-site restore leaves open

A full-site restore is a blunt instrument by design — it puts everything back to exactly how it was at one point in time, which is correct when the whole site needs to go back, and badly wrong when only one thing broke. Roll back a whole site to fix one corrupted plugin file, and you also undo every legitimate post, comment, and setting change made since that backup — real work, discarded to fix a problem that only ever touched one file.

How Time Machine actually works

WP Warden’s Time Machine opens up one of your site’s existing backup archives and lets you browse its contents directly — individual files, specific plugins or themes, media, or even individual database tables — and pull back just the piece you actually need. It’s worth being precise about what this is: not a separate, continuously-running version history tracking every file change as it happens, but a way to reach into a backup you already have and take exactly one thing out of it, restored on its own, without touching anything else on the live site.

What’s browsable and restorable

Anything that was part of the original backup archive is fair game: a single plugin’s files if an update went wrong, a theme template a client accidentally broke, a media file that got deleted, or one specific database table if a plugin corrupted its own settings without touching the rest of the site’s content. Selecting just what you need and confirming runs synchronously — you get a result back directly, not a queued job you have to wait on and check later.

The real limitation worth knowing upfront

Two things are worth knowing before you rely on this in a real emergency. First, how far back you can reach is exactly as far as your backup retention goes — this isn’t an independent history separate from your regular backups, it’s a way to open the ones you already have. Second, it currently works against a backup’s local copy on the site itself; if the specific backup you need only exists in your off-site cloud storage with no local copy retained, that particular snapshot isn’t browsable this way. Practically, this means your most recent backups — the ones most likely to still have a local copy — are the ones you can count on for this kind of surgical restore.

When to reach for this instead of a full restore

• Use single file restore when: you know specifically what broke — one plugin, one theme file, one table — and everything else on the site is fine.
• Use a full backup restore when: you don’t know exactly what’s wrong, multiple things broke at once, or the site’s overall state needs to go back to a specific point in time, not just one piece of it.

FAQ

Does single file restore work if I only have cloud backups, not local ones?

Not directly — it currently requires a local copy of the specific backup you want to browse. If that snapshot is cloud-only, a full restore of that backup is the available path instead of a single-file pull from it.

Can I restore an entire plugin, not just one file inside it?

Yes — a whole plugin or theme’s file set is one of the restorable units, alongside individual files, media, and database tables, so you’re not limited to restoring one file at a time if the whole plugin needs to go back.

Is this the same thing as version control for WordPress?

No — version control tracks every change continuously with its own independent history. Time Machine works from your existing backup snapshots, so its granularity in time is however often those backups run, not a change-by-change history in between them.

Start a free 14-day trial and fix the one file that broke without touching everything else.

← Back to the Blog