What Is It?
Images & Snapshots provide the images used to provision Block Storage volumes. Use IONOS CLOUD public images, upload your own private images via FTP, or take snapshots of provisioned Block Storage and create new volumes from them. Snapshots are full, non-incremental copies stored in Essential quota, while images serve as templates for VM provisioning with support for Live Vertical Scaling (LVS) and UEFI or virtual CD-ROMs for application installation.
Quick Facts
| Aspect | Details |
|---|---|
| Snapshot Type | Full copy (not incremental) |
| Storage | Consumes Essential quota (full volume size, regardless of data used) |
| Scope | Data center location-specific, usable across VDCs in same location |
| Source | Any provisioned Block Storage (Essential, Balanced, Performance, or DAS NVMe) |
| Image Types | Public (IONOS CLOUD provided: Alma, Debian, Rocky and Ubuntu Linux, SLES (BYOS), RHEL, Windows Server 2019 to 2025, MS SQL Server 2019, 2022 and 2025), Private (uploaded via FTP), ISO images for a virtual CD-ROM drive |
| UEFI Support | Snapshots and images can be UEFI-compatible |
| Live Vertical Scaling | Supported by all images (Windows: CPU cores only) |
| Cloud-Init | Linux only: all public Linux images, and private Linux images that include Cloud-Init; not for Windows images; set at initial provisioning only |
Image Types
| Type | Boot Mode | Availability | Features |
|---|---|---|---|
| Public Images | BIOS/UEFI (automatic) | IONOS CLOUD provided | LVS enabled, OS type included, UEFI-compatible (Windows), BIOS/UEFI (Linux) |
| Private Images | MBR upload via FTP; UEFI-bootable and marked UEFI-compatible for UEFI data centers | User-uploaded via FTP | Must be UEFI-bootable before upload to boot in UEFI data centers (Intel Sierra Forest, AMD EPYC Turin) |
What You Can Do
Create Snapshots
Take point-in-time copies of any Block Storage volume. Snapshot uses entire volume size (a 100 GiB volume creates a 100 GiB snapshot, even if only 10 GiB is used). Snapshots are full, independent copies, not incremental.
Note: Make sure enough Essential quota is available before you create a snapshot.
Share and Control Access
Share snapshots with groups in the Security tab (Visible to Groups: Add Group or Remove Group); Visible to Users shows the users who already have access. Enable 2-Factor Protection to restrict access to users with 2FA enabled.
Edit Snapshot Metadata
Update editable fields including Name, Description, OS Type, Live Vertical Scaling settings (CPU, RAM, hot-plug NIC/VirtIO), and UEFI support flag. Changes saved via Meta Data tab.
Upload Private Images
Upload custom images via FTP or FTPS to the upload server of each data center location (MBR-boot images only): HDD images in vmdk, vhd, vhdx, cow, qcow, qcow2, raw, vpc or vdi format, and ISO images. Private images must be UEFI-bootable before upload if targeting UEFI-enabled data centers. To move an existing legacy BIOS image to UEFI, back it up with Backup Service, restore it onto a UEFI target VM, then set UEFI Support to Image is UEFI-compatible in the DCD.
Reuse Across VDCs
Use snapshots in any Virtual Data Center within the same data center location. Snapshots cannot be used across different geographic locations.
Cloud-Init Integration
Inject user-data scripts or cloud-config at provisioning time. Images with Cloud-Init enabled support automated configuration during VM startup.
Manage Lifecycle
Create snapshots (requires Create Snapshots privilege), view via Snapshots tab, update metadata as needed, and delete when no longer required. Deleted snapshots cannot be restored.
Note: Authentication settings specified during snapshot creation are stored with the snapshot and not altered by IONOS CLOUD. Snapshots cannot be edited to change authentication, so change the authentication on the source volume before you take the snapshot.
Best For
| Scenario | Why It Fits |
|---|---|
| Fast VM cloning | Quick rollout of multiple VMs with identical configuration from single snapshot |
| Recovery points | Recovery point for rollback in the same location; for off-site disaster recovery, add Backup Service or Object Storage |
| Development/testing | Create baseline snapshots before changes, restore if needed |
| Template management | Custom images for standardized deployments across teams |
| Migration to UEFI | Transition private images to UEFI for modern data center compatibility |
Key Considerations
Billing & Costs
- Main billing: Per GB of snapshot storage, 0.04 EUR per GB per 30 days (same rate as Essential)
- Storage consumption: Snapshots use the full volume size, not actual data used; uploaded private images are not charged and do not use your resource quota
- No retention limits: Snapshots persist until manually deleted (ongoing cost)
- Licensing: Bring-Your-Own-License is not supported. Windows Server and RHEL licenses are provided and charged by IONOS CLOUD, also when a VM boots from a private image with such an OS. SLES public images use Bring Your Own Subscription (Berlin and Frankfurt only)
Limitations
- Snapshots are full copies, not incremental (each snapshot consumes full volume size)
- Snapshots and private images are limited to the data center location where they were created or uploaded (cannot move across regions)
- Sufficient Essential quota required before snapshot creation
- Private image upload via FTP supports MBR-boot images only; to boot in UEFI data centers the image must also be UEFI-bootable and marked UEFI-compatible
- UEFI-enabled data centers require UEFI-bootable images
- Authentication settings are stored with the snapshot and cannot be changed afterwards; change them on the source volume before taking the snapshot
- Deleted snapshots cannot be restored
- Windows LVS supports CPU core scaling only (not full LVS)
Management Options
- Data Center Designer (DCD)
- Snapshots tab for viewing and management
- Security tab for sharing and access control
- Meta Data tab for editing snapshot properties
- FTP upload for private images
- Cloud API and SDKs