ExifToolGui’s job ends where the pixels begin. It inspects and fixes what a photo says — dates, credits, keywords, location — and it does not denoise, sharpen or enlarge the image itself. For the frames that need that work, the current tool class is AI photo editors: programs that use learned models to denoise high-ISO shots, upscale low-resolution files and generally rescue detail. This page covers the options linked from this site, described only at the level that can be stated responsibly — what each is for — with no invented version numbers and no prices. It closes the Workflows & Buying Guides hub sequence that starts with the metadata-first Lightroom workflow and the backup workflow. The metadata tools are on the download page.

Why the metadata pass comes first

AI editing produces new files, and new files are where metadata goes to be rewritten, dropped or quietly altered by export settings. Run the order this site teaches — metadata first — and two good things happen. Your masters carry true dates and credits before any editor touches them, so derivatives start from the truth; and you build the checking habit that catches what an export changed, by re-reading the finished file in ExifToolGui afterwards. The workflow is a loop, not a line: fix, edit, re-check. Skipping the first fix means every upscale of a family scan carries the scanner’s wrong date into the future, beautifully denoised and permanently mislabelled.

The options, described plainly

• Topaz Photo — an AI photo editor centred on denoise, sharpening and upscaling problem frames: the low-light shot, the heavy crop, the small old file that needs to become printable. Linked here as Topaz Photo.
• DxO PhotoLab — a RAW editor whose AI denoise is its headline strength, used by photographers who want the noise work inside a full develop workflow rather than as a separate rescue step. Linked here as DxO PhotoLab.
• Luminar Neo — an AI-driven photo editor positioned on creative editing with automated assistance, the option readers who dislike subscription-style suites often ask about. Linked here as Luminar Neo.

Some links on this page are affiliate links — see our affiliate disclosure. Those three descriptions are deliberately category-level. Features, versions and prices change faster than any guide can responsibly track, and the vendors’ own pages — reached through the links — are the place for the current specifics and trial terms.

Choosing by the problem in front of you

Noise is the problem (high-ISO events, old compact-camera files, night scans): denoise-led tools are the shortlist, and the honest test is your own worst file run through a trial, judged at the size you will actually print or share. Resolution is the problem (small originals, deep crops, phone photos destined for a wall): upscaling is the headline feature to test, again on your file, because source quality decides what any upscaler can honestly invent. The whole edit is the problem (you want developing and AI assistance in one place): a full editor with AI features fits better than a single-purpose rescuer. In all three cases the discipline is identical: work on a copy, export deliberately, and re-check the result’s metadata before it joins the library — dates and credits verified in ExifToolGui, location present or absent by your decision, not by an export default.

The archival case deserves its own sentence, because it is where this tool class earns the most gratitude. Old family scans and early digital files arrive with everything stacked against them: noise, low resolution, faded contrast — and, very often, scanner-written dates standing where capture dates should be. The full treatment is the loop in miniature: fix the dates on the scans first (our scanned-photo date guide covers setting a real capture date), denoise and upscale the copies, then verify that the finished files still carry the corrected dates and the family names you keyworded. Sentimental value is still value, and it deserves accurate records as much as client work does.

What AI editing cannot do

It cannot recover information that was never captured — upscaling synthesises plausible detail, it does not retrieve the real detail a bigger sensor would have recorded, and denoising trades texture for smoothness in ways that deserve a zoomed look before you commit a whole set. It cannot fix wrong metadata; a denoised file with the wrong date is still wrong, which is why this page is sequenced after the metadata guides rather than instead of them. And it cannot substitute for the archive habits in the backup workflow: the rescued frame, once you love it, needs the same three-copy protection as everything else you keep.

Frequently Asked Questions

Should AI editing come before or after metadata work?

After. Fix dates, credits and keywords on the masters in ExifToolGui first, edit copies in the AI tool, then re-read the exported file’s metadata and repair anything the export changed. That loop is the whole method.

Which of the three options is best?

The one that handles your actual problem file best in a trial: denoise-led rescue, RAW development with AI denoise, or AI-assisted creative editing are different centres of gravity. This page describes categories honestly and links the vendors; it does not crown a winner without your test file.

Will an AI editor preserve my metadata?

Not automatically — export settings decide what is written, kept or dropped. Verify with ExifToolGui after export: capture date, Artist, Copyright, keywords and GPS state, on every file that matters.

That completes the desk: metadata fixed, library backed up, problem frames rescued. Browse the full sequence in the Workflows hub, and revisit the comparisons in the Comparisons hub when the next tool decision arrives.

Two different disasters bring readers to this page, and they need different tools. In the first, photos are gone — deleted, or on a card that was formatted or is failing. In the second, the photos are there but broken — files that will not open, images or videos damaged in transfer or by a bad card. Recovery software addresses the first disaster; repair software addresses the second. ExifToolGui does neither — it views and edits metadata in files that exist and open — and this page says so plainly before comparing the tools that do. It lives in the Workflows & Buying Guides hub with the backup workflow that prevents most of these cases, plus the card reader guide for the reader-versus-card diagnosis. The metadata side is on the download page.

First rules, before any tool

• Stop using the card or drive. New data written over deleted files is what makes them unrecoverable; every photo taken on a card with deletions still on it lowers the odds.
• Work on a copy where you can. Recovery belongs on an image or duplicate of the medium, not on the only original, whenever the tool allows it.
• Save recovered files somewhere else. Never recover onto the same card or drive you are recovering from.
• Expect partial results. No tool can guarantee recovery: overwritten data may be unrecoverable, and a physically dead card may need a laboratory, not software. Any page that promises otherwise is selling, not informing.

