New in version 1.2.0.

MapProxy supports multiple backends to store the internal tiles. The default backend is file based and does not require any further configuration.


You can configure a backend for each cache with the cache option. Each backend has a type and one or more options.

    sources: [...]
    grids: [...]
      type: backendtype
      backendoption1: value
      backendoption2: value

The following backend types are available.


This is the default cache type and it uses a single file for each tile. Available options are:


The directory layout MapProxy uses to store tiles on disk. Defaults to tc which uses a TileCache compatible directory layout (zz/xxx/xxx/xxx/yyy/yyy/yyy.format). tms uses TMS compatible directories (zz/xxxx/yyyy.format).


tms layout is not suited for large caches, since it will create directories with thousands of files, which most file systems do not handle well.


When true MapProxy will use the actual grid name in the path instead of the SRS code. E.g. tiles will be stored in ./cache_data/mylayer/mygrid/ instead of ./cache_data/mylayer/EPSG1234/.

New in version 1.5.0.


Directory where MapProxy should directly store the tiles. This will not add the cache name or grid name (use_grid_name) to the path. You can use this option to point MapProxy to an existing tile collection (created with gdal2tiles for example).

New in version 1.5.0.


Use a single SQLite file for this cache. It uses the MBTile specification.

Available options:

The path to the MBTiles file. Defaults to cachename.mbtiles.

You can set the sources to an empty list, if you use an existing MBTiles file and do not have a source.

    sources: []
    grids: [GLOBAL_MERCATOR]
      type: mbtiles
      filename: /path/to/bluemarble.mbtiles


The MBTiles format specification does not include any timestamps for each tile and the seeding function is limited therefore. If you include any refresh_before time in a seed task, all tiles will be recreated regardless of the value. The cleanup process does not support any remove_before times for MBTiles and it always removes all tiles. Use the --summary option of the mapproxy-seed tool.


New in version 1.3.0.

Store tiles inside a CouchDB. MapProxy creates a JSON document for each tile. This document contains metadata, like timestamps, and the tile image itself as a attachment.


Besides a running CouchDB you will need the Python requests package. You can install it the usual way, for example pip install requests.


You can configure the database and database name and the tile ID and additional metadata.

Available options:

The URL of the CouchDB server. Defaults to http://localhost:5984.
The name of the database MapProxy uses for this cache. Defaults to the name of the cache.

Each tile document needs a unique ID. You can change the format with a Python format string that expects the following keys:

x, y, z:
The tile coordinate.
The name of the grid.

The default ID uses the following format:



You can’t use slashes (/) in CouchDB IDs.


MapProxy stores a JSON document for each tile in CouchDB and you can add additional key-value pairs with metadata to each document. There are a few predefined values that MapProxy will replace with tile-depended values, all other values will be added as they are.

Predefined values:

{{x}}, {{y}}, {{z}}:
The tile coordinate.
The creation time of the tile as seconds since epoch. MapProxy will add a timestamp key for you, if you don’t provide a custom timestamp key.
The creation time of the tile in UTC in ISO format. For example: 2011-12-31T23:59:59Z.
The center coordinate of the tile in the cache’s coordinate system as a list of long/lat or x/y values.
The center coordinate of the tile in WGS 84 as a list of long/lat values.


    sources: [mywms]
    grids: [mygrid]
      type: couchdb
      url: http://localhost:9999
      db_name: mywms_tiles
        mydata: myvalue
        tile_col: '{{x}}'
        tile_row: '{{y}}'
        tile_level: '{{z}}'
        created_ts: '{{timestamp}}'
        created: '{{utc_iso}}'
        center: '{{wgs_tile_centroid}}'

MapProxy will place the JSON document for tile z=3, x=1, y=2 at http://localhost:9999/mywms_tiles/mygrid-3-1-2. The document will look like:

    "_attachments": {
        "tile": {
            "content_type": "image/png",
            "digest": "md5-ch4j5Piov6a5FlAZtwPVhQ==",
            "length": 921,
            "revpos": 2,
            "stub": true
    "_id": "mygrid-3-1-2",
    "_rev": "2-9932acafd060e10bc0db23231574f933",
    "center": [
    "created": "2011-12-15T12:56:21Z",
    "created_ts": 1323953781.531889,
    "mydata": "myvalue",
    "tile_col": 1,
    "tile_level": 3,
    "tile_row": 2

The _attachments-part is the internal structure of CouchDB where the tile itself is stored. You can access the tile directly at: http://localhost:9999/mywms_tiles/mygrid-3-1-2/tile.