API key now required to use Map component

By July 1st, 2017, you’ll need to provide your own Google Maps API key to use the maps component in your Webflow projects. For instructions on how to make this update, check out the full tutorial in our help center.

Why the change? Last year, Google removed keyless access to their API, requiring everyone to supply an API key to serve their maps on their site.

Will this cost me anything? Probably not. The Google Maps API is free up to 25,000 map loads per day (which covers more than 99% of Webflow sites) with overage pricing kicking in after that.

What about exported sites? On exported sites, you can re-export your site after adding your API key, or edit the code directly to add your API key.

What happens on July 1st? On July 1st, we'll be removing our own API key, which means any sites that you haven’t added your own API key to will see broken maps.

For more details about the change, check out the forum. For details on registering and adding your API key, check out our article on Google Maps.

Due to some recent changes from the Google Maps team, you’ll need to register your own Google Maps API key and add it to your projects that use the Maps component. But don’t worry — maps are still free for up to 25,000 map loads per day.