Home / GIS and Open Map Data for Beginners

OpenStreetMap on Garmin: Load OSM Maps Onto Your Device, Two Routes

A man in hiking gear checking his smartphone for navigation

Photo: Tima Miroshnichenko / Pexels

Your Garmin knows the world through the maps loaded on it, and for much of the planet the best map available is the one OpenStreetMap's volunteers drew. Garmin's own maps are strong on major roads in wealthy countries and thin everywhere else: the hiking trail, the new suburb, the rural road network of a country Garmin's cartographers visit rarely. OpenStreetMap fills exactly those gaps, and the Garmin format is open enough that the community has spent years building tools to convert OSM data into device-ready maps. The OSM wiki's OSM Map On Garmin pages document the whole practice. This guide teaches the two routes: the pre-made download, for most people, most of the time; and the build-your-own route through mkgmap, for people who want contours, custom styling, or a region nobody pre-builds.

Interactive tool

Get the Map Aboard: The Garmin Checklist

Check off each step as you finish it. Your progress stays on this page.

0 of 7 complete

0% done

Route One: The Pre-Made Image

Volunteers and services run the conversion for you and publish ready-made, routable map images for countries and regions, updated on regular cycles from current OSM data. The workflow:

  1. Choose a provider from the wiki's list of OSM Map On Garmin providers and pick your country or region. Larger areas may come as several tiles or one combined image.
  2. Download the file, typically named gmapsupp.img. That name is not a suggestion: it is the filename the device's classic loading convention expects.
  3. Connect the device (or its microSD card) to your computer, and copy the file into the Garmin folder: on the card, the folder at the card's root named Garmin; the image goes inside it.
  4. Eject cleanly, restart the device, and enable the new map in the device's map settings (next section).

That is the entire route for most users, and its simplicity is the point: someone else's pipeline did the conversion, and your job is reduced to choosing a region and placing one file correctly. Which makes the placement rules worth their own section, because nearly every failure of this route is a file in the wrong folder wearing the wrong name.

The File-Placement Discipline

Garmin devices are strict about where map images live, and silent about it: a map in the wrong place does not produce an error, it produces an absence. The rules that matter: the image belongs in a folder named Garmin, at the root of the device storage or the memory card. The classic filename is gmapsupp.img; many newer devices accept additional images with other names in the same folder, which is how several regional maps coexist, but the gmapsupp convention remains the safe baseline, and renaming a downloaded image to match it is standard practice when a provider ships a different name. One image can hold one map product (possibly assembled from many tiles), so combining regions means either downloading a combined image or building one, not dropping five files and hoping. After copying, eject the device properly before unplugging: a half-written multi-hundred-megabyte image corrupts quietly, and the device will simply not list the map. If the map does not appear, check folder, name, and file size, in that order, before suspecting the download.

A hiker with a backpack using a smartphone to navigate in a forest
A hiker with a backpack using a smartphone to navigate in a forest

Enabling and Choosing Maps on the Device

Loading is not using. On the device, open the map settings (the exact menu path varies by model family, typically under Setup, Map, then the map information or select-map screen) and you will see the maps the device found: the built-in basemap, any Garmin products, and your OSM image. Enable the OSM map and disable overlapping products for the same area, because two routable maps covering the same ground confuse routing and clutter the display; the device draws and routes best with one authority per territory. Verify with a search: find a local trailhead or a street the Garmin product never had. If the OSM detail is there, the pipeline worked end to end, and the device in your hand now navigates on the map the volunteers drew, including, on hiking models, the trails that are the usual reason for this whole exercise. Our guides to finding coordinates on a Garmin and to how GPS works on Garmin watches cover the device side of the partnership once the map is aboard.

Route Two: Build Your Own With mkgmap

The pre-made route fails in three situations: your region is not offered, you want contour lines woven in, or you want control over what the map emphasizes. The build-your-own route answers all three, and its engine is mkgmap, the community's converter from OSM data to Garmin image format. The pipeline in outline: download an OSM extract for your area (the PBF workflow our download guide covers), optionally download elevation data for the same area, run mkgmap with a style that decides how OSM tags become Garmin features, and receive a gmapsupp.img built to your specification, ready for the same folder discipline as any downloaded image. The style is where the craft lives: mkgmap styles decide which paths render as trails, whether cycleways route, how much detail survives at each zoom, and they are shared and refined by the community, so most builders start from a published style and adjust. The wiki's tool table also lists the supporting cast, osm2mp for other device ecosystems, GroundTruth for map generation with its own rules, and QLandkarte for viewing Garmin maps on a computer before committing them to the device.

Contours and Routing: The Two Options Worth Understanding

