TileServer GL
Self-HostedOpen-source map tile server for self-hosting vector and raster maps
Overview
TileServer GL is an open-source map tile server enabling self-hosting of vector (Mapbox Vector Tiles, MBTiles) and raster maps. It supports formats like GeoJSON, Shapefiles, and raster images, integrating seamlessly with Leaflet/OpenLayers. Deploy via Docker, Node.js, or pre-built binaries for Windows/macOS/Linux. Customize styles using Mapbox Style Spec to match project designs. Ideal for privacy-focused apps, offline use, or projects needing full control over map data without third-party APIs—lightweight and scalable for small to large deployments.
Self-Hosting Resources
Below is a reference structure for docker-compose.yml.
⚠️ Do NOT run blindly. Replace placeholders with official values.
version: '3'
services:
tileserver_gl:
image: <OFFICIAL_IMAGE_NAME>:latest
container_name: tileserver-gl
ports:
- "8080:<APP_INTERNAL_PORT>"
volumes:
- ./data:/app/data
restart: unless-stopped Key Features
- Serve vector and raster maps from a self-hosted server
- Supports MBTiles, GeoJSON, and Shapefile data formats
- Easy deployment via Docker, Node.js, or pre-built binaries
Frequently Asked Questions
? Is TileServer GL hard to install?
No—TileServer GL is easy to install using Docker (with a single command), Node.js/npm, or pre-built binaries for Windows, macOS, and Linux. Official docs provide step-by-step guides for each deployment method.
? Is it a good alternative to Mapbox Tiles API?
Yes—TileServer GL supports the same Mapbox Style Specification and MBTiles format as Mapbox, making it a great alternative for self-hosting. It avoids API costs and privacy concerns by keeping map data under your control.
? Is it completely free?
Yes—TileServer GL is open-source under the MIT License, so it’s completely free to use, modify, and distribute. You only need to supply your own map data (e.g., OpenStreetMap-derived MBTiles), which can be obtained for free or purchased.
Top Alternatives
People Also Ask about TileServer GL
Tool Info
Pros
- ⊕ Privacy-focused (no reliance on third-party map APIs)
- ⊕ Customizable map styles using Mapbox Style Specification
- ⊕ Compatible with popular frontends like Leaflet and OpenLayers
Cons
- ⊖ Requires own map data (e.g., MBTiles) which is not included
- ⊖ Basic knowledge of map formats needed for initial setup
- ⊖ Limited enterprise-level support compared to proprietary solutions