ExifToolGui Portable vs Installer: Which Should You Use?

ExifToolGui V6 — Frank Bijnen’s maintained continuation of Bogdan Hrastnik’s Windows front-end for Phil Harvey’s ExifTool — is distributed two ways: portable executables you simply unzip and run, and an installer that sets the program up and can fetch ExifTool for you. The two routes produce the same program, but they differ in exactly the places that cause confusion: what happens with ExifTool, and which Windows build you end up with. This page lays out the differences from the V6.3.12 release itself, then the 32-bit versus 64-bit question, so you can pick deliberately instead of re-downloading later. Both routes are linked from our download page; more guidance sits in the Troubleshooting hub.

What you actually download in each case

The V6.3.12 release offers four assets. The portable route gives you a single executable per architecture: ExifToolGUI_X64.exe for 64-bit Windows (21,758,464 bytes, as measured for this site) or ExifToolGUI.exe for 32-bit Windows (15,870,976 bytes). The installer route gives you ExifToolGUI_install_6.3.12.1.exe — the updated installer asset; the original 6.3.12.0 installer is the same program, and the .1 update changed only the installer (it downloads the ExifTool package from SourceForge during install if selected, with no functional changes to the GUI, per the release notes). The portable tradition is old in this program: the original v5 GUI already needed no installation — unzip it anywhere, make a shortcut, and settings go to an .ini file beside the executable rather than the registry. V6 keeps its settings the same way (ExifToolGUIV6.ini).

The decisive difference: ExifTool

Neither program is usable without ExifTool, and here the routes genuinely diverge. The portable executables do not bundle ExifTool at all — it is a separate required download that you must obtain, rename (exiftool(-k).exe becomes exiftool.exe) and pair yourself, keeping the exiftool_files folder with the exe. The installer can fetch ExifTool during setup: you choose the zip by Phil Harvey (downloaded and renamed into the install folder for you) or the self-installing package by Oliver Betz. So the portable route is not worse — it is more manual. Users who hit the ‘ExifTool not found’ error are disproportionately portable users who reasonably assumed the engine was inside. If that is you right now, the fix is five minutes of pairing, detailed in the not-found guide — or, if the installer’s fetch itself failed, pair it manually after installing.

32-bit vs 64-bit: which build your Windows needs

Match the build to your Windows, with one helpful asymmetry: 64-bit Windows runs both builds, while 32-bit Windows runs only the 32-bit build. The release names make the mapping explicit — ExifToolGUI_X64.exe is the Win64 portable, ExifToolGUI.exe is the Win32 portable. If you are on 64-bit Windows (the common case today), take the X64 portable, or let the installer decide: on Win64, the installer installs the Win64 files by default. There is one deliberate exception, straight from the V6 documentation: pass the /Win32 switch to the installer to force the Win32 files even on a 64-bit system. That switch exists for people who have a specific reason to run the 32-bit build on a 64-bit machine — if you do not have such a reason, the default is the right answer. What you should not do is mix pieces casually: whichever route you take, keep each program’s file set together (the GUI’s files in its folder, exiftool.exe with its exiftool_files folder), because partial moves are the root of most pairing failures.

So which should you choose?

  • Choose the installer if you want the ExifTool pairing done for you, you are setting the program up once on your main PC, and you are happy for it to live in an installed location with its settings file there. The installer’s architecture choice is also automatic on 64-bit Windows.
  • Choose the portable build if you want the program on a USB stick or in a folder you control, you work on more than one PC, or you prefer software that writes its settings beside itself and touches nothing else. Accept that pairing ExifTool is a manual step — once per location.
  • Either way, you end up with the same V6.3.12 program, the same GPL-3.0 licence (the licence verified for Bijnen’s fork), and the same requirement: ExifTool present, correctly named, with its folder. Switching routes later costs nothing but a re-download and a re-pairing.

One shared caveat closes the comparison: both routes are Windows-only. The V6 documentation describes Windows 7 and 8 support and highly recommends Windows 10 or 11; there is no portable trick that makes this GUI a Mac or Linux program. Cross-platform needs are a different conversation — see ExifToolGui on Linux for the working options there.

Frequently asked questions

Is the portable version missing features?

The release notes draw the portable/installer line at distribution and at the ExifTool fetch — not at features. The portable penalty is manual pairing, not reduced capability. The one component to keep with the program is the map’s WebView2Loader.dll; if the map matters to you, keep the extracted file set intact, as the map page in the Troubleshooting hub explains.

I installed with the installer on 64-bit Windows but want the 32-bit build. How?

Re-run the installer with the /Win32 switch. The V6 documentation states that Win64 systems get Win64 files by default and that /Win32 forces Win32 files — that switch is the supported way to make the exception.

Can I switch from portable to installed later?

Yes. The program’s settings live in an .ini file (ExifToolGUIV6.ini) rather than deep system state, and your photos are never tied to the distribution route. Re-pair ExifTool after the switch — the pairing is per location — and continue where you left off.

Similar Posts