Recovery vs repair: the distinction that picks the tool

Recovery tools scan storage for files that were deleted or lost — photos on a formatted card, a vanished folder — and reconstruct what the medium still holds. Repair tools take a file you already have, which exists but is corrupt, and rebuild it into something that opens: the category example in this comparison is EaseUS Fixo, which repairs corrupt photo and video files. The disasters feel similar (‘my photos won’t open’) and the tools are not interchangeable: running recovery on a corrupt-but-present file finds nothing to recover, and running repair on a deleted file finds nothing to repair. Diagnose which disaster you have — files missing, or files present but broken — and the table below narrows to the right row.

The tools compared

Some links on this page are affiliate links — see our affiliate disclosure. Compare more than one recovery tool against your actual card before paying for anything: reputable recovery tools let you scan and preview what was found first, and the scan result — not the marketing — is the evidence that your files are still there to be recovered.

Triage order matters as much as tool choice. Before any recovery scan, rule out the cheap explanations: try the card in a second reader and with a different cable, because a card that fails in one reader and reads in another was never a recovery case at all — the isolation routine is in the card reader guide. Only when the card fails everywhere, or files are genuinely missing, does the scan begin; and only when the scan’s preview shows your files do you have evidence that recovery is possible and a basis for choosing between the tools in the table.

After recovery: rebuild the metadata, then the backup

Recovered files often return with wounds metadata tools can actually address: file names that are generic, timestamps from the recovery process rather than the shoot, descriptive fields stripped along the way. That is ExifToolGui’s legitimate role in this story — after recovery, on the recovered copies, verify what capture dates survive, repair the ones that demonstrably do not (using evidence from neighbouring files, never guesses presented as fact), and re-apply credits and keywords. Then close the loop with Back Up the Photo Library You Just Cleaned: the recovered, re-documented library should immediately become a backed-up library, because a second loss after a lucky recovery is the one outcome nobody should accept.

Frequently Asked Questions

Can recovery software guarantee my photos back?

No, and distrust any tool that guarantees it. Recovery depends on the deleted data not having been overwritten and the medium still being readable. Overwritten data may be unrecoverable, and results are routinely partial — some files whole, some damaged, some gone.

My photos exist but will not open. Recovery or repair?

Repair. A present-but-corrupt file is a repair case (the Fixo row in the table). Recovery tools are for files that are deleted or lost. If the files are missing entirely, that is the recovery case.

Can ExifToolGui recover or repair photos?

No. ExifToolGui views and edits metadata in files that exist and open. Its role here is after recovery: checking and repairing metadata on the recovered copies, and documenting the library properly this time.

Prevention beats every row of that table: keep the Workflows hub bookmarked, and make the backup workflow your next read if this page was a close call rather than a catastrophe.

Every photo workflow on this site starts at the same place: getting files off a card and onto the computer, intact, so the metadata pass can begin. The card reader is the unglamorous tool that decides how that ingest feels — and when a card misbehaves, the reader is also the first suspect to eliminate. This guide frames the reader brands photographers shortlist, as examples to check through Amazon links with this site’s tag, and explains how to match a reader to your cards. It sits in the Workflows & Buying Guides hub with external SSDs, the backup workflow and the recovery comparison. The metadata tools wait on the download page.

Some links on this page are affiliate links — see our affiliate disclosure. As with our SSD guide, no prices are printed: listings carry the current figures, and reader line-ups change by card generation.

The examples readers check first

• ProGrade Digital card readers — a reader line built specifically for professional photo and video cards, including SD and CFexpress models: check ProGrade readers on Amazon.
• Lexar Professional card readers — Lexar’s reader range for its professional card lines, again spanning SD and CFexpress: check Lexar readers on Amazon.

Two brands are enough for a shortlist because the deciding factor is rarely the logo: it is whether the reader matches your card types and your computer’s ports. Buy the match, from a maker whose business is cards and readers, and the ingest step disappears into the background — which is where it belongs.

Match the reader to your cards first

Card families are not interchangeable, and neither are their slots. SD cards (including the UHS generations) and CFexpress cards (Type A and Type B are physically different) each need a reader built for them; a multi-format reader only helps if its slots are the formats you actually shoot. Start from your camera bag, not from the product page: list the exact card types you own today and the ones your next camera body is likely to use, then choose a reader (or a pair) that covers that list. The second match is the computer side: the reader’s cable and connector must suit your machine’s ports, and an adapter chain between a fast reader and a slow port quietly turns ingest back into a wait. Photographers running both SD and CFexpress commonly end up with either one dual-slot reader that genuinely covers both formats, or two dedicated readers — both patterns are fine; the wrong-format purchase is the only real mistake.

Reader, card or cable? Troubleshooting the ingest

When transfers fail or a card does not appear, isolate before you conclude the worst. Try the same card in a different reader (or a different slot), and a known-good card in the suspect reader; swap the cable before blaming either. This matters beyond convenience: a card that is actually failing needs the recovery discipline — stop writing to it, image it, work on the image — while a card that only fails in one reader needs a new reader. Our recovery comparison covers the failing-card branch. Once files are safely across, the routine of this site takes over: verify the ingest by opening the folder in ExifToolGui, confirm dates and counts look sane, run the metadata pass, and refresh backups per the backup workflow. Readers that support both of your card families make that routine a single plug-in rather than a juggling act.

