Server Snapshots vs Golden Images: Which to Build From

For most multi-server setups, adding capacity means ordering a server, waiting for it, installing everything, copying configuration from an existing one and testing. That is usually days of work, which is why it tends to happen after a slowdown rather than before one.

The faster way is to launch new servers from an image. There are two kinds of image people use, and they behave very differently: a snapshot of an existing server, and a golden image built on purpose as a template. This guide explains the difference, when each one fits and how to build your first golden image. The glossary covers snapshot and image if you want the short definitions.

What a server snapshot is

A snapshot captures one server exactly as it is at a moment in time: the operating system, installed software, configuration, data, logs and everything else on the disk.

It is quick. One click or one command, and you have a copy.

It is complete. Nothing is left out, which is what you want before a risky change.

It carries everything with it. That includes things that should be unique to one server: its hostname, SSH host keys, machine identifier, logs, temporary files and any credentials stored on disk.

That last point is why snapshots make good rollback points but awkward templates. Launch five servers from one snapshot and you get five copies of one server's identity and history.

What a golden image is

A golden image is a template built on purpose. It contains the operating system, the software every server in a role needs and the standard configuration, and nothing specific to any one server.

It is clean. No logs, no unique keys, no leftover data. Each new server generates its own identity at first boot.

It is repeatable. It is built from a written list of steps, ideally a script, so you can rebuild it next month with updates applied.

It is versioned. "web-2026-11" is a known starting point. You know what is in it and when it was made.

Per-server details such as hostname, role-specific settings and secrets are added when each server launches, usually by a first-boot tool such as cloud-init or by configuration management.

Use both. Snapshot a server before you change it. Launch new servers from a golden image.

If you want an environment where launching a new server from an image is routine, our pricing page shows what each InMotion Cloud Virtual Private Cloud plan includes.

Why golden images help with more than speed

Every server starts identical. That solves firewall and configuration drift at the source, because new servers do not inherit one-off changes from an old one.

Replacing a broken server becomes routine. Rather than repairing a server in place, launch a fresh one from the image and retire the old one.

Patching gets easier. Rebuild the image with updates each month, then roll new servers in and old ones out.

How to build your first golden image

1. Write down your last server build. Every step, from the operating system install to the last configuration change. That list is the first draft of your image.

2. Start from a clean base. A fresh operating system image from your provider, not an existing server.

3. Apply the common steps. Install packages, add standard configuration, set up monitoring agents and harden the defaults. Script it if you can, so the next build is identical.

4. Leave out anything server-specific. Hostnames, IP addresses, secrets and application data get added at launch, not baked in.

5. Clean up before saving. Remove logs, shell history, temporary files, SSH host keys and the machine ID so each new server generates its own.

6. Save, name and test it. Save the image with a dated name, launch a test server from it and check it comes up correctly.

The quick check

Time how long your last new server took, from the decision to add it to the moment it took real traffic. If it was more than a day, that is how far behind you will be the next time traffic jumps.

Then look at how it was built. If the answer is "copied from the old one and fixed what broke", you have been building from snapshots, and every new server has inherited the old one's history.

How InMotion Cloud handles this

On InMotion Cloud, your servers run as virtual machines, and both approaches are built in. You can take instance snapshots before changes, save and manage your own images with our guide to creating and managing images, and launch new servers from them in minutes. If a server misbehaves, you can rebuild it from an image rather than repairing it in place.

What goes into your image is still your decision. Our engineers can help you turn your last server build into a golden image you can reuse.

Summary

A snapshot copies one server as it is, which makes it a good rollback point and a poor template. A golden image is a clean, repeatable starting point for every new server in a role. Snapshot before changes, launch from golden images, and rebuild the image regularly so new servers start up to date.

Frequently asked questions

What is the difference between a snapshot and a golden image? A snapshot is a copy of one server at a moment in time, including its unique identity and data. A golden image is a clean template built on purpose for launching many identical servers.

Can I use a snapshot as a template? You can, but every server launched from it inherits the original's hostname, keys, logs and leftovers. Clean it up first or build a proper golden image.

How often should I rebuild a golden image? Regularly, often monthly, so new servers start with current updates. Version each build with a date in its name.

What should never go into a golden image? Passwords, API keys, application data, hostnames, SSH host keys and logs. Add per-server details at launch instead.