Strip EXIF metadata from images on Mac before sharing
Image privacy is more than cropping the visible part. A clean share copy should also avoid carrying camera, location, software, profile, and timestamp details that the recipient does not need.
The short answer: to strip EXIF metadata from images on Mac, work on a copy, inspect what metadata is present, remove metadata from the share-ready version, and keep the original file untouched when metadata may still matter for provenance or review.
TeenyTool is my app, so the bias is clear. Its Strip EXIF tool is useful for practical image sharing because it can inspect metadata, save a stripped copy, handle batches, and keep the workflow local. It is not a forensic redaction suite, and it does not hide information visible in the pixels.
This guide is the TeenyTool spoke for the TeenyApps Mac image handoff checklist. Pair it with the TeenyColor guide to check image color shift on Mac when the same image also needs color evidence.
Quick metadata decision table
| Image use | Metadata decision | Why |
|---|---|---|
| Public blog, forum, or social post | Strip the share copy. | The audience usually needs the image, not camera, location, or editing details. |
| Client handoff or support ticket | Strip unless the recipient asked for provenance. | Private customer, project, or device context can travel farther than intended. |
| Internal archive | Keep the original metadata. | Dates, profiles, camera data, and software history can be useful later. |
| Photo review or legal evidence | Do not strip casually. | Metadata may be part of the review record or evidence chain. |
| Batch of mixed images | Split the batch by sharing rule. | One batch action should not erase metadata that one image still needs. |
01Decide what the image is allowed to reveal
Metadata is not automatically bad. It can explain when an image was made, what profile it used, which camera produced it, or what software wrote the file. That is useful for internal archives, photo review, color work, and some evidence workflows.
The risk starts when the image leaves that context. A screenshot, photo, support image, or client mockup can carry location, dates, device details, camera data, software names, profile names, and editing clues. The recipient may never need any of that.
Make the decision before you run a tool. "Public copy" and "archive copy" are different files. Do not damage the source just to make the upload folder look clean.
02Inspect before you strip
Preview can show information about PDFs and images, including file size, author name, and image resolution. That is a good first check when the question is simple: what is this file, how large is it, and what obvious details are attached?
TeenyTool's Strip EXIF view goes deeper for the local image pass. The source reads image properties with Image I/O, flattens nested metadata into visible rows, and groups entries as EXIF, TIFF, GPS, date/time, or general metadata. Each value has an inline copy button, which helps when you need to record the risky field before removing it from the share copy.
If there is no meaningful metadata, do not invent a job. Check the filename, visible image content, and destination instead.
03Strip the share copy, not the source
TeenyTool writes output with a clear _stripped suffix for single images. For batch work, it saves stripped outputs into a ZIP. That naming is useful because the original file stays available if you later need profile data, timestamps, or other provenance.
The Strip EXIF source sets common Image I/O metadata dictionaries to null when writing the output, including EXIF, EXIF auxiliary, GPS, TIFF, IPTC, JFIF, Maker Apple, DNG, CIFF, 8BIM, and profile-name properties. For WebP, the source removes EXIF and XMP chunks and rewrites the RIFF size.
That is a practical privacy pass for routine sharing. It is not a promise that every possible hidden signal in every image format is gone. If the stakes are higher than a normal handoff, use the review process for that environment.
04Batch strip only when the rule is the same
Batch work is efficient when every image has the same sharing rule. TeenyTool's shared image support accepts up to 50 images or 500 MB at a time, validates image file types, rejects folders, and preserves output names with safe suffixes.
Do not throw archive images, public screenshots, and client photos into one batch because they happen to sit in the same Finder folder. Split them first. One image may need stripped metadata. Another may need metadata preserved because the date, profile, or camera detail is part of the record.
If the batch is headed to a public page, support ticket, or client folder, strip the share copies and keep the originals in a source folder.
05Metadata removal is not visual redaction
Removing EXIF does not hide a customer name visible in a screenshot. It does not blur a license key, crop a private route, hide a window title, remove a reflection, or rename a revealing file.
Run a visible-image check after metadata stripping. Open the output. Check the crop, zoom level, filenames, folder names, browser tabs, desktop icons, account names, QR codes, and any text in the image. Then upload the stripped copy, not the original.
For the broader file check, use the TeenyApps hub linked above. For color drift in the exported copy, use the TeenyColor guide linked above.
Five-minute EXIF stripping checklist
- Decide whether this is a source image, working image, or share-ready copy.
- Inspect the image metadata before removing anything.
- Keep metadata when provenance, archive, or evidence matters.
- Strip metadata from public, client, support, and forum copies when provenance is not needed.
- Batch strip only images that share the same rule.
- Open the stripped output and check the visible image content.
- Upload or send the stripped copy, then keep the source until the handoff is accepted.
Sources checked
- TeenyTool claims were checked against the TeenyTool homepage and local Swift source for
StripEXIFView,BatchImageSupport, Image I/O metadata reads, metadata grouping, output naming, WebP EXIF/XMP removal, batch limits, and ZIP output. - Apple Support: View information about PDFs and images in Preview on Mac.
- Apple Support: Crop, resize, or rotate an image in Preview on Mac.
- Apple Developer: CGImageDestination.
- Apple Developer: kCGImagePropertyGPSDictionary.
- Apple Developer: kCGImageMetadataShouldExcludeGPS.
FAQ
How do I strip EXIF metadata from images on Mac?
Work on a copy, inspect the image metadata, run a local metadata stripping tool, save the output with a clear suffix, then open the output before sharing it.
Should I remove metadata from every image before sharing?
No. Remove metadata when the image is going public, to a client, into a support ticket, or into a forum. Keep metadata when it is needed for archive, provenance, photo review, or internal evidence.
Does removing EXIF guarantee an image is private?
No. Metadata removal does not hide visible information inside the image. Review the pixels, crop, filename, folder context, and destination before sharing.
Make a clean copy before the image leaves your Mac.
teenytool includes Strip EXIF plus 75+ local utilities for images, text, colors, files, PDFs, developer snippets, calculations, and timers.