Ingest verification deserves thirty seconds of ritual, because the reader is where silent trouble enters a library. After a transfer, compare the file count on the card with the count that arrived; open the first and last frames; and only format the card in the camera, never in the reader, once the copies are verified and the backup refresh has run. If counts disagree, the card stays unformatted and the diagnosis above begins. That tiny ceremony, repeated every ingest, is what makes ‘the reader ate my shoot’ a story other people tell.

Buying notes that stay true

• Inventory your card types (SD generation, CFexpress Type A or B) before opening a single listing.
• Match the connector to your computer’s ports; budget for the right cable as part of the reader.
• Prefer makers whose core business is cards and readers — the two shortlist examples above are that kind of maker.
• Keep the old reader when you upgrade: a second reader is the cheapest card-vs-reader diagnostic there is.
• Check the live listing for your region and card format; no price is quoted on this page on purpose.

Frequently Asked Questions

Do I need separate readers for SD and CFexpress?

You need slots for both formats if you shoot both. Some readers cover both in one unit; others are dedicated. What matters is that every card type you own has a matching slot — SD and CFexpress, and CFexpress Type A versus Type B, are physically distinct.

My card does not show up. Is it the card or the reader?

Isolate it: the same card in another reader, and a known-good card in yours. If the card fails everywhere, treat it as a failing card — stop writing to it and follow the recovery comparison linked above. If it only fails in one reader, replace the reader.

Why are no speeds or prices listed here?

Achieved ingest speed depends on the card, the reader and the computer’s port together, and prices move. This page gives the durable decision — format match, port match, reputable maker — and links live listings for the current numbers.

Read the companion hardware guide, Best External SSDs for Photo Work, and browse the rest of the Workflows hub for the full desk setup.

An external SSD earns its place in a photo workflow three ways: as the fast working drive a batch metadata job runs against, as one leg of a backup pattern, and as the drive that travels when the library does. This guide frames the external SSDs most often chosen for photo work as examples to check — with Amazon links carrying this site’s tag — and then spends most of its length on the part that outlives any model cycle: how to choose. It belongs to the Workflows & Buying Guides hub, next to the backup workflow and card readers for photographers. The metadata side of the desk is on the download page.

Some links on this page are affiliate links — see our affiliate disclosure. Prices are deliberately not printed here: they move, and the linked listings are the place to check the current figure for your region and capacity.

The examples readers check first

• Samsung T7 portable SSD — the previous-generation example in Samsung’s portable line, widely used as a photo working and travel drive: check Samsung T7 listings on Amazon.
• Samsung T9 portable SSD — the newer-generation example in the same line, the one our backup workflow links as its rotating off-site copy: check Samsung T9 listings on Amazon.
• SanDisk Extreme Pro portable SSD — the rugged-line example from SanDisk’s portable range, the other name photographers routinely shortlist: check SanDisk Extreme Pro listings on Amazon.

Treat those three as a starting shortlist, not a ranking carved in stone: generations refresh, capacities and regional line-ups differ, and the right answer depends on the ports your computer actually has and the size of the library the drive must hold. What does not change is the checklist below.

Choose by the job, then by the drive

Capacity from your library, not from the shelf. Measure the library the drive must hold — masters, exports and working room — and buy above that figure with headroom for a year or two of shooting; a drive bought exactly at today’s library size is next year’s migration project. Connection from your computer. A portable SSD can only run as fast as the port it plugs into, so match the drive’s interface to the ports your machines actually offer rather than to the best port on a spec sheet. Role from your pattern. A working drive lives on the desk and wants speed and capacity; a backup drive wants to be the second copy, stored apart; a travel drive wants to be small, bus-powered and replaceable. One drive playing all three roles is one drive whose loss hurts three ways — see the backup workflow for how the roles separate.

Using an external SSD in a metadata workflow

ExifToolGui batch work — shifting dates across a season of photos, writing credits to a whole archive, verifying tags file by file — reads and writes many small pieces of many files, and it feels noticeably better on an SSD than on a spinning drive, especially across thousands of files. The disciplined pattern: keep masters on the fast drive while a batch is in progress, verify the results by re-reading in ExifToolGui, and only then refresh the backup copies from the finished state. Editing against the backup copy itself inverts the safety order; the SSD guide and the backup workflow are written to be read as a pair for exactly that reason. If a drive or card ever starts misbehaving — files vanishing or failing to open — stop writing to it and read Recover Deleted or Corrupt Photos before anything else touches it.

Housekeeping is the unglamorous half of SSD ownership for photo work. Give the drive a file system your machines share if it must move between computers, or dedicate it to one machine if it will not; eject it properly rather than pulling the cable, especially mid-batch; and keep a plain text note in its root folder recording what lives on it and when it was last verified against the library. None of that is product-specific — it is how a fast drive stays a trustworthy drive across years of shoots.

Buying notes that stay true

• Buy capacity for the library you will have, not the one you have.
• Match the connector to your computers; carry the right cable and treat it as part of the drive.
• One drive is a copy, not a backup — pair any purchase with the 3-2-1 pattern.
• Check the current listing for your region: models, capacities and bundles vary, and no price is quoted on this page on purpose.
• Label the drive with its role and the date it entered service; future-you, mid-restore, will be grateful.

Frequently Asked Questions

Which of the three examples should I buy?

