ExifToolGui needs ExifTool — Phil Harvey’s command-line application and Perl library — paired beside it, and ExifTool’s version numbers contain a distinction most download pages flatten: as of this writing, the latest version overall is 13.59 (released May 27, 2026), while the latest production release is 13.55 (April 7, 2026). Those are both true, they mean different things, and Harvey’s own history page draws the line explicitly. This page explains the distinction exactly as its author states it, then helps you choose which of the two belongs beside your GUI. Both the GUI and ExifTool are linked from our download page; pairing mechanics live in the Troubleshooting hub, and platform context in the Platforms & Versions hub.

The distinction, in the author’s own terms

ExifTool’s history page states: ‘The most recent production release is Version 13.55. (Other versions are considered development releases, and are not uploaded to MetaCPAN.)’ So the numbering after 13.55 — 13.56, 13.57, 13.58 and 13.59 — are development releases: real, published, downloadable releases, but not what the author designates as the production line. And 13.59 is simultaneously the latest release overall: a security update (May 27, 2026) that also added a NewUUID Extra tag and new decoding, including a Canon RF lens and the Sony ILCE-7RM6. Any page that calls 13.59 ‘the latest production release’ is wrong per the author; any page that hides 13.59’s existence is incomplete. The vocabulary matters because ‘production’ is Harvey’s stability designation, and ‘latest’ is a calendar fact — you are choosing which of the two properties you value, with full knowledge of both.

Choosing: stability designation or newest changes

• Pair production 13.55 if you want the release the author designates for production use — the conservative choice for a working photo library, where the value is a settled, designated-stable engine under your edits. It is also the line distributed through MetaCPAN, per the history page’s note.
• Pair latest 13.59 if you want the newest work: the security update and the newest camera and lens decoding (a new Canon RF lens and Sony ILCE-7RM6 support arrived in this release). For users whose newest camera files are the ones being tagged, development releases are how support reaches them first.
• Either way, the GUI does not care which you picked. ExifToolGui drives exiftool.exe as its engine; both 13.55 and 13.59 pair by the same rules. Switching later is a folder swap, not a reinstallation of the GUI.

One framing rule this site follows, and recommends: when you describe your setup to anyone — a forum, a colleague — name the number and its status (‘13.59, the latest development release’ or ‘13.55, the production release’). Half the confusion in ExifTool discussions is two people saying ‘latest’ and meaning different lines.

Pairing the version you chose

The mechanics are identical for both versions, and they are ExifTool’s own documented ones. Download the Windows zip for your chosen version (for 13.59, the 64-bit zip is exiftool-13.59_64.zip; a 32-bit zip is also published). Extract it fully. The executable inside is named exiftool(-k).exe — rename it to exiftool.exe for command-line and GUI use (or to plain exiftool if your Windows hides extensions). And keep the exiftool_files folder with the exe: ExifTool’s documentation states that if you move the exe, that folder must move too. If you use the ExifToolGui installer instead, it can fetch ExifTool during setup — Harvey’s zip, renamed into the install folder, or Oliver Betz’s self-installing package (the Windows builds rest on Betz’s launcher work). Failure at any of these steps presents as the classic error, fixed in the not-found guide. The GUI version you pair the engine with should itself be current: V6.3.12, whose changes are itemised in What’s New in V6.3.12.

Verify your download against the publisher’s checksums

ExifTool is one of the tidy cases in software distribution: the publisher posts a checksum file for each release (checksums-13.59.txt for the current one), so the file you pair can be checked against the author’s own record. The 13.59 64-bit zip downloaded for this site’s research measured 11,183,675 bytes, and its SHA-256 — 44b512b25af500724ba579d0a53c8fc5851628b692dd5e5d94ae4a15c2cba9ec — matched the published checksum file exactly, as did its MD5. Verifying takes a minute and closes the one gap the version choice cannot: that the file on your disk is the file the number on the label promises. Note also where the file comes from: exiftool.org’s download links currently redirect to SourceForge, to reduce load on the project’s server — a redirect there is the expected route, not a warning sign.

Frequently asked questions

Is 13.59 safe to use if it is ‘only’ a development release?

