Skip to content

Cloud Servers Updated 2026-07-22

Manage server snapshots

Review, manage, and delete point-in-time snapshots of your cloud servers from the Snapshots page in the console.

The Snapshots page lists every point-in-time snapshot the console holds for your cloud servers, grouped by the server each one belongs to. From here you review a server’s snapshot history, check the status and size of each snapshot, and delete the ones you no longer need.

Where to find it

In the console sidebar, open Infrastructure → Snapshots. The counter in the top-right (for example, 8 Snapshots) reflects the total across all of your servers.

What you can do here

  • Read the per-server list. Each server appears as its own card — a cloud icon, the server name (for example web-1e42), and a badge with the number of snapshots it holds. The table underneath lists that server’s snapshots, newest first.
  • See how a snapshot was created. The Type column records the origin. The snapshots here read Scheduled, meaning the console took them automatically on a recurring schedule.
  • Check status. The Status column shows Built once a snapshot has finished and is ready to use.
  • Check size. The Size column shows how much space a snapshot occupies, from a few hundred megabytes up to gigabytes for a fuller disk.
  • Delete a snapshot. The trash icon in the Actions column removes that single snapshot. This frees the space it used and cannot be undone, so keep any snapshot you might still want to restore from.
  • Open the server. The Manage button on a server’s card opens that server’s management view.

Creating and restoring

Taking a snapshot on demand and restoring a server from one are done from the server itself, not from this list — open the server with Manage, or from Infrastructure → Servers. This page is the inventory: what exists, and what to clear out.

Good to know

  • The Scheduled snapshots on this page double as your automated backups — they are the same recurring points, read through a different lens.
  • A snapshot captures the server’s disk at a moment in time. It is a fast way to roll back a bad change, not a substitute for exporting data you need to keep independently of the server.
  • Snapshots are tied to the server that created them. If a server is deleted, its snapshots go with it.
  • Sizes differ between snapshots because each reflects the amount of data on disk when it was taken. A larger jump — for example, a 1.6 GB snapshot next to ~150 MB ones — usually means more was written that day.
  • This area of the console is being expanded; the columns described above are what a snapshot row shows today.

To capture a snapshot on demand or restore a server from one, see Manage a server.