Upload Data to Create Hosted Tilesets

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. Flex and Pro support up to 20 GB per file unless custom Pro terms apply.

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.

Step 1 - Select a tileset format

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

Step 2 - Upload file

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

Step 3 - Processing

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

Step 4 - Tileset ready

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

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, 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.

Tileset validation and performance checks

New uploads are checked for file validity, tile weight, and rendering complexity before publishing. These checks help prevent very large tiles from causing slow map rendering, high bandwidth usage, or unnecessary pressure on the tile cache.

• Vector tiles are checked for average tile size, largest tile size, layer count, and fields per layer.
• Raster tiles are checked for average tile size, largest tile size, and tile resolution when it can be detected from the tileset.
• Existing ready tilesets uploaded before this validation policy remain available as legacy tilesets.

Current vector tileset limits

Current raster tileset limits