‘Development release’ is the author’s classification, not a warning label this site can upgrade or downgrade: Harvey publishes these releases, designates 13.55 as production, and notes development versions are not uploaded to MetaCPAN. 13.59 is, additionally, described in the history as a security update. Choose by the criterion that matters to you — the production designation, or the newest changes — with both facts in view.

Does ExifToolGui require a specific ExifTool version?

The V6 documentation’s requirement is that ExifTool be downloaded and installed — the pairing itself — rather than one pinned version. The practical discipline is to run a current, deliberately chosen release (13.55 production or 13.59 latest) and to keep its files together.

What licence does ExifTool carry?

Harvey’s wording, which this site uses verbatim rather than abbreviating: ExifTool is free software that you can redistribute and/or modify under the same terms as Perl itself. That is a different licence statement from the GUI fork’s GPL-3.0 — one more reason the GUI and the engine should never be merged into a single product description. Their relationship is traced in V5 vs V6 for the GUI side.

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.

Two different programs share the name ExifToolGui, and telling them apart explains most version confusion around this software. V5 is the original: Bogdan Hrastnik’s Windows front-end for Phil Harvey’s ExifTool, documented on the GUI pages of exiftool.org. V6 is the maintained fork: Frank Bijnen’s continuation of Hrastnik’s program on GitHub, currently at V6.3.12. They are related by lineage, not by authorship, licence or era — and one thing this page will not do is repeat the claim, common on download sites, that the original ended at a neat final version number. The primary source does not support one. The platform and version series is in the Platforms & Versions hub; current files are on the download page.

The original: Bogdan Hrastnik’s GUI, documented to 2012

The facts the primary source supports are these. Hrastnik published the first ExifToolGUI, v1.00, on May 27, 2007, writing on exiftool.org/gui that he had made it for his own private use. The official GUI page documents the program as ‘ExifToolGUI for Windows v5.xx’ and its footer was last modified in May 2012. That is where the verifiable trail of the original line ends in this site’s fact base: the page states no final version number for the 5.x line, and no primary source confirming a specific last release was found — so this site describes the original’s 5.x line as documented up to 2012 on exiftool.org/gui, and nothing stronger. What the v5 program was, the page does document: a Windows GUI to view all metadata ExifTool recognises, edit the frequently used tags, and modify multiple selected files at once, with Filelist, Metadata, ExifTool direct and GoogleMap panels. Its requirements were of its era — Windows XP through Windows 7-64bit — and its preparation ritual is the one still quoted today: unzip the Windows ExifTool package, rename exiftool(-k).exe to exiftool.exe, and place it where the GUI expects, on pain of a startup error. The GUI itself needed no installation, kept settings in ExifToolGUI.ini beside the executable, and used UTF-8 for all metadata display and editing.

The fork: Frank Bijnen’s V6, the current program

The GitHub repository, created in July 2023, describes itself as ‘an updated version of the ExifToolGui program created by Bogdan Hrastnik’ — a continuation, openly credited. Its licence is verified and specific: GPL-3.0, per the repository’s licence detection and Bijnen’s updated licence statement of March 23, 2024. (Note the asymmetry: no licence for Hrastnik’s v5 is stated on the original’s page, so GPL-3.0 belongs to the fork and must not be projected backwards onto v5.) The current release is V6.3.12, updated May 8, 2026, and ExifTool’s own site now links this fork as the current Windows GUI. Documented platform support moved with the times: Windows 7/8 runnable, Windows 10 or 11 highly recommended. The fork’s practical additions over the documented v5 picture include an installer that can fetch ExifTool during setup (the original ritual, automated), an OpenStreetMap map rendered via WebView2 with MapTiler layers in place of the v5 GoogleMap panel, and active release maintenance — V6.3.12 alone updated the Japanese translation, improved HEIC handling, added SubjectArea to the Regions tab and fixed a style-change crash, as itemised in What’s New in V6.3.12.

Side by side

