Photo metadata when settling a family member's estate

Nearly every page on this site assumes you are the photographer, the subject, and the account holder, deciding in the moment what happens to your own picture before it leaves your own hands. Settling a family member's estate breaks every part of that assumption at once. You did not take most of these photos. You are rarely in them. You may not even have a clear legal right to the account they are sitting in yet. And the archive itself was never curated with any of this in mind — it is decades of unsorted pictures, suddenly needing to be triaged for an obituary slideshow, a memorial page, and the rest of the family, often within days, and often by someone who is grieving while they do it.

MetadataWipe removes EXIF, GPS and other header data from a single JPEG or PNG, entirely in your browser — the right tool once you've decided which specific photo is going public.

Open MetadataWipe tool

Why this isn't just another old-photo backlog

This site already has a guide on whether to go back and clean metadata from old photos, and at a glance an inherited archive looks like an extreme version of exactly that problem — years of pictures, accumulated without much thought about metadata, now under review. The difference is ownership and knowledge. That guide is written for someone auditing their own archive: you know roughly what you've already posted, which accounts are public, and which habits you've already built. With a deceased relative's photos, you usually know none of that. You don't know what they already shared, under what account, to what audience, years before you ever opened the folder. You're triaging a record built by someone else's decisions, not reviewing your own.

Who actually has the right to this archive

Before any question about metadata, there's a prior question that's easy to skip past in the moment: do you actually have the legal standing to access this account or archive at all? In the United States, the Revised Uniform Fiduciary Access to Digital Assets Act (RUFADAA) — released by the Uniform Law Commission in 2015 and, as of 2021, enacted in most states — gives an estate's personal representative a right to a deceased user's electronic communications only where the user consented to that access, either through a provider's own planning tool, such as Facebook's Legacy Contact feature or Google's Inactive Account Manager, or in a will. Where neither exists, the account provider's own terms of service stay in control, and the provider is within its rights to refuse the request outright. Being named executor, holding a death certificate, or simply being the closest surviving relative does not, by itself, override that.

If you or the relative lived in the EU, the picture is different again and arguably murkier. Recital 27 of the GDPR states outright that the regulation does not apply to the personal data of deceased persons, leaving member states free to legislate their own rules for it — which not all of them have done, and not in the same way. So the strong, harmonized protection a living EU resident's photos enjoyed does not carry over to their estate by default; what applies depends entirely on the specific country. None of this is legal advice, and the details genuinely vary by provider, state and country — but it's worth confirming before you act, not after you've already downloaded or shared something you didn't have standing to touch.

What's actually sitting in the archive

Once you do have legitimate access, the contents are rarely uniform, and treating them as one undifferentiated pile is where most of the mistakes happen. Some of what you'll find is already public — photos the relative posted themselves, years ago, to an account that's still live. Stripping metadata from your own copy of those does nothing to the copy that's already out there; the two are unconnected files. Some of it is private and has never left a device or a personal cloud account, including photos with GPS tags pointing at a house that a surviving spouse or sibling still lives in today — a location that was the relative's home, but is someone else's current address now. And some of it carries exactly the kind of information a family actually wants to keep: a capture date that pins down when a milestone happened, or a caption that names who's in frame, which may be the only record left of either.

If you end up requesting a formal data export from a provider — through an online tool designation, a will, or a RUFADAA-style fiduciary request — expect the same thing described in our guide on what's in the data export you download from your account: a complete, portable archive built for completeness, not for sharing, often carrying more embedded context than the original photos did on their own. The same caution applies here as there, just inherited rather than requested for yourself.

A workflow for triaging an inherited archive

Confirm your legal standing before you download or copy anything. Check for an online-tool designation, a will provision, or your jurisdiction's fiduciary-access rule. Don't treat "I'm family" as sufficient on its own.
Sort by destination, not by age. Separate photos headed somewhere public — a memorial site, an obituary slideshow, a tribute post — from photos staying inside the private family record. The two groups get opposite treatment.
Leave the private family record alone. Dates and captions in photos that are only ever going to circulate among relatives are worth more intact than stripped. Don't run the whole archive through a cleaning tool out of a general sense of caution.
Clean only the photos going public, one at a time. For each photo bound for a public page, check it individually for GPS data and other identifying header fields before it goes up, especially if it shows a home a living relative still occupies.
Check who else is identifiable, not just where. A public memorial photo can expose a still-living spouse, sibling, or grandchild's location or routine just as easily as it exposes the deceased's.
Keep the untouched originals somewhere separate before you clean anything. Once a copy is stripped, the discarded date and location data is gone for good — work from a copy, never the only copy.

