WebP is fine for the web and hostile to forms
Search demand for “webp to jpg” is a conversion-out problem, not a web-performance problem. People already have a WebP — they need a JPEG a 2014 upload validator will eat. ExactKB uses the browser’s built-in WebP decoder, then the same exact-KB JPEG encoder as the rest of the site.
You usually got the WebP by right-clicking a photo on the web, exporting from a design tool, or saving from WhatsApp Web. None of those tools know your SSC or ATS limit. They give you a modern container and call it a day.
Keep the kilobyte target in the same step
Saving a WebP as JPG at quality 95 can make the file larger. If the next error is “must be under 100 KB,” you did two tools for one job. This page defaults to 100 KB. Use 50 KB for SSC/PAN-style fields and 20 KB for signatures. The result card shows whether we only re-encoded or also resized.
Animated WebP is out of scope. ExactKB reads a still. If you drop an animation, you will get a single frame (often the first). Do not use this page to flatten memes for a government form.
PNG instead?
Switch the output menu to PNG only if the destination forbids JPEG (some signature fields). PNG cannot quality-search; ExactKB will shrink dimensions to fit. For photographs, JPG is the correct output. Transparent WebP becomes white on JPEG, same as transparent PNG.
How to tell you actually have a WebP
The extension may be .webp, or it may be .jpg with WebP bytes inside — some downloaders lie. If a portal says invalid JPEG, drop the file here anyway. The browser decoder will accept WebP regardless of the name. We emit a real JPEG with a .jpg download name that includes the kilobyte size.
Privacy is the same as the rest of ExactKB: no upload, no account, EXIF stripped by the canvas. Read privacy if you are converting a screenshot that might contain personal data — we do not see it, but you should still crop before you encode.