The short answer
There is no dependable rule that ordinary editing removes metadata; inspect the exact exported file after the last edit. An editor may retain EXIF, add XMP workflow history, preserve an ICC profile, write comments, or strip selected fields according to export settings.
This matters when a source photo passes through phone markup, desktop editing, automated optimization, a content-management system, or a collaboration tool.
Editing can preserve, rewrite, or add fields
A nondestructive editor may leave the source untouched and store adjustments in a catalog, sidecar, or XMP block. An export can copy original EXIF, write a new software tag, update dimensions and orientation, embed a color profile, and carry selected copyright or caption fields. A simple crop therefore says almost nothing about whether GPS or authorship survived in the exported file.
Format choice also changes the container. Converting JPEG to PNG may drop one metadata structure but add text or color chunks. Exporting WebP can include EXIF or XMP when the application supports them. A screenshot creates a new capture whose operating system or app may write fresh fields. These outcomes depend on product, version, settings, and route through the application—not on a universal rule about “editing.”
Audit the last mile of the workflow
Inspect after the final resize, optimization, watermark, color conversion, or content-management download. An earlier clean file can gain metadata again when another application opens and saves it. Compare the inspected file’s name, byte size, type, and pixel dimensions with the export receipt or folder listing so a preview or stale draft is not mistaken for the delivery copy.
If a workflow repeatedly adds unwanted fields, create an export preset and test it across every format you publish. Keep one controlled fixture with known GPS, author, and description fields, run it through the pipeline, and inspect the result after software updates. This turns metadata handling into a regression check instead of a one-time assumption and gives teams a concrete signal when a tool changes behavior.
Use the browser tool on the final file
Complete the edit, export the intended format, close the editor if necessary, then choose that saved output in the metadata viewer. Choose the exact JPEG, PNG, or WebP copy you intend to share and select Inspect metadata. Read the grouped results and distinguish removable findings from retained color information. If removal is appropriate, create a cleaned copy. The tool rewrites supported container metadata without canvas recompression, reparses its output, and enables download only after verification reports no supported removable metadata.
Keep the original separately, download the “-clean” copy, and inspect that downloaded file again when the decision is sensitive. This workflow gives evidence about one exact file; it does not alter earlier exports or copies already sent elsewhere. The selected bytes and parsed values stay in the current browser tab rather than being uploaded to an image-processing endpoint.
Interpret the result within its scope
Compare file type, size, dimensions, and grouped findings with the intended export, keeping color information distinct from privacy-oriented fields. A screenshot or format conversion may change metadata, but neither action guarantees removal and both can introduce new software or time information.
A clean result is deliberately narrow: it means the parser did not find a supported privacy-sensitive or removable item in that file. It is not proof against every proprietary block, concealed payload, visible clue, filename disclosure, remote copy, or steganographic technique. Review pixels, context, audience, and destination separately, and use a purpose-built forensic workflow for high-risk decisions.