The one whose capacity clears your library with headroom and whose connection matches your computer’s ports. The three listed — Samsung T7, Samsung T9 and SanDisk Extreme Pro portable SSDs — are the standard shortlist examples; the listings linked above carry the current variants.

Why are there no prices or speed figures on this page?

Prices change constantly and vary by region and capacity, and headline speeds depend on the host port. Publishing stale figures would mislead; the linked listings show the live numbers for the exact variant you are considering.

Can I run my whole library from an external SSD?

Many photographers do, with the drive as the working copy — provided it is not also the only copy. Working from an external SSD plus a separate backup (cloud and/or NAS) is the pattern this site’s backup workflow describes.

Complete the desk with the card reader guide, and keep the whole set of workflows in view in the Workflows hub.

You have just spent real effort on your photo library in ExifToolGui — dates repaired, credits and keywords written, locations decided. That cleaned library is now worth more than the raw card dumps it came from, and it usually exists in exactly one place. This workflow fixes that: a simple, durable backup pattern for a metadata-cleaned library, built from a cloud copy plus local hardware, using the tools linked from this site. It sits in the Workflows & Buying Guides hub alongside the metadata-first workflow, external SSDs for photo work and recovery options for when prevention came too late. ExifToolGui itself is on the download page.

The pattern: copies in different places, on purpose

The durable idea in backup is not a product; it is separation. Keep at least three copies of the library, on at least two different kinds of storage, with at least one copy somewhere else — the classic 3-2-1 pattern. A single external drive beside the computer fails the ‘somewhere else’ test (theft, fire and flood take both), and a cloud folder alone fails the ‘different kinds’ test if the account or the sync misbehaves. The workflow below builds the pattern from two purchases most photographers make anyway — a cloud plan and local drives — plus one habit: backing up after the metadata pass, so the copies being protected are the cleaned masters, not pre-fix drafts.

The cloud copy: pCloud

One off-site copy should be automatic and boring. The cloud option linked from this site is pCloud, used here in the plain role of remote storage for a full library copy: point it at the cleaned masters folder, let the initial upload finish, and treat its job as done when the remote copy matches the local one. Some links on this page are affiliate links — see our affiliate disclosure. Whichever cloud service a reader uses, the workflow requirements are the same: the whole library, not a selection; uploads verified, not assumed; and the account protected like the asset it now holds, because the cloud copy is the one that survives a bad day at home.

The local copies: a NAS and a portable SSD

Local copies are for speed — restoring a folder from the shelf beats re-downloading a library. Two local forms cover most desks. A network-attached storage box holds the always-on local copy that every machine in the house can reach; readers shopping for one can start from Synology NAS enclosures on Amazon. A portable SSD holds the travelling or rotating copy — the one that can live off-site at a relative’s house or in a desk at work, which quietly satisfies the separation rule; the current example linked from our SSD guide is the Samsung T9 portable SSD on Amazon. The model-by-model discussion is in Best External SSDs for Photo Work; here, the role matters more than the model: one local copy reachable, one local copy removable.

The routine that keeps it true

• Back up after the metadata pass, not before: the copies must contain the fixed dates and credits.
• Verify by sampling: open a few backed-up files in ExifToolGui and confirm the metadata you wrote is present in the copies.
• Rotate the portable copy off-site on a rhythm you will actually keep — monthly beats a perfect plan abandoned by March.
• Test a restore once: copy one folder back from each backup and open it. An untested backup is a hope, not a backup.
• Never edit the only copy: metadata work happens on the master; backups are refreshed from it, never edited in place.

Two refinements separate a durable pattern from a pile of copies. First, keep the untouched camera originals distinguishable from the cleaned masters — a clearly named archive folder for as-shot files, a working library for the corrected ones — so a future fix can always start from the true original. Second, let at least one copy be versioned in effect: when you refresh a backup after a big metadata session, you are replacing yesterday’s truth with today’s, so the off-site rotation doubles as your undo window for anything you regret in the latest pass. Separation plus one step of history is what makes the pattern forgiving.

Notice what this workflow does not promise: it does not resurrect files already lost. If the situation is a deleted or corrupted library rather than a healthy one to protect, start with Recover Deleted or Corrupt Photos — and then come back here, because a successful recovery is the best possible argument for never needing one again.

Frequently Asked Questions

Is one external drive a backup?

It is a copy, which is a start, but it fails the separation test: it lives where the original lives and stores the same single kind of copy. The pattern on this page adds a second local form and one off-site (cloud) copy.

Should I back up before or after fixing metadata?

After — the point of the exercise is protecting the cleaned library. Backing up the pre-fix state as well does no harm, but the copies you verify and rotate should be the corrected masters.

How do I know the backup kept my metadata?

Sample it: open backed-up files in ExifToolGui and read the fields you wrote (dates, Artist, Copyright, keywords). Backup tools copy files; verifying the contents of a few copies proves the whole pipeline.

Protect the work, then keep making it: more guides are in the Workflows hub, and the reader hardware angles continue in Best Card Readers for Photographers.

Most photo workflows start in the editor and treat metadata as an afterthought — which is how wrong dates, missing credits and stray GPS coordinates survive into finished, exported, shared files. This workflow reverses the order: a short, deliberate metadata pass in ExifToolGui first, then editing and organising in Lightroom with clean files. ExifToolGui (Bogdan Hrastnik’s GUI, continued as V6 by Frank Bijnen) handles the forensic work through Phil Harvey’s ExifTool; Lightroom does what it is for — developing and managing the corrected library. The workflow lives in the Workflows & Buying Guides hub with the backup workflow and AI editing after metadata. Tools start at the download page.

