“ExifTool Not Found” in ExifToolGui: Fix the Pairing

ExifToolGui is a Windows graphical front-end for ExifTool — and that sentence explains this error. The GUI written originally by Bogdan Hrastnik and continued today as V6 by Frank Bijnen does not contain ExifTool itself. Phil Harvey’s ExifTool is a separate download, and when ExifToolGui cannot find a correctly prepared exiftool.exe where it expects one, it reports that ExifTool was not found. This is the single most common setup failure with this program — it shows up in this site’s search data as the query exiftool not found — and in almost every case the fix is not a reinstall or a setting. It is completing the pairing properly. If you do not have both pieces yet, start from our download page, then work through the checks below. More fixes like this one live in the Troubleshooting hub.

Why the GUI and ExifTool are two downloads

ExifTool is a platform-independent Perl library plus a command-line application by Phil Harvey. It has no graphical interface of its own. ExifToolGui is a third-party Windows front-end that sends your edits to ExifTool and shows you the results. The V6 documentation states the requirement plainly: ExifTool is a required, separate download. The portable V6 executables do not bundle it. Only the V6 installer can fetch ExifTool for you during setup, and even then it is downloading the separate program — your choice at install time is the ExifTool zip by Phil Harvey, which the installer downloads and renames into the install folder, or the self-installing package by Oliver Betz. So a fresh portable copy of the GUI with no ExifTool beside it is not broken. It is simply unpaired, and this error is how it tells you.

Check 1: the file must be renamed to exiftool.exe

This is the step most people miss. The Windows package of ExifTool does not ship a file called exiftool.exe. Inside the zip, the executable is named exiftool(-k).exe. The (-k) form is meant for double-clicking and drag-and-drop use: you drop files onto it to view their metadata. For command-line use — which is exactly how ExifToolGui drives it — ExifTool’s own documentation says to rename exiftool(-k).exe to exiftool.exe (or simply to exiftool, if your Windows is set to hide file extensions). If the file in your folder is still called exiftool(-k).exe, the GUI will not recognise it as its engine, no matter how many times you point the folder at it. Rename it, keeping the name exact, and start the GUI again.

Check 2: the exiftool_files folder must travel with the exe

The renamed executable is not self-contained. ExifTool’s Windows documentation states that if you move exiftool.exe, you must also move the exiftool_files folder that came in the same zip. A very common way to break a working setup is tidying up: copying just the exe into a tools folder, or into the GUI’s folder, and leaving exiftool_files behind in the Downloads folder or the extraction folder. The pairing then looks right — a file named exiftool.exe is present — but the program behind it cannot run properly. The reliable habit is to extract the whole zip first, rename the exe inside the extracted folder, and then move the exe and the exiftool_files folder together, as one unit, wherever they need to live.

Check 3: rebuild the pairing cleanly if it is still not found

If the name and the folder both look right and the error persists, rebuild the pairing from a clean extraction rather than patching a half-moved one:

  • Download a fresh ExifTool Windows zip from the download page (the current version is 13.59; see which ExifTool version to pair for the production-versus-latest distinction).
  • Extract the entire zip to a folder of your choice before renaming or moving anything.
  • Rename exiftool(-k).exe to exiftool.exe inside that folder.
  • Keep exiftool_files beside the exe — move both together if you relocate them.
  • Start ExifToolGui and test with one photo: select a file and check that its metadata loads. Metadata appearing in the panels means the pairing works.

If you used the portable GUI, also read Portable vs Installer — it explains which pieces each distribution does and does not bring with it. And if the GUI itself now refuses to open at all, that is a different failure: work through ExifToolGui Won’t Start next.

If you installed with the installer instead

The installer path avoids the manual rename because the installer can download ExifTool during setup and place it, renamed, into the install folder. If you chose that option and still see a not-found error, the download step itself is the suspect — an interrupted fetch during setup leaves the GUI installed without its engine. That case has its own page: Installer Can’t Download ExifTool walks through pairing the engine manually afterwards, which is always an option because the manual pairing is the same pairing, just done by hand.

Frequently asked questions

I downloaded ExifTool. Why does the GUI still say it is not found?

Most likely the executable still carries its shipped name, exiftool(-k).exe. ExifToolGui looks for exiftool.exe. Rename the file exactly, make sure the exiftool_files folder sits beside it, and restart the GUI.

Does the portable version of ExifToolGui include ExifTool?

No. The portable V6 executables do not bundle ExifTool; it is a separate required download. Only the installer can fetch ExifTool during setup, if you select that option.

Can I keep exiftool.exe anywhere I like?

What matters is that the GUI can find the correctly named executable and that the exiftool_files folder moves with it — ExifTool’s own documentation makes that pairing a condition of moving the exe at all. Keep the two together and the location is a matter of your own organisation.

Similar Posts