What a BMW Map Update Actually Changes Across CIC, NBT, NBT EVO, and MGU
BMW publishes navigation map updates twice a year for most regions, and most owners click through to download them without ever knowing what is actually inside. The download is a 14 to 22 GB archive depending on region. Inside that archive is half a year of road network changes, point-of-interest revisions, address corrections, speed camera databases, and (on newer headunits) hybrid offline-online routing data. If you are about to spend an hour copying files to a USB stick and another hour waiting for the import, it helps to know what you are actually getting.
This article walks through what the BMW map update process delivers across the four iDrive generations that still receive updates: CIC, NBT, NBT EVO, and MGU. We cover what changes between releases, how the headunit handles the import, where the FSC code fits in, and the small set of differences between the systems that matter to owners.
If you are about to download a fresh map and want to verify your headunit will accept it, jump to the Compatibility table. If you have already downloaded and installed and the iDrive is now asking for a code, our separate guide on FSC codes after map updates covers that specifically. The article you are reading is the broader context.
What is in a BMW map release
BMW sources cartography from HERE Technologies, the same Dutch-headquartered map provider that also feeds Mercedes, Hyundai, and several non-automotive customers. HERE refreshes its base data continuously; BMW packages snapshots of that data twice a year and ships them as numbered releases.
The 2025-1 Europe map released in spring 2025 is roughly 18.4 GB compressed. Inside, the contents break down approximately as:
- Road network and topology data: the main road graph, including new roads built since the previous release, road class downgrades or upgrades, and routing topology metadata. About 8-10 GB on a typical European release.
- Address and POI database: street names, house number ranges, point-of-interest names, business hours, telephone numbers. About 3-4 GB.
- Junction views and 3D landmarks: rendered images that the iDrive shows for major motorway junctions and city landmarks. About 2-3 GB.
- Country-specific traffic regulations: speed limit databases by road segment, regional truck restrictions, environmental zones (LEZ/UEZ), tolling rules. About 1 GB.
- Speed camera database (region-dependent): the legality of including this varies by country; BMW omits the layer in some markets. About 50-200 MB where present.
- Voice guidance phonetic data and prompts: pronunciation databases for local street names. About 1-2 GB.
The single biggest functional update in any release is usually the road network. New motorway junctions, redrawn city centre traffic schemes, recently completed bypasses, and the latest roundabout reconfigurations show up here. For drivers who travel internationally this is the difference between the GPS sending you down a road that no longer exists and routing you correctly.
How frequently maps get released and why
BMW labels releases by year and quarter: 2024-1, 2024-2, 2025-1, 2025-2. Each release is approximately six months of accumulated cartography updates from HERE. The release cadence has been twice yearly since 2014; before that it was once yearly with smaller incremental patches.
The reason BMW does not release more often is the activation overhead. Each release requires a new FSC for paid customers, requires dealer support training, requires the engineering team to validate the headunit firmware against the new map, and requires the customer to download a multi-GB file. Doing this monthly would be unbearable for everyone in the chain. Twice a year balances freshness against operational cost.
Tesla, by comparison, ships map updates over the air whenever convenient because their headunit firmware and map firmware are integrated. BMW's hardware supports OTA updates from MGU iDrive 7 onwards, but the activation model means even MGU-equipped cars typically run the most recent paid update rather than constantly streaming new map fragments.
Compatibility table by headunit
| Headunit | iDrive Generation | Years built | Receives updates until | Map archive type |
|---|---|---|---|---|
| CIC | iDrive 3 | 2008-2013 | BMW Premium maps released through 2024; HERE legacy after | FSCNAVISALA / FSCNAVNCAR (DVD-style packages) |
| NBT | iDrive 4 | 2012-2016 | Active through 2026 | NEXT, MOTION_NEXT (USB-distributed) |
| NBT EVO ID4 | iDrive 4 EVO | 2014-2016 | Active through 2027 | EUROPE_NBT_NEXT, etc. |
| NBT EVO ID5 | iDrive 5 | 2016-2018 | Active through 2028 | EUROPE_NBT_NEXT_2 (similar packaging) |
| NBT EVO ID6 | iDrive 6 | 2017-2020 | Active through 2029 | EUROPE_NBT_NEXT_2 + LIVE layer |
| MGU (ID7) | iDrive 7 | 2018-2022 | Active indefinitely | MGU JOY / LIVE / NEXT (smaller diff updates) |
| MGU2 (ID8) | iDrive 8 | 2021-now | Active indefinitely | SFA-distributed, OTA primary |
The "Receives updates until" column reflects current BMW lifecycle policy. CIC owners can technically still get maps, but the most recent CIC-compatible release as of publication is the 2024-2 archive; we do not expect 2025 releases to ship for CIC. NBT through MGU all continue to receive current cartography. MGU2 (iDrive 8) receives map updates over-the-air and via SFA push; the FSC archive model does not apply.
How to identify your headunit without taking anything apart
Three reliable signals.
The iDrive screen aspect ratio. CIC has a 4:3 or 5:3 screen with a thick bezel. NBT introduced the widescreen format. NBT EVO and MGU look similar at first glance but the resolution differs (NBT EVO 1280x480, MGU 1920x720 on most chassis).
The boot animation. CIC shows a static BMW logo. NBT shows an animated BMW kidney grille morphing into the logo. NBT EVO ID5 and ID6 show the BMW Connected Drive logo briefly before the main interface. MGU shows the BMW M animation if the car is M-equipped, otherwise a horizontal blue bar across the BMW logo. iDrive 8 shows a different transition animation entirely.
The engineering menu. Hold the iDrive controller down for 6 seconds. CIC shows a text-only menu with white-on-blue. NBT shows a black menu with software version info. NBT EVO ID5 onwards shows a tabbed black menu. MGU's engineering menu requires a service mode entry sequence rather than a hold.
If you are still uncertain after these checks, send your VIN to us and we identify the headunit from BMW's parts database within an hour. It is a free service we provide because routing customers to the wrong map version is the most preventable customer support load we have.
What changes between releases
Quantitatively, here is what an average European release contains.
| Category | Per release | Cumulative since previous release |
|---|---|---|
| New road segments added | 200-500 km | 1,000-2,500 km |
| Removed or rerouted segments | 50-200 km | 300-1,000 km |
| Speed limit changes | 3,000-8,000 segments | 15,000-40,000 segments |
| Address range corrections | 1.2-2.5 million | 6-12 million |
| POI additions | 40,000-80,000 | 200,000-400,000 |
| POI removals (closed businesses) | 15,000-35,000 | 75,000-175,000 |
| 3D landmark refreshes | 500-1,500 | 2,500-7,500 |
The numbers are typical for a European release. North America is roughly half this volume. Middle East and Russia are smaller still.
For a daily driver who covers 30,000 km per year on familiar routes, the practical impact of a single release is small. The roads you drive every day are unlikely to have changed in a way that affects routing. The value shows up on long trips, in unfamiliar cities, and when navigating to addresses that were issued in the past 6 months.
Why your old map still gets you most places
This is the question we hear most from owners debating whether to update at all. The honest answer is that the old map is fine for known routes and for major motorways and highways, which change very slowly. The old map is not fine for new urban developments, recently rerouted city centres, and the address of a business that opened in the past year.
If your driving is 90% commute and 10% road trip, the value of fresh maps is mostly in the 10%. If you only ever use the GPS in a city you have lived in for 20 years, you can run 2018 maps indefinitely without practical limitation.
Where the FSC code fits in
BMW gates each new map release behind an FSC code that is bound to your VIN, your headunit hardware ID, and the map version. Without the code, the headunit refuses to use the new map files even if they are correctly imported.
This means a map update has two halves:
- The map files themselves, which are free to download from BMW's portal or from our mirror.
- The FSC code, which is paid (€20-€60 from a specialist, €200-€400 from a BMW dealer, free for some old CIC and NBT releases via legacy generators).
You can do step 1 without step 2 — the headunit imports the files but shows "Card is not free for use" or "FSC code missing" until the matching code is installed. Some owners do this on purpose to wait for the cheapest provider to source the code. The map files import cleanly and sit dormant; once the code is installed, the new maps activate immediately.
Owners who want to skip the recurring FSC purchase should look at Connected Package Professional Lifetime. The activation includes RTTI (live traffic streamed from BMW servers), which routes around current congestion better than offline cartography. Many of our long-term customers stop buying map FSCs entirely after Connected Package Lifetime is installed; the offline base map is good enough for general routing, and RTTI handles the time-sensitive part.
The import process per system
CIC
Pre-2014 CIC cars used a DVD import via the optical drive in the car. Mid-life CIC cars (2012-2013) added USB import support. The DVD path is being deprecated by BMW because the discs are fragile and the optical drives in the cars are increasingly failing. The USB path works on all CIC firmware revisions from approximately 2011 onwards.
Import time on CIC is around 60-90 minutes including the FSC validation step. The headunit must remain on the entire time. We recommend running the engine or connecting a battery charger.
NBT
USB import only. Format the stick to FAT32, copy the maps archive to the root, plug in. Import time 40-70 minutes depending on the size of the archive. The headunit can show "no progress" for long stretches; this is normal and reflects the internal compression/decompression cycle.
NBT EVO ID5 / ID6
USB import is the typical path, but unique to NBT EVO is that the system supports differential updates. If you import a 2025-1 archive over a 2024-2 base, the headunit only writes the differences. Import time drops from 60-90 minutes (full reinstall) to 15-30 minutes (differential).
The differential path requires that the previous map version was a recent BMW release. Cars that were running modified or community-built maps cannot use the differential path; they need a full reinstall.
MGU (iDrive 7)
Two paths: USB import (similar to NBT EVO) or over-the-air partial updates (MGU is the first iDrive that streams map deltas from BMW servers when the car has internet connectivity). OTA updates require Connected Package Professional or higher.
USB import takes 30-50 minutes. OTA updates trickle in over days or weeks while the car is parked at home with Wi-Fi access; total bandwidth consumed is 5-10 GB per release.
MGU2 (iDrive 8)
SFA-based activation, OTA-primary distribution. The customer rarely interacts with the update process directly; the car handles it in the background when conditions are right. USB import is supported as a fallback for cases where OTA is unavailable, but most owners will never use it.
Common problems during the import
| Problem | Cause | Fix |
|---|---|---|
| "USB device not recognised" | Stick is exFAT or NTFS | Reformat to FAT32. 64GB is the practical maximum for FAT32 on Windows; some BMWs accept up to 128GB sticks formatted FAT32 with a third-party tool. |
| "Update interrupted, please retry" | Stick removed too early or battery voltage dropped | Reconnect, restart the import. Use a battery charger for sessions over 30 minutes. |
| Import completes but car still shows old maps | FSC missing or for the wrong version | Get a fresh FSC for the new version. Covered in our FSC code guide. |
| "Cannot read DVD" (CIC only) | Optical drive failure | Switch to USB import path. Some CIC firmware revisions need a software update before USB import is recognised; we can do this remotely. |
| Import freezes at 30% | Corrupt download (rare) | Re-download the archive and verify the SHA-256 against the source listing. Our mirror publishes hashes for every archive. |
| "Map version mismatch" after restart | Headunit firmware too old to recognise the new map format | Update headunit firmware via E-Sys or at the dealer. We can do this remotely as part of an FSC installation session. |
Frequently asked questions
How long do map updates remain available for older cars?
BMW supports map updates for approximately 10 years from the headunit's launch date. CIC launched in 2008 and is now in the wind-down phase. NBT launched in 2012 and still receives updates as of 2025. NBT EVO and MGU are firmly within the support window.
Can I install a North American map on a European headunit?
The map files import successfully but the FSC will not work because the activation is region-bound. The car ends up with a partial map state that does not route correctly. We do not recommend cross-region imports unless you are doing a region change deliberately, in which case the procedure is more involved than just swapping files.
Why is my headunit asking for a code if I never had one before?
BMW shipped your car with a "first owner's activation" baked in. This activation only covers the maps that were current at the time of manufacture. The first time you update to a newer map version, the iDrive demands a fresh code because the new version is outside what the original activation covered. This is the "I never paid for this before, why now?" surprise that catches most owners off-guard.
Is using your map mirror legal?
The map archives themselves are distributed by BMW for free download to BMW owners. We mirror them with proper attribution to BMW and HERE. Distribution of the archives without an FSC does not violate BMW's terms because the archives without activation are non-functional. The legal gate is the FSC code, which is what BMW charges for.
Can I downgrade to an older map version?
Yes if you have an FSC for that version. The headunit accepts older maps as long as the matching FSC is installed. Some owners deliberately run older maps because the database for their region was more accurate in a previous release.
Why do BMWs sometimes navigate to addresses that don't exist?
Address ranges in the map are interpolated from the data BMW receives from HERE. New developments that were issued addresses but have not yet been verified by HERE's field teams sometimes have incorrect coordinates. The headunit confidently routes you to the interpolated location, which can be a few hundred metres off. Each map release reduces this error count but does not eliminate it.
What about countries that BMW does not include in standard maps?
Most former Soviet republics, several Sub-Saharan African countries, and a handful of Caribbean and Pacific islands are missing from BMW's standard regional maps. HERE has data for some of these but BMW does not package them. Third-party map projects (e.g. open-source community efforts) cover some gaps, but compatibility with the BMW headunit is hit-or-miss.
Does CarPlay replace the need for BMW maps?
For many owners, yes. Apple Maps and Google Maps via CarPlay route in real-time using internet data, which is more current than any offline map. The native BMW navigation still has advantages — works without phone signal, integrates with the head-up display and steering wheel controls, surface-renders 3D landmarks — but CarPlay is the practical answer for most journeys. Connected Package Lifetime activates CarPlay alongside RTTI as a single bundle, which is why it is the most efficient path for owners who care about both.
Can the BMW dealer block my headunit if I install third-party maps?
No. The headunit hardware does not have a remote disable mechanism, and BMW's dealer software does not flag third-party maps as a fault. We have not seen a single case in 7 years of operation where a dealer disabled or restricted a headunit because of map installation history.
Does the import affect my car's other functions?
No. The map import only affects the navigation subsystem. Audio playback, climate, drive modes, gauge cluster, and all other vehicle systems continue working normally during and after the import.
What to do next
Three practical paths depending on where you are in the process:
- Need a map for your car right now: visit our maps section and pick the region. Each region page has the latest archive plus the previous two versions in case you want to install something specific.
- Need an FSC code to activate a freshly-imported map: see our FSC code guide for the specifics, then order from our code catalogue.
- Tired of paying for FSCs every 6 months: look at Connected Package Professional Lifetime instead. We covered the activation procedure in this guide.
If you are unsure which iDrive system your car has, send us your VIN and we identify it for free. The single most preventable mistake we see is owners ordering an FSC for the wrong headunit and having to refund/reorder after the iDrive rejects it. The VIN check takes us under an hour and saves both sides time.
For the broader BMW activation context, our tutorials section covers FSC codes, Connected Package, remote tuning, and other coding work in similar depth. Most map update customers come back within a year for one or two of these adjacent activations.