Why metadata first, in one argument

Editors trust embedded metadata. Import order, timeline views, smart collections and export naming all read capture time; search and filtering read keywords and captions; clients and stock pipelines read credit and rights fields. If those fields are wrong at import, every downstream convenience quietly automates the error — the trip sorts wrong, the wrong name is credited, the location you meant to keep private is embedded in the export. Fixing the fields at the file level, before import, means every tool that touches the file afterwards inherits the truth. ExifToolGui is the right instrument for that pass because it shows everything ExifTool recognises and writes at that depth — not just the fields an import dialog happens to surface.

Step 1: the fix pass in ExifToolGui

• Verify capture times. Sort by DateTimeOriginal; fix a wrong camera clock with Modify → DateTime shift, set exact dates where a single value is wrong, then run DateTime equalize so EXIF and XMP agree.
• Write credit once. In the Workspace, set Artist and Copyright on the whole selection — the values every later export should carry.
• Keyword the keepers. Apply the shared event/place keywords to the batch, then add per-photo terms to the standouts.
• Decide location deliberately. Keep GPS in your masters if it serves your archive; plan to strip it from sharing copies later, not from the masters by accident.
• Re-read to verify. Click away and back; the stored values, not the typed ones, are what Lightroom will inherit.

Work on copies until the pass is routine, as with every batch write on this site. The detailed mechanics live in the Tutorials cluster — date shifting, batch editing and Workspace building are each covered step by step — but the pass itself takes minutes once the Workspace panel for it exists.

Step 2: import and finish in Lightroom

Import the corrected files and let the library work on true data: the timeline is right on day one, and the credits and keywords you wrote at file level are the starting point rather than a repair job. From here the workflow is the familiar one — organise, develop, export — with one discipline added: when an export needs different metadata behaviour (location removed for a public copy, for example), make that copy deliberately and keep the master untouched. If you later edit in Lightroom or Photoshop and do not yet have them, the route for readers is Adobe Photography (Lightroom and Photoshop). Some links on this page are affiliate links — see our affiliate disclosure. How Bridge-style library management compares with the specialist pass is covered in ExifToolGui vs Adobe Bridge.

Step 3 (optional): rescue the problem frames

Every shoot has a few frames that matter and are technically poor — noisy, soft, low-resolution. Those belong to a different tool class than metadata editors: AI photo editors and denoisers. Where readers ask for an option, the one linked from this site is Topaz Photo, used for denoise and upscale work on selected frames rather than whole folders. Keep the order: rescue after the metadata pass, and re-check the rescued file’s metadata afterwards (exports from any editor can rewrite fields), because the file that returns to the library should still carry the dates and credits you fixed in step 1. The fuller tour of this step is After the Metadata: AI Denoise and Upscale Options.

The habit that holds it together

Metadata-first is a habit, not a project: fix, then finish, every time, in that order. Pair it with the companion discipline in Back Up the Photo Library You Just Cleaned — a cleaned library is worth protecting properly — and a folder of camera files becomes an archive whose contents you can assert, not merely assume.

Frequently Asked Questions

Why not just fix metadata inside Lightroom after import?

Because import builds order, collections and exports on the embedded values from the first minute, and library-level fixes do not always rewrite the file-level fields other tools will read later. A file-level pass in ExifToolGui fixes the source every tool inherits.

Does ExifToolGui edit photos like Lightroom does?

No. ExifToolGui views and edits metadata only — it develops nothing. That division is the workflow: ExifToolGui for the data about the photo, Lightroom for the photo itself.

What if an editor’s export changes my metadata?

It can — exports may rewrite or drop fields depending on settings. Re-open exported keepers in ExifToolGui and re-read the key fields; restoring a field on the export copy takes seconds once checking is a habit.

More workflows are collected in the Workflows hub; the metadata tools themselves are on the download page.

This is the comparison with a twist: the two sides are the same tool. ExifTool, by Phil Harvey, is a platform-independent Perl library plus a command-line application for reading, writing and editing metadata — and it has no graphical interface of its own. ExifToolGui — Bogdan Hrastnik’s GUI, continued as V6 by Frank Bijnen — is a Windows front-end that drives that same ExifTool on your behalf. So the question is never which is more powerful in principle; it is which interface makes you faster and less error-prone. This page, in the Comparisons hub with ExifToolGui vs jExifToolGUI and ExifToolGui vs GeoSetter, compares them honestly, including why many people end up keeping both. Everything is available from the download page.

Licences, so they are on the record: ExifTool is free software under the same terms as Perl itself, in its author’s wording, and the V6 GUI fork is GPL-3.0. Nothing in this comparison is a sales pitch; it is an ergonomics decision.

The two interfaces at a glance

ExifTool’s own documented scope frames both columns: it reads, writes and edits EXIF, GPS, IPTC, XMP, JFIF, GeoTIFF, ICC Profile, Photoshop IRB, FlashPix, AFCP, ID3 and maker notes; it deletes metadata individually, in groups or altogether; it geotags from GPS track logs with time-drift correction; and it renames and organises files by date or any other metadata. The GUI does not add engine capability — it surfaces the documented workflows its author chose to build panels and menus for, no more and no less.

What the command line does better