• Author: V5 — Bogdan Hrastnik. V6 — Frank Bijnen (continuing Hrastnik’s program, credited in the repo).
• Home: V5 — exiftool.org/gui, page last modified May 2012. V6 — github.com/FrankBijnen/ExifToolGui, releases ongoing (V6.3.12, May 2026).
• Licence: V5 — none stated on the original’s page (unverified). V6 — GPL-3.0, verified.
• Windows: V5 — XP to Win7-64bit era. V6 — Win7/8 documented, Win10/11 highly recommended.
• ExifTool setup: both need ExifTool separately; V5 made the rename fully manual, V6’s installer can fetch and rename it for you, and V6’s portable builds keep the manual ritual.
• Map: V5 — GoogleMap panel. V6 — OpenStreetMap via Edge WebView2, MapTiler layers (V4 in V6.3.12).
• Settings: both keep an .ini beside the program (ExifToolGUI.ini; ExifToolGUIV6.ini for the fork).

Which should you use?

On a current Windows PC there is no real contest, and the original’s own ecosystem says so: exiftool.org links Bijnen’s fork as the current Windows GUI. V6 is maintained, licensed clearly, documented for Windows 10/11, and pairs with current ExifTool versions — the choice of which one is its own question, answered in Which ExifTool Version Should You Pair. The original line matters as history and as the source of the pairing ritual every user still performs; if you are following an old tutorial that assumes v5 — including its GoogleMap panel or its Win7-era requirements — translate it through the differences above, or work from the V6 material in the Platforms & Versions hub. And if you meet a page stating a definitive final version for the original with a date and a hash attached, treat it the way this site does: as a claim still waiting for a primary source.

Frequently asked questions

Is V6 made by the same author as V5?

No. V5 is Bogdan Hrastnik’s program. V6 is Frank Bijnen’s continuation of it, hosted on GitHub since 2023 and credited as such in its own README. Phil Harvey, author of ExifTool itself, is a third person — he makes the engine both GUIs drive.

What was the final version of the original ExifToolGui?

This site cannot tell you, because the primary source does not: exiftool.org/gui documents the v5.xx line and was last modified in May 2012, without stating a final version number. Claims of a specific final 5.x release circulate on third-party sites but are not verified from the author’s page, so they are not repeated here as fact.

Can V6 read my old V5 setup?

The kept-through-lineage pieces are the concepts: the pairing with a renamed exiftool.exe, settings in an .ini beside the program (named ExifToolGUIV6.ini in the fork), and the Workspace way of defining tag panels. For a fresh start on a modern PC, install V6.3.12 from the download page and pair a current ExifTool — the migration that matters is versions, not settings archaeology.

Start with the honest answer: there is no Linux build of ExifToolGui. Not of Frank Bijnen’s maintained V6 fork, and not of Bogdan Hrastnik’s original. Both are Windows programs — the V6 documentation describes Windows 7/8 support and recommends Windows 10 or 11. If you work on Linux and arrived here hoping for a download, this page will not waste your time pretending otherwise. What it can do is lay out the options that genuinely work on Linux, with their real conditions: the cross-platform GUI in this family, and the engine underneath everything, which is at home on Linux in a way the GUI never was. The platform series is collected in the Platforms & Versions hub; Windows users want the download page instead.

Option 1: jExifToolGUI — the cross-platform GUI in this family

The GUI that does run on Linux is a different program: jExifToolGUI, by Harry van der Wolf. It is a Java/Swing front-end for ExifTool built for Windows, Linux and macOS, and its conditions are explicit. It requires Java 8 (1.8) or newer. And — the family resemblance — ExifTool is not included: you download and install ExifTool separately, and the GUI drives it, exactly the pairing pattern Windows users know. Its documented capabilities cover the jobs most people want a GUI for: copying tags from a reference image to many photos, extensive renaming from EXIF data, GPS and geotagging work, lens templates, and user-defined tag sets. Two facts must travel with the recommendation. Its latest release is 2.0.2, dated March 18, 2023 — and its README states, in capitals, that development has stopped; the author invites a takeover or fork that has not superseded it. So jExifToolGUI is a working option today and a frozen one: fine to use, wrong to build long-term plans on. Its predecessor, pyExifToolGUI, is formally superseded — its own site tells users to switch to jExifToolGUI.

Option 2: ExifTool itself — the engine is platform-independent

