Skip to content
Exepad Docs

Versions & rollback

Publishing is safe partly because it’s never a one-way door. Each time you publish, Exepad keeps a copy of that exact release. If a new version turns out to have a problem, you can bring an earlier one back and publish it again — without losing your work.

Every release is saved

Section titled “Every release is saved”

Think of each publish as a snapshot of your app at that moment. Your first publish is one snapshot; publishing again creates another, and so on. Exepad keeps this history for you automatically — there’s nothing to set up and nothing to remember to save.

Each saved release notes when it went live, so you can tell your versions apart and find the one you want.

Putting an earlier version back

Section titled “Putting an earlier version back”

If something’s wrong with what’s live — a change didn’t land the way you expected, or you spot a mistake after publishing — you don’t have to fix it under pressure. Putting an earlier version back takes two quick steps:

  1. Restore the earlier release — Exepad brings that version back into your draft (your private working copy).
  2. Publish it — that puts the earlier, working version back in front of your visitors.

Your live app doesn’t change until you publish, so you stay in full control of exactly what people see.

How this relates to your draft

Section titled “How this relates to your draft”

Your draft is your private working copy — the version you’re actively editing. Your live app is whatever you last published. They’re separate:

  • Restoring an earlier version changes your draft; it doesn’t change what’s live on its own.
  • Your live app updates only when you publish — at which point your current draft becomes the new live release, added to the history alongside the others.

For the moment-to-moment history of edits while you build (before publishing), see Version history. This page is about the versions you’ve published and shared.

Next steps

Section titled “Next steps”