> For the complete documentation index, see [llms.txt](https://help.felt.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.felt.com/upload-anything/data-limits.md).

# 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](/plans-and-billing/plan-usage.md).

## 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](#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](/upload-anything/files/spreadsheets-and-geocoding.md). |

You can upload files in their original format, or compressed as `.zip`, `.7z`, `.rar`, `.tar`, or `.gz`. See [Supported file types](/upload-anything/files/supported-file-types.md).

## 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](/layers/organize-layers.md).

## 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](/upload-anything/data-sources/add-a-source.md).
* Streamed URLs: stream large vector data from [vector tiles](/upload-anything/urls/vector-tiles.md), or turn on **Stream vector data** for a large ArcGIS service, so Felt loads only the data in view. See [ArcGIS services](/upload-anything/arcgis-services.md#stream-large-services).
* Raster streaming: stream Cloud Optimized GeoTIFFs (COGs) and STAC catalogs from a bucket without uploading them. See [Stream large rasters](/upload-anything/stream-large-rasters.md).
* REST API: upload and manage large datasets in code. See [REST API](/developers/rest-api.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.felt.com/upload-anything/data-limits.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.