The deeper answer is that the program doing the actual metadata work was never Windows-bound. Phil Harvey describes ExifTool as a platform-independent Perl library plus a command-line application for reading, writing and editing meta information — EXIF, GPS, IPTC, XMP, maker notes and more. On Linux, the full Perl distribution (the Image-ExifTool tar.gz, 7.9 MB listed for the current release) is the native route: no front-end, no pairing problem, every capability the GUIs expose, driven from the command line or from scripts. The licence wording to use for ExifTool is Harvey’s own: free software, redistributable and modifiable under the same terms as Perl itself. Version choice applies on Linux exactly as on Windows — the latest release overall is 13.59 (May 27, 2026), while the latest production release is 13.55 — and the version-pairing guide explains how to choose between them. For many Linux users this is not a consolation prize: batch metadata work is scriptable in a way no GUI session is, and the GUI was always a convenience layer over this engine, never the engine itself.

What does not work, stated plainly

This page will not recommend routes it cannot source. The V6 documentation’s silence about Linux is total — no build, no instructions, no compatibility statement — so claims that the Windows GUI simply runs under Linux are not something the maintainer’s material supports, and you will not find them made here. Likewise, ExifToolGui’s own site history offers no Linux chapter: the original GUI’s page described a Windows program for the WinXP-to-Win7 era, and the fork continues on Windows. If a workflow absolutely requires the ExifToolGui interface itself — its Workspace panels, its specific layout — it requires Windows, and the platform guides for that route are the Windows 11 and Windows 10 pages. Linux users choosing between the two real options above are choosing between a frozen-but-friendly GUI and a living command-line engine; many end up with the engine for batch work and, at most, the Java GUI for browsing.

A practical recommendation

• You want a graphical program on Linux today: jExifToolGUI 2.0.2, with Java 8 or newer and a separately installed ExifTool — adopted with eyes open about its stopped development.
• You want capability and longevity: ExifTool itself, as the Perl distribution, at production 13.55 or latest 13.59 by the same logic as the pairing guide. This is the option with an actively maintained future.
• You want ExifToolGui specifically: that means Windows 10 or 11, per its own documentation — there is no Linux edition to wait for on any announced roadmap this site can source.

Background on how the Windows line reached this point — an original documented up to 2012, then a maintained fork — is in ExifToolGui V5 vs V6, which also explains why the ‘ExifToolGui’ name and the cross-platform alternatives are so often confused.

Frequently asked questions

Will there be a Linux version of ExifToolGui?

Nothing in the maintainer’s repository or documentation announces one, and this site does not speculate. As published, both the original GUI and the V6 fork are Windows-only. The maintained, living software on Linux in this family is ExifTool itself.

Is jExifToolGUI the same program as ExifToolGui?

No. Different author (Harry van der Wolf), different technology (Java/Swing), different licence line (GPL v3+), and a different feature set — it is an alternative front-end for the same ExifTool engine, not a port of ExifToolGui. Its development has stopped at 2.0.2 (2023-03-18).

Does ExifTool on Linux do everything the GUI does?

The direction of dependency runs the other way: the GUIs expose ExifTool’s capabilities through panels. ExifTool reads, writes, renames, geotags from track logs and deletes metadata in groups or altogether, per its own feature list. What you give up on the command line is the visual workflow, not the metadata power.

Windows 10 is, with Windows 11, one of the two platforms the ExifToolGui documentation explicitly points users to. The V6 documentation for Frank Bijnen’s continuation of Bogdan Hrastnik’s GUI says the program should run on Windows 7 and 8, and that it is highly recommended to use Windows 10 or 11. So on Windows 10 you are not running legacy software on sufferance — you are in the maintainer’s recommended configuration. This page covers compatibility, how setup works on this system, and where Windows 10 differs from 11 in the current release notes. Start from the files on our download page; the series lives in the Platforms & Versions hub.

Compatibility on Windows 10

ExifToolGui is Windows-only: no Mac or Linux build exists for the original GUI or the V6 fork. The current release, V6.3.12 (May 8, 2026, GPL-3.0), is the build to run, and on 64-bit Windows 10 — the common case — the Win64 files are the default choice: the installer installs Win64 files by default on a 64-bit system (with /Win32 to force Win32), and the portable line offers ExifToolGUI_X64.exe alongside the Win32 ExifToolGUI.exe. That 32/64-bit detail is one of the few real decisions in setup, and it is unpacked in Portable vs Installer. The other structural fact of setup is that the GUI is a front-end: Phil Harvey’s ExifTool does the metadata work, it is a separate download, and no version of Windows changes that arrangement.

