Slice GeoTIFF/COG files into standard XYZ tile pyramids (z/x/y directories). All processing in your browser—nothing uploaded.
Web Worker streams TIFF reading in background
File data never leaves your browser
Output follows OSM/Google z/x/y tile structure
Select a GeoTIFF or COG file (.tif/.tiff)
TIFF to XYZ Tiles slices a GeoTIFF or Cloud Optimized GeoTIFF into a standard XYZ tile pyramid - the z/x/y folder structure used by OpenStreetMap, Google Maps, Leaflet, and MapLibre. You choose the zoom range (0-20, with a suggested maximum derived from the source resolution), a tile size of 256 or 512, and PNG, JPEG, or WEBP output; a Web Worker streams the TIFF in the background so even large files slice without freezing the page.
It is the fastest route from a finished map image to an interactive slippy map: publish scanned historic maps, rendered analysis results, or drone orthophotos as tiles that load instantly at every zoom level.
Select a single .tif or .tiff file - its dimensions and a suggested maximum zoom level are detected automatically after loading.
Configure the zoom range, tile size (256 or 512), and output format - PNG for transparency, JPEG for photographic content - and pick the output folder when prompted.
Let the slicing finish; the tile pyramid is written directly into the directory you chose, ready to drop into any tile server or static file host.
AThe tool suggests the level at which one tile pixel corresponds to roughly one source pixel. Going beyond it upscales the source and looks blurry, though levels up to 20 are allowed for matching another dataset. Set the minimum zoom to where overview browsing should start, usually 0.
AYes - the output follows the standard z/x/y tile layout on the Web Mercator grid that these libraries expect, so pointing a tile layer at the directory (served over HTTP) works out of the box. The same holds for OpenLayers and most tile servers.
APNG is lossless and supports transparent pixels for data with holes; JPEG compresses photographic imagery much harder but loses some detail and has no alpha channel; WEBP often achieves the best ratio of the two, at the cost of support on very old browsers.