> 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-user-manual/maps/data-sources/pre-generated-tilesets.md).

# Pre-generated tilesets

Pre-generated tilesets are sources with tiles that have been previously generated using either the [CARTO Analytics Toolbox](/data-and-analysis/analytics-toolbox-for-bigquery/key-concepts/tilesets.md) or [Workflows](/carto-user-manual/workflows/components/tileset-creation.md). Both the creation and storage of these tilesets occur in the data warehouse. This type of data source is ideal for managing very large, static datasets. They are efficient, cost-effective, and provide high-performance visualization.

<figure><img src="https://3029946802-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FybPdpmLltPkzGFvz7m8A%2Fuploads%2Fgit-blob-8e3d36be4bafb6487f53d0187323ce2850c81a2c%2Fpre-generated%20tilesets.gif?alt=media" alt=""><figcaption></figcaption></figure>

## Visualizing pre-generated tilesets

Builder supports the visualization of the four types of pre-generated tilesets:

* **Vector Tilesets:** Pre-generated tilesets processed from point, line, or polygon tables for smooth, interactive maps.
* **Point Aggregation Tilesets**: These tilesets aggregate point data with their properties into tilesets, perfect for visualizing dense point clusters.
* **Quadbin Aggregation Tilesets**: Aggregated grid for scallable hierarchy management.
* **H3 Aggregation Tilesets:** Aggregate quadbin indices into tilesets for scallable spatial hierarcy management.

To ensure optimizal visualization and performance, you must make use of the different parameters that allow you to have full-control of the tileset specification. To learn more about this type of source in terms of performance consideration, review this [section](/carto-user-manual/maps/performance-considerations.md).


---

# 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-user-manual/maps/data-sources/pre-generated-tilesets.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.