Automation and reach. A command can be saved, re-run next month on a new folder, embedded in a script, and aimed at an entire directory tree with conditions (‘only files where the camera model is X and GPS is missing’). It runs identically on Windows, macOS and Linux, which is why archives and newsrooms standardise on it. It also exposes everything: any tag, any group, any combination, including the long tail no GUI panel will ever include. The costs are real too — a mistyped argument writes exactly what you said, not what you meant, to every file the command touches, and discovering a tag’s current values means asking in text rather than glancing at a panel. The command line rewards precision and punishes its absence at full batch scale.

What the GUI does better

Visibility and guardrails. In ExifToolGui you select files in a list, see the current values in the Metadata panel, edit in the Workspace, and re-read to verify — the loop that catches the wrong folder, the wrong file and the stale display before anything is written. Recurring jobs become Workspace definitions instead of remembered syntax. The Modify menu covers the operations home users actually repeat: DateTime shift and equalize for clock errors, geotagging from a log file, renaming from DateTime, metadata removal. And the map view makes manual geotagging a visual act rather than a pair of typed coordinates. The honest limits: Windows-only, and bounded by the workflows the GUI implements — an exotic tag surgery that ExifTool can do may have no panel here (the GUI’s ExifTool direct tradition exists partly for that gap).

Coming from pyExifToolGui?

If you arrived here from pyExifToolGUI, Harry van der Wolf’s earlier Python/PySide GUI, one fact matters: pyExifToolGUI is no longer supported, and its own site directs users to switch to jExifToolGUI, the same author’s Java successor. We position the choice honestly: jExifToolGUI is the author’s designated successor and the cross-platform route (Windows, Linux, macOS), though its development has itself stopped at release 2.0.2 — see that comparison for the full picture. On Windows, ExifToolGui V6 is the maintained front-end in this family. And if neither GUI fits, the command line underneath all of them remains fully supported by Phil Harvey — the GUIs come and go, the engine is the constant.

Verdict: keep both, in the right order

Learn the GUI first if you are new: it teaches you what tags exist and what correct looks like, with verification built in. Graduate to the command line for the jobs that repeat identically, span platforms, or reach tags no panel shows. Many experienced users do metadata repair interactively in the GUI and bulk, scripted passes on the command line, against the same paired ExifTool — production release 13.55, or the latest release overall, 13.59, a distinction our version guide explains.

Frequently Asked Questions

Does the GUI make ExifTool more powerful?

No — it makes ExifTool more approachable. The engine’s capabilities are identical; the GUI surfaces the documented workflows (viewing, Workspace editing, Modify operations, map geotagging) as panels and menus instead of commands.

Can I use both the GUI and the command line with one ExifTool?

Yes. The GUI pairs with a correctly named exiftool.exe (renamed from exiftool(-k).exe, with its exiftool_files folder); that same executable is the command-line tool. One pairing serves both interfaces.

I used pyExifToolGui. What replaces it?

Its own site says pyExifToolGUI is no longer supported and directs users to jExifToolGUI. On Windows, the maintained alternative is ExifToolGui V6; on any platform, the ExifTool command line itself is always an option.

Whichever interface you pick, the files start at the download page, and the other pairings live in the Comparisons hub.

Exif Pilot and ExifToolGui are both Windows metadata editors, and on a feature checklist they look like close cousins: both view and edit EXIF, GPS, IPTC and XMP data. The differences that matter live one layer down — in how batch work is priced, in a file-location constraint, and in the engine underneath. Exif Pilot (by Two Pilots / ColorPilot) offers a free core editor, with batch processing sold as a paid plug-in. ExifToolGui — Bogdan Hrastnik’s GUI, continued as V6 by Frank Bijnen — is GPL-3.0 free software whose batch capability is built in, because it is a front-end for Phil Harvey’s ExifTool. This comparison, in the Comparisons hub with ExifToolGui vs XnView MP and ExifToolGui vs the command line, sticks to sourced facts for both sides. Get ExifToolGui from the download page.

The one-line summary: for single-file editing, both are plausible; for folder-scale work, the pricing model and the batch design decide it, and they point the same way.

The two programs at a glance

Note what the free core of Exif Pilot genuinely includes, because it is respectable: creating and deleting tags (not just editing existing ones), GPS fields, keywords, and structured import/export through XML, CSV and Excel files. A reader whose work is one file at a time, with spreadsheet-driven values, is served by that core. The comparison turns on what happens when the unit of work becomes a folder.

Batch work: built-in design vs paid plug-in

Batch capability is not an add-on in ExifToolGui’s lineage; the original GUI’s stated goals, from its earliest documentation, include selecting multiple files and modifying them at once, and the V6 program carries that through its Workspace saves (values written to all selected files) and Modify operations (DateTime shift, equalize, geotagging, removal). In Exif Pilot, multiple-photo processing — along with tag-to-tag copying and command-line use — is the paid Batch Editing Plug-in, priced at €79.95 on the vendor’s page as sourced for this comparison. Neither model is dishonest; they are simply different answers to who pays for scale. A hobbyist editing a card’s worth of photos after every trip does folder-scale work constantly, and for that reader the plug-in is not an edge feature — it is the product. In ExifToolGui that same work is included, under GPL-3.0, with ExifTool (free software under the same terms as Perl itself) as the engine, separately downloaded and paired.

Constraints and working style

