ExifToolGui V6.3.12: What’s New

ExifToolGui V6.3.12 is the current release of Frank Bijnen’s maintained fork of Bogdan Hrastnik’s Windows front-end for ExifTool — released May 8, 2026, under GPL-3.0, on GitHub. This page is a faithful rundown of its release notes and nothing else: every item below comes from the V6.3.12 release itself, because a changelog page that embellishes its source helps no one. The notes are short and practical — a translation update, a meaningful HEIC improvement, a map refresh, a flexibility change in how tag fields are defined, and one crash fix — plus a later installer-only update that deserves its own clarification. The release files are linked from our download page; version context lives in the Platforms & Versions hub.

The release items, one by one

  • Updated Japanese translation. The release refreshes the program’s Japanese language support — one of the optional language components the V6 line maintains alongside the program.
  • Improved HEIC support. EXIF and XMP tags of HEIC files are now usable in the file list with readmode set to internal, and a bug that auto-rotated HEIC previews was fixed. The notes add the platform condition: Windows 11 ships the codec this relies on. This is the item with the widest user impact in the release, and it is covered in context in the Windows 11 guide.
  • SubjectArea added in the Regions tab. The Regions tab — where region-based metadata such as face and subject areas is surfaced — gained SubjectArea, extending the region information the GUI presents and edits alongside ExifTool’s tag model.
  • MapTiler baselayers updated to V4. The map’s MapTiler layers moved to V4, a Hybrid satellite layer was added, and label sizes were fixed. If the map is part of your geotagging workflow, this release is the map refresh; the map’s requirements (WebView2Loader.dll plus the Edge WebView2 runtime) are unchanged, and its failure modes are covered in the Troubleshooting hub.
  • Tag-form definitions in file list and Workspace. Field definitions for the file list and the Workspace now accept tag forms written as G0:G1:Tag, G1:Tag, G0:Tag, or a bare Tag. In plain terms: where you define which tags appear as columns or panel fields, you can now specify the tag with its group prefixes in any of those forms, rather than being limited to one spelling — a precision improvement for users who build custom Workspaces.
  • Crash fix: access violation when changing styles. The release fixes an access violation triggered by changing styles. A crash with a named trigger and a shipped fix is the most concrete reason in this list to move off an older V6 build if you have hit instability.

What shipped in the release

The V6.3.12 release assets are the two portable executables — ExifToolGUI.exe (Win32, 15,870,976 bytes as measured for this site) and ExifToolGUI_X64.exe (Win64, 21,758,464 bytes) — and the installer, ExifToolGUI_install_6.3.12.0.exe. As with every V6 release, the portable executables do not bundle ExifTool: the engine remains a separate download that you pair, by the rename ritual or the installer’s fetch. Which shape of the program to run is decided in Portable vs Installer, and which engine version belongs beside it in Which ExifTool Version Should You Pair. The project behind the release is actively followed — measured for this site at 1,048 GitHub stars — and exiftool.org links this fork as the current Windows GUI.

The 6.3.12.1 installer note — read this before version-hunting

After V6.3.12 shipped, the same release gained an updated installer: ExifToolGUI_install_6.3.12.1.exe. The versioning trips people up, so the release’s own wording governs here: the .1 is not a new program version. It is an updated installer for the same V6.3.12 program, which downloads the ExifTool package from SourceForge during install if that option is selected — and the notes state explicitly that there are no functional changes in the GUI executable. Practical consequences: if you installed with the .1 installer, your program is V6.3.12, full stop; if you run the portable build, there is no .1 anything to chase; and if an older installer struggled to fetch ExifTool, the updated installer — or five minutes of manual pairing — is the fix, as the installer-download guide explains.

Should you update?

If you run any earlier V6, this release gives you three concrete reasons: the style-change crash fix, the HEIC improvement if you handle phone photos (strongest on Windows 11, per the notes’ codec remark), and the map layer refresh if you geotag visually. The tag-form change matters if you maintain custom Workspace or file-list definitions. Updating the GUI does not touch your photos and does not change your ExifTool: the pairing rules are the same before and after (exiftool.exe, correctly named, with its exiftool_files folder). How the fork reached this release from Hrastnik’s original is traced in V5 vs V6.

Frequently asked questions

Is V6.3.12.1 a newer version of the program?

No. It is an updated installer for V6.3.12, released so the installer can download the ExifTool package from SourceForge during setup. The release notes state there are no functional changes in the GUI itself.

What is the single biggest change in V6.3.12?

By user impact, the HEIC improvement: EXIF/XMP tags usable in the file list with readmode=internal and the preview auto-rotation fixed, leaning on the codec Windows 11 ships. The style-change crash fix is the other item with a clear before-and-after.

Did V6.3.12 change the ExifTool pairing?

No. The arrangement is unchanged: ExifTool is a separate required download, unbundled in the portable builds, fetchable by the installer. The release’s new tag-form definitions concern how you write tag names in Workspace and file-list definitions, not how the engine is paired.

Similar Posts