Platform Limits
Check Mappinest upload limits, dataset limits, hosted storage allowances, tile validation limits, and API request behavior.
This page is the quick reference for limits that affect uploads, hosted storage, dataset delivery, tile delivery, and API access.
Hosted storage limits
The hosted-file limit is shared. Each active uploaded tileset, imported dataset, or blank dataset counts as one hosted file. See Storage usage for how the console reports current usage against these allowances.
PAYG applies to request usage and does not increase hosted storage or hosted-file allowances. If a plan downgrade leaves the account over either allowance, the storage remediation and retention process starts when the lower plan becomes active.
Upload limits
The console accepts MBTiles and PMTiles for tilesets, plus GeoJSON and JSON for editable datasets. See Upload Data for the complete format table and workflow links.
Tileset file size applies to MBTiles and PMTiles, and dataset file size applies to GeoJSON and JSON sources. Daily upload tries are shared across tileset uploads and dataset imports, including dataset replacements. Other dataset limits are listed separately below.
An upload that starts counts even if it later fails or is cancelled. When the daily limit is reached, new uploads return HTTP 429 with DAILY_UPLOAD_LIMIT. Try again the next day or upgrade your plan.
Dataset limits
Mappinest checks both the uploaded source and the GeoJSON created during import. A source file can be under 20 MiB and still be rejected if the published GeoJSON exceeds 20 MiB or contains more than 12,000 features.
Read Upload GeoJSON for source requirements, Feature Pagination for page behavior, and Dataset Studio for editor-specific limits.
Tileset limits
New tileset uploads are checked for tile weight and rendering complexity before they are published through the Tiles API.
Vector tilesets
Raster tilesets
Any single tile above 5 MB is outside the standard upload limits. These limits apply to new uploads and replacements.
Monthly included usage
Monthly tile requests, map loads, and dataset requests are plan allowances, not limits. See Plans and billed usage for the included amounts and what happens above them. Track request volume in Usage to spot growth, campaign spikes, or incorrect integrations early.
API keys
The number of API keys an account can create depends on its plan. See API Keys & Access for key types, scopes, and domain restrictions.
Rate limits & error handling
Separate from monthly included usage, API requests use endpoint-specific rolling limits to keep the platform stable. When a limit is exceeded, the API returns HTTP 429. See API Error Codes for common responses.
For rolling request limits, read the current limit from the API response headers. Daily upload tries use the separate plan limit above. If you require higher usage limits, please contact us.
Last updated: September 28, 2026