> 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/faqs/carto-basemaps.md).

# CARTO Basemaps

[Does CARTO provide a basemap service?](#does-carto-provide-a-basemap-service)

[What is the pricing for CARTO basemaps? Is it free?](#what-is-the-pricing-for-carto-basemaps-is-it-free)

[Why do I see an "API key required" watermark?](#why-do-i-see-an-api-key-required-watermark)

[Should I move from raster to vector basemaps?](#should-i-move-from-raster-to-vector-basemaps)

[How frequently does CARTO update its basemaps?](#how-frequently-does-carto-update-its-basemaps)

[Can I use other basemaps in CARTO?](#can-i-use-other-basemaps-in-carto)

***

### **Does CARTO provide a basemap service?**

Yes. We provide a basemap service using vector tiles, and we make them automatically available in all the components in the CARTO platform (Builder, Workflows, etc...), for all users.

We also serve a set of **raster (PNG) basemaps** at `basemaps.cartocdn.com`, which predate the vector service and are widely used from Leaflet and OpenLayers. These are still available, but they now require an API key and are being retired — see [Should I move from raster to vector basemaps?](#should-i-move-from-raster-to-vector-basemaps)

Our basemaps are also compatible with Maplibre GL JS, so that [developers using deck.gl and CARTO for Developers can make use of it in their own applications](/carto-for-developers/key-concepts/carto-for-deck.gl/basemaps.md).

The data for the CARTO basemaps is based on OpenStreetMap. Our basemaps are fully managed and powered by CARTO, including our own CDN, which makes them performant, scalable and customizable. Developers and users can choose between multiple [predefined basemap styles](https://github.com/CartoDB/basemap-styles), or even design their own styles following the *OpenMapTiles* specifications.

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

### **What is the pricing for CARTO basemaps? Is it free?**

**There is a free tier, and it is generous.** Anyone can [request an API key](https://carto.com/basemaps/apikey) and use CARTO basemaps free of charge up to a fair use limit of **5 million tile requests per calendar month**. You do not need a CARTO account, and you do not need to tell us in advance whether your project is commercial.

Two conditions apply to free use:

* **Attribution must stay visible.** CARTO and OpenStreetMap must be credited on every map, as described in [attributions](https://carto.com/attributions). This is what the free tier is in exchange for.
* **Your key is yours.** Keys are per-customer and must not be shared or reused across unrelated projects.

**Above the fair use limit**, we will normally get in touch rather than cut anyone off. What happens then depends on the use: if it is non-commercial we will usually raise the limit at no charge, and if it is commercial we may ask you to move onto a commercial agreement. To find out more about [pricing](https://carto.com/pricing/), [request a demo](https://carto.com/request-live-demo/) & we'll be able to discuss your use case with you.

Basemaps are also included at no additional cost with a CARTO Enterprise license or a [CARTO grant](https://carto.com/grants/), with limits set by your agreement rather than by the fair use limit above.

Full terms are in the [CARTO Basemaps Terms and Conditions](https://carto.com/legal/basemap-terms).

### **Why do I see an "API key required" watermark?**

If the tiles in your map are covered by a repeated **"API key required"** watermark, they are being requested from our raster basemap endpoint without an API key.

**Your map still works.** The watermark is a notice, not an outage, and nothing has been blocked.

**Why we did this.** CARTO has given these basemaps away for many years, and we would like to carry on doing that. The difficulty is that without a key we cannot tell who is using the service or how much — which means we cannot warn anyone before they hit a limit, cannot tell a student project apart from a company running a product on our tiles, and cannot plan the service properly. Keys fix that, and they let us set the free tier much higher than we could when usage was anonymous.

**How to remove it.** [Request an API key](https://carto.com/basemaps/apikey), then add it to your tile URL as a `key` parameter:

```
https://basemaps.cartocdn.com/rastertiles/voyager/{z}/{x}/{y}.png?key=YOUR_KEY
```

It is free within the fair use limit, it takes a minute, and you do not need a CARTO account.

**If you use basemaps inside the CARTO platform** — Builder or Workflows — this does not affect you and there is nothing to do.

**Please do not try to remove or hide the watermark.** Sections 6.b and 15.e of the [terms](https://carto.com/legal/basemap-terms) require that CARTO's notices and attribution stay visible, and a key is free — just ask us for one.

### **Should I move from raster to vector basemaps?**

**Yes, and we would recommend it regardless of the watermark.** Our vector basemaps are better on every axis that matters:

* **Sharper cartography** — crisp at any zoom level and on any display density, with no separate `@2x` request to think about.
* **Fresher data.** Vector basemaps are updated on a regular cadence. **We are considering stopping data updates to the raster basemaps**, in which case raster cartography will stay where it is and the gap will widen over time.
* **Restyleable at runtime.** Colours, labels and layer visibility can be changed in the browser instead of being baked into a PNG.
* **Cheaper and faster to serve**, which is a large part of how we can afford to keep the free tier generous.

**Only the raster basemaps are watermarked today.** Vector is unaffected. That said, **we recommend every basemap user request a key now**, whichever they use: we may extend the key requirement to vector in future, and having one already in place makes that a change you never notice rather than an interruption.

Migrating means moving from a tile-URL template to a MapLibre GL JS style URL:

```javascript
// Before — raster tiles in Leaflet
L.tileLayer('https://{s}.basemaps.cartocdn.com/rastertiles/voyager/{z}/{x}/{y}.png?key=YOUR_KEY', {
  attribution: '&copy; <a href="https://www.openstreetmap.org/copyright">OpenStreetMap</a>, &copy; <a href="https://carto.com/attributions">CARTO</a>',
  subdomains: 'abcd', maxZoom: 20
}).addTo(map);

// After — vector style in MapLibre GL JS
const map = new maplibregl.Map({
  container: 'map',
  style: 'https://basemaps.cartocdn.com/gl/voyager-gl-style/style.json?key=YOUR_KEY'
});
```

| Raster style          | Vector equivalent                                                  |
| --------------------- | ------------------------------------------------------------------ |
| `rastertiles/voyager` | `https://basemaps.cartocdn.com/gl/voyager-gl-style/style.json`     |
| `light_all`           | `https://basemaps.cartocdn.com/gl/positron-gl-style/style.json`    |
| `dark_all`            | `https://basemaps.cartocdn.com/gl/dark-matter-gl-style/style.json` |

Attribution requirements are unchanged — see [attributions](https://carto.com/attributions).

### **How frequently does CARTO update its basemaps?**

At a minimum, CARTO updates the underlying data for its **vector** basemaps **at least once a year,** including new roads, labels, areas, and other data points. Most years we provide updates every 3 or 6 months so that data is fresh and up-to-date, but the schedule and frequency is not guaranteed.

The **raster** basemaps are on the same data today, but as noted above we are considering stopping their data updates as part of retiring them. If you need current cartography, use the vector basemaps.

### **Can I use other basemaps in CARTO?**

Yes! While customers and grantees can automatically make use of our basemaps, you can use any other basemap service of your preference:

* CARTO provides out-of-the-box integration for [Google Maps basemaps in Builder](/carto-user-manual/maps/basemaps.md#google-maps-basemaps).
* Admins can configure [additional custom basemaps ](/carto-user-manual/settings/customizations/configuring-your-organization-basemaps.md)that will be available for their users in Builder
* Developers can integrate [any basemap provider in their CARTO + deck.gl applications](/carto-for-developers/key-concepts/carto-for-deck.gl/basemaps.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 dynamically by asking a question.

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

```
GET https://docs.carto.com/faqs/carto-basemaps.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.