Exif Pilot’s documented constraint — processed files must be in the same directory — is a small sentence with real workflow weight: archives organised in nested folders need gathering or repeated passes, where a selection-based front-end works on the folder you open as it lies. Working style differs too. Exif Pilot centres on its tag list and its import/export formats; ExifToolGui centres on the Workspace, where you define the tag panel for the job (a dates panel, a credits panel, a location panel) and save the definition for reuse, plus a Modify menu for operations rather than value typing. Neither is objectively better as an interface; they reward different habits. What is objective is the depth ceiling: ExifToolGui’s ceiling is ExifTool itself — the full tag universe of EXIF, GPS, IPTC, XMP, JFIF, ICC, maker notes and more that the engine documents — while a self-contained editor’s ceiling is its own implementation.

Verdict

Choose Exif Pilot if you edit metadata file by file, value its XML/CSV/Excel import-export in the free core, and will never need batch work — or are willing to pay €79.95 for the plug-in when you do. Choose ExifToolGui if folders are your unit of work: batch editing is built in and free, the Workspace is yours to shape, and the engine underneath is ExifTool, the reference tool in this field. For Windows users, that combination is why this site is built around it.

Frequently Asked Questions

Is Exif Pilot completely free?

Its core is free: view, edit, create and delete EXIF, GPS, IPTC and XMP data, keywords, and XML/CSV/Excel import-export. Batch processing is not in the free core — it is a paid plug-in at €79.95, which also adds tag-to-tag copy and command-line use.

What does ‘files must be in the same directory’ mean in practice?

Exif Pilot processes files that live in one directory. A library spread across nested folders needs the files gathered or processed folder by folder. ExifToolGui works on the selection in the folder you open, with batch saves to all selected files.

Which handles more metadata formats and tags?

ExifToolGui’s ceiling is ExifTool’s: Phil Harvey’s engine documents support for EXIF, GPS, IPTC, XMP, JFIF, GeoTIFF, ICC Profile, Photoshop IRB and maker notes from around 30 camera makers. Exif Pilot’s documented scope is EXIF, EXIF GPS, IPTC and XMP.

See the remaining pairings in the Comparisons hub, including ExifToolGui vs GeoSetter, and download ExifToolGui and ExifTool from the download page.

Adobe Bridge and ExifToolGui both put metadata panels in front of a photographer, and that surface similarity hides a real difference in purpose. Bridge is Adobe’s asset manager for commercial creative workflows — the place a Lightroom and Photoshop user browses, organises and inspects a library, with metadata panels for keywords, IPTC fields and related information. ExifToolGui — Bogdan Hrastnik’s GUI, continued as V6 by Frank Bijnen — is a single-purpose Windows front-end for Phil Harvey’s ExifTool, built to view and edit metadata at the engine’s full depth. This page compares them for metadata work specifically, using only what can be stated honestly about both. It lives in the Comparisons hub with ExifToolGui vs XnView MP and ExifToolGui vs jExifToolGUI; ExifToolGui itself is on the download page.

A disclosure note on method: this site has not verified Adobe’s current pricing or licensing terms for Bridge in its fact base, so this page makes no price claims and no ‘free’ claims about Bridge at all. What it can compare — purpose, metadata depth, and how the two fit around a Lightroom or Photoshop workflow — is compared in full.

The two programs at a glance

The pattern in the table is depth versus context. Bridge gives metadata a home inside a managed library: you see and edit fields while browsing the same collection you will open in Adobe’s editors. ExifToolGui gives metadata the whole program: the tag set is the interface, the Workspace shows exactly the tags you choose, and operations like shifting every timestamp by an offset or removing whole metadata groups are first-class menu entries rather than side effects of an export.

Metadata depth: panels in a library vs the full tag set

For everyday descriptive work — keywords, captions, credit lines — a library tool’s metadata panels are convenient because the library is already open. The limits appear at the edges: auditing every tag a file carries (maker notes, serial and lens data, embedded XMP history), repairing EXIF capture times that an editor’s import assumed were right, aligning EXIF and XMP date-times after a fix, or removing metadata groups wholesale before a file leaves the studio. Those are ExifTool operations, and a dedicated front-end exists to expose them. ExifToolGui’s documentation tradition — view all metadata ExifTool recognises, edit the frequently used tags, modify many files at once — is exactly that edge-case list turned into a program.

How the two fit together in practice

They are sequential more often than they are rivals. A clean pattern for an Adobe-centric studio: do the forensic pass in ExifToolGui first (dates true, credits and keywords written, location data deliberately kept or stripped), then let the library tool manage the corrected files day to day. If you later edit in Lightroom or Photoshop, the Photography plan is the usual Adobe route, and our link for readers who want it is Adobe Photography (Lightroom and Photoshop). Some links on this page are affiliate links — see our affiliate disclosure. That sequencing is also the subject of our metadata-first Lightroom workflow, which walks the hand-off step by step.

There is also an audit argument for the specialist pass, and it is the one studios feel first. When a file leaves the building — to a client, a publication, a marketplace — someone may ask what it contains: whose credit, which date, whether location is embedded. A library panel answers from the fields the library tracks; ExifToolGui answers from the file itself, tag by tag, including the groups nobody thought to ask about until they mattered. Running that check before delivery is cheap insurance, and it is a check the browsing tool was never designed to perform.

Verdict

For metadata work as the main event — inspection depth, date repair, batch operations, removal — ExifToolGui is the specialist and costs nothing, under GPL-3.0, on Windows. For metadata as one panel inside a managed Adobe library, Bridge is the natural home, on Adobe’s commercial terms. Most Adobe-workflow photographers who care about provably correct files end up wanting the specialist pass first, whichever library they live in afterwards.

