Re-image a VM with a fresh OS template while keeping the IP, attached volumes, and specs
Updated May 8, 2026Reinstall replaces the VM’s OS disk with a fresh OS template. The VM keeps its ID, public IPv4, attached volumes, and CPU/RAM/disk specs — everything else on the OS disk is destroyed.
Reinstall is destructive. The OS disk is wiped and all snapshots and backups of this VM are deleted. If you want to keep anything, take a snapshot to attached volumes or push to Object Storage first.
Disk size — base disk being wiped and reprovisioned scales with size (a 25 GiB disk is faster than a 480 GiB one)
First boot work — cloud-init / sysprep / OS first-boot configuration runs after the disk lands; some templates do more work on first boot than others
There’s no published SLA for reinstall duration. For reference: a fresh Ubuntu 24.04 on a 25 GiB disk typically completes in 1–3 minutes; a Windows Server 2022 on a 50 GiB disk typically takes longer due to sysprep. Plan for up to 10 minutes in worst-case scenarios so you don’t get nervous mid-rebuild. See Storage model for the survival matrix across reinstall, factory reset, and delete.
Pick the new OS template (or stay on the same one for a clean reinstall) and the version.
Same OS lineup as VM creation. Switch between Linux distros, jump from Linux to Windows, or stay put for a clean reinstall. The Marketplace tab is also available for pre-built application images.