Static maps that fit in a single URL.

A map rendered to an ordinary image file, a PNG, WebP or JPEG, that you request with a URL. You say where, how far zoomed in, how big and in which style, and you get back a picture of exactly that view. No JavaScript, no interactive map, just an image you can put anywhere an image goes.

Anywhere a map library cannot run: transactional email, PDFs and invoices, link previews and social cards, printed labels, notifications, dashboards that are rendered on the server, and slow pages where an interactive map would be too heavy. It is also the quickest way to show a location at all: one img tag.

One unit per image, at any size up to the cap. A High-DPI image, requested with @2x for sharp screens, costs two, because it carries four times the pixels. Units come from the same monthly pool as maps, geocoding and routing.

Up to 1280 pixels a side, so 1280 by 1280 at most. With @2x that becomes 2560 by 2560 actual pixels while the layout, the label sizes and the line widths stay those of the 1280 image.

Yes. Up to fifty markers per image, each with its own colour, size and a short label; lines as coordinate lists or an encoded polyline, up to five hundred points per image, with a stroke, a width and an optional fill that turns them into shapes; and a circle of any radius around the centre. You can also let the image frame itself around your overlays, with padding, instead of picking a centre and zoom.

Five street styles: light, dark, grayscale, white and black. Three formats: PNG, WebP and JPEG, chosen by the file extension in the URL. Labels come in the local name by default and can be switched to any of forty-one languages, or turned off altogether for a clean backdrop under your own overlays.

Static renders use the street styles only: no satellite imagery, no terrain shading and no 3D buildings yet, all of which the interactive map does have. Markers are coloured dots in three sizes with an optional label, not custom icons. If you need any of those in a picture today, render a screenshot of the interactive map instead.

The key is visible to anyone who can see the URL, so treat it that way: use a key whose only job is static maps, keep its allowed-origins list empty because an img tag sends no origin, and let the monthly quota and the spending cap you set be the meter. A leaked key can cost you units, never money beyond the cap.

Yes. The free plan includes 10,000 units a month with no card and no sales call, which is 10,000 images if that is all you spend them on. It is a hard cap, so a runaway loop cannot produce a bill.

In the European Union, end to end. No part of the request path touches a US-controlled provider, which is what makes the GDPR and data-residency conversation short. We publish a DPA and a full sub-processor list.