MapProxy speeds up mapping applications by pre-rendering and integrating maps from multiple sources and storing in a local cache. Layers can be made transparent, projections can be changed, multiple map layers can be transformed into one, watermarks can be added, and more...

MapProxy is flexible and scales from simple to complex use-cases: from a single tile cache for an OpenLayers web client to a central SDI node that combines, unifies and accelerates dozens of distributed WMS services.


MapProxy is used for the German broadband atlas to deliver maps for thousands of users and the German Federal Agency for Cartography an Geodesy uses MapProxy to aggregate WMS services from all 16 states on the fly.


MapProxy is one of our open source projects. We administer the project by making regular releases and by adding new features. We also offer free and commercial support and we develop new features on customer's request. More Informations →

Core Features

Some of MapProxy core features are listed below. More information about MapProxy are available on

Input sources:
  • WMS 1.0.0–1.3.0 (MapServer, GeoServer, etc.)
  • TMS, WMTS (TileCache, GeoWebcache, etc.)
  • Mapserver and Mapnik (directly, without WMS)
  • any TileCache, Google Maps or Bing compatible source
  • WMS (1.0.0-1.3.0)
  • TMS / WMTS
  • KML SuperOverlays
Tile cache:
  • simple but powerful configuration format (YAML/JSON)
  • stores identical images just once (e.g. ocean tiles)
  • stores tiles in filesystem, MBTile files or CouchDB
  • add watermark to tiles or attribution lines to the images
And more:
  • limit sources to geometries (from Shapefile for example)
  • accelerates existing WMS 10 to 100 times
  • many more

Implemented Standards

MapProxy implements the following open specifications:

  • OGC WMS 1.0.0, 1.1.0, 1.1.1, 1.3.0
  • OGC WMTS 1.0.0 (KVP and RESTful)
  • OSGeo TMS 1.0.0
  • OGC KML 2.2 SuperOverlays