Updated 2026-09-03
Why Browser-Side Image Tools Are More Private
How local conversion differs from upload-based tools, and what still leaves your device.
Upload-based converters
Classic online tools receive your file on a server, process it, store it briefly (or longer), and send back a download link. Even trustworthy vendors introduce a third copy of the image outside your device. That copy may appear in logs, backups, or CDN caches depending on how the service is built. For confidential screenshots, unpublished product shots, or personal documents, that model is hard to justify.
What “in your browser” means here
Image Reshaper reads the file you select, draws it with canvas APIs, and builds a downloadable blob URL. Conversion does not require an Image Reshaper account, and we do not need the image bytes on our servers to finish the task. Optional analytics, when enabled and allowed by your consent choices, record events such as which tool opened—not the picture itself.
You still choose what leaves the machine afterward: if you email the download or upload it to a form, that is a separate action. Stripping metadata before sharing reduces the chance that GPS or device tags travel with the file.
Practical habits
Prefer local tools for anything you would not post publicly. Crop out sensitive edges. Remove metadata. Double-check the download before you attach it. When a cloud converter is unavoidable, use a redacted copy, not the only original.