---
title: "Export an image to Object Storage"
description: "Copy a saved image into an E2E Object Storage bucket as a raw disk file, to keep a copy outside the platform or to move the image to another region."
content_type: "how-to"
product: "images"
platform: "MyAccount"
url: "/myaccount/images/how-to/export-an-image/"
topic: ["import-and-export"]
relationships: {"requires":["/myaccount/object-storage/how-to/generate-an-access-key/"]}
---

# Export an image to Object Storage

Exporting a saved image writes a copy of it into one of your E2E Object Storage buckets, as a
single raw disk file. Use it to keep a copy of the image outside the Saved Images list, to
download it to your own servers, or to move the image to the other region, where you import the
file again.

## Before you begin

You need:

- A saved image in Delhi or Chennai that reads **Ready** or **Available** in the **State** column.
  It must be saved from an unencrypted node.
- A bucket in Delhi or Chennai to receive the file. You can also create one from the export
  panel.
- An access key attached to that bucket with the **Bucket Admin** or **Bucket Writer** role. The
  export writes a file, which a **Bucket Reader** key cannot do. See [Generate an access
  key](/myaccount/object-storage/how-to/generate-an-access-key/) to create one and attach it.

The file is stored in your bucket like any other object, and you pay for its storage there.

## Export the image

1. On the **Nodes** page in MyAccount, click **Saved Images**. Find the image and open its
   **Actions** menu.
2. Click **Export To Object Storage**. A panel of the same name opens on the right of the page.
3. In **Region**, choose where the bucket is: **Delhi-NCR** or **Chennai**. To move the image
   to the other region, choose that region here.
4. In **Bucket Name**, choose the bucket. The list shows your buckets in the region you chose. To
   use a new bucket, choose **Create New Bucket…** at the end of the list; **Create Storage Bucket**
   opens without leaving the panel. A new bucket starts with no access key, so attach one before you
   export: in Object Storage, open the new bucket's **Permissions** tab, click **Attach Access
   Key**, attach your key with **Bucket Admin** or **Bucket Writer**, and then start the export
   again.
5. Enter the **Access Key** and **Secret Key** of the key attached to the bucket. The secret key
   is shown only once, when the key is created; if you no longer have it, create a new key and
   attach that one instead.
6. Click **Confirm**.

E2E first checks that the keys can reach the bucket. If they cannot, the export is refused with
**Access Denied.** Check that you copied both keys correctly, and that the key is attached to
this bucket with a role that can write.

## Check that the export finished

An export takes a few minutes, longer for a larger image. The image's **State** reads
**Exporting** until it finishes, and most of its other actions stay unavailable until then. You
get an email when the export finishes, whether it worked or failed.

To see the result, open the bucket and its **Objects** tab. The export is one file at the top
level of the bucket, named after the image, its region, and the time the export started:

```text
web-base_Delhi_20260923101500.raw
```

E2E can import a raw file, so you can bring this one straight back in; see
[Import a custom image](/myaccount/images/how-to/import-a-custom-image/).

## Move the image to the other region

To move an image between Delhi and Chennai, carry it through Object Storage.

1. Export the image to a bucket in the region you want it in, as described in
   [Export the image](#export-the-image).
2. At the top of MyAccount, switch to that region.
3. Import the exported file there, as described in
   [Import a custom image](/myaccount/images/how-to/import-a-custom-image/). In Delhi, the
   **Private EOS Bucket** tab reads the file with your access key and the bucket stays private.
   In Chennai, use the **Public URL** tab, which needs **Download** turned on for the bucket
   until the image reads **Ready**.

The image then appears on the **Saved Images** page of the new region, under the name you gave
it with a number added, such as web-base_I-48213377, ready to launch nodes from. Once it reads
**Ready**, E2E holds its own copy: turn **Download** off again if you turned it on, and delete
the `.raw` file if you no longer need it in the bucket.

If an export will not start or does not finish, see
[Troubleshooting image import and export](/myaccount/node/troubleshooting/image-import-export/).