The EXIF Editor Handbook: How to Fix, Not Fake, Your Photo Metadata

What is an EXIF editor and when do you actually need one?

An EXIF editor is software that reads and changes the hidden information inside your photos: camera model, date taken, GPS coordinates, author name, copyright notices, and dozens of smaller fields. You need one when that information is wrong, outdated, missing, or dangerous to share, because your camera writes it automatically and never asks your opinion.

EXIF dates back to 1995. Almost every photo carries this invisible layer, and a good editor opens it without touching a pixel.

You need one when the data lies: a wrong camera clock, an old business name on a client batch, a photographer's home GPS in wedding photos, a rebrand that left the old name everywhere, blank copyright on delivered files. I built my own editor after one too many afternoons fixing this by hand. An agency shoot once landed forty photos on my desk carrying the freelancer's home GPS and personal copyright line.

EXIF, IPTC, and XMP: what is the difference and why should I care?

EXIF is the technical layer your camera writes automatically (dates, camera settings, GPS). IPTC is the editorial layer for people and rights (creator name, copyright, caption, keywords), the standard that press and stock workflows use. XMP is Adobe's flexible layer for licensing terms, custom fields, and the AI-generation flag Google now reads. All three live side by side in one file.

Google treats them differently. IPTC creator and copyright details can be displayed in Google Images, a feature Google documents in its image metadata guidelines. IPTC captions can help Google understand image content alongside alt text. Google has also started labeling AI-generated images using the XMP digital source type field. Camera EXIF like ISO and phone model? No documented ranking use. So edit with intent: IPTC for ownership, XMP for licensing and AI disclosure, EXIF for accuracy.

Does editing EXIF data really help my images rank on Google?

No, not in any way Google has confirmed. Google representatives have said for over a decade that EXIF is not a ranking factor, and the most cited controlled study found geotagging helped some searches while hurting others, with no net benefit. What Google does use is narrow: IPTC copyright display, captions as a content signal, and the XMP AI flag. Alt text, filenames, page context, and structured data remain the real levers.

I say this carefully because it cuts against a lot of marketing copy in this industry. In 2014, Google's Matt Cutts said Google was not using EXIF data. Google's Martin Splitt has since reportedly reiterated the same position. John Mueller has said there is no need to geotag images for SEO. Google's image best practices list filenames, alt text, page context, structured data, quality, and performance. EXIF GPS is not mentioned once.

Then the field tests. A Sterling Sky study found Google strips EXIF from Google Business Profile photos on public display. A 10-week test published on Search Engine Land by Evergrow Marketing, across 27 lawn care locations, found geotagged images lifted "near me" rankings in the targeted towns but lowered rankings for town-named searches and made no difference at the business's own location; the agency decided not to geotag client images. Search Engine Journal's Ask an SEO column concluded there is nothing beyond anecdotal evidence that geolocation data helps. I ran my own small version early in my career. Four weeks of tracking, nothing moved, and I stopped selling geotagging as an SEO service that month.

What can go wrong if I write fake GPS coordinates into my photos?

Fake coordinates can backfire. Google strips EXIF from images uploaded through Google Business Profile, so the coordinates may never reach any ranking system. Worse, the best-known controlled test found that geotagging photos for towns away from the business location was followed by ranking decreases for several query types. Invented location data is also a trust problem if any platform ever cross-checks it.

Somewhere along the way, "geotag your photos" mutated from "keep location data accurate" into "invent location data for SEO." That is fabrication, and it is bad strategy on top of being dishonest. Google strips EXIF from Business Profile uploads on public display, and Google's own people say they do not use the coordinates. The Search Engine Land test found ranking drops on town-named searches when images were tagged for other towns, and further drops when they targeted the wider service area. A fake geotag is a file claiming to have been taken somewhere it was not. My rule for every client: write coordinates that are true, or write none at all.

How do I fix a photo whose date and time are wrong?

Open the photo in an EXIF editor, find the DateTimeOriginal field, and correct it. If a whole batch is off by the same amount (daylight saving, a wrong timezone, a camera clock set months ago), shift every photo by that offset at once. Check which of the three dates you are changing, because they mean different things.

Cameras do not know about daylight saving or your flight to another timezone. Wrong timestamps are the most common metadata problem I see. The trap is that a photo carries several dates. DateTimeOriginal is when the shutter fired, and it is the one you almost always want. CreateDate is when the file was written. The file's modified date resets every time you copy or edit it.

