ExifToolGui First Launch: Set Up ExifTool Correctly
The first launch of ExifToolGui decides whether every later task feels easy or broken. ExifToolGui V6.3.12, maintained by Frank Bijnen as a fork of Bogdan Hrastnik’s original GUI, is only a front-end: all reading and writing is done by Phil Harvey’s ExifTool, a separate program the GUI must be able to find. This guide assumes you have the files from the download page and covers the checks to run before you edit anything that matters.
You will confirm three things in order: that the GUI can find exiftool.exe, that the file list and Metadata panel show real values for a test photo, and that a small test edit on a copied file saves and reads back correctly. If you have not installed yet, start with how to install ExifToolGui on Windows 11, then return here. More guides live in the Tutorials hub.
Make Sure the GUI Can Find exiftool.exe
If you used the installer and let it fetch ExifTool, exiftool.exe already sits in the installation folder and this step is a formality. If you use a portable build, place your renamed exiftool.exe in the same folder as the GUI executable, together with the exiftool_files folder that ships in the ExifTool zip. The GUI shows an error at startup when ExifTool cannot be found, and that error always means a pairing problem, not a damaged photo library.
A common cause is the file name. The Windows zip ships the program as exiftool(-k).exe, a name meant for drag-and-drop viewing. For command-line and GUI use it must be renamed to exiftool.exe (or simply exiftool if your Windows hides file extensions). Check the name first, check the folder second, and only then suspect anything else.
- exiftool.exe sits in the same folder as the GUI executable.
- The exiftool_files folder sits next to exiftool.exe.
- The file is renamed from exiftool(-k).exe to exiftool.exe.
Read the Main Window: File List, Metadata and Workspace
Open a folder containing a few JPEG photos. The file list shows one row per file, and clicking a file loads its metadata into the Metadata panel. The panel is driven by the current Workspace definition, which decides which tags are displayed and which can be edited. The default workspace already covers the frequently used tags, so there is no need to customise anything on day one.
Pick a photo you took yourself and sanity-check three values against reality: the camera model, the capture date and time, and one descriptive field such as Artist if your camera writes it. Correct values prove ExifTool is reading the file. Blank values on a phone photo may simply mean that tag was never written, which is normal and different from a pairing failure, where every file shows nothing.
Run One Safe Test Edit on a Copy
Before trusting the setup with originals, copy one photo to a test folder, open that folder in the GUI, and make a tiny reversible edit: select the copy, find a descriptive tag in the Workspace, type a test value, and save. Then click away and click back onto the file. If your test value is still there, the full read, write and re-read loop works.
This ten-minute habit protects you later. Batch features in this program apply changes to every selected file at once, which is exactly what you want once the setup is proven, and exactly what you do not want to discover is misconfigured on a folder of originals. The same copy-first approach runs through batch-editing a whole folder and the date fixes in changing DateTimeOriginal.
Know Where Settings Live and What Is Optional
The V6 GUI stores its settings in ExifToolGUIV6.ini beside the program, rather than scattering values through the Windows registry, so a portable setup stays portable when you move the folder, as long as exiftool.exe and exiftool_files move with it. Workspace definitions can be saved and re-used, a topic covered in depth in ExifToolGui Workspaces explained.
Two extras are optional on first launch. Language DLLs only matter if you want a non-English interface. The map needs WebView2Loader.dll and the Microsoft Edge WebView2 runtime and is only used for geotagging work such as geotagging from a GPX track log. Neither affects basic viewing and editing, so you can ignore both until you need them.
Keep the Pairing Intact When You Move Folders
Most first-launch problems return later for one mundane reason: the folder moved and ExifTool did not move with it. If you relocate a portable setup, move the GUI executable, exiftool.exe and the exiftool_files folder together as one unit, then repeat the thirty-second read test from this guide on arrival. A setup that was verified after its last move is a setup you can trust for the next batch.
The same discipline applies after downloading a newer ExifTool. The latest release overall is 13.59 (May 27, 2026) and the latest production release is 13.55 (April 7, 2026); swapping versions means replacing exiftool.exe and its companion folder as a matched pair, not dropping a lone new executable beside an old exiftool_files folder. Re-run the test edit after any swap, before the folder of originals, every time.
Frequently Asked Questions
Why does ExifToolGui say ExifTool was not found?
The GUI cannot see exiftool.exe. The portable builds do not bundle ExifTool, so download it separately, rename exiftool(-k).exe to exiftool.exe, and place it next to the GUI with its exiftool_files folder.
Which ExifTool version is current?
The latest release overall is 13.59 (May 27, 2026); the latest production release is 13.55 (April 7, 2026). Either pairs with ExifToolGui V6.3.12.
Where does ExifToolGui store its settings?
In ExifToolGUIV6.ini beside the program. Workspace definitions are stored there and can also be exported and imported as named definition files.
Once the test edit reads back correctly, your setup is done. Work through the Tutorials hub in any order from here: fix a date, shift a camera clock, or clean location data, knowing the pairing underneath each task has already been proven on a copy.