LogoLogo
HomeAcademyLoginTry for free
  • Welcome
  • What's new
    • Q2 2025
    • Q1 2025
    • Q4 2024
    • Q3 2024
    • Q2 2024
    • Q1 2024
    • Q4 2023
    • Q3 2023
    • Q2 2023
    • Q1 2023
    • Q4 2022
    • Q3 2022
  • FAQs
    • Accounts
    • Migration to the new platform
    • User & organization setup
    • General
    • Builder
    • Workflows
    • Data Observatory
    • Analytics Toolbox
    • Development Tools
    • Deployment Options
    • CARTO Basemaps
    • CARTO for Education
    • Support Packages
    • Security and Compliance
  • Getting started
    • What is CARTO?
    • Quickstart guides
      • Connecting to your data
      • Creating your first map
      • Creating your first workflow
      • Developing your first application
    • CARTO Academy
  • CARTO User Manual
    • Overview
      • Creating your CARTO organization
      • CARTO Cloud Regions
      • CARTO Workspace overview
    • Maps
      • Data sources
        • Simple features
        • Spatial Indexes
        • Pre-generated tilesets
        • Rasters
        • Defining source spatial data
        • Managing data freshness
        • Changing data source location
      • Layers
        • Point
          • Grid point aggregation
          • H3 point aggregation
          • Heatmap point aggregation
          • Cluster point aggregation
        • Polygon
        • Line
        • Grid
        • H3
        • Raster
        • Zoom to layer
      • Widgets
        • Formula widget
        • Category widget
        • Pie widget
        • Histogram widget
        • Range widget
        • Time Series widget
        • Table widget
      • SQL Parameters
        • Date parameter
        • Text parameter
        • Numeric parameter
        • Publishing SQL parameters
      • Interactions
      • Legend
      • Basemaps
        • Basemap selector
      • AI Agents
      • SQL analyses
      • Map view modes
      • Map description
      • Feature selection tool
      • Search locations
      • Measure distances
      • Exporting data
      • Download PDF reports
      • Managing maps
      • Sharing and collaboration
        • Editor collaboration
        • Map preview for editors
        • Map settings for viewers
        • Comments
        • Embedding maps
        • URL parameters
      • Performance considerations
    • Workflows
      • Workflow canvas
      • Results panel
      • Components
        • Aggregation
        • Custom
        • Data Enrichment
        • Data Preparation
        • Generative AI
        • Input / Output
        • Joins
        • Parsers
        • Raster Operations
        • Spatial Accessors
        • Spatial Analysis
        • Spatial Constructors
        • Spatial Indexes
        • Spatial Operations
        • Statistics
        • Tileset Creation
        • BigQuery ML
        • Snowflake ML
        • Google Earth Engine
        • Google Environment APIs
        • Telco Signal Propagation Models
      • Data Sources
      • Scheduling workflows
      • Sharing workflows
      • Using variables in workflows
      • Executing workflows via API
      • Temporary data in Workflows
      • Extension Packages
      • Managing workflows
      • Workflows best practices
    • Data Explorer
      • Creating a map from your data
      • Importing data
        • Importing rasters
      • Geocoding data
      • Optimizing your data
    • Data Observatory
      • Terminology
      • Browsing the Spatial Data Catalog
      • Subscribing to public and premium datasets
      • Accessing free data samples
      • Managing your subscriptions
      • Accessing your subscriptions from your data warehouse
        • Access data in BigQuery
        • Access data in Snowflake
        • Access data in Databricks
        • Access data in Redshift
        • Access data in PostgreSQL
    • Connections
      • Google BigQuery
      • Snowflake
      • Databricks
      • Amazon Redshift
      • PostgreSQL
      • CARTO Data Warehouse
      • Sharing connections
      • Deleting a connection
      • Required permissions
      • IP whitelisting
      • Customer data responsibilities
    • Applications
    • Settings
      • Understanding your organization quotas
      • Activity Data
        • Activity Data Reference
        • Activity Data Examples
        • Activity Data Changelog
      • Users and Groups
        • Inviting users to your organization
        • Managing user roles
        • Deleting users
        • SSO
        • Groups
        • Mapping groups to user roles
      • CARTO Support Access
      • Customizations
        • Customizing appearance and branding
        • Configuring custom color palettes
        • Configuring your organization basemaps
        • Enabling AI Agents
      • Advanced Settings
        • Managing applications
        • Configuring S3 Bucket for Redshift Imports
        • Configuring OAuth connections to Snowflake
        • Configuring OAuth U2M connections to Databricks
        • Configuring S3 Bucket integration for RDS for PostgreSQL Exports in Builder
        • Configuring Workload Identity Federation for BigQuery
      • Data Observatory
      • Deleting your organization
    • Developers
      • Managing Credentials
        • API Base URL
        • API Access Tokens
        • SPA OAuth Clients
        • M2M OAuth Clients
      • Named Sources
  • Data and Analysis
    • Analytics Toolbox Overview
    • Analytics Toolbox for BigQuery
      • Getting access
        • Projects maintained by CARTO in different BigQuery regions
        • Manual installation in your own project
        • Installation in a Google Cloud VPC
        • Core module
      • Key concepts
        • Tilesets
        • Spatial indexes
      • SQL Reference
        • accessors
        • clustering
        • constructors
        • cpg
        • data
        • http_request
        • import
        • geohash
        • h3
        • lds
        • measurements
        • placekey
        • processing
        • quadbin
        • random
        • raster
        • retail
        • routing
        • s2
        • statistics
        • telco
        • tiler
        • transformations
      • Guides
        • Running queries from Builder
        • Working with Raster data
      • Release notes
      • About Analytics Toolbox regions
    • Analytics Toolbox for Snowflake
      • Getting access
        • Native App from Snowflake's Marketplace
        • Manual installation
      • Key concepts
        • Spatial indexes
        • Tilesets
      • SQL Reference
        • accessors
        • clustering
        • constructors
        • data
        • http_request
        • import
        • h3
        • lds
        • measurements
        • placekey
        • processing
        • quadbin
        • random
        • raster
        • retail
        • s2
        • statistics
        • tiler
        • transformations
      • Guides
        • Running queries from Builder
        • Working with Raster data
      • Release Notes
    • Analytics Toolbox for Databricks
      • Getting access
        • Personal (former Single User) cluster
        • Standard (former Shared) cluster
      • Reference
        • lds
        • tiler
      • Guides
      • Release Notes
    • Analytics Toolbox for Redshift
      • Getting access
        • Manual installation in your database
        • Installation in an Amazon Web Services VPC
        • Core version
      • Key concepts
        • Tilesets
        • Spatial indexes
      • SQL Reference
        • clustering
        • constructors
        • data
        • http_request
        • import
        • lds
        • placekey
        • processing
        • quadbin
        • random
        • s2
        • statistics
        • tiler
        • transformations
      • Guides
        • Running queries from Builder
      • Release Notes
    • Analytics Toolbox for PostgreSQL
      • Getting access
        • Manual installation
        • Core version
      • Key concepts
        • Tilesets
        • Spatial Indexes
      • SQL Reference
        • h3
        • quadbin
        • tiler
      • Guides
        • Creating spatial index tilesets
        • Running queries from Builder
      • Release Notes
    • CARTO + Python
      • Installation
      • Authentication Methods
      • Visualizing Data
      • Working with Data
        • How to work with your data in the CARTO Data Warehouse
        • How to access your Data Observatory subscriptions
        • How to access CARTO's Analytics Toolbox for BigQuery and create visualizations via Python notebooks
        • How to access CARTO’s Analytics Toolbox for Snowflake and create visualizations via Python notebooks
        • How to visualize data from Databricks
      • Reference
    • CARTO QGIS Plugin
  • CARTO for Developers
    • Overview
    • Key concepts
      • Architecture
      • Libraries and APIs
      • Authentication methods
        • API Access Tokens
        • OAuth Access Tokens
        • OAuth Clients
      • Connections
      • Data sources
      • Visualization with deck.gl
        • Basemaps
          • CARTO Basemap
          • Google Maps
            • Examples
              • Gallery
              • Getting Started
              • Basic Examples
                • Hello World
                • BigQuery Tileset Layer
                • Data Observatory Tileset Layer
              • Advanced Examples
                • Arc Layer
                • Extrusion
                • Trips Layer
            • What's New
          • Amazon Location
            • Examples
              • Hello World
              • CartoLayer
            • What's New
        • Rapid Map Prototyping
      • Charts and widgets
      • Filtering and interactivity
      • Summary
    • Quickstart
      • Make your first API call
      • Visualize your first dataset
      • Create your first widget
    • Guides
      • Build a public application
      • Build a private application
      • Build a private application using SSO
      • Visualize massive datasets
      • Integrate CARTO in your existing application
      • Use Boundaries in your application
      • Avoid exposing SQL queries with Named Sources
      • Managing cache in your CARTO applications
    • Reference
      • Deck (@deck.gl reference)
      • Data Sources
        • vectorTableSource
        • vectorQuerySource
        • vectorTilesetSource
        • h3TableSource
        • h3QuerySource
        • h3TilesetSource
        • quadbinTableSource
        • quadbinQuerySource
        • quadbinTilesetSource
        • rasterSource
        • boundaryTableSource
        • boundaryQuerySource
      • Layers (@deck.gl/carto)
      • Widgets
        • Data Sources
        • Server-side vs. client-side
        • Models
          • getFormula
          • getCategories
          • getHistogram
          • getRange
          • getScatter
          • getTimeSeries
          • getTable
      • Filters
        • Column filters
        • Spatial filters
      • CARTO APIs Reference
    • Release Notes
    • Examples
    • CARTO for React
      • Guides
        • Getting Started
        • Views
        • Data Sources
        • Layers
        • Widgets
        • Authentication and Authorization
        • Basemaps
        • Look and Feel
        • Query Parameters
        • Code Generator
        • Sample Applications
        • Deployment
        • Upgrade Guide
      • Examples
      • Library Reference
        • Introduction
        • API
        • Auth
        • Basemaps
        • Core
        • Redux
        • UI
        • Widgets
      • Release Notes
  • CARTO Self-Hosted
    • Overview
    • Key concepts
      • Architecture
      • Deployment requirements
    • Quickstarts
      • Single VM deployment (Kots)
      • Orchestrated container deployment (Kots)
      • Advanced Orchestrated container deployment (Helm)
    • Guides
      • Guides (Kots)
        • Configure your own buckets
        • Configure an external in-memory cache
        • Enable Google Basemaps
        • Enable the CARTO Data Warehouse
        • Configure an external proxy
        • Enable BigQuery OAuth connections
        • Configure Single Sign-On (SSO)
        • Use Workload Identity in GCP
        • High availability configuration for CARTO Self-hosted
        • Configure your custom service account
      • Guides (Helm)
        • Configure your own buckets (Helm)
        • Configure an external in-memory cache (Helm)
        • Enable Google Basemaps (Helm)
        • Enable the CARTO Data Warehouse (Helm)
        • Configure an external proxy (Helm)
        • Enable BigQuery OAuth connections (Helm)
        • Configure Single Sign-On (SSO) (Helm)
        • Use Workload Identity in GCP (Helm)
        • Use EKS Pod Identity in AWS (Helm)
        • Enable Redshift imports (Helm)
        • Migrating CARTO Self-hosted installation to an external database (Helm)
        • Advanced customizations (Helm)
        • Configure your custom service account (Helm)
    • Maintenance
      • Maintenance (Kots)
        • Updates
        • Backups
        • Uninstall
        • Rotating keys
        • Monitoring
        • Change the Admin Console password
      • Maintenance (Helm)
        • Monitoring (Helm)
        • Rotating keys (Helm)
        • Uninstall (Helm)
        • Backups (Helm)
        • Updates (Helm)
    • Support
      • Get debug information for Support (Kots)
      • Get debug information for Support (Helm)
    • CARTO Self-hosted Legacy
      • Key concepts
        • Architecture
        • Deployment requirements
      • Quickstarts
        • Single VM deployment (docker-compose)
      • Guides
        • Configure your own buckets
        • Configure an external in-memory cache
        • Enable Google Basemaps
        • Enable the CARTO Data Warehouse
        • Configure an external proxy
        • Enable BigQuery OAuth connections
        • Configure Single Sign-On (SSO)
        • Enable Redshift imports
        • Configure your custom service account
        • Advanced customizations
        • Migrating CARTO Self-Hosted installation to an external database
      • Maintenance
        • Updates
        • Backups
        • Uninstall
        • Rotating keys
        • Monitoring
      • Support
    • Release Notes
  • CARTO Native App for Snowflake Containers
    • Deploying CARTO using Snowflake Container Services
  • Get Help
    • Legal & Compliance
    • Previous libraries and components
    • Migrating your content to the new CARTO platform
