This content applies to a previous version of CARTO

In October 2021 we released a new version of our platform. You can find the latest documentation at docs.carto.com

Back to Help Center

How to Submit a Bug in CARTO

Best practices to submit a bug in CARTO

Who is this for?

  • Developers and data scientists
  • CARTO clients and users not requiring developer support should follow guidelines on the support details page

A bug represents a problem causing the CARTO platform to stop working or produce invalid output.

When should I report a bug?

  • You’ve identified a specific, repeatable problem in the platform
  • Your map or app stops functioning with the same workflow each time
  • You’re encountering identical unknown errors when running Python scripts

Why should I report a bug?

Effective bug reports increase the likelihood of fixes, resolving workflow blockages and benefiting all CARTO users.

Where should I report a bug?

Builder maps

Open a new issue in the GitHub cartodb repository with comprehensive details. Adding a .carto file significantly aids developer reproduction efforts.

CARTO applications

Report bugs to the appropriate repository based on technology:

  • CARTO.js (layers/dataviews issues): carto.js repository
  • CARTO VL (styling/vector rendering): carto-vl repository
  • Airship (layouts/web components): airship repository
  • CARTOframes/CARTO Python SDK: cartoframes or carto-python repositories

How should I report a bug?

Avoid duplicates

Check existing known bugs first. Consult HELP articles and GIS StackExchange to distinguish actual bugs from misunderstandings.

Be specific

Summarize concisely and avoid combining multiple issues. Choose descriptive titles:

  • “My Builder map returns an unknown error when styling by numeric values”
  • Not: “My map is not working”

Steps To Reproduce (STR)

Clearly outline reproduction steps without assumptions or omissions. Detailed, reproducible bugs get fixed faster.