Remove image metadata from a copy before sharing

Decide what information you want to withhold

Camera files can contain information beyond the visible picture, such as capture settings, dates, device details and, where recorded, location. You may not want to pass those fields on with a casual product photograph or a picture sent to someone you do not know. Preparing a separate sharing copy keeps that decision apart from storing your original.

Not every image contains the same fields. A photo picker, messaging application or earlier export may already have changed them. This tool does not display a complete before-and-after metadata inventory, so it should not be treated as proof that a particular GPS coordinate existed in the source or was the only information removed.

What the operation actually does

The image is decoded, drawn and saved as a fresh file in its supported format. Source EXIF, GPS and comment information is not copied into that export. This is a broader image rewrite rather than a surgical editor that removes one chosen field while leaving every other byte untouched.

The browser may include its own encoding information in the new file. That is why the result is described as a copy without the original metadata, not a mathematically empty metadata container. If a particular recipient has strict technical rules, check the final file with a suitable metadata inspector and follow the recipient’s required workflow.

There are no switches on this page for keeping the camera name, removing only location or editing individual dates. If you need selective metadata management, use an editor that exposes those fields and lets you inspect the result. A broad re-encode is appropriate only when its other changes are acceptable for your purpose.

Keep originals when the record matters

Retain the original if the photo forms part of a claim, application, work record or other process that may require its original information. Do not remove fields simply because a smaller or cleaner-looking copy seems more convenient. The receiving organisation may want the unmodified source, and you should follow its instructions.

For everyday sharing, a separate copy is usually easier to manage than changing the only file. Use a clear filename and a known saved location. On a shared computer, remember that the downloaded image is still a file on that device. Local processing does not control who can later open your Downloads folder or cloud-synchronised storage.

The visible picture is not redacted

A house number, street sign, parcel label or reflection can reveal information even after source location fields are not copied. Names on a certificate and details on a screen remain pixels in the image. Review the whole picture before publishing it, including small areas around the main subject.

This page has no blur, crop or redaction control. If information needs to be concealed visually, use an appropriate editing workflow and inspect the resulting file. Do not assume that removing metadata has hidden the subject, made a face unrecognisable or prevented someone inferring a location from the scene.

Re-encoding can affect the image

The exported copy is not promised to be byte-for-byte identical to the original. In formats that use lossy compression, the picture can change slightly, and the file size may increase or decrease. Compare fine detail, edges, colours and any required text before deciding that the sharing copy is suitable.

For photographs with unusual colour profiles or a specialist printing purpose, retain the original and use a colour-managed workflow where needed. This tool prepares ordinary browser-readable images; it does not certify faithful reproduction on every monitor or printer. A successful download is a technical processing result rather than an approval of the image for every use.

Check the orientation after processing

Some photographs use an orientation instruction to tell a viewer how to display the stored pixels. When the browser decodes and re-encodes an image, that visual orientation needs checking in the new copy. Open the saved output and compare its top edge and any lettering with your intended view.

If the output is sideways, use the original to investigate the orientation issue instead of repeatedly rewriting the already changed copy. A normalisation tool and a manual image editor solve different cases. The metadata remover is not a button for choosing any arbitrary rotation, and it does not decide what the scene should look like.

Supported inputs and processing failures

This operation supports JPG, PNG and WebP still images. It is not a metadata cleaner for PDFs, Office documents, videos or every image format. HEIC photographs need an appropriate export or conversion route first. Do not assume an unsupported file has no metadata simply because this tool cannot process it.

The file-size cap is 25 MiB per input, with a separate image budget of 18 million decoded pixels. A valid but very large picture can fail within those limits of the workflow. If processing stops, open the source in its original application and obtain an appropriate still-image export. Your selected original is not overwritten by a failed operation.

Review the download in the way that matters

Download the new copy, inspect the visible image and confirm the format and size expected by the receiving service. If your main concern is a specific metadata field, inspect the final copy using a tool that can read that field. Keep any sensitive original out of the upload selection by checking the exact filename you choose.

Your file is processed on this device rather than sent to a Make My Files Work conversion server. That limits this workflow’s transfer of the picture; it does not change what the service you later upload to may collect. Decide where you send the finished file separately from how you prepared it here.

A sensible two-copy arrangement

Keep an untouched original in your normal photo storage and put the prepared sharing copy in a separate, clearly named location. This lets you choose the less revealing copy for an ordinary listing while retaining capture information if you later need it for your own records. Check that any synchronised folder behaves as you expect.

Before sending, inspect the attachment selected by the receiving application. Some gallery pickers show multiple near-identical versions without an obvious filename. If that makes the choice uncertain, use a file picker that shows the saved name and location. The privacy decision only helps if you actually send the copy you prepared.

Questions that come up