Create a re-encoded sharing copy instead of copying source metadata

A camera image can contain metadata such as camera settings, a timestamp or location records. Those fields are different from the visible picture. A street sign, document, reflection or recognizable building remains visible even when the file no longer carries the original camera records. Treat metadata removal as one step in preparing a sharing copy, not a complete privacy review.

This workflow decodes the image, draws it to a canvas and creates a new file. It does not copy the original EXIF block into that output. It is not a forensic metadata scrubber and does not provide an inspection report proving the absence of every possible identifying field. The encoder may write its own basic file information. If your use requires a specific metadata guarantee, inspect the downloaded file with an appropriate metadata analysis tool and follow the requirements of that use.

The starting settings use PNG, Keep original pixels and sharpening off. This avoids a deliberate resize or an extra lossy photo encode while creating the new raster file. It can produce a much larger file than the source JPEG, so it is a starting point for a careful copy rather than a promise of smaller storage. Browser decoding and canvas rendering still have limits, especially for specialized color workflows.

If you need a smaller opaque sharing photo, compare JPEG at a suitable quality after checking the basic export. Keep PNG when the source has transparency that matters, because JPEG and this tool's WebP output use a white background. Do not remove your only original: its camera records or other information may be useful for your own archive. Save the re-encoded file separately and label it clearly so it cannot be confused with the source when you attach or publish it.

Before sending the copy, inspect the entire picture for names, addresses, screens, plates, booking codes and other visible information. Crop or redact in a suitable editor when necessary. This page does not detect faces, blur private text or remove reflections. Changing the file container does not make a sensitive photograph safe to share with any audience.

Review the download's filename as well. A filename can itself reveal a client name, address or project detail even when the source metadata was not copied. Open the exact downloaded file, verify its appearance and inspect metadata separately if that matters for your task. For a batch, check representative files from each camera or source type rather than assuming one successful result proves all of them. Local processing means this compressor does not receive the images, but the later service or person you choose to share with still receives the exported file and its visible contents.

For a public property image, a family photograph and a document example, the sensitive details can be very different. Review the image according to that purpose rather than following a single filename or extension rule. A document example may need proper redaction, while a travel photograph may reveal a location without any GPS field at all. Keep the unedited source in your own storage and share only the reviewed copy intended for the recipient. Avoid repeatedly converting the file as a substitute for checking its contents.