Where this site's tool fits, and where it doesn't

MetadataWipe decodes a single JPEG or PNG onto a canvas and re-encodes it, entirely in your browser, which removes that one file's EXIF, GPS and other header data in one pass. It is exactly the right step for the specific photo you've decided is going on a memorial page or into a public tribute post. It has no bulk mode, no field-level control to keep a date while dropping a location, and no way to process an entire inherited archive at once — which is precisely why the triage above has to come first. Decide what's public, clean only that, and leave the rest of the record as it is.

Common mistakes and misconceptions

"I'm the closest living relative, so I have the right to download everything." Access to a deceased person's online accounts is usually governed by a specific legal mechanism — an online-tool designation, a will, or a fiduciary-access statute like RUFADAA in the US — not by how close the relationship was. A provider can and sometimes does refuse a request from even an obviously grieving, obviously related family member if none of those conditions are met.

"Stripping metadata from everything protects the family." It erases the dates and captions that often make an old photo useful in the first place, on files that were never going anywhere public to begin with. The protection that actually matters applies narrowly, to the specific photos headed outside the family.

"If a photo's already been posted somewhere, it doesn't matter what my copy's metadata shows." Posting your own copy of a photo publicly is a new disclosure, from a new account, even if an old post of the same image exists somewhere else. Don't assume the earlier post already covers the one you're about to make.

"GDPR will have handled this if the relative lived in the EU." Recital 27 explicitly excludes deceased persons' data from the regulation. Whatever protection applies depends on that specific country's own rules, which vary and may not exist at all.

"One cleaning pass through the whole archive is the efficient way to do this." It's the way to permanently lose dates and context from thousands of photos that were never going to be shared outside the family. Triage first; clean only what's leaving.

Related guides

Frequently asked questions

Does being next of kin automatically give me the right to download a deceased relative's online photo account?

Not automatically, and this trips up a lot of families. In the United States, the Revised Uniform Fiduciary Access to Digital Assets Act (RUFADAA), released by the Uniform Law Commission in 2015 and enacted in most states by 2021, gives a personal representative of the estate a right to access a user's electronic communications only if the deceased consented to that disclosure — either through a provider's own online tool, such as Facebook's Legacy Contact or Google's Inactive Account Manager, or in a will. If neither exists, the provider's terms of service remain in control, and the provider can refuse. Being next of kin, having a death certificate, or even being the named executor does not by itself override that. Outside the US, the details vary by country, so treat the specific rule for your jurisdiction and provider as something to check rather than assume.

Does GDPR or a similar privacy law protect a deceased relative's photos the same way it protected them while they were alive?

No, not automatically. Recital 27 of the EU's GDPR states plainly that the regulation does not apply to the personal data of deceased persons, and that member states may provide their own rules for handling it. In practice this means the strong, uniform protection a living EU resident's photos get disappears at death unless the specific member state has separately legislated something to fill that gap — and not all of them have, or have done so in the same way. If you are handling a deceased relative's photos in the EU, do not assume the GDPR is doing any work here; check the local rule for that country instead.

Should I strip metadata from every photo in an inherited archive before sharing it with family?

No. An inherited archive is exactly the case where stripping everything is the wrong instinct, because the embedded dates, and sometimes captions, are often the only record of when and where a photo was taken — information a family genuinely wants to keep, not a liability to delete. The better split is by destination: keep full, unmodified originals as the private family record, and only strip metadata from the specific copies headed somewhere public, such as a memorial website, an obituary slideshow, or a social media tribute post, where a stranger could read GPS coordinates for a house a living relative still occupies.

Can MetadataWipe handle a large inherited photo archive all at once?

No. The tool opens one JPEG or PNG at a time, decodes it onto a canvas and re-encodes it in your browser, which strips the entire tag layer from that file at once — there is no bulk queue and no field-level option to keep a date while dropping a GPS tag. For an archive spanning decades, that means triage has to happen first: decide which specific photos are going into something public, and only run those through. The rest of the archive — the private family record — is better left with its metadata intact.

Remove EXIF data, GPS location and common photo metadata from a JPEG or PNG in your browser, once you've decided which photo is actually going public.

Try MetadataWipe free