Exporting data

Export the result of any node in your workflow as a file you can open straight away in desktop GIS, spreadsheets or data pipelines, with no manual conversion. You can export to CSV, GeoJSON, Shapefile, GeoParquet, GeoPackage and KML, the same formats available when exporting data from Builder.

How to export

1. Run the workflow and select the node you want to export.

2. In the Data tab of the Results panel, click the export button .

3. Choose a File format and click Export data. CSV is selected by default, and the dialog remembers your last choice during the session.

4. The export runs in the background and shows up in the activity panel in the top bar, named after the node. When it finishes, click Download to get the file.

The file contains every row of the node's result, not only the page shown in the Data tab. Shapefile exports download as a .zip file.

Available formats

Outputs with a geometry column can be exported in any format. Outputs without one, such as a spatial index output (H3, Quadbin) or a Group by result, can only be exported as CSV or Parquet. The other formats are shown disabled, with a tooltip explaining why.

Exporting as a Viewer

Viewers of a shared workflow get the same export options, as long as the Editor turns on Export data from node in the Settings for viewers menu, next to the Preview button. This setting is off by default.

To produce a file every time the workflow runs, for example on a schedule or when executed via API, use the Export as File component instead.

Export limitations

• GeoJSON, Shapefile, GeoPackage and KML exports fail if the file grows beyond 4 GB. CSV and GeoParquet aren't subject to this limit, so use them for large results.

• Shapefile supports a single geometry type and files up to 2 GB. Use GeoPackage for results that mix points, lines and polygons, and GeoParquet for large results.

• Tileset and raster outputs can't be exported.

Bucket considerations

For CARTO Cloud, CARTO automatically manages buckets and data exports. Be aware that for exports from Snowflake and Redshift sources, the AWS cluster needs to match the organization's CARTO Cloud region. Check your CARTO Cloud region in Settings.

For Self-Hosted deployments, a bucket owned by the customer needs to be configured, and exports from BigQuery connections require it to be a Google Cloud Storage bucket. Learn more in Configure your own buckets.