JPG · PNG · WebP — one re-encode, no upload
JPG, PNG or WebP. One re-encode.
Re-encode any image to JPG, PNG or WebP in your browser. Pick the format the destination actually renders — JPG for every government photo field, WebP for the web, PNG for logos — and do it in one pass so you only pay one generation of loss.
- 100% client-side
- Nothing is uploaded
- No account
- Canvas / WebAssembly on your device
Loading compressor…
Decision table: which format at which KB cap
| You are sending to | Pick | Why |
|---|---|---|
| Government photo upload field | JPG/JPEG | Only format every validator reliably accepts for photos |
| Signature upload that says “PNG” | PNG transparent | Value is the alpha — do it on Signature |
| Website, Gmail, CMS, WhatsApp for web | WebP | 40–60% of JPEG bytes at equal visual quality — fastest load |
| Logo / screenshot / flat graphic | PNG or lossless WebP | Keeps glyphs and edges razor-sharp; JPG fuzzies text |
| “Any format, ≤ 500 KB” generous cap | WebP | Headroom for higher dimensions at same KB |
One re-encode, not two
Every JPEG/WebP encode loses a generation. Converting a PNG screenshot to JPG then later compressing that JPG to 100 KB costs two losses. Do it once: choose the destination format and the KB cap together. UnderKB decodes once, resizes once (if needed), then encodes once to the format you chose — the byte count shown is the byte count the destination receives.
Do not convert a file that is already in the right format and under the cap. A 42 KB JPG that is already valid gains nothing from a trip through WebP and back — it only softens.
EXIF, GPS and camera serials are dropped during re-encode — useful privacy hygiene for any public upload.
Quality vs size: what to expect
| Source | To JPG q80 | To WebP q80 | To PNG |
|---|---|---|---|
| 600×800 portrait, camera JPG | ~90 KB | ~45 KB (half) | ~700 KB (not for photos) |
| 140×60 signature strokes | ~12 KB JPG | ~8 KB WebP | ~6–14 KB transparent PNG (correct) |
| Screenshot with text | ~180 KB JPG (fuzzy) | ~110 KB WebP | ~90 KB PNG (sharp) |
Frequently asked questions
Should I convert to WebP for a government portal?
No. Most Indian form validators check for JPEG MIME and reject WebP even under the cap. Choose JPG for every government photo field; use WebP only when the destination renders it (websites, Gmail, CMS).
Does converting twice hurt quality?
Yes — every JPEG/WebP encode is a generation loss. Choose the destination format and KB cap together and encode once. Re-encoding a 42 KB JPG that already fits only removes detail.
When is PNG the right choice?
For logos, screenshots, flat graphics and transparent signatures — anything with sharp edges or transparency. PNG photographs are huge and gain no visual quality; use JPG or WebP for photos.
Is EXIF stripped when I convert?
Yes. Decoding and re-encoding drops EXIF, GPS and camera serials — the file carries only pixels and colour profile, useful privacy hygiene for public uploads.
Is my file uploaded during convert?
No. Decoding, resizing and re-encoding all happen in this tab with Canvas/WebAssembly. You can disconnect the network after the page loads.