Why Photo Metadata Matters for Freelancers — Client Sites and Camera Serials

A freelance JPEG can pin a client’s private property on a map and tie a leaked frame to a specific camera body. That is a confidentiality problem, not a portfolio-export checklist.

Ready to clean a photo? MetadataWipe processes JPEG and PNG files locally — no account and no server transfer.

Open MetadataWipe tool

Freelancers carry other people’s secrets in camera headers. The assignment might be a divorce attorney’s documentary stills, a product embargo, a private-equity site visit, or a family that paid you not to advertise their address. The JPEG still writes GPS if Location Services was on, and many bodies write a serial number that says which physical camera made the frame. Those two fields do different damage. GPS is the client’s property. The serial is you — useful when a leaked image is being blamed on “some photographer,” useful to a thief matching a pawned body, and poisonous when you were hired to be uncredited on a sensitive job.

A separate MetadataWipe page walks through stripping files before a public portfolio goes live. This page is why the tags matter even if you never publish a case study: the file that leaves your card reader is already a confidentiality object. MetadataWipe rebuilds a JPEG or PNG in the browser so typical GPS, serial-adjacent tags, and timestamps are not copied into the copy you hand off. Processing stays on this device.

GPS that describes the client, not the freelancer

Phones and many mirrorless bodies geotag by default when location is enabled. On a residential interior job, that pin is the client’s house. On a corporate job it may be a building that is not in the press kit — a test kitchen, a server room, a founder’s apartment used as a set. Clients notice when a JPEG opened in Preview’s inspector or in Lightroom’s map module shows the alley behind a storefront that was supposed to stay unnamed. NDAs that mention “location of the shoot” are talking about this field even when the lawyer never said “EXIF.”

Timestamps compound it. DateTimeOriginal can prove you were on a closed set the night before an announcement, or that a “day-in-the-life” series was actually shot in one hour. Embargoed work is a calendar secret. The pixels can wait. The clock in the header should not travel with a preview you send to a retoucher whose Dropbox is shared with an intern.

Serial numbers as a fingerprint of the kit — and of you

Canon, Nikon, Sony, and others have used EXIF or MakerNote fields for body serials. Used-gear buyers already treat shutter count and serial as identity. In a freelance dispute, the same identity is evidence: this frame came from body X, and body X was on your insurance schedule that week. That can protect you if someone else leaked a file. It can also identify you when the client wanted an uncredited photographer on a medical, legal, or labor-sensitive shoot. IPTC By-line is a credit you chose. A serial is a hardware ID you may not have meant to publish.

Serials also correlate jobs. Two “anonymous” stills on a leak site with the same BodySerialNumber are the same camera. If you shoot both a controversial documentary and a luxury-real-estate job on one body, a researcher can join the sets. Wiping the serial on files that leave your custody is how you stop that join. Keeping serials on your offline masters is how you still prove provenance if you need to. Those are different copies.

For stripping author and contact tags you typed yourself, see remove photographer info from an image. For the public case-study workflow, see remove metadata from freelance portfolio photos. This page is the reason those steps exist: client coordinates and kit identity.

How to wipe a handoff JPEG in MetadataWipe

  1. Export a JPEG or PNG you are actually sending. iPhone HEIC must be saved as JPEG first. This site’s tool opens JPEG and PNG. Do not send a DNG “for quality” to a client portal that will rewrite it later anyway.
  2. Open the MetadataWipe tool. Drop the file. Confirm GPS, DateTimeOriginal, Make/Model, and any serial-looking field the panel shows before you strip, so you know the wipe did work afterward.
  3. Strip locally. The canvas rewrite does not copy typical EXIF/IPTC/XMP into the new file. Your original stays on disk.
  4. Re-open the download in the same panel. GPS and camera serial should be gone. If a sidecar .xmp is sitting next to the JPEG in the folder you are about to zip, leave the sidecar out — wiping the JPEG does not delete the XMP.
  5. Send only the cleaned file. Keep geotagged masters in the job folder you do not share. If you need copyright on the public copy, re-add IPTC in a tool that does not restore GPS.

Jobs where these two fields actually bite

A documentary still from a private home for a legal matter. Faces may be in the frame with consent. The GPS is the address opposing counsel was not supposed to get from a photo. Wipe the handoff JPEG. Do not strip the evidence master if a lawyer told you to preserve it — that is a different page and a different duty.

An embargoed product on a kitchen island. The photo is the product. The header is the founder’s apartment and Sunday 11:41 p.m. A retailer who saves the preview can read both. Wipe before the JPEG hits Slack.

A second shooter delivering cards at wrap. Their Lightroom ingest will keep every tag you did not strip. If the lead photographer’s NDA forbids location disclosure, the second shooter’s selects are still a leak. Wipe before the cards are copied, or copy then wipe, then deliver.

A stolen-camera or “who leaked this” argument. Here you may want the serial on a file you control. That is a reason to keep masters, not a reason to email geotagged selects. Provenance and confidentiality are solved with two copies, not one dirty file.

Habits that keep client GPS intact

Leaving Location Services on “for the map module.” Cull with a private GPS log if you must. Do not send the geotagged export.

Zipping JPEG plus XMP for a retoucher. The sidecar puts the pin back.

Wiping the hero and sending three unedited alternates. Each file has its own header.

Trusting a WeTransfer or Dropbox preview to “flatten” metadata. Many transfer tools send the bytes you gave them.

Related guides

See also:

Frequently asked questions

How does GPS in a freelance photo become the client’s problem?

Location Services writes the shoot coordinates into EXIF. If the job was at a private residence, a pre-launch factory, a clinic, or a founder’s home office, that pin is the client’s site — not yours. A JPEG that later sits in a WeTransfer folder, a subcontractor’s drive, or a public case study can be opened in any EXIF viewer. The pixels were licensed. The coordinates may still be confidential.

What does a camera serial actually identify?

Many interchangeable-lens bodies write a serial into EXIF or MakerNotes (Canon’s BodySerialNumber / InternalSerialNumber, Nikon serial fields, and similar). In a dispute over who photographed a leaked still, or which kit was on a closed set, that serial is a fingerprint of a physical camera. It can also match stolen-gear databases. It is not the same as an IPTC copyright line you intended to keep.

Is this the same as wiping photos before a Behance case study?

Related, but the risk starts earlier. Portfolio publication is one leak path. The other is handing a client, an editor, or a second shooter a “selects” folder whose headers still describe the house you were not supposed to geolocate. Wipe the files that leave your encrypted disk, not only the ones you later post.

Does MetadataWipe send client photos to a server?

No. JPEG and PNG are read into browser memory on your device. Typical EXIF, IPTC, and XMP blocks are not copied into the cleaned download. The original is not sent to MetadataWipe for processing.

Remove EXIF data, GPS location, and common photo metadata in your browser.

Try MetadataWipe free