Google introduces new pricing plans for Maps API


google_moneyBack in 2012 Google introduced fees for developers using Maps API. Developers were offered Google Maps Premium – a paid for service starting from $10,000 a year, which also offers branded maps and custom uses of Google Maps. If they opt not to pay for this, fees were $4 per 1,000 page loads over the 25,000 per day – or  $10 per Street View load over the 10,000 per day. Smaller and bigger players like Foursquare immediately started to switch to other platforms and after just couple of weeks Google had to quickly lower prices. The mess of these business decisions was still visible in APIs pricing plans.

This week together with a new logo Google has finally brought in much needed change to this pricing. The Maps API team said:

Today we’re introducing a simple and flexible option for developers to instantly and easily scale with these Web Service APIs, by opening them up to pay-as-you-go purchasing via the Google Developers Console.

In this new purchasing structure, the Google Maps APIs (Geocoding, Directions, Distance Matrix, Roads, Geolocation, Elevation, and Time Zone) will be free of charge for the first 2,500 requests per day, and developers will pay $0.50 USD per 1,000 additional requests up to 100k requests per API per day. Developers with over 100k requests per day will get a premium pricing model.

I'm a professional always thinking outside the box and a self-confessed gadget addict. As a son of a professor of cartography I was surrounded by maps all my life and as a result spatial way of thinking and seeing reality is naturally embedded in who I am.


  1. Are you sure? You wrote “developers will pay $0.50 USD per 1,000 additional requests”. So you’ll pay 100 * $0.50 (because for 99,750 requests you need 100 packages of 1000 requests) = $50. Its acceptable then…

  2. You made wrong calculations. As Lukasz noted you’re not going to pay that money. Anyway, even if I agree OSM can be a valuable solution, Google APIs offer much more reliable results in certain contexts. I work mostly with OS technologies but I have to admit that Google infrastructure has the big benefit of being pervasive, ubiquitous, easy to use and, most importantly, for spatial tools it has a much more uniform coverage and a better visual balance for general porpuse mapping. Don’t get me wrong, I’m a big fan of OSM, I contribute to and use it, but Google has good reasons to offer (IMHO fair) bill its APIs….

    • Giovanni. There are pros and cons of every API. I guess that everything depends on your needs, requirements and personal preferences. Personally I use Google Maps as my main mapping service, so you don’t have to convince me how good it is:). $50 per 100k requests is a fair price.

  3. I wish i can find some help in here…

    1- How can i tell the potential count of requests of my application?
    2- my application is to track my 15 vehicles and to check the nearest vehicles to a specific point and report the travel time including the traffic integration.



Please enter your comment!
Please enter your name here