> 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/plans-and-billing/plan-usage.md). # Plan usage Track map views, processing, storage, and Felt AI credits. Learn what counts toward usage limits and what happens when you reach them. Each workspace has limits for map views, processing, storage, and Felt AI credits. See the [Felt pricing page](https://felt.com/pricing) for amounts. Felt never charges for going over a limit. On a paid plan, an admin can [buy more usage](#buy-more-usage). | Limit | What counts | When it resets | | --------------- | ----------------------------------------------------------------------------------- | ------------------------------------------------ | | Map views | Each load of a map in a browser, an embed, or an app built with the Platform add-on | The first day of each month | | Processing | Uploads, refreshes, and spatial analysis results | The first day of each month | | Storage | The amount of data the workspace holds | Doesn't reset: it goes down when you delete data | | Felt AI credits | The work Felt AI does for each request | The first day of each month | Usage limits are different from data limits, which are fixed caps such as the largest file you can upload. See [Data limits](/upload-anything/data-limits.md). ## Check your usage The **Usage** tab shows monthly usage and current storage. Go to [felt.com/maps/latest/usage](https://felt.com/maps/latest/usage), or click your workspace name in the sidebar, click **Workspace settings**, and click the **Usage** tab. On the Free plan, admins can open **Usage** to see map views. The tab has a section for each limit on your plan: | Section | Shows | | --------------- | ------------------------------------------------ | | Map views | The maps with the most views this month | | Processing | Each dataset that used processing this month | | Storage | Each dataset's size, which counts toward storage | | Felt AI credits | Felt AI credits used, by tool and by member | ## What counts toward processing and storage Uploads (including data from URLs), layer refreshes, and new spatial analysis results count toward processing. Each refresh processes the full dataset again. **Refresh source list** updates only the source's list of tables and files, not layer data. | Pattern | Monthly processing | | --------------------------------- | ------------------ | | One upload of a 2 GB file | 2 GB | | 100 MB layer refreshed once a day | 3 GB | | 500 MB dataset refreshed hourly | About 360 GB | Felt measures uncompressed size, so the **Usage** tab can show a larger size than the zipped file you uploaded. Streamed vector tiles, streamed Cloud Optimized GeoTIFFs (COGs), WMS and WMTS layers, and field photos don't count toward processing or storage. Viewing and sharing maps never use processing. Deleting a layer or map doesn't reduce the processing already counted toward your limit. To use less processing, refresh large layers only as often as their data changes, and trim rows and columns before you add a dataset. ## Felt AI credits Felt AI credits are included with the plan and shared across the workspace. Requests that read more data use more credits. Credits cover Felt AI on maps, in the **Extension editor**, in custom HTML popups, in SQL queries, and in MCP tools that run Felt AI. Other MCP tools don't use Felt AI credits. For the list of MCP tools that use credits, see [MCP integrations](/felt-ai/mcp.md#felt-ai-credits). When the workspace reaches its Felt AI credits limit, Felt AI stops taking new requests until the limit resets or an admin buys more usage. Anything Felt AI has already built keeps working. See [AI assistant](/felt-ai/ai-assistant.md). ## What happens at a limit Felt emails workspace admins when usage reaches 80% and 100% of the processing, storage, and map views limits. Reaching a limit stops new work of that kind, and existing layers keep working. | Limit reached | What stops | | --------------------- | ----------------------------------------------------------------------------------------- | | Processing or storage | New uploads and scheduled refreshes | | Map views | Viewing for people outside the workspace, who see a page saying the map is over its limit | | Felt AI credits | New Felt AI requests | ## Buy more usage Admins on a paid plan can buy more processing, map views, or Felt AI credits anytime on the **Billing** tab at [felt.com/maps/latest/billing](https://felt.com/maps/latest/billing). More usage is billed monthly until an admin removes it. Prices and amounts are on the [Felt pricing page](https://felt.com/pricing). --- # 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/plans-and-billing/plan-usage.md?ask=&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.