Powered by GitBook
On this page
  • Usage quota
  • Average monthly usage
  • Editor users
  • Viewer users
  • Tokens
  • Location Data Services (LDS)
  • Increasing quotas
  • Legacy quotas

Was this helpful?

Export as PDF
  1. CARTO User Manual
  2. Settings

Understanding your organization quotas

PreviousSettingsNextActivity Data

Last updated 1 year ago

Was this helpful?

Every CARTO subscription plan includes a set of available quotas such as the total number of editor users that the organization can create.

Let’s review these quotas more in depth, with examples to help you predict usage.

Usage quota

Not all API requests are worth the same. Here's a rundown of what each API does and how it is weighted against the Usage quota.

API
When is it used?
Weight
Example

Maps API

To load layers and tiles in a map. Every time you interact with a map these requests are needed, including opening, styling, editing, exploring, or zooming in a map.

0.2

5 requests to the Maps API will consume 1 Usage quota unit.

SQL API

To push queries to the data warehouse for analytical purposes (that is, not to render a map) All components in Workflows use this API. Creating tilesets or enrichments from the CARTO Workspace will also make use of it.

10

1 request to the SQL API will consume 10 Usage quota units.

SQL API (Widgets)

To display responsive data charts that match and filter your current map view.

Widgets in Builder and widgets created by developers using our official libraries make use of the SQL API Widgets endpoints.

