Remove Metadata From Freelance Portfolio Photos

Publish case-study imagery without leaking client locations, shoot times, or gear serial numbers.

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

Open MetadataWipe tool

Freelance photographers and designers showcase client work on personal sites — revealing craft and inadvertently leaking where and when shoots happened. A restaurant campaign photo may GPS-tag the client's back alley. A product launch sample may timestamp an embargoed reveal. Camera serials can tie unpublished series together.

MetadataWipe lets creatives strip envelope data in the browser before portfolio publication, protecting client confidentiality and your own gear fingerprint without sending masters to cloud cleaners.

How to use MetadataWipe

  1. 1. ('Export finals.', 'Export web-resolution JPEGs you plan to publish — not RAW masters unless policy allows.')
  2. 2. ('Load in MetadataWipe.', 'Open each image on the homepage tool locally.')
  3. 3. ('Review tags.', 'Check GPS, timestamps, lens serials, and embedded user comments from Lightroom exports.')
  4. 4. ('Strip and publish.', 'Download wiped copies and use only those on your portfolio CDN.')

Portfolio Metadata and Client NDAs

Location tags betray confidential set addresses for film and commercial work.

Timestamps can prove a leak before an official product announcement.

Serial numbers help competitors map which bodies you shoot on.

Case-study JPEGs that still name the shoot

Behance projects and a freelancer's own work page usually serve the JPEG Lightroom wrote to disk—not the recompressed tile a social network would have rewritten. That master still carries GPS from the client's warehouse, DateTimeOriginal from a Sunday night reshoot, camera make and model that identify rented bodies, and an IPTC author line with the name on your invoices. A visitor who saves the hero image can read those fields in any EXIF viewer. The pixels sell the craft; the header can violate an NDA.

Sidecar .xmp files sitting next to the JPEG are a second copy of the same story. Wiping the JPEG does not delete the sidecar. If you zip a project folder for a prospect, the XMP goes along unless you leave it out.

Cleaning a portfolio export in the browser

Work from a duplicate of the JPEG or PNG you intend to publish. Open the MetadataWipe homepage tool, drop the file in, and read the panel before you strip anything. Confirm GPS, DateTimeOriginal, Make, Model, and IPTC author are actually present so you know the wipe did work afterward.

  1. Reject HEIC, TIFF, and PSD. Export a JPEG from Lightroom or Photos first; this page's tool opens JPEG and PNG only.
  2. Strip locally. The canvas rewrite never uploads the case-study file.
  3. Re-open the download in the same panel and confirm GPS and IPTC author are gone.
  4. Publish that download, not the file still linked from a NAS folder or cloud original.

If the case study includes a dashboard capture, treat that PNG the same way. Software tags and capture clocks identify a small client's stack as clearly as a lens serial.

When a client NDA meets a Lightroom catalog

A product designer documenting a factory visit often leaves GPS on because Lightroom's map module is useful during culling. The public case study does not need that map. After you pick hero frames, export JPEG, wipe in the browser, and only then place the images in the CMS. Keep cataloged originals offline.

A wedding photographer posting a blog teaser faces a different leak: DateTimeOriginal plus GPS can reconstruct the couple's home and the ceremony minute. Faces may be approved; the header is not part of the model release. Wipe the JPEGs that go on the blog.

A consultant embedding before/after UI photos in a PDF pitch should still wipe the source JPEGs. MetadataWipe does not rewrite PDF Author fields. Clean the images, then place those cleaned files into the deck so the PDF is not a wrapper around dirty JPEGs.

Portfolio habits that keep EXIF intact

Most leaks are workflow, not malice. The site looks finished while the media library still holds camera originals.

  1. Linking the Lightroom export folder. Those JPEGs were built for color, not for public headers.
  2. Zipping JPEG plus .xmp for a prospect. The sidecar restores IPTC author and GPS the moment they open it in Bridge.
  3. Publishing a TIFF “for quality.” This tool does not open TIFF; make a JPEG, wipe it, and use that.
  4. Replacing a wiped file with a fresh crop from the catalog. A new export is a new EXIF block unless you wipe again.

Related guides

See also:

Frequently asked questions

What metadata do portfolio photos leak?

GPS from on-location brand shoots, client property coordinates, capture timestamps tied to embargoed launches, and camera serial numbers used to fingerprint your kit.

Should I wipe before or after retouching?

Wipe before publishing the final export. Some editors strip tags; many preserve or add XMP — verify the file you actually publish.

Can I keep copyright metadata?

MetadataWipe removes marketing-sensitive tags. If you need copyright assertions, re-add them in tools that do not restore GPS.

Do Behance and personal sites strip EXIF?

Do not rely on platforms. Wipe locally before publishing.

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

Try MetadataWipe free

Creative portfolios are marketing assets — but EXIF turns them into evidence. A wedding photographer's 'favorite frame' may include GPS of a private estate. A UX designer's app mockup photo may timestamp a stealth client visit. Agencies under NDA cannot afford either leak.

MetadataWipe supports a pre-publish checklist: export, wipe, verify, load. Everything runs client-side so unreleased work never transits a metadata vendor while you are trying to remove location tags.

What Freelance Portfolio Metadata Exposes — and Why

GPS from on-site shoots reveals client facilities and private residences.

DateTimeOriginal conflicts with staged 'timeless' branding and embargo windows.

Lens and body serials fingerprint your kit across anonymous portfolio pieces.

Realistic Scenarios

Scenario A — Food photographer: Strips GPS from kitchen shoots before Instagram portfolio updates.

Scenario B — Brand designer: Wipes timestamps from embargoed packaging photos on a personal site.

Scenario C — Documentary stills: Removes location tags from sensitive community projects while keeping captions authoritative.

Step-by-Step: How to Use the Tool

  1. Batch-export portfolio JPEGs from Lightroom, Capture One, or Figma renders.
  2. Load each publish-bound file into MetadataWipe.
  3. Remove all metadata fields reported in the panel.
  4. Download wiped exports and spot-check in a viewer.
  5. Publish only wiped files to your site, Behance, or Dribbble embeds.

Common Mistakes

Publishing RAW files for 'quality'. Use web JPEGs; RAW carries extensive metadata and is rarely needed online.

Trusting 'Save for Web'. Verify — some workflows preserve XMP.

Wiping only the hero image on a case study. Strip every image in the gallery.

Why Browser-Only Portfolio Cleaning Matters

Portfolio masters are your reputation — sending them to random EXIF websites before launch is opposite of professional OPSEC. MetadataWipe keeps files on your workstation until metadata is gone, aligning with how studios already treat color-critical exports. Agency producers should add metadata wiping to the same checklist as model releases and location permits — all three govern what leaks when work goes public.