Setup: the install tutorials, applied to Windows 10

The installation walkthroughs on this site were written around the current release and apply directly to Windows 10, because the steps are about the pairing, not the OS version:

• Install ExifToolGui on Windows 11 — the full installer walkthrough. On Windows 10 the same choices appear: let the installer fetch ExifTool (Phil Harvey’s zip, renamed into the install folder, or Oliver Betz’s self-installing package), and let it pick the Win64 files on a 64-bit system.
• First-launch setup — what to check the first time the program opens: that the pairing is recognised, that a test photo’s metadata loads, and that the panels show what ExifTool reads.
• The portable alternative: unzip ExifToolGUI_X64.exe’s release set, download ExifTool’s Windows zip, rename exiftool(-k).exe to exiftool.exe, and keep the exiftool_files folder beside it. The rename is the step everyone misses; the not-found guide exists because of it.

Whichever route you take, verify setup with one photo before batch work: select a file, see its metadata, make one small edit, save, and re-read. That minute of testing validates the whole chain — GUI, pairing, write path — on your machine.

Where Windows 10 differs from Windows 11 in the release notes

One difference is documented, and it concerns HEIC photos. V6.3.12 improved HEIC support — EXIF/XMP tags usable in the file list with readmode=internal, and auto-rotating previews fixed — and the release notes add that Windows 11 ships the needed codec. The notes make no equivalent statement for Windows 10, so this site will not promise Windows 10 users the identical HEIC preview experience; the tag support in the GUI is the same release, but the codec half of the feature is tied by the maintainer to Windows 11. Everything else in the current release — the SubjectArea addition in the Regions tab, the MapTiler V4 map layers, the tag-form definitions, the style-change crash fix — is platform-neutral within Windows. The side-by-side is in the Windows 11 guide, and the release itself is itemised in V6.3.12: What’s New. The map deserves one Windows 10 note of its own: it needs WebView2Loader.dll plus the Microsoft Edge (WebView2) runtime, listed in the requirements for the OpenStreetMap feature only — everything else in the program works without them.

Keeping a Windows 10 setup current

Because the GUI and ExifTool update on independent schedules — the GUI’s latest is V6.3.12; ExifTool’s latest overall is 13.59 while its production release is 13.55 — a Windows 10 setup stays current by watching two version numbers, not one. Which ExifTool to pair, and how to read that production-versus-latest distinction, is decided in Which ExifTool Version Should You Pair. The discipline that makes updates painless is the pairing discipline: keep exiftool.exe with its exiftool_files folder, keep the GUI’s files together, and a version swap is a folder swap rather than a troubleshooting session. If something does misbehave after a change, the Troubleshooting hub orders the checks by likelihood — pairing first, files second, platform last, because on Windows 10 the platform is rarely the problem.

Frequently asked questions

Is Windows 10 still a good platform for ExifToolGui?

By the program’s own documentation, yes: Windows 10 is named, with Windows 11, as highly recommended, above the documented Windows 7/8 baseline. The current V6.3.12 release is the build to run there.

The install tutorials mention Windows 11. Do they apply to me?

The steps do. Installation is about distribution choice and the ExifTool pairing — installer fetch versus manual rename — and those are identical on Windows 10. Where a tutorial step depends on the OS itself, this page flags it; the HEIC codec note is the main one.

Which build do I download for 64-bit Windows 10?

The Win64 one: ExifToolGUI_X64.exe as a portable, or the installer, which installs Win64 files by default on Win64 systems. The /Win32 installer switch exists to force the 32-bit files, for the rare case that needs them.

Windows 11 is the platform ExifToolGui is currently developed for in practice. The program — Frank Bijnen’s V6 continuation of Bogdan Hrastnik’s Windows front-end for Phil Harvey’s ExifTool — documents Windows 7 and 8 as runnable, but its documentation states plainly that Windows 10 or 11 is highly recommended, and its current release, V6.3.12, contains a note that only makes sense on Windows 11: an improvement to HEIC photo support that relies on a codec Windows 11 ships. This page covers compatibility, the pairing you still have to do, and exactly what the V6.3.12 release notes say about HEIC. Program files are on our download page; the platform series continues in the Platforms & Versions hub.