1

1 request to the SQL API (Widgets) will consume 1 Usage quota unit

Import API

To import geospatial files from your computer (or from a url) to your data warehouse.

10

1 imported file will consume 10 Usage quota unit.

LDS API

LDS stands for "Location Data Services" and it is used to geocode addresses and compute isolines based on your data.

0.1

1 request to the LDS API to geocode a table will consume 0.1 Usage quota units.

The weights above apply to usage after March 25th, 2024 for SaaS deployments, or 2024.4.17 version onwards for CARTO Self-Hosted deployments. For usage prior to that date or in previous versions, check the reference below.

Usage Quota API weights before March 25th, 2024 (SaaS) or version 2024.4.17 (Self-Hosted)
  • Maps API: 0.1 The change in Maps API to 0.2 has been rolled out progressively and is tied to performance optimizations (less requests). It has no impact on the total number of usage quota consumed.

  • SQL API: 10 It previously included both widgets and non-widgets requests. We split these two categories, lowering the weight of SQL API widget requests.

  • Import API: 10

  • LDS API: 0.1

Only successful requests (2xx) are counted towards the usage quota.

Metadata-related endpoints are excluded from the usage quota calculations, such as retrieving the details of a sql job, map or import job.

Cached requests are included in the usage quota calculations, so viewers will get the best performance regardless of the usage quota.

