> For the complete documentation index, see [llms.txt](https://docs.glesys.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.glesys.com/products/storage/archive-storage/how-tos/create-an-archive.md).

# Create an archive

***

## Create an archive using the control panel

To create your archive, click on **Archives** in the left-hand menu and then click **Create Archive**.

<figure><img src="/files/vKJQOWGcOVvGza10X2TP" alt=""><figcaption></figcaption></figure>

In the dialog box that opens, enter a username for the storage. The username will consist of the project name and the name you specify, for example, *cl43212\_glesys* if you choose *glesys* as the name.

You also need to choose a password to protect the archive. If you can't think of a password, you can generate one by clicking the **Generate** button. Finally, select the size of the archive. The price of the archive will update as you select the size.

Once you’ve made all the selections, click **Create**.

<figure><img src="/files/nF5aMUu5v2FI7MATmK4g" alt=""><figcaption></figcaption></figure>

The archive is now ready for use.

## Create an archive using the API

To create an archive using the [API](/platform/control-panel/api.md), use the [archive/create](https://github.com/GleSYS/API-docs/wiki/API-Documentation#archivecreate) endpoint.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.glesys.com/products/storage/archive-storage/how-tos/create-an-archive.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.