Compatibility: what the documentation actually promises

ExifToolGui is Windows-only software — there is no Mac or Linux build of the V6 fork, just as there was none of the original. Within Windows, the V6 requirements text says the GUI should run on Windows 7 and 8 in both 32- and 64-bit forms, with Windows 10 or 11 highly recommended. On Windows 11 you are therefore squarely in the configuration the maintainer points users to, running the current release: V6.3.12, released May 8, 2026, under GPL-3.0, maintained on GitHub where ExifTool’s own site links it as the current Windows GUI. One compatibility point is about the engine rather than the interface: the GUI is only a front-end, so your Windows 11 setup is complete only when ExifTool itself is present and paired — see the pairing notes below and, if you are choosing versions, Which ExifTool Version Should You Pair.

The HEIC notes from V6.3.12, exactly as released

HEIC is the photo format most Windows 11 users meet through phones, and V6.3.12’s release notes address it directly. The notes record improved HEIC support: EXIF and XMP tags of HEIC files are usable in the file list with readmode set to internal, and a bug that auto-rotated previews was fixed. Then comes the platform note: Windows 11 ships the codec needed for this. Read that carefully, because it defines what is the program’s doing and what is the operating system’s. ExifToolGui surfaces HEIC metadata in its list and panels; the preview rendering leans on a codec provided by Windows 11 itself. On Windows 11, in other words, HEIC handling in the current release is a combination of the GUI’s new tag support and a codec your OS already carries — one of the concrete reasons the documentation’s ‘highly recommended’ points at the newer systems. The same release also added SubjectArea to the Regions tab — region data being closely related to how modern phone photos describe their content — updated its map layers, and updated the Japanese translation; the complete rundown is in ExifToolGui V6.3.12: What’s New.

Setup on Windows 11 still means two downloads

Windows 11 does not change the program’s fundamental arrangement: ExifToolGui and ExifTool are separate pieces of software by different authors, and the portable GUI does not bundle the engine. Your two routes are the ones compared in Portable vs Installer. With the installer, ExifTool can be fetched during setup (Phil Harvey’s zip, renamed into the install folder for you, or Oliver Betz’s self-installing package), and on 64-bit Windows — the normal Windows 11 case — the installer installs the Win64 files by default, with /Win32 available to force the 32-bit files. With the portable X64 executable, you pair ExifTool manually: extract its zip, rename exiftool(-k).exe to exiftool.exe, and keep the exiftool_files folder beside the exe. Skip that pairing and the GUI’s first message will be the well-known one — the fix is in the not-found guide. The map feature has one more Windows 11-relevant piece: it renders through the Microsoft Edge (WebView2) runtime with WebView2Loader.dll, both listed in the V6 requirements as needed only for the OpenStreetMap map.

Windows 11 next to Windows 10

If you are moving between machines, the honest summary is that ExifToolGui treats Windows 10 and 11 as its recommended home in both cases — the documentation names them together. The platform difference that actually shows up in the release notes is the HEIC codec point above, which the maintainer ties to Windows 11 explicitly. Our Windows 10 guide covers the same program from the other side, including the install walkthroughs it links. Whichever system you land on, the version discipline is the same: current GUI (V6.3.12), a deliberately chosen ExifTool (production 13.55 or latest 13.59 — the distinction matters and is explained in the version-pairing guide linked above), and files kept together.

Frequently asked questions

Does ExifToolGui run on Windows 11?

Yes — Windows 11 is one of the two systems the V6 documentation highly recommends (Windows 10 is the other). The documented baseline is Windows 7/8, so Windows 11 is comfortably inside the supported picture for the current V6.3.12 release.

Why do HEIC photos behave better on my Windows 11 PC?

Per the V6.3.12 release notes, HEIC support improved in the GUI — EXIF/XMP tags usable in the file list with readmode=internal, and auto-rotating previews fixed — and Windows 11 ships the codec the feature relies on. It is the combination of the new release and the OS-provided codec.

Do I still need to download ExifTool separately on Windows 11?

Yes. The GUI never absorbed its engine. The installer can fetch ExifTool during setup; the portable build cannot. Either way, a working Windows 11 setup is GUI plus ExifTool, paired.