Limits
Felt is built for geospatial data at scale — up to 50 million features per layer and 500 layers per map.
Felt is built to handle real-world geospatial data at scale. A single layer can hold up to 50 million features, and a single map can hold up to 500 layers — so you can bring your full dataset to the map, not a sample of it.
Capacity guidelines
Features per layer
50 million
Layers per map
500
Tables per connected source
5,000
Edit at scale, instantly
Felt's Lightning tiling engine lets you bring in millions of features and edit them the moment they land — changes render immediately, your whole team can edit at once, and statistics are calculated live across millions of features. Learn more about editing layers.
Browser upload limits
These limits apply to direct browser uploads — data you drag and drop or add through Upload Anything. They aren't hard ceilings on what Felt can handle; see Bringing in larger data below.
Supported files can be uploaded in their original format or compressed as .zip, .gz, or .tar.
Bringing in larger data
When your data is larger than a browser upload allows — or you want it to stay live — bring it in another way:
Cloud sources — connect databases and warehouses like Snowflake, BigQuery, and Postgres / PostGIS, and storage like Amazon S3, Azure Blob Storage, and Google Cloud Storage directly, with no file-size cap. See Cloud sources.
URL and streaming sources — stream large, global, or frequently updating datasets as external vector tiles, or stream large ESRI Feature and Map services so Felt loads only the data in view. See URLs.
Very large rasters — stream terabyte-scale COGs and STAC catalogs in place. See Raster infrastructure.
API — bring in and manage large datasets programmatically with Felt's API.
So a 5GB file or 50 layers in one upload is just the starting point.
Raster at scale
Felt serves very large rasters elegantly. Instead of uploading and duplicating files, Felt streams Cloud Optimized GeoTIFFs (COGs) and STAC catalogs directly from cloud storage such as Amazon S3, Azure Blob Storage, and Google Cloud Storage — indexed for location and metadata filtering and ready for immediate visualization. You can work with terabyte-scale raster datasets without ever hitting a file-upload limit.
Learn more in Raster infrastructure and Raster streaming best practices.
Frequently asked questions
How many features can a single layer hold?
A single layer can hold up to 50 million features, and you can edit them instantly thanks to Felt's Lightning tiling engine.
What if I have more than 5,000 tables in a connected source?
Felt supports up to 5,000 tables in a connected source. If you have more than that, limit which tables you expose to the Felt credentials — connect Felt with a database user whose access is scoped to only the tables you want available. See Cloud sources.
What's the largest file I can upload?
Through your browser, Felt supports files up to 5GB, in their original format or compressed as .zip, .gz, or .tar. Image and PDF overlays can be up to 20MB. See Files for details. For larger or live data, connect a Cloud sources or stream it URLs.
What if I need to go beyond these limits?
The browser-upload limits aren't caps on what Felt can handle. Connect a Cloud sources, stream from a URLs or via Raster infrastructure, or use Felt's API. If you still need more, get in touch.
Last updated
Was this helpful?