JPG -> WEBP · Local tool
JPG to WebP
Turn JPG photos into WebP for the web, with the size shown before you commit.
Last updated
01 / Your device
the file stays here
02 / Browser memory
the work runs locally
03 / Back to you
saved on this device
When you would use this
Situations, not settings.
- A page scoring badly on image weight
- Lighthouse flags the photos before anything else, and WebP is the format it is asking for. The JPGs are already on disk.
- A content system that now prefers WebP
- Newer themes and image fields expect it. Converting the photos you already have is less work than fighting the upload rules.
- Product shots going into a shop listing
- The same picture at a smaller download, which is what a shop page gets judged on. Check the measured size, because a heavily compressed JPG can come back bigger.
How it works / no cloud
A conversion engine, not an upload form.
Your browser already decodes JPG and encodes WebP, so filetity reads the photo with the browser's own codec, redraws it on a canvas and re-encodes it as WebP at the quality you choose. No conversion service, no upload, and no engine to download.
- Offline ready
- Installable app
- No file limit queue
Straight answers
No accordion. Nothing hidden.
- Is it free?
- Yes, with no watermark and no page limit.
- Does it need an account?
- No. There is no account system.
- Is my file processed on my device?
- Yes. The file is read by your browser and never uploaded. There is no server to send it to.
- What formats are supported?
- JPG in. WebP out, one file per image, or a ZIP when you convert several.
- What are the limits?
- No image count limit. Both formats are lossy, so a JPG that has already been squeezed can come out no smaller, or larger. The measured size is shown before you download.
- Does it work on mobile?
- Yes, on any modern mobile browser. Large files are limited by the memory the phone gives the browser.
- Does it work offline?
- Yes, once the page has loaded. The tool keeps working with no network connection.
- Will the WebP definitely be smaller than my JPG?
- Not always. WebP compresses better than JPG from the same original, but your JPG is not an original: it has already been through one lossy pass, and re-encoding cannot undo that. A lightly compressed JPG usually shrinks. One that was already squeezed for email can come out the same size or bigger. The result is measured and shown before you download, so you can keep the original when it wins.
- How much quality does this cost?
- A little. Two lossy formats in a row means a second approximation over data that was already approximated once, so fine texture and hard edges soften slightly. A higher quality setting reduces it and costs file size. Nothing avoids it entirely, because the JPG cannot be un-compressed first.
- Does my photo get a transparent background?
- No. WebP supports transparency and a JPG has none to carry across, so the result is fully opaque. Changing the format cannot add an alpha channel that was never there.
- Should I convert my whole photo library?
- No. WebP is a delivery format. Converting a library re-compresses every file for a saving you may not get, and leaves you with images some desktop tools still refuse. Convert the copies that go on a web page and keep the originals.
Keep working locally
4 available · more coming