My favorite cautionary tale: a photographer friend delivered 300 wedding photos stamped one hour off because the camera never adjusted in spring. One ExifTool command shifted every timestamp by an hour. Five minutes of work after two hours of confusion.

How do I add my name and copyright to my photos so it travels with the file?

Write your name into the IPTC Creator field and your rights statement into the IPTC Copyright Notice field, then verify with a metadata viewer. These fields are the industry standard for ownership. Stock platforms and newsrooms read them, they survive many kinds of sharing and re-uploading, and setting them before delivery beats trying to reclaim ownership later.

A directory site once lifted one of my photos, cropped out the watermark, and used it on their page. The IPTC copyright survived the crop because their crop did not touch the metadata. When I filed the DMCA takedown, that embedded notice was part of my evidence. The image came down in 48 hours.

The fields you want: Creator (your name), Copyright Notice ("© 2026 Your Name. All rights reserved."), and optionally Rights Usage Terms if you license the image. Do this before delivering files to anyone. One caveat: copyright metadata is evidence of ownership, not a lock.

Can editing metadata damage my image quality?

Not when done properly. Metadata lives in a separate block from the pixels, so changing a date or copyright line does not have to re-compress your image. The risk is not the metadata edit itself. It is tools that rewrite the entire JPEG at a lower quality setting while they are in there.

Two warnings from my own experience. First, some editors do not just change the metadata block. They decode and re-encode the whole image on save at whatever default quality the developer chose. I once watched a batch tool turn crisp portfolio JPEGs into slightly soft versions because it re-saved everything at 80 percent quality. Test every new editor on copies first.

Second, MakerNotes. These are the camera maker's private fields, and they are fragile. Some editors corrupt them on round-trips. If you do not need MakerNotes, leave them alone, work on copies until you trust the tool, then verify with a viewer.

Should I edit metadata online or install desktop software?

Use an online EXIF editor for quick, one-off fixes on a few images with nothing to install. Use desktop software for batches, RAW support, or automation. The trade-off is convenience against power, and privacy against features, depending on where the processing happens. Pick the online route when speed matters and the desktop route when volume matters.

Online editors win on speed. Open a page, drop in a photo, fix the fields, download. No install, no learning curve, works on any machine. The limits are real: file-count caps, rarely any RAW support, nothing scriptable.

Desktop software wins on power. ExifTool can rename, redate, and retag ten thousand photos with one command. Lightroom applies a metadata preset to an entire shoot on import. The costs are the learning curve, the install, and for some tools real money. And the privacy question people skip: most online editors, including mine, upload your photo to a server to write the changes. Mine processes the file on our server and deletes it immediately after, never storing it, but if a photo is too sensitive to leave your device at all, a desktop tool or a browser-local editor is the right choice.

Which EXIF editors are actually worth using?

It depends on your volume and patience. ExifTool is the free gold standard for power users comfortable with a terminal. ExifPilot and Lightroom suit photographers working in batches. HoudahGeo and GeoSetter serve GPS-specific jobs. Online editors, including the one I built, suit quick fixes with no install. There is no single best tool, only the best tool for the job.

Honest notes from real use:

• ExifTool by Phil Harvey: free, open source, available on all major platforms, reads and writes nearly everything, and the engine behind half the tools on this list. The catch is the command line.
• ExifToolGUI: a free Windows wrapper, dated but it works.
• ExifPilot: a GUI batch editor around 40 dollars, with an interface that feels like 2010.
• Adobe Lightroom Classic: metadata presets on every import are excellent, but it is a subscription and heavyweight for metadata-only work.
• Adobe Bridge: free with Creative Cloud, decent IPTC editing.
• HoudahGeo: Mac-only, around 39 dollars, the nicest GPS tool on a Mac.
• GeoSetter: a free Windows geotagger with a map, aging.
• Photo Exif Editor (Android): handy for quick phone fixes, limited fields.
• Other online editors: pi7.org processes in your browser with no upload. metadata-editor.com is capable but server-side, so I keep sensitive photos away.
• My own: I built the LocalSEOFlow EXIF Metadata Editor for the small job I kept needing: up to 50 images (10 MB each), descriptions, keywords, copyright, author, and GPS with a map picker. Files are processed on our server and deleted immediately after, never stored. It will not replace ExifTool for ten thousand files, and I am not going to pretend it does.

How do I remove location data before sharing a photo publicly?

Open the photo in an editor and delete the GPS latitude, longitude, and related location fields, or replace exact coordinates with city-level ones. Do this before uploading anywhere the public can download the original. Your phone embeds GPS in every photo by default, so check your camera settings to stop it tagging future photos.