Frequently Asked Questions

Can ExifToolGui and Bridge be used on the same library?

Yes, sequentially: fix and audit metadata in ExifToolGui, then browse and organise the corrected files in your library tool. The files are standard photos with standard metadata; no conversion is involved.

Which shows more metadata?

ExifToolGui, by design: it surfaces everything ExifTool recognises, arranged in Workspace panels you define. Library tools show the fields their workflow needs, which is a subset aimed at keywords and descriptive data.

Why does this page state no price for Bridge?

Because this site’s fact base did not verify Adobe’s current Bridge pricing or terms, and unverified prices are not published here. Check Adobe’s own site for current terms; ExifToolGui’s basis is verified: GPL-3.0 free software.

Continue in the Comparisons hub with ExifToolGui vs Exif Pilot, or go straight to the files on the download page.

This comparison pairs two programs that photographers often install side by side without realising they are different species. XnView MP, from XnSoft (Pierre-Emmanuel Gougelet), is a cross-platform image viewer, organizer and converter that also shows and partly edits metadata. ExifToolGui — Bogdan Hrastnik’s GUI, continued as V6 by Frank Bijnen — is a dedicated Windows front-end for Phil Harvey’s ExifTool that does nothing but metadata, and does it at full ExifTool depth. Choosing between them is really choosing what the program is for. This page is part of the Comparisons hub, with ExifToolGui vs jExifToolGUI and ExifToolGui vs Adobe Bridge; files are on the download page.

The honest summary: if you want one program to browse, organize and convert a library and glance at its metadata, XnView MP is built for that. If the metadata itself is the job — auditing every tag, repairing dates, writing descriptive fields, removing location data — ExifToolGui is built for that. Many libraries end up using both, in sequence.

The two programs at a glance

Two rows decide most real cases. The writing row: XnView MP’s documented editing reaches IPTC fully and XMP partly, which covers captions and keywords for many users but is not a general metadata editor — EXIF repair work such as DateTimeOriginal correction is ExifTool territory. And the licence row: XnView MP is freeware with a use condition, not free software — private, educational and non-profit use is free, while commercial use requires a licence. ExifToolGui’s V6 fork is GPL-3.0 free software with no such use split.

Browsing and organising vs auditing and repairing

XnView MP’s centre of gravity is the library itself: thumbnails, organisation, batch renaming and conversion across more than 500 formats it can read. Metadata there is something you check while doing something else — confirm a date, read a caption, fix a keyword on export. ExifToolGui’s centre of gravity is the file’s tag set: a file list, a Metadata panel driven by your own Workspace definitions (you choose exactly which tags are shown and editable), an ExifTool direct view, and Modify operations for date shifts, geotagging from track logs and metadata removal. When a reader asks ‘why does this photo sort wrong / share its location / carry the wrong credit’, the auditing tool is the one that answers, because it shows everything ExifTool can see rather than the common fields only.

Platform and workflow fit

XnView MP runs on Windows, macOS and Linux, so a mixed-OS household or studio can standardise on it in a way ExifToolGui (Windows-only, both in the original and in Bijnen’s fork) cannot match. On a Windows desk, the question flips to depth versus breadth in the daily workflow. A practical combined pattern, and the one this site’s guides assume: browse and cull in your viewer of choice, then open the keepers in ExifToolGui for the metadata pass — dates verified, credits and keywords written through the Workspace, GPS deliberately kept or removed — before the files go anywhere else. The tools are complements wearing similar clothes, not substitutes, and treating the viewer as your metadata editor is where partial XMP writing quietly limits you.

One more practical distinction belongs in this section: breadth of display is not depth of record. A viewer that opens 500+ formats is showing you the fields it chooses to surface for each; a metadata front-end is showing you the record the file actually carries, including groups a viewer has no reason to display, such as maker-note internals or embedded GPS detail. When a file’s history matters — a submission, a dispute, a privacy decision before sharing — the record, not the summary, is the evidence, and that is the ground ExifToolGui was built to stand on.

Verdict

Choose XnView MP as your library front door if organising, viewing and converting are the daily work and your metadata needs stop at viewing EXIF/IPTC/XMP and writing IPTC plus some XMP — and note the licence condition if the use is commercial. Choose ExifToolGui when the metadata is the deliverable: full-depth inspection, date and time repair, batch descriptive editing and removal, all through ExifTool, under GPL-3.0, on Windows. Choose both if, like many photographers, you have a library to run and files whose metadata must be provably right.

Frequently Asked Questions

Can XnView MP replace ExifToolGui for metadata editing?

Only for light needs. XnView MP shows EXIF/IPTC/XMP and can write IPTC and partly XMP. Full-depth work — viewing every tag ExifTool recognises, repairing EXIF dates, removing metadata groups — is what the dedicated ExifTool front-end exists for.

Is XnView MP free for commercial work?

No. Its licence is freeware for private, educational or non-profit use; commercial use requires a licence. ExifToolGui’s V6 fork, by contrast, is GPL-3.0 free software.

Which one runs on Mac or Linux?

XnView MP — it is cross-platform on Windows, macOS and Linux. ExifToolGui is Windows-only. The cross-platform ExifTool GUI in this family is jExifToolGUI, compared in the hub.

Browse the full Comparisons hub for the remaining pairings, including ExifToolGui vs Exif Pilot, and get ExifToolGui and ExifTool from the download page.