JFIF to JPG Free Convert a file

Privacy Policy

Last updated: August 2026.

Your images

JFIF to JPG Free's conversion tools run entirely in your browser. Files you drop, select, or paste are processed locally using the Canvas and File APIs - they are never uploaded to a server, and we never see, store, or have access to them. This isn't a policy choice we could reverse; the tools are architecturally incapable of transmitting your images anywhere.

Cookies and local storage

The site does not currently set cookies or use browser local storage for tracking or any other purpose.

Third-party resources currently loaded

To render correctly, pages on this site load two third-party resources every time you load the page:

  • Google Fonts (fonts.googleapis.com, fonts.gstatic.com) - for the site's typefaces.
  • jsDelivr CDN (cdn.jsdelivr.net) - for the JSZip library used by the "download all as .zip" feature, on pages that offer it.

A third resource loads conditionally, only if you actually use Full Convert mode to produce a JPG or WEBP file: esm.sh (esm.sh), which serves the WebAssembly compression library (jsquash, built on Google's own MozJPEG and WebP codecs) that does the real re-encoding. If that request fails for any reason - an ad blocker, a network issue - the tool automatically falls back to your browser's built-in encoder instead, so conversion still works.

None of these requests carry any image data. They fetch code and fonts only, and the code that does receive your image data - the compression library - runs the encoding entirely on your device; it never transmits the image anywhere.

The contact form is a separate case: submitting it sends whatever name, email, and message you type to Web3Forms (web3forms.com), a third-party service that relays the message to us by email. This only happens if you actually submit the form - it doesn't run on any other page, and it never has access to your images.

The support chat bubble (available on every page) searches a local copy of this site's own help content - every tool page's FAQ and every blog post - directly in your browser using simple keyword matching. Nothing you type into it is sent to us, to a third-party AI service, or anywhere else; the only network request it makes is fetching that help-content file itself (no message content included), the same way loading any other page asset works.

Planned, not yet active

We plan to add Google AdSense (for advertising) and an analytics tool in the future. Neither is active on the site today. When added, this policy will be updated to describe what data those services collect (typically things like page views and non-identifying usage patterns, not the contents of any image you convert) before they go live.

Contact

Questions about this policy? Use the contact form.