How to protect your WordPress content with Spectersync

Spectersync wasn’t built as a backup tool. It was built to let you edit WordPress posts in the browser — by hand or with an AI recipe — and publish back safely. But because it pulls your whole archive into a clean, structured copy and keeps a snapshot behind every publish, it gives you a real safety net for the part of WordPress you can least afford to lose: the words. This guide is about that — what it covers, what it doesn’t, and how the two editions differ. Subscribe now and your workspace opens with 500 free credits; browsing and reviewing are free.

What people usually mean by “WordPress backup”

There are two very different things called a backup in the WordPress world, and they get conflated in marketing copy all the time.

The first is a full site backup: themes, plugins, the database, uploaded media, the wp-config.php and .htaccess files. This is what UpdraftPlus, BackupBuddy, your host’s nightly snapshot, and a handful of other tools do. If your server is wiped, you restore the full backup and the site comes back as it was. This is the kind of backup you absolutely need, and Spectersync is not that. Keep your full-site backup running.

The second is a content backup: the words. The posts and pages you actually wrote. The thing that took you years to produce and that no plugin reinstall can re-create. This is the part Spectersync protects — as a clean, structured copy in your workspace, plus a snapshot behind every change you publish.

Both backups matter. They protect against different failures. This guide is about the second.

Why Spectersync protects the part you wrote

A few properties that turn out to matter more than you’d think:

• Clean, structured copy. Every post lands in your workspace as plain prose with its metadata intact — title, slug, status, categories, tags, dates, featured-image URL, meta title, meta description. Not locked in a database format you’d need a running WordPress to read.
• A snapshot behind every publish. When you publish a change, Spectersync keeps a snapshot of what came before. Reverting a bad edit — yours or an AI recipe’s — is a decision, not a recovery project.
• Conflict-safe. If a post changed on both sides since the last sync, Spectersync pauses and asks rather than silently overwriting one with the other. You don’t lose work to a clobber.
• Recoverable in place. If you need to restore a post, you publish the good version back to WordPress over the REST API. The same machinery that runs the bulk SEO sweep puts a post back the way it was.

If you haven’t connected your site yet, the connect guide walks through it. The setup is a one-time thing — Application Password, connect, done.

What this protects against (and what it doesn’t)

The realistic list of failure modes Spectersync saves you from:

• A plugin update wrecks a bunch of posts. Restore the good version from the snapshot, publish it back.
• An AI editing pass goes wrong. If you’re following the AI editing workflow, the diff catches most of it before it ships — and the snapshot is your undo button for the rest.
• A contributor overwrites a post. The conflict prompt flags it before it lands, and the snapshot holds the prior version.
• You decide to migrate away from WordPress entirely. Your content is already a clean, structured copy — a far better starting point for a migration than a SQL dump.

The failure modes it does not cover:

• Themes, plugins, custom code. Not in scope. Use a real site backup for these.
• Uploaded media files. Featured images are referenced by URL, but the binary files themselves live on your server’s media library. A real backup grabs the wp-content/uploads directory.
• Database tables outside posts and pages. Comments, users, settings, custom post types. Again — real site backup.
• A hostile takeover of your WordPress admin. Spectersync publishes to WordPress with your credentials. If someone else has those, it won’t save you from them pushing junk.

The mental model

Run a real WordPress backup for the site as a whole. Run Spectersync for the words. The first protects you from infrastructure failure. The second protects you from losing the thing you actually made — and as a bonus gives you the workspace you need for every other job on this site, from a quick edit to a full bulk SEO sweep across the archive.

Want it as files on your own disk, in git?

Some people want the stronger guarantee: every post as a plain .md file on their own machine, in a git repository they can git log, git diff, and push off-site to GitHub — a continuous, versioned, three-places-at-once content backup. That’s exactly what the desktop and open-source edition is for: the engine runs locally, your content is files on disk, and nothing routes through our servers. The hosted webapp is the fastest way in; the desktop edition is the one to reach for when the backup is the point. Subscribe now →