For the complete documentation index, see llms.txt. This page is also available as Markdown.

Data limits

Check Felt's file size, upload, column, and geocoding limits.

Felt is built for large geospatial data, and most of its data limits apply only to files you upload in your browser. Browser uploads can be up to 100 GB per file, and data you connect or stream from where it lives isn't limited by file size. Felt's data limits are the same on every plan that includes uploads. For monthly limits on processing, map views, and Felt AI credits, and for storage capacity, see Plan usage.

Upload limits

Upload limits apply to data you add with Upload Anything, whether you upload a file, drag it onto the map, or add it from a URL.

Limit
Maximum
What to do instead

File size

100 GB per file

Connect the data where it lives. See Bring in larger data.

Image or PDF size

20 MB per file

Compress or resize the file.

Files in one upload

25

Upload the rest in batches.

Layers in one file or URL

50

Split the file, or add an ArcGIS service one layer at a time with a URL that ends in a layer number, such as /MapServer/0.

Columns in one dataset

500

Remove columns you don't need before you upload.

Rows geocoded from addresses

10,000

Add latitude and longitude columns, or split the spreadsheet. See Spreadsheets and geocoding.

You can upload files in their original format, or compressed as .zip, .7z, .rar, .tar, or .gz. See Supported file types.

Map and layer size

Felt doesn't cap features per layer, layers per map, or tables per source, so you can bring your full dataset to the map instead of a sample. Maps get slow past about 50 million features in a layer, 500 layers on a map, or 5,000 tables in a source. To keep a long legend manageable, group related layers. See Organize layers.

Bring in larger data

For data that exceeds upload limits or changes often, bring it in another way:

  • Database and bucket sources: connect a database or warehouse, such as Snowflake, BigQuery, or Postgres / PostGIS, or a bucket, such as Amazon S3. There's no file size limit, and layers can refresh on a schedule. See Add a source.

  • Streamed URLs: stream large vector data from vector tiles, or turn on Stream vector data for a large ArcGIS service, so Felt loads only the data in view. See ArcGIS services.

  • Raster streaming: stream Cloud Optimized GeoTIFFs (COGs) and STAC catalogs from a bucket without uploading them. See Stream large rasters.

  • REST API: upload and manage large datasets in code. See REST API.

Last updated

Was this helpful?