Custom images are Linux and Unix-like images you import to DigitalOcean. You can create Droplets based custom images, which lets you migrate and scale your workloads without spending time recreating your environment from scratch.
Images must be less than 100 GB uncompressed.
Windows images are not supported.
ISO images are not currently supported, but we’re considering ISO support in the future. In the interim, if you have an ISO image you want to use, you can create a new image using your VM software of choice and save it again in a supported format. For a detailed walk-through, see How to Create a DigitalOcean Droplet from an Ubuntu ISO Format Image.
Unlike stock images provided by DigitalOcean, Droplets created from custom images use DHCP to obtain an IP address from the DigitalOcean platform. The custom image’s network configuration doesn’t require any additional setup to use DHCP.
You cannot use IPv6 with Droplets created from custom images.
You cannot enable monitoring automatically during Droplet creation when using a custom image. Instead, enable monitoring manually.
You must add an SSH key when creating Droplets from a custom image. These Droplets have password authentication disabled by default and you cannot use the control panel to reset the root password.
Importing a custom image by URL will fail if the image is served by a CDN that doesn’t support HEAD requests. If you have trouble importing an image via a URL, try downloading the file and uploading it directly.
Droplets created from a custom image do not receive an anchor IP address and do not require one to use a reserved IP. When you assign a reserved IP address to a Droplet created from a custom image, the reserved IP is automatically mapped to the Droplet’s public IPv4 address instead of an anchor IP.
You cannot see the total storage used by custom images.
The image upload window does not correctly display the size of the image.