Print maps & generate images

If you need a static non-zoomable image of a map for your web, graphic design or for a print, you can generate it using one of the pre-defined styles or with your own design.

Sign-in to MapTiler Cloud, select one of the maps and scroll down. There is a button Generator for static maps in the last section Static map as an image.

Here you can generate your own map with graphical static maps generator or use it as an API for your own application.

Visual generator

The visual generator is very simple: you just set the size of an image, optionally check the self-explaining Double resolution (for retina displays) and zoom to the selected area.

Below there are two clickable links, which are automatically updating while you are changing the parameters of your request, but they should give you the same image if you click on them.

The maximal resolution for an image is currently set to 2048 x 2048 px or 1024 x 1024 px for retina displays (x2).

Visual generator for static maps

Visual generator for static maps. This particular image will include only the area in the black box: city center of Athens and their harbor Piraeus

API description

If you want to build your own application, there are two basic options of how to define the area of your interest. First one is called Center-based URL, where the area displayed on an image is defined by longitude and latitude of the image’s center point and image resolution. The other option, Bounds-based URL, is defined by a couple of coordinates defining bottom left and top right corner.

Autofitting polygon/polyline

It is also possible to use auto instead of the region specification (center or bounds) in the URL. In such case, the area will be automatically calculated based on a path from the query (path or encodedpath has to be specified). See the format’s documentation and possible values below.

Adding overlay & more

It is possible to add these parameters to the URL (in addition to the required key):


  • path - comma-separated lng,lat, pipe-separated pairs
    • e.g. 5.9,45.8|5.9,47.8|10.5,47.8|10.5,45.8|5.9,45.8
    • latlng ( latlng=true or latlng=1) - indicates the path coordinates are in lat,lng order rather than the usual lng,lat
  • encodedpath - Path encoded according to Google Encoded Polyline Format
    • e.g. _p~iF~ps|U_ulLnnqC_mqNvxq`@
    • encodedpath has priority over path (if both are specified)
  • fill - color to use as the fill (e.g. redrgba(255,255,255,0.5)#0000ffnonefalse)
  • stroke - color of the path stroke
  • width - width of the stroke (in pixels)
  • padding - “percetange” padding for fitted endpoints (bounds-based and auto)
    • e.g. value of 0.1 means “add 10% size to each side to make sure the area of interest is nicely visible”


  • markers - comma-separated lng,lat, pipe-separated pairs
    • e.g. 14.4,50.1|8.6,47.4|2.4,48.9 - 3 separate markers will be displayed
    • each marker can have a color - specified as the 3rd parameter (e.g. 14.4,50.1,red|8.6,47.4,blue)


  • attribution (attribution=false or attribution=0) to disable attribution (make sure to display the correct attribution yourself in case you use this)
Was this article helpful?
0 out of 0 found this helpful