OpusDesk Image Tools
LOCAL IMAGE WORKSPACE

Remove image metadata

Re-encode supported JPG, PNG or WebP locally to remove supported private metadata. Check visible content and filenames separately before sharing.

Local processing · No account · No image upload

The existing interactive controls below are in Traditional Chinese. The English guide explains this exact operation.

正在載入本地工具…

Check both the picture and the information attached to it

An image may contain location, capture time, device, author or editing-software information in addition to visible pixels. This workspace decodes and re-encodes a supported JPG, PNG or WebP without copying the supported private EXIF, GPS, XMP, IPTC, thumbnail and text fields. It is not a tool for erasing visible names, people, addresses or document details. Those may need a separate redaction or editing workflow.

The output preserves normalized display direction, but JPEG re-encoding can be lossy. Inspect the result rather than treating metadata cleanup as a quality guarantee. The page keeps the supported source format selected and does not substitute an unchanged original for a cleaned result. Unknown proprietary blocks should not be claimed as universally removed. A downloaded filename can still reveal personal information even when metadata is absent.

Worked example

A PNG containing a supported private text field can be decoded and exported as a fresh PNG without copying that field. This does not remove a street address visible inside the picture. Likewise, a JPEG with a location field still needs an appearance check after re-encoding. Keep the source under your control; this workspace does not delete or securely erase it.

Local processing and limits

One supported static image is processed at a time. The general input limit is 10 MiB and twelve million pixels; AVIF processing is limited to four million pixels. Unsupported animation, image sequences, HDR and unverified container features are refused. Large images need more memory even when their compressed file is small. A failed operation does not switch to a server-upload fallback.

The browser downloads its own application and codec resources from the same host. Your selected image, result, filename and metadata are not sent to an upload service. Images are not written to localStorage, IndexedDB or a service-worker recovery cache. Reloading the page leaves the image workspace empty. Downloaded files remain under your control; inspect them before sharing.

Frequently asked questions

Does removing metadata make an image anonymous?

No. Visible content, filenames and unverified private structures may still reveal information. Review the actual output and its context before sharing.

Are my images uploaded?

No. Images, results, filenames and metadata are processed in page and local worker memory. The website downloads its own program and codec files; hosting may process ordinary request metadata.

Will it change my original file?

No. The download is managed separately. Keep the original yourself; this workspace does not overwrite a source file or provide a cloud backup.

What can stop an operation?

Unsupported or damaged input, a file over 10 MiB, pixel limits, missing resources or a timeout can stop processing. General images are limited to twelve million pixels; AVIF processing is limited to four million. Animated images and unverified HDR or high-bit-depth features are not supported.