GeoTIFF to MBTiles

Convert one small, georeferenced RGB or RGBA GeoTIFF into a raster MBTiles file on Apify. Choose the zoom range and download the map, a PNG preview and a conversion report.

Use it for preparing imagery for a workflow that accepts raster MBTiles. The output uses Web Mercator (EPSG:3857), 256 × 256 PNG tiles and TMS tile rows. Reprojection uses nearest-neighbour resampling, which can look blocky when enlarged.

What you get

• MAP.mbtiles: a SQLite raster tile archive with bounds and zoom metadata.
• PREVIEW.png: a downsampled view of the highest-zoom tiles, including transparent padding outside the image.
• OUTPUT: a JSON report with completion status, source (bundled example or uploaded record), dimensions and CRS, geographic bounds, zoom range, tile count, output size and SHA-256 hash. The same report appears in the dataset.

The actor reopens each completed archive through GDAL's MBTiles driver before returning it. It does not certify positional accuracy or compatibility with a particular map viewer.

Supported images and limits

This version accepts standalone, north-up TIFFs with internal georeferencing and explicitly labelled 8-bit red, green and blue bands, plus an optional alpha band. Supported source coordinate systems are EPSG:4326, EPSG:3857 and WGS84 UTM zones (EPSG:32601–32660 and EPSG:32701–32760).

Each run processes one file, with these limits:

• Input: 32 MiB and 16 million source pixels.
• Zooms: integers from 0 to 14, including every level in the chosen range.
• Output: at most 500 tiles and 128 MiB.
• Conversion worker: stops after roughly two minutes if conversion is unfinished. Uploading and storing output also take time.

The complete extent must fit between ±180° longitude and approximately ±85.05° latitude. Antimeridian-crossing extents are refused. The actor does not clip the image to fit these limits.

Elevation, single-band or palette images, scientific multiband data, rotated geotransforms, missing CRS and other coordinate systems are unsupported. There is no colour balancing, smooth resampling, vector conversion or map hosting. Use a full GIS or tiling tool when you need those controls.

Price and example

A successful conversion of your own file costs US$0.50, charged once after the map, preview and report are saved. The bundled example, refused inputs and failed conversions have no conversion fee.

Apify also charges US$0.00005 per run start at the default 1 GB memory setting, including example, refused and failed runs. Higher memory settings increase the start fee. Running this actor has no additional platform usage charge. Storage or downloads you use separately through your Apify account may have their own charges.

To try the bundled GeoTIFF, leave Try the bundled CC0 example on and leave Uploaded TIFF store empty. Its report identifies the source as bundled example. Selecting a store while the example is on refuses the run and asks you to turn the example off.

Run a conversion

1. Upload your TIFF as a binary record in an Apify key-value store. Use the content type image/tiff or application/octet-stream, rather than text or JSON. Apify documents the Store record API.
2. Turn Try the bundled CC0 example off. Select your store in Uploaded TIFF store and enter the TIFF record key, such as image.tif. The actor needs read access to the selected store.
3. Confirm you have the rights to process the image, which must contain no personal information. Set minimum and maximum zoom, then start the run.
4. Read OUTPUT. For your file, its source is uploaded record. Download MAP.mbtiles and PREVIEW.png only when its status is success.

Example input:

{
  "useDemo": false,
  "inputStoreId": "YOUR_STORE_ID",
  "recordKey": "image.tif",
  "rightsConfirmed": true,
  "minZoom": 5,
  "maxZoom": 8
}

Set the run's maximum charge to at least US$0.51 to convert your own file. A lower limit refuses the conversion; you pay only the Apify start charge.

A completed Apify run can still report refused or error: the report is the conversion result. A refusal includes a reason, and no completed map or preview is returned. If the requested extent exceeds 500 tiles, reduce maximum zoom or raise minimum zoom.

Data and support

Your TIFF is processed on Apify, and the map, preview and report are saved in the run's Apify storage. Manage retention and access through your Apify account. The actor does not fetch imagery from external URLs. Supply only imagery you have rights to process, without personal information. Do not use the output for safety-critical navigation, surveying or certified map accuracy.

Built and maintained by Madrasco using AI agents. AI agents wrote the code and this description. Use the actor's Issues tab for support, or email support@madrasco.dev. Platform replies may be AI-assisted; the human owner is available on request.