> For the complete documentation index, see [llms.txt](https://docs.carto.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.carto.com/carto-self-hosted/concepts/object-storage.md).

# How CARTO uses Object Storage (blob buckets)

Understand how CARTO uses object storage (blob buckets) across cloud providers

## Overview

CARTO Self-Hosted uses **object storage** (also called blob storage or bucket storage) to handle data and assets used by the platform: imported datasets, generated map thumbnails, customization assets, and optionally data exported from your data warehouse.

You provide and manage these buckets in your own cloud account. CARTO connects to them using the credentials and configuration you supply. Supported storage providers:

| Provider                   | Service name                      |
| -------------------------- | --------------------------------- |
| Google Cloud               | Cloud Storage (GCS)               |
| Amazon Web Services        | Simple Storage Service (S3)       |
| Microsoft Azure            | Azure Blob Storage                |
| Any S3-compatible provider | Oracle OCI, OVH, Ceph, and others |

{% hint style="info" %}
**S3-compatible storage.** Any store that speaks the S3 API works, including on-premises and sovereign-cloud providers. You configure it as S3 and point CARTO at your own endpoint — see [Configure your own buckets](/carto-self-hosted/configuration/data-and-storage/configure-your-own-buckets.md).
{% endhint %}

## What CARTO stores in object storage

Every CARTO Self-Hosted installation uses two mandatory buckets and one optional bucket. The names shown in the Admin Console (Kots) and in `customizations.yaml` (Helm) are different. Use the tab for your deployment method:

{% tabs %}
{% tab title="☸️ Kots (Admin Console)" %}

| Bucket            | Required | Purpose                                                                            | Example contents            |
| ----------------- | -------- | ---------------------------------------------------------------------------------- | --------------------------- |
| **Temp Bucket**   | Yes      | Upload and import datasets into CARTO                                              | `.csv`, `.geojson`, `.zip`  |
| **Assets Bucket** | Yes      | Generated map thumbnails and customization assets (logos, markers, etc.)           | `.png`                      |
| **Export Bucket** | Optional | Export data from your data warehouse — create only if you use data export features | `.csv`, `.json`, `.parquet` |
| {% endtab %}      |          |                                                                                    |                             |

{% tab title="🛞 Helm (customizations.yaml)" %}

| Bucket                | Required | Config key                                                   | Purpose                                                                            | Example contents            |
| --------------------- | -------- | ------------------------------------------------------------ | ---------------------------------------------------------------------------------- | --------------------------- |
| **Import Bucket**     | Yes      | `workspaceImportsBucket`                                     | Upload and import datasets into CARTO                                              | `.csv`, `.geojson`, `.zip`  |
| **Thumbnails Bucket** | Yes      | `workspaceThumbnailsBucket`                                  | Generated map thumbnails and customization assets (logos, markers, etc.)           | `.png`                      |
| **Export Bucket**     | Optional | `workspaceExportsBucket` (BigQuery) / `awsExportBucket` (S3) | Export data from your data warehouse — create only if you use data export features | `.csv`, `.json`, `.parquet` |
| {% endtab %}          |          |                                                              |                                                                                    |                             |
| {% endtabs %}         |          |                                                              |                                                                                    |                             |

{% hint style="info" %}
Objects in the **assets / thumbnails** bucket (such as map thumbnails) are publicly readable by default, so features like custom branding and map markers render correctly. The import/temp and export buckets are private.
{% endhint %}

## Ownership and management

The buckets are part of **your** infrastructure: you create them, control access to them, and manage their lifecycle and cost. CARTO only reads from and writes to them using the access you grant. This keeps full ownership of the stored data with your organization.

## Next steps

* [Object Storage prerequisites](/carto-self-hosted/planning/prerequisites/object-storage.md) — what to provision before deploying
* [Configure your own buckets](/carto-self-hosted/configuration/data-and-storage/configure-your-own-buckets.md) — step-by-step configuration guide


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.carto.com/carto-self-hosted/concepts/object-storage.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.