Upload Data to Create Hosted Tilesets

Upload MBTiles or PMTiles files through the Mappinest console and prepare them for hosted tile delivery.

Supported formats

The console currently supports MBTiles and PMTiles uploads in both raster and vector form. GeoJSON and Shapefile are planned, but they are not available yet in the current upload flow.

Accepted file types and upload limits

This table shows what the current console upload accepts and which per-file limits apply. MBTiles and PMTiles uploads are plan-based: Free supports up to 1 GB per file, while Flex and Pro support up to 20 GB per file. Hosted storage is separate and plan-based, so total storage above 1 GB requires Flex and total storage above 20 GB requires Pro.

File typeTilesetsDatasetsTransfer limits
MBTiles
20 GB (raster or vector tileset)
PMTiles
20 GB (raster or vector tileset)
GeoJSON
10 MB
Shapefile
10 MB

Upload workflow

Use the dashboard console to add a new tileset, choose the input format, and let Mappinest validate and prepare the tileset for delivery endpoints.

Hosted storage follows plan rules. Free allows up to 10 files and 1 GB total storage. Flex allows up to 50 files and 20 GB total storage. If you need more than 20 GB of hosted storage or custom ingest terms, contact us about Pro.

Step 1 - Select a tileset format

Choose the input format before the upload starts. The console currently supports MBTiles and PMTiles uploads.

Upload format picker in the console

Step 2 - Upload file

Select the file from your machine and start the upload from the console UI.

Upload progress dialog in the console

Step 3 - Processing

After upload completes, the tileset is validated and processed before tile delivery is enabled.

Processing tileset in the console

Step 4 - Tileset ready

Once processing finishes, the tileset appears in the Tilesets list and is ready to use through delivery endpoints.

Tileset ready in the console

Tileset naming

When you upload a file, the filename is sanitized - special characters are removed and spaces are replaced with underscores. If a tileset with the same name already exists, a version suffix is appended to keep the key unique and the cache stable.

The final tileset Id takes the form username.tileset (without file extension), for example mappinest.Counties. To find it, open the Tilesets table, click the tileset name to open the Studio preview, then click Show API URL - the id appears in the TileJSON and tile endpoint URLs.

Tileset lifecycle

After upload, each tileset goes through validation and preparation before it is ready to serve through the Tiles API.

  1. The uploaded file is validated to confirm it can be read and that the required tileset metadata is present.
  2. If validation passes, the tileset is processed and prepared for delivery through the standard tile endpoints.
  3. Once publishing finishes, the tileset becomes ready to use through TileJSON, vector tile or raster tile XYZ URL.

Last updated: April 14, 2026