OpenStreetMap is the rare free thing whose price is printed on the label. The data is licensed under the Open Database License, the ODbL, and its core demand is simple to state: credit OpenStreetMap and its contributors, make clear the data is available under the license, and, if you build a new database from it, share that database under the same terms. In practice, nearly every question users bring is about the first demand, and nearly every mistake is a small one: a credit buried where no reader goes, a logo mistaken for attribution, a screenshot with the credit cropped away. This guide gives the practical rules per medium, drawn from openstreetmap.org's copyright page and the OSM community's attribution guidance, so the credit you give is the credit the license asks for.
Home / GIS and Open Map Data for Beginners
OpenStreetMap Attribution: How to Credit OSM Correctly on Any Medium

Photo: Ketut Subiyanto / Pexels
Credit OpenStreetMap Correctly: The Checklist
Check off each step as you finish it. Your progress stays on this page.
0 of 6 complete
0% done
The Core Obligation, in Plain Language
The license asks for two things whenever you publicly use OSM data. First, credit the source: the community's required form names the contributors, conventionally rendered as "© OpenStreetMap contributors," and the credit must be legible and placed where a user of your work will encounter it, not archived in a file no one opens. Second, make the license discoverable: link the credit, or accompany it, to openstreetmap.org/copyright, the page that states the terms, or provide the license text itself where links are impossible. Where the map is interactive, the credit links directly. Where it is not, print carries the credit line and the URL in words. Two clarifications prevent most anxiety. You do not need permission, and you do not need to ask; the license is the permission, granted in advance to everyone who honors it. And the credit belongs to the contributors collectively, not to the OpenStreetMap Foundation as a vendor; you are acknowledging a crowd of mappers, which is precisely the acknowledgment that keeps the crowd mapping.
Interactive Maps: The Corner Credit Done Right
On a web or app map, attribution lives in the map's corner, the convention every major library implements. If you use Leaflet, MapLibre, or OpenLayers with OSM tiles or data, the control is built in; your job is to not remove it, not style it into invisibility, and not cover it with your own interface elements. The credit should read as the contributors credit and link to the copyright page. If your map combines sources, each source's credit stands in the same place: OSM's line does not absorb your imagery provider's, and theirs does not absorb OSM's. One more duty specific to interactive products: if your map is built from OSM data you rendered yourself rather than the standard tile layer, the credit is the same, because the obligation follows the data, not the tiles. And if your users can report or correct map errors, linking a note or edit path is community good practice, the kind of reciprocity the attribution guideline encourages, though the license's hard demand remains the credit and the link.
Static Images, Screenshots, and Social Posts
The moment a map becomes a picture, corner controls vanish and the duty becomes manual. For a static image used in an article, a report, a slide, or a social post, place the credit on the image itself or in its immediate caption, where a reader encountering the image alone will see it. "Map data © OpenStreetMap contributors" with the copyright page URL is the working form. The common failures are all editorial: cropping a screenshot so the corner credit falls outside the frame, covering it with a headline, or assuming a credit on the article's credits page covers an image that will be copied and shared alone. Images travel; captions and credit lines must travel with them. If the image is small, the credit can be small, but legible at the size the image is consumed. This site's own articles follow the rule you are reading: every map image carries its data credit in place, because a map blog that teaches attribution in one article and crops it in another teaches only the cropping.

