Download ExifToolGUI v6.3.12
Download ExifToolGui V6.3.12 (released May 8, 2026) for Windows 11/10. The main buttons below go to the files published in the FrankBijnen GitHub release. ExifTool is a separate, required companion download — it is listed below as well.
Portable Builds & the Required ExifTool Companion
The portable executables do not bundle ExifTool. Download ExifTool separately and place exiftool.exe next to the portable GUI (see the setup notes below).
Fulfilling ExifTool Core Requirements
ExifToolGUI operates strictly as a graphical presentation layout wrapper. It requires Phil Harvey’s core ExifTool engine to read and write metadata. Depending on how you deploy the app, follow the matching setup sequence below.
Using the Setup Installer (ExifTool Fetched During Setup)
The V6 installer can fetch ExifTool for you during setup, so a separate manual ExifTool download is not required if you use one of these options:
- Run the installer and, in the ExifTool step, choose to download and install ExifTool during setup.
- Choose “by Phil Harvey” — the setup downloads the ExifTool zip package, unzips it and renames the executable to
exiftool.exeinside the installation folder. - Or choose “by Oliver Betz” — the setup downloads and runs his self-installing ExifTool package after the GUI installation.
- Architecture: on 64-bit Windows the installer installs the 64-bit files by default. Pass
/Win32to the installer to force the 32-bit files instead.
Using Standalone Portable Executables (Manual Setup)
The portable builds (ExifToolGUI_X64.exe / ExifToolGUI.exe) do not bundle ExifTool, so pair them with a separate ExifTool download:
- Download the ExifTool Windows Executable zip package from exiftool.org — the same 64-bit file is offered here as exiftool-13.59_64.zip.
- Unpack the archive to extract the application object named
exiftool(-k).exe. - Rename the file from
exiftool(-k).exeto exiftool.exe. - Place the renamed
exiftool.exein the same folder as the portable GUI executable, and keep theexiftool_filesfolder next to it — if you move the executable, move that folder as well.
WebView2Loader.dll together with the Microsoft Edge (WebView2) runtime. Both are optional and are needed only for the map — the file list and metadata editing do not depend on them.
Release History — Checked Against the GitHub Releases
The rows below are taken from the release notes published in the FrankBijnen GitHub repository (listing checked on 2026-10-23). Only releases whose notes were read directly are listed here.
For the full release history, see the GitHub releases page: github.com/FrankBijnen/ExifToolGui/releases. Download release files from that repository rather than from third-party file hosts.
System Compatibility & Runtime Environment
ExifToolGui V6 is Windows-only — there is no Mac or Linux build of this GUI. The notes below summarise the requirements stated in the V6 documentation.
➔ 64-Bit Native Architecture
A 64-bit portable executable (ExifToolGUI_X64.exe) is published alongside the installer, and on 64-bit Windows the installer installs the 64-bit files by default.
➔ Legacy 32-Bit (x86) Windows
A 32-bit portable executable (ExifToolGUI.exe) is published with the V6 releases. If you install on 64-bit Windows but need the 32-bit files, run the installer with the /Win32 parameter. The V6 documentation states the GUI should run on Windows 7 and 8 (32/64-bit), with Windows 10 or 11 recommended.
➔ Map Feature (Optional)
The OpenStreetMap map pane is optional. It needs WebView2Loader.dll and the Microsoft Edge (WebView2) runtime. The rest of the GUI — file list, metadata panels and editing — does not depend on the map components. Optional language DLLs and an alternate, larger GeoLocation database are also listed in the V6 documentation.
How to Verify File Cryptographic Integrity
To check that a downloaded file was not altered or corrupted in transit, calculate its SHA-256 hash and compare it with the values listed below. A matching hash means the file is byte-for-byte identical to the file that was measured.
Open Native Windows PowerShell
Press the Windows Key, type PowerShell into your native start application bar grid, and launch the terminal sandbox environment.
Execute the Fingerprint Command
Change directories to your localized user downloads path and run the built-in file hashing engine utility command:
PS C:\> Get-FileHash .\ExifToolGUI_install_6.3.12.1.exe -Algorithm SHA256
Cross-Match String Outputs
Compare the hash shown in your PowerShell window with the SHA-256 values listed below for the exact file name you downloaded. If the two values match exactly, your copy is identical to the measured release file. If they differ, delete the file and download it again from the GitHub release.
fe1d69effefc5585093c39c784cfc1a468df8dca9fc55ec0895dcadf83bee0af ExifToolGUI_install_6.3.12.0.exe (original V6.3.12 installer, 27,144,135 bytes — approx. 25.9 MB)
b2a2e5db481d28cbd74452eee1e28cc264d03d58f07d8248f2a81e1088c2bf3f ExifToolGUI_X64.exe (portable Win64, 21,758,464 bytes)
6c872bd6434dd00ccf6885ed330b9be7c3fa746b55e0f36ccec2c4925a644bff ExifToolGUI.exe (portable Win32, 15,870,976 bytes)
59ca2b87b32502abbcfd51b4f4e605b6965bbbb5e11b37516b376afd1cab46dc exiftool-13.59_64.zip (ExifTool 13.59, 11,183,675 bytes)
44b512b25af500724ba579d0a53c8fc5851628b692dd5e5d94ae4a15c2cba9ec
GUI hashes: SHA-256 measured from the official GitHub release file on 2026-10-23 (GitHub does not publish digests for these assets). ExifTool zip hash: matches the publisher’s official checksum file (exiftool.org/checksums-13.59.txt).
Just Downloaded? Here is What to Do Next
If your browser or Windows flags the file, use the checks below instead of following override instructions from any website — including this one.
If the Browser Warns About the File
Browsers may warn that a file “isn’t commonly downloaded”, especially for smaller open-source projects. Do not look for override steps — use the warning as a prompt to verify instead:
- Confirm the download came from the GitHub release link on this page (github.com/FrankBijnen/ExifToolGui).
- Verify the file’s SHA-256 hash against the verification section above before running anything.
- If the hash does not match, delete the file and download it again from the GitHub release page.
If Windows Shows a Security Warning
Windows may show a “Windows protected your PC” dialog for a program it does not recognise. This page does not instruct you to override Windows security prompts.
- Check the file name and SHA-256 hash first (see the verification section above).
- Confirm the file came from the GitHub release linked on this page, not from a file host or another website.
- If anything differs — a different file name, a different hash, or a download from another site — do not run the file.
Need the portable builds or the ExifTool companion file instead?
Go back to our download options at the top of this page.
Unofficial Mirror (Terabox)
The two links below are kept for existing users. They point to files hosted on Terabox, a third-party file host. They are not the GitHub release, this site cannot verify the files behind them, and the GitHub links at the top of this page are the recommended source. If you use a mirror file, verify its SHA-256 against the values in the verification section above before running it.
