[Yandex Cloud documentation](../../index.md) > [Yandex Compute Cloud](../index.md) > [Concepts](index.md) > Images

# Images

An _image_ is a complete copy of the file system structure and data on a disk.

It is designed to quickly create a data disk, primarily, a VM boot disk. Images can be used for distributing software, e.g., OS distributions or disks with pre-installed software.

You can use images with outdated OS versions on your VMs; however, you will not be able to get support for these VMs if you have any issues.

{% note tip %}

To regularly back up your data on disks, use [snapshots](snapshot.md).

{% endnote %}

Each image will get assigned a particular [virtualized hardware generation](hardware-generations.md) on which you can deploy a VM instance from that image. You can assign a particular hardware generation to an image only at the time of creating it.

Once the image is created, you cannot change the generation assigned to it. Instead, you can [create](../operations/image-create/create-from-image.md) a new image from the current one with another hardware generation assigned.

You can create an image from a [disk](../operations/image-create/create-from-disk.md), [snapshot](../operations/image-create/create-from-snapshot.md), or [another image](../operations/image-create/create-from-image.md). If you have an image file, you can [import](../operations/image-create/upload.md) it to Yandex Cloud.

You can use the management console to create images of network SSDs and HDDs. To create an image of a non-replicated SSD or an ultra high-speed network storage with three replicas (SSD), use the CLI, Terraform, or API.

When you create a Windows boot disk image, specify this in the operating system type. This is important for proper CPU emulation and calculating resource usage costs.

Supported formats: `Qcow2`, `VMDK`, `RAW`, and `VHD`.

## Image family {#family}

If you regularly update your images, you can group them into families. You can use the family name to find the latest image in the family.

{% note warning %}

All images belonging to the same family must be in the same folder.

{% endnote %}

> Let's assume you want to [upload](../operations/image-create/upload.md) an image of your operating system to Yandex Cloud. When creating an image, specify a family, e.g., `best-linux-distro`. This will allow other users to get the latest version of your operating system by specifying the family and image folder ID in the [request](../api-ref/Image/getLatestByFamily.md).

## Public images {#public}

{% note info %}

The terms and conditions of technical support for public images may differ. For more information, see the product page in [Yandex Cloud Marketplace](https://yandex.cloud/en/marketplace).

{% endnote %}

Public images are, e.g., [products and solutions from Yandex Cloud Marketplace](https://yandex.cloud/en/marketplace).

You can learn how to get a list of public images [here](../operations/images-with-pre-installed-software/get-list.md).

To make your image available to other Yandex Cloud users, grant them public access to it. To do this, assign the `compute.images.user` [role](../security/index.md) to the `All authenticated users` [public group](../../iam/concepts/access-control/public-group.md). However, the `compute.images.user` role does not grant permission to delete or edit your image.

## Images optimized for deployment {#images-optimized-for-deployment}

_The feature is at the [Preview](../../overview/concepts/launch-stages.md) stage._

{% note info %}

You can migrate both optimized and non-optimized images.

{% endnote %}

Use optimized images only if you have a lot of disks and deployments.

An image can be optimized for frequent VM deployments. This speeds up the deployment of VMs and enables you to quickly expand your computing power and use the relevant tools from your own image.

Fast deployment is achieved by using multiple layers for storing data in a storage. The first layer stores the image source data, while the second one stores user data. When creating VM disks from optimized images, the first layer is reused rather than copied to a new storage location every time. Disks created from optimized images run on VMs in the same way as disks created from regular images: they can be used as boot disks and are fully available for data storage. The performance of these disks does not differ from that of regular ones.

Regular images from Cloud Marketplace are already optimized for deployment. To optimize your image, select the **Optimization** option when uploading the image.

By default, optimized images have a zero [quota](limits.md#compute-quotas). To increase the [quota](https://console.yandex.cloud/cloud?section=quotas), contact [support](../../support/overview.md).

## Use cases {#examples}

* [Getting started with Packer](../tutorials/packer-quickstart.md)
* [Building a VM image with infrastructure tools using Packer](../tutorials/packer-custom-image.md)
* [Assigning a domain name to a web server VM](../tutorials/bind-domain-vm/index.md)
* [Migrating to Yandex Cloud with Hystax Acura](../tutorials/hystax-migration.md)

## See also {#see-also}

* Learn how to create a VM from a [custom](../operations/vm-create/create-from-user-image.md) or [public](../operations/images-with-pre-installed-software/create.md) image.
* [Setting up a custom disk image](../operations/image-create/custom-image.md)
* [Importing an image from a different cloud or folder](../operations/image-control/import.md)
* [Configuring image access permissions](../operations/image-control/access.md)