Print: Books, Posters, and Paper Maps
Print removes the hyperlink and keeps everything else. The credit line appears on the map itself, in the margin or legend block where map credits have lived for centuries, naming the contributors and giving the copyright page URL in text. For a book or report with many maps, a single consolidated credits entry can serve if each map's context points to it, but the safer and more courteous practice, and the one cartographers recognize, is a short credit on each map plus the full license reference in the front matter or colophon. Print runs are unforgiving: check the credit at proof stage, at the physical size, because a credit that exists but cannot be read by the book's actual audience fails the license's spirit and arguably its letter, which asks for notice reasonable to the medium. A poster on a wall is a medium whose reasonable notice is a readable line at the poster's foot, and it takes ten seconds to add before the print run and is impossible to add after.
Produced Works Versus Derivative Databases: Where Share-Alike Lives
The ODbL's share-alike clause frightens more users than any other line, and the distinction that defuses it is between a produced work and a derivative database. A produced work is something you make using the data: a map image, a routing result, a printed atlas, an app screen. Produced works need attribution, but they do not need to be shared under the ODbL, and your own creative layers in them keep your own terms. A derivative database is a database built from OSM's data: corrected, merged, extended, and redistributed as data. If you publicly release a derivative database, the ODbL requires offering it under the same license, so the commons you drew from is replenished. The practical borderline cases: geocoding results and route outputs are produced works; a cleaned, merged street dataset you ship to customers is a derivative database; an internal derivative you never distribute triggers no release duty, though attribution still applies when the public sees its fruits. When in doubt, the community guidance and, for commercial stakes, a lawyer are the authorities; this guide's job is to make sure the question you ask them is the right one.
Tiles, Styles, and the Other Credits You May Owe
Attribution questions often tangle because a finished map has several parents. The standard OSM tile layer is one rendering; a map built with a commercial style, a satellite backdrop, or a hosted tile service carries that provider's terms too, which may require their own credit and may restrict use in ways the ODbL does not. Crediting OpenStreetMap does not discharge a tile provider's terms, and obeying a provider does not discharge the data credit. Read the stack: data license (ODbL, credit the contributors), tile or style terms (the provider's), and any imagery license (the imagery owner), and place each credit where its terms expect it. Our article on using OpenStreetMap in a website walks the embedding mechanics; the credit stack described here is the legal shadow those mechanics cast, and the two are best learned together.
Fixing a Missing Credit, and Why It Is Worth Doing Well
If you discover a published map of yours lacks proper credit, the fix is neither dramatic nor shameful: add the credit, update the image or the page, and move on. The community's enforcement culture is overwhelmingly corrective rather than punitive; mappers would rather be credited late than litigated early, and the project's guidance is written to help users comply, not to trap them. It is worth doing well for a selfish reason too. Attribution is the visible receipt of the bargain that built the best free map of the world: millions of contributors gave their surveys, traces, and local knowledge in exchange for acknowledgment and a commons that stays open. Every correct credit is a small proof that the bargain holds, shown to exactly the audience, map users, from whom the next contributors will come. Credit like you want to be credited is not just the license's demand. It is the project's growth engine, and it costs you one line of text.
What Attribution Is Not: Logos, Links Home, and Other Near Misses
A short catalog of near misses saves real projects, because each of these has been offered in good faith as compliance. A link to openstreetmap.org's homepage is not the license link; the requirement points at the copyright page, which is where the terms and the contributors' credit live. Displaying the OpenStreetMap logo is not attribution; a logo identifies a brand and says nothing about data provenance or license, and the credit is a sentence, not a badge. Crediting "OpenStreetMap" alone, without the contributors, misses the license's actual beneficiary; the data is the contributors' work, and the standard credit names them. Burying the credit in source code comments, metadata, or a colophon page no map reader reaches fails the visibility principle, which the community guidance states plainly: the credit belongs where users of the map will see it. And crediting in a smaller size or lower contrast than your own interface text, the dark pattern of compliance, invites exactly the community complaint the honest corner credit never draws. Each near miss costs the same line of text as the real thing. There is no economy in them, only risk.
Related Guides
Readers working through this topic usually need its closest companions too. These GIS and open map data guides cover the neighboring ground:
- OpenStreetMap Nominatim: The Geocoder, Its Endpoints, and Its House Rules: Nominatim is the search engine that turns OpenStreetMap data into answers: give it an address and it returns coordinates, give it coordinates and...
- OpenStreetMap Zoom Levels: What You Can See From Level 0 to 19: Every slippy map, OpenStreetMap included, is built on a ladder of zoom levels, 0 to 19 on the standard layer, where each step doubles the tiles in...
- JOSM: The OpenStreetMap Desktop Editor for Mappers Who Outgrow iD: JOSM is the Java desktop editor that serious OpenStreetMap contributors graduate to: it edits relations comfortably, validates your work before...
Frequently Asked Questions
What exactly must the OpenStreetMap credit say?
Credit the contributors, conventionally "© OpenStreetMap contributors," and link or refer to the license at openstreetmap.org/copyright. The credit must be legible and placed where users of the map will see it: the map corner for interactive maps, on or beside the image for static uses, and in the margin or credits for print.
Do I need permission to use OpenStreetMap data commercially?
No permission is needed. The Open Database License grants use, including commercial use, in advance, provided you give attribution and honor the share-alike term for derivative databases you distribute. The license is the permission; your part is the credit and, where it applies, the sharing.
Does using OSM tiles versus OSM data change the attribution?
No. The obligation follows the data. Whether you display the standard tile layer, render your own tiles from OSM data, or compute with it behind an app, the contributors' credit and the license link are owed in the same form, placed reasonably for the medium.
What is a derivative database, in practice?
A database built from OSM data and redistributed as data: merged, corrected, or extended datasets shipped to others. If you publicly distribute one, the ODbL requires offering it under the same license. Maps, images, routes, and other produced works made from the data are not derivative databases and carry attribution duties only.
What happens if I forget the attribution?
In practice, you will usually be asked to add it, and adding it promptly resolves the matter. The community enforces correctively. Deliberate or commercial-scale misuse can escalate to license termination and legal claims, but the ordinary path is simple: credit the contributors, link the copyright page, and the issue closes.
Photo credits: Ketut Subiyanto (Pexels); Ketut Subiyanto (Pexels). Photos are served from this site; follow the credit to the library page for the original.