Remove Metadata From a Photo Before Publishing on Medium or Substack

Medium essays and Substack newsletters are long-lived publications. The hero image under the title, the inline photo mid-essay, and the social preview crop are not throwaway Stories frames. They stay attached to your byline in archives, RSS, and search results. If those JPEGs came from a phone on the kitchen table, GPS and device tags can ride along for as long as the article stays up — unless you strip them before upload.

This page is about personal blog and newsletter publishing hygiene. It is distinct from print-catalog intake and stock-photography submission, which are commercial pipelines with different buyers and contracts. Here the audience is readers of your writing, and the file is part of your public archive — not a one-off print proof or a licensing library ingest. MetadataWipe rebuilds JPEG or PNG in your browser so typical EXIF, IPTC, and XMP are not copied into the version you place in the editor. Processing stays on this device.

Why newsletter and essay images are a lasting exposure

Permanence. A Substack post from 2024 may still be the entry people find in 2026. A Medium piece can be republished, snapped into publications, and screenshotted for quote cards. The header on the master you keep uploading is a standing detail, not a one-week Story.

Byline adjacency. Catalog and stock pages elsewhere on this site concern files that leave for a printer or a library. On Medium and Substack, the photo sits next to your name and bio. A home GPS pin next to a personal essay about “leaving the city” is a quieter leak than a geotag on a meme, and easier to overlook because the workflow feels like writing, not “posting to social.”

Reuse across issues. Writers often recycle a desk photo, a city walk, or a book-stack flat-lay across multiple newsletters. Wipe once, store a clean master, and upload that copy every time. For commercial print placement of product or lookbook shots, see remove metadata before print catalog submission. For licensing libraries with different metadata norms, see strip metadata before stock photography submission.

What a phone-shot article image typically still contains

GPS. “Writer at the café” and “morning pages at home” are classic newsletter photography. Location Services on Camera can pin the café booth or the apartment. Readers did not ask for coordinates; the CMS did not need them to render the hero.

Timestamps. DateTimeOriginal can contradict a carefully vague essay timeline, or show that a “travel dispatch” was filed from the same room as last month’s post. Harmless for many writers; unnecessary for all of them.

Device and software tags. Make, Model, and editor Software fields fingerprint the phone and the last app that saved the file. They do not improve load time or SEO. IPTC caption fields you typed for yourself can also travel if you do not wipe — useful in stock workflows, often unwanted in a personal essay upload.

Pixels versus headers. MetadataWipe does not remove a visible address on a storefront or a child’s face in a lifestyle shot. Crop or choose a different frame first, then strip tags so a final export does not reintroduce Software metadata.

How to strip article photos in MetadataWipe before Medium or Substack

1. Export the final JPEG or PNG you will set as the hero or inline image — after crop and color, before CMS upload. Convert HEIC to JPEG if needed.
2. Open the MetadataWipe tool. Drop the file. Confirm GPS, time, and camera tags in the panel.
3. Strip locally. The cleaned download should not carry typical EXIF, IPTC, or XMP from the original.
4. Re-open the download in the panel to verify, then keep that file in a “publish-ready” folder.
5. Upload only the cleaned file in the Medium or Substack editor. Repeat for every inline image in the draft, not only the hero.

Disabling location for future phone shots helps. It does not clean the library of essay photos you already shot last year.

Realistic Medium and Substack scenarios

A personal essay with a home-office hero. Soft light, laptop, plant. GPS still names the block. Wipe before the draft goes live.

A travel newsletter that never lists the hotel. Prose stays atmospheric; the JPEG pins the room. Strip before upload, especially if subscribers include people you would not invite over.

A guest post on Medium that reuses an old camera-roll JPEG. New placement, old header. Wipe on reuse even if the photo “already ran” somewhere else.

A Substack Notes or social share crop exported from the same master. Each export can rewrite tags. Prefer one cleaned master for every crop.

Mistakes writers make with CMS image uploads

Assuming Medium or Substack always strips EXIF. Do not rely on platform stripping. Upload a file you already cleaned.

Claiming the platforms always preserve GPS either. Pipelines change. Your habit should not depend on guessing: strip first.

Cleaning the hero and forgetting inline figures. Every image is its own file with its own header.

Dragging from Photos/Recents after wiping a differently named export. Editors often grab the dirty original because it sorts first.

Treating newsletter photos like stock submissions. Stock buyers sometimes want selective IPTC; your essay usually wants a full wipe. Use the stock guide when you are actually submitting to a library — not when you are publishing your own archive.

Related guides

See also:

• Remove metadata before print catalog submission
• Strip metadata before stock photography submission