Why this exists
Most online converters work the same way: you hand your photographs to a stranger's server, it processes them, and you trust a page of text about what happens next. For a task a browser is perfectly capable of doing on its own, that is a poor trade — and it is slower, because your file has to travel twice.
Browsers have been able to do this work locally for years. This site is what happens when you build the tool that way instead.
How it works
The converter is a static website with no server-side component. When you add an image, it is decoded and re-encoded by WebAssembly builds of the same libraries desktop software uses — libwebp for WebP, mozjpeg for JPEG, libheif for the HEIC files iPhones produce — all running inside your own browser tab.
Shipping a real encoder rather than calling the browser's built-in canvas export has a practical consequence: Safari cannot produce WebP through that API at all, and the tools that rely on it silently fail or hand back a PNG. It also means genuine control over quality, effort, lossless mode and target file size, instead of a single slider.
What it does not do
There is no account to create, no watermark, no daily quota and no paid tier holding features back. There are no analytics scripts, no tracking cookies and no third-party embeds — every asset, fonts included, is served from this domain.
It is also honest about its limits. The encoder writes WebP, PNG and JPEG. It does not write PDF, GIF or SVG, and animated GIFs convert to their first frame only, which is flagged in the file list rather than done quietly.
Getting in touch
Bug reports, formats worth adding and awkward files that break the converter are all genuinely welcome. The contact page has the address, and the privacy page explains how to verify the claims above rather than take them on trust.