ExifToolGui on Windows 10: Compatibility and Setup

Windows 10 is, with Windows 11, one of the two platforms the ExifToolGui documentation explicitly points users to. The V6 documentation for Frank Bijnen’s continuation of Bogdan Hrastnik’s GUI says the program should run on Windows 7 and 8, and that it is highly recommended to use Windows 10 or 11. So on Windows 10 you are not running legacy software on sufferance — you are in the maintainer’s recommended configuration. This page covers compatibility, how setup works on this system, and where Windows 10 differs from 11 in the current release notes. Start from the files on our download page; the series lives in the Platforms & Versions hub.

Compatibility on Windows 10

ExifToolGui is Windows-only: no Mac or Linux build exists for the original GUI or the V6 fork. The current release, V6.3.12 (May 8, 2026, GPL-3.0), is the build to run, and on 64-bit Windows 10 — the common case — the Win64 files are the default choice: the installer installs Win64 files by default on a 64-bit system (with /Win32 to force Win32), and the portable line offers ExifToolGUI_X64.exe alongside the Win32 ExifToolGUI.exe. That 32/64-bit detail is one of the few real decisions in setup, and it is unpacked in Portable vs Installer. The other structural fact of setup is that the GUI is a front-end: Phil Harvey’s ExifTool does the metadata work, it is a separate download, and no version of Windows changes that arrangement.

Setup: the install tutorials, applied to Windows 10

The installation walkthroughs on this site were written around the current release and apply directly to Windows 10, because the steps are about the pairing, not the OS version:

  • Install ExifToolGui on Windows 11 — the full installer walkthrough. On Windows 10 the same choices appear: let the installer fetch ExifTool (Phil Harvey’s zip, renamed into the install folder, or Oliver Betz’s self-installing package), and let it pick the Win64 files on a 64-bit system.
  • First-launch setup — what to check the first time the program opens: that the pairing is recognised, that a test photo’s metadata loads, and that the panels show what ExifTool reads.
  • The portable alternative: unzip ExifToolGUI_X64.exe’s release set, download ExifTool’s Windows zip, rename exiftool(-k).exe to exiftool.exe, and keep the exiftool_files folder beside it. The rename is the step everyone misses; the not-found guide exists because of it.

Whichever route you take, verify setup with one photo before batch work: select a file, see its metadata, make one small edit, save, and re-read. That minute of testing validates the whole chain — GUI, pairing, write path — on your machine.

Where Windows 10 differs from Windows 11 in the release notes

One difference is documented, and it concerns HEIC photos. V6.3.12 improved HEIC support — EXIF/XMP tags usable in the file list with readmode=internal, and auto-rotating previews fixed — and the release notes add that Windows 11 ships the needed codec. The notes make no equivalent statement for Windows 10, so this site will not promise Windows 10 users the identical HEIC preview experience; the tag support in the GUI is the same release, but the codec half of the feature is tied by the maintainer to Windows 11. Everything else in the current release — the SubjectArea addition in the Regions tab, the MapTiler V4 map layers, the tag-form definitions, the style-change crash fix — is platform-neutral within Windows. The side-by-side is in the Windows 11 guide, and the release itself is itemised in V6.3.12: What’s New. The map deserves one Windows 10 note of its own: it needs WebView2Loader.dll plus the Microsoft Edge (WebView2) runtime, listed in the requirements for the OpenStreetMap feature only — everything else in the program works without them.

Keeping a Windows 10 setup current

Because the GUI and ExifTool update on independent schedules — the GUI’s latest is V6.3.12; ExifTool’s latest overall is 13.59 while its production release is 13.55 — a Windows 10 setup stays current by watching two version numbers, not one. Which ExifTool to pair, and how to read that production-versus-latest distinction, is decided in Which ExifTool Version Should You Pair. The discipline that makes updates painless is the pairing discipline: keep exiftool.exe with its exiftool_files folder, keep the GUI’s files together, and a version swap is a folder swap rather than a troubleshooting session. If something does misbehave after a change, the Troubleshooting hub orders the checks by likelihood — pairing first, files second, platform last, because on Windows 10 the platform is rarely the problem.

Frequently asked questions

Is Windows 10 still a good platform for ExifToolGui?

By the program’s own documentation, yes: Windows 10 is named, with Windows 11, as highly recommended, above the documented Windows 7/8 baseline. The current V6.3.12 release is the build to run there.

The install tutorials mention Windows 11. Do they apply to me?

The steps do. Installation is about distribution choice and the ExifTool pairing — installer fetch versus manual rename — and those are identical on Windows 10. Where a tutorial step depends on the OS itself, this page flags it; the HEIC codec note is the main one.

Which build do I download for 64-bit Windows 10?

The Win64 one: ExifToolGUI_X64.exe as a portable, or the installer, which installs Win64 files by default on Win64 systems. The /Win32 installer switch exists to force the 32-bit files, for the rare case that needs them.

Similar Posts