Privacy

Image files you convert with Formatly stay on your device. We do not receive, store, or process those files on a server for conversion. Decoding and encoding run in the browser session that you started.

A practical check: in DevTools → Network, convert a photo or paste JSON. There is no request that carries the file bytes to Formatly for processing. Page views and codec scripts are not the same as an upload. If a converter required a server, you would see the original file leave this origin as a POST or PUT.

Formatly does not require an account to convert images. There is no conversion history stored on a Formatly backend because conversion never leaves the client for that purpose.

The homepage may keep a short “Recently opened” list of tools you visited in this browser (localStorage only). That list never leaves your device and is not sent to Formatly servers. You can clear it from the homepage at any time.

This page describes product behavior for the converters and tools. The marketing site may still use ordinary web analytics or hosting logs for the HTML pages themselves — those are separate from the file bytes you drop into a tool. Technical detail on local processing is on security.

Questions about the project: see about.