Two build choices deserve attention even if you never build, because pre-made providers offer them as variants. Contours: elevation lines are not part of OSM's core data; they are generated from elevation models (SRTM and its successors) and merged into the image, either integrated with the map or as a separate transparent layer the device overlays. For hiking and mountaineering use, a map without contours is a rumor; choose the contour variant whenever a provider offers one. Routing: a routable image carries the graph the device navigates on, with road classes and restrictions translated from OSM tags; a non-routable image is display-only, fine for a reference layer, useless for turn-by-turn. Providers label these plainly; builders set them in mkgmap's options. Match the variant to the job, because the wrong pairing, a beautiful non-routable map on a navigation device, a routable road map asked to guide a mountain traverse, fails in the field, where failure is expensive.

Keeping the Map Current

An OSM map on a Garmin is a snapshot, and OSM moves. The update routine is the download route repeated: fetch the provider's fresh image for your region, replace the file in the Garmin folder, done. Build it into the rhythm of trip preparation rather than treating it as maintenance: before a significant trip, refresh the maps for its area, the same week you check batteries and boots. Builders re-run mkgmap against a fresh extract. Either way the cost is minutes, and the benefit is the trail rerouted last spring, the road opened last month, the bridge that is no longer out. The device will never prompt you; Garmin products update through Garmin's channels, and OSM images update through yours. That small responsibility is the honest price of a map made by everyone, and it is cheaper than the price of the alternative, which is navigating a country from a snapshot somebody else chose the date of.

Troubleshooting: The Map Does Not Appear

Work the checklist in order; nearly every invisible map is one of these five. Wrong folder: the image sits somewhere other than a folder named Garmin at the storage root; the device does not search, it looks in one place. Wrong name: a provider shipped the image under a descriptive filename and your device family expects gmapsupp.img; rename it. Corrupt copy: the transfer was interrupted or the device was unplugged without ejecting, leaving a truncated image the device silently ignores; compare the file size on the device against the download, and recopy with a clean eject. Not enabled: the map loaded fine and is switched off in the map settings, or an overlapping product is enabled instead; check the select-map screen before touching files. Format mismatch: the download was a different product type (an installer package for a computer program, or a map set meant for a different device family) rather than a device image; return to the provider and fetch the gmapsupp variant. Notice what is not on the list: the map being "incompatible with OpenStreetMap." The pipeline is two decades mature; when it fails, it fails at placement, naming, copying, or enabling, the four human steps, which is good news, because human steps can simply be done again, carefully.

One Image, Several Regions: Map Sets

A refinement for travelers whose trips cross provider boundaries. A single gmapsupp image can be assembled from multiple regional tiles, and the better providers offer exactly that: pick the countries or states your trip touches and download one combined image covering them all, rather than juggling files at every border. Builders do the same in mkgmap by feeding it several extracts in one run. The reason to combine is the device's file discipline from earlier: one image, one map product, no ambiguity about which file rules which territory. The reason not to over-combine is freshness and size: a combined image of a continent is a heavy download to refresh for the sake of one province's new roads. Combine to the shape of your traveling life (your country plus its neighbors, your state's trail regions), refresh that set on the trip rhythm, and leave the rest of the world for the trips that go there.

A Word on Watches and Handhelds

This article has spoken of "devices" generally, and the family divides in ways worth one paragraph. Handheld and automotive units are the classic gmapsupp audience: generous storage, a file system you can reach by USB, map sets chosen in advance. Watches are the constrained cousins: smaller storage, maps managed through Garmin's own apps and regions rather than loose files in many models, and the OSM route correspondingly narrower, which is why our Garmin watch guides treat their offline maps as their own subject. The wiki's pages keep the per-family detail current, and the right first question for any specific model is which loading convention it follows. The principle survives the division: the data is the same open map, the tools are the same community pipeline, and only the last meter, the file's path onto the hardware, changes its shape. Learn your device's last meter and the rest of this article is yours.

Related Guides

If this page answered part of the question, these GIS and device guides cover the rest of the same ground:

Frequently Asked Questions

Can a Garmin device really use OpenStreetMap maps?

Yes. Community tools convert OpenStreetMap data into Garmin's image format, and volunteers and services publish pre-made routable images for most countries and regions. The OSM wiki's OSM Map On Garmin pages document the providers and tools.

Where do I put the map file on my Garmin?

In a folder named Garmin at the root of the device storage or its memory card, with the image named gmapsupp.img under the classic convention. A map in the wrong folder or with the wrong name does not produce an error; the device simply never lists it.

What is mkgmap?

It is the community converter that builds Garmin map images from OpenStreetMap data. Builders use it with a style file that decides how OSM tags become Garmin features, and with options for contours and routing, to produce a gmapsupp.img tailored to a region or purpose.

Should I choose a pre-made map or build my own?

Pre-made for most people and most trips: choose your region, download, place the file correctly. Build your own with mkgmap when your region is not offered, when you need contours integrated your way, or when you want control over styling and routing behavior.

How do I update the OpenStreetMap data on my Garmin?

Repeat the download: fetch the provider's current image for your region and replace the file in the Garmin folder, or re-run your mkgmap build against a fresh extract. Do it in trip-preparation week; the device will not prompt you.

Photo credits: Tima Miroshnichenko (Pexels); Kamaji Ogino (Pexels). Photos are served from this site; follow the credit to the library page for the original.