Your phone is the main culprit. Most smartphones embed GPS in every photo by default. The photo of your new apartment or your client's property interior carries coordinates accurate to a few meters. My wake-up call was the real estate story from the opening: eleven days live, three aggregator sites, exact home coordinates in the file.

Decide whether you need location at all. For a travel post, city-level coordinates are honest and useful. For a home interior or a child's photo, strip GPS entirely, and strip it before you share. Cropping and filtering leave GPS intact unless your editor strips it. The permanent fix: turn off location tagging for everyday shooting. On iPhone it is under Privacy and Security, Location Services, Camera. On Android it is in the camera app settings.

What should I check before publishing a client's photos on their website?

Check four things: business name and copyright match the current client, GPS coordinates are accurate or removed, timestamps are sane, and no personal data from the photographer or a previous owner remains. Then re-read the file in a metadata viewer to confirm what actually got written. This ten-minute checklist has saved me from real embarrassment more than once.

This is my pre-publish checklist, built from real mistakes. One, ownership. Does the Creator or Copyright field name your client, or the photographer, the stock site, or the previous business on the domain? I once found a client's "new" photos carrying a competitor's copyright. Two, location. Are the GPS coordinates true for the shoot? Wrong location data is worse than none. Three, dates. A photo stamped 2019 on a page about a 2026 renovation is a credibility leak. Four, leftovers: old software tags, device names, serial numbers.

Then verify. Open the saved file in a viewer and read the raw fields. Editors sometimes fail silently, especially on GPS reference fields. Trust the re-read, not the save button.

Which photo formats keep their metadata, and which ones eat it?

JPEG keeps full EXIF reliably and is the safest format for metadata. WebP supports EXIF and XMP well. PNG can carry EXIF, but many tools strip it, so XMP is safer there. AVIF and HEIC support is improving but still inconsistent. Facebook and Instagram strip nearly all metadata on upload, and some image CDNs strip it unless you configure preservation.

Format choice is a quiet metadata killer. JPEG is the old reliable: full EXIF, IPTC, and XMP, every tool reads it, every platform accepts it. WebP is the modern web favorite and handles EXIF and XMP properly. PNG is the tricky one: the format can hold EXIF, but countless exporters, optimizers, and CMS pipelines strip it without telling you. If ownership data must survive in a PNG, embed it as XMP and test the full pipeline. HEIC, the iPhone default, is getting better, but tool support is still patchy, so convert to JPEG before serious metadata work.

Then the platform problem. Upload to Facebook or Instagram and your metadata is gone from the copy others see, stripped on ingest. Good for privacy, bad for anyone counting on metadata surviving social sharing. Some image CDNs and WordPress optimization plugins strip metadata too, sometimes as a file-size "feature." If metadata must survive to the live site, test the whole chain: editor, export, upload, CDN, then download the live file and read it.

How do I verify my metadata edits actually worked?

Re-open the saved file in a separate metadata viewer and read the raw fields. Check that text fields show your new values, GPS coordinates include their reference markers (N/S, E/W), and dates use the correct format. Never trust the save button alone, because editors can fail silently on specific fields.

Verification is the step everyone skips and the step that catches everything. The common silent failures, from my own error log: GPS written without reference fields is invalid, and some viewers show it while others ignore it. XMP edits never sync back to the EXIF equivalents, so one tool shows your change and another does not. Dates written in the wrong format look right in the editor and read as garbage elsewhere. And thumbnails: the small preview embedded in EXIF is a separate JPEG, and some editors leave a stale thumbnail carrying the old data.

My routine: save the edited file, open it in a different tool from the one that edited it, and read the raw tag list. Check the three fields you changed and one you did not. If all four are correct, the batch is good.

The bottom line

An EXIF editor is a fix-it tool, not a ranking tool. It corrects wrong dates, records true locations and real ownership, and removes dangerous personal data. It does not persuade Google to rank your images. The industry spent years selling the fantasy, and I would rather sell you the truth and keep your trust.

My workflow in short: shoot with correct camera settings, disable GPS for personal shots, batch-fix dates and copyright before delivery, strip location before public sharing, and verify every edit in a separate viewer. Boring, repeatable, effective.

Now I am curious about your side. Have you ever found surprising metadata in your own photos: a wrong location, a stranger's copyright, a date from another decade? And be honest: did you believe the geotagging-for-rankings claim before today?

Frequently asked questions