The Usage quota is annual, and it will reset AFTER your reset date. During the reset date, you'll still see consumption for the ongoing period, and it will only display "0" the following day.

The Usage quota is a soft quota, which means that even if your organization exceeds this quota the platform will continue to work as usual for all users, from editors to live public maps. This avoids unnecessary disruptions, and also allows great flexibility for accidental or unforecasted usage peaks

Lastly, the usage quota is updated every day, so if you do actions now, you should see the changes reflected the following day.

Average monthly usage

Because the Usage quota is annual and it is consumed progressively, we provide a simple estimation on how good you're doing versus your quota at any time. If we estimate that your organization will run out of quota, we will provide an estimated date where your quota will exhaust.

This estimation is based on your current consumption and assumes your organization will keep using the platform at that same rate.

Editor users

Users set as “Admin” also count towards the editor quotas.

Example:

If I already have 3 out of 3 editors/admins available, I won’t be able to invite new editors or promote viewers to editors or admins.

Viewer users

Example

If I already have 50 out of 50 viewers available, I won’t be able to invite viewers or demote editors to viewers. Also, users that try to join or request to join the organization will be blocked.

Tokens

Temporary access tokens (for example those generated using an M2M application) don't count towards this quota.

Example

If I already used 100 out of 100 tokens, I won't be able to create new tokens using the Tokens API or any other method. Existing tokens will still work as usual.

Location Data Services (LDS)

LDS credits are consumed for every geocoded row and for every isoline calculated.

The tracker for LDS credits in Workspace updates automatically in near real-time.

Example

If I have already geocoded 50,000 rows and calculated 50,000 isolines, and my LDS credits quota is 100,000, I won't be able to process more geocoding or isolines..

Increasing quotas

Legacy quotas

Enterprise organizations created before March 2023 might have a different set of quotas

Since the rollout of the new Usage quota model has been progressive for existing customers, it's possible that your "Usage & Quotas" page looks slightly different than documented above. Here's a collection of older quotas that are now deprecated.

  • Total maps

  • Public maps

  • Total connections

  • Total applications

In general, if you see these quotas under your "Usage & Quotas" page, they still apply to your organization. If you have questions, please contact your Account Manager.

Every time any user in your organization interacts with the CARTO Platform through the UI or through our APIs, Usage quota units will be consumed from your annual quota. Technically speaking, this quota is based on requests to the following : Maps API, SQL API, Import API, and LDS API.

An editor is a user that has permissions to create and edit maps, connections, applications… This is a hard quota, and will be enforced whenever you try to add new editors or when new editors try join the organization. For more information on how to manage users, check .

A viewer is a user that can only view the objects (maps, applications…) produced in the organization. They can’t create or edit anything in the organization… This is a hard quota, and will be enforced whenever users try to signup or whenever you try to add new viewers through invitations or roles. For more information on how to manage users, check .

Using the you can create permanent tokens that your apps and projects will use to access the . This quota is the maximum amount of tokens you can have at the organization level. This is a hard quota and will be enforced whenever you try to generate a new token.

Whenever you or based on your data, you're using our Location Data Services, abbreviated as LDS. The use of LDS is limited by an annual quota (LDS credits) that you can track here.

If you need to increase any of these quotas, please contact your Account Manager, Customer Success Manager or send an email to

CARTO APIs
Managing User Roles
Managing User Roles
Tokens API
CARTO APIs
support@carto.com
geocode a table
calculate isolines