ExifToolGui Map Not Loading: WebView2 and OpenStreetMap Checks
The map in ExifToolGui — the V6 continuation, by Frank Bijnen, of Bogdan Hrastnik’s Windows front-end for ExifTool — is the one feature with its own extra requirements. Manual geotagging depends on it: you position the map, and the GUI writes that location to your selected files. When the map panel stays blank or never loads, the cause is almost never your photos. It is the map’s own supporting pieces: in V6, the map is an OpenStreetMap view rendered through Microsoft’s Edge WebView2 technology, and the V6 documentation lists exactly what that needs. This page checks those pieces in order. The rest of the fix series is in the Troubleshooting hub, and current program files are on the download page.
What the V6 map needs — and what it does not
From the V6 documentation’s requirements section: WebView2Loader.dll and the Microsoft Edge (WebView2) runtime are required only for the OpenStreetMap map feature. They are explicitly optional extras for everything else. Two conclusions follow, and both are useful. First, if the rest of ExifToolGui works — files load, metadata reads and saves — but the map does not, your ExifTool pairing is fine and you should not disturb it; the fault is confined to the map’s components. Second, if you never use the map, a missing WebView2 piece is not a defect in your setup at all. The original v5 GUI used a GoogleMap panel; V6 replaced that approach with the OpenStreetMap/WebView2 combination, which is why advice written for the old version does not apply here.
Check 1: WebView2Loader.dll is present with the program
WebView2Loader.dll is the loader library that connects the GUI to the Edge runtime. If you run the portable build and at some point moved only the executable out of its extracted folder, the DLL can be left behind — the same partial-move mistake that breaks the ExifTool pairing when exiftool_files is separated from exiftool.exe. The fix is the same habit: keep the program’s files together. Re-extract the portable download in full, or reinstall with the installer, and check that WebView2Loader.dll sits with the program files before testing the map again. Our Portable vs Installer comparison explains what each distribution contains and how the pieces are laid out.
Check 2: the Microsoft Edge (WebView2) runtime is installed
The DLL is only the loader; the actual rendering is done by the Microsoft Edge (WebView2) runtime on your PC. Windows 11 machines and up-to-date Windows 10 machines commonly have this runtime already, because other programs depend on it too — but ‘commonly’ is not ‘always’, and a machine without it shows exactly this symptom: everything works except the map. Treat the runtime as a Windows component to confirm, not a setting inside ExifToolGui: there is no map switch in the GUI that substitutes for it. If the runtime is absent, installing it is a system-level step done once, outside the GUI, after which the map feature has what it needs. The runtime is a Microsoft component; obtain it through Microsoft’s own channels, not bundled downloads from third-party sites.
Check 3: be on V6.3.12 for the map fixes
The map itself changed in the current release. The V6.3.12 release notes (May 8, 2026) record that the MapTiler baselayers were updated to V4, a Hybrid satellite layer was added, and label sizes were fixed. If your map loads but its layers or labels misbehave on an older V6 build, updating is the sourced fix — the release directly addresses the map stack you are looking at. Version 6.3.12 also improved HEIC support and fixed a style-change crash; the full list is in ExifToolGui V6.3.12: What’s New. Note what updating cannot fix: if WebView2Loader.dll or the Edge runtime is missing, a newer GUI still lacks its map components. Check 1 and Check 2 come first.
Check 4: the map needs to reach its tile services
Stated plainly, as a general fact about how web-based maps work: an OpenStreetMap view displays map tiles fetched from online services — in V6’s case with MapTiler baselayers — so the map panel needs a working internet connection at the moment you open it, through the WebView2 component. Offline, or behind a connection that blocks the component, the panel has nothing to render even when every file is in place. Test on an ordinary open connection if you can; a map that loads there but not on a restricted network has told you the answer. This is a property of online maps generally, not a defect in your installation. While you work through these checks, the rest of the program remains fully usable — including geotagging from a GPX track log, which does not depend on the visual map at all.
Frequently asked questions
The map is blank but everything else works. Is my ExifTool pairing broken?
No. Reading and writing metadata does not use WebView2 at all. A working GUI with a blank map points at the map’s own pieces: WebView2Loader.dll beside the program, the Edge (WebView2) runtime installed, and a connection the tile services can be reached through.
Do I need the map to geotag photos?
Not necessarily. The map is for manual, visual geotagging — placing files at the map position. ExifToolGui also geotags in batch from a GPS track log file, a workflow that never opens the map panel. The map is one route to coordinates, not the only one.
I have the original V5 GUI. Do these checks apply?
Only partly. V5’s map was a GoogleMap panel with different plumbing; the WebView2 and MapTiler details here are V6 facts. If you are still on the original line, V5 vs V6 explains what changed and why the maintained fork is the version to troubleshoot on a modern PC.