Map Tile Packager
Choose only local raster tiles that you created or have permission to package and redistribute. Validate z/x/y.png or .jpg paths and explicitly select the input XYZ (north-origin) or TMS (south-origin) row scheme. Inspect holes in a selected XYZ rectangle at each zoom, then build and reopen a normalized XYZ ZIP+manifest and actual MBTiles 1.3 SQLite with TMS tile_row. No remote tile service is fetched automatically.
Key features
- Validate local z/x/y paths, per-zoom coordinate ranges and duplicate tile coordinates
- Check actual PNG/JPEG signatures, 256 or 512px square dimensions and file/count limits
- Flip XYZ/TMS y exactly and report coverage and missing cells for selected zoom rectangles
- Embed user-entered source, license, attribution and redistribution confirmation in manifest and MBTiles metadata
- Create and reopen ZIP XYZ tile paths and MBTiles 1.3 SQLite metadata/tiles
- Download all missing coordinates as CSV and record each file's SHA-256 in the manifest
How to use
- Confirm the tile source and redistribution permission, then choose a local z/x/y PNG/JPEG folder.
- Choose the original XYZ or TMS y scheme and review selected zooms and XYZ x/y rectangles.
- Enter source, license and attribution, then confirm permission to redistribute these tiles.
- Build the package, inspect coverage and missing coordinates, and download MBTiles, ZIP and missing CSV.
Use cases
- Bundle self-made map tiles into an offline SQLite database
- Check zoom, coordinate and hole coverage in a permitted local tile folder
- Prepare tile data for clients using different XYZ/TMS row numbering
Frequently asked questions
How does this differ from Archive Workbench?
Archive Workbench checks ZIP entry paths/CRC and repacks arbitrary files. This tool checks map z/x/y, XYZ/TMS rows, per-zoom coverage and gaps, geospatial bounds and the MBTiles SQLite schema.
How do XYZ and TMS y numbers differ?
For the same zoom, y_TMS = 2^z − 1 − y_XYZ. MBTiles 1.3 requires TMS tile_row. The specification example XYZ 11/327/791 is stored with tile_row 1256.
Does it automatically download remote map tiles?
No. Only the local folder selected in this browser is read. Check each service's bulk storage and redistribution terms yourself. The checkbox records your statement; it does not verify or grant rights.
Which images and ranges are supported?
One format per MBTiles: PNG or JPEG, square 256 or 512px raster tiles. Limits are 512 tiles, 1 MiB each, 16 MiB total, zoom 0–14 and 4096 selected rectangle cells. Mixed formats, invalid coordinates and duplicates are rejected.
What happens if tiles are missing inside a selected range?
The gap stays visible in per-zoom expected/included/missing counts and the missing CSV. ZIP and MBTiles contain only real supplied tiles; no placeholder tile is fabricated.
How are formats and metadata stored?
ZIP contains normalized XYZ paths and a JSON manifest. MBTiles is SQLite with metadata(name, format, bounds, center, minzoom, maxzoom, source, license and attribution) and tiles tables. JPEG uses format=jpg. Both outputs are reopened to verify bytes and fields.
Privacy
Local tiles, source and license text are processed in this browser and saved only in downloads. The tool never contacts a map tile service or uploads files to a site server API.
Comments & questions