JPG to WebP Guide: Convert Photos and Compare Quality
Admin ·
JPG to WebP creates new WebP images from JPG or JPEG files in your browser. Select a few photos, choose quality and an optional size limit, convert, and compare the downloaded result with the original. You can also rotate, flip and package several results in one ZIP.
An ordinary JPEG photo usually already contains compression losses. A new format cannot reconstruct that discarded detail, and WebP is not guaranteed to be smaller. Keep the original photo while you decide whether the new file has suitable dimensions, appearance and size for its destination.
Convert a representative photo before a large batch
Choose images accepts files selected from your device; you can also drag them into the workspace. Begin with a photograph that includes fine detail, a smooth gradient and any small text you need to preserve. The initial quality is 90 and the maximum image side is 0, which keeps the decoded dimensions unless rotation swaps their order.
Choose Convert to WebP, then inspect the result card and download a sample. Check its actual byte size and view important details at their intended display size. A small thumbnail can hide artifacts that become obvious when a product image or photograph is enlarged.
- Keep your source JPEG until the exported WebP has been checked.
- Use a smaller maximum side when the destination does not need the full camera resolution.
- Compare the output itself; a quality number or filename extension is not a visual-quality guarantee.
Google WebP FAQ: quality, lossless conversion and larger results
Choose the format for the image you actually have
JPG and JPEG are common filename extensions for the same image format. Renaming a file to .webp does not change its contents; this tool decodes the source and encodes a new WebP. The usual web JPEG is lossy, but the wider JPEG standard also contains other coding modes. An accepted header does not guarantee that your browser can decode every uncommon variant.
Progressive JPEG loading describes how the JPEG is encoded and displayed. Conversion produces a new still WebP rather than retaining the original progressive JPEG scan structure. Choose your format around the receiving application and image content, not a rule that one extension is always best.
| Starting point | Useful decision | What conversion cannot do |
|---|---|---|
| Ordinary JPEG photograph | Try WebP and compare appearance and bytes | Recover detail discarded by earlier compression |
| PNG artwork with transparency | Use PNG to WebP if WebP suits the destination | Make this JPG-only route accept a PNG |
| A destination requiring JPEG | Keep an appropriate JPEG copy | Make an unsupported WebP upload acceptable |
JPEG committee: JPEG 1 overview and coding modesweb.dev: JPEG compression and progressive imagesweb.dev: WebP image encoding
Treat quality as an encoder choice, not retained detail
The quality control ranges from 10 to 100 and is passed to the browser encoder. Lower values often trade detail for fewer bytes, but neither the visual change nor the saving is fixed. The new value cannot be compared directly with the unknown setting that produced the original JPEG.
There is no explicit lossless-mode selector. A browser can choose different encoding behavior at different quality settings; 100 is not a portable promise of an unchanged image. Decoding, color handling, resizing and any earlier JPEG losses still matter. Even lossless encoding of decoded pixels cannot recover information absent from the JPEG.
| Choice | What to examine | Avoid assuming |
|---|---|---|
| Start at 90 | Compare fine detail, gradients and file size | That 90 means 90 percent of the original detail |
| Try a lower value | Look for blocking, softness or ringing at useful size | That every ten-point reduction saves a fixed percentage |
| Try 100 when useful | Compare bytes and appearance again | That the output is always smaller or guaranteed pixel-identical |
Google WebP FAQ: quality, lossless conversion and larger resultsMDN: OffscreenCanvas.convertToBlob and quality settingsweb.dev: JPEG compression and progressive images
A larger WebP is still a possible result
The converter exports WebP even when that new file is larger than the JPEG. This differs from the separate image compressor’s conditional keep-original behavior. The result card compares the source and output sizes so that you can decide whether to keep the conversion.
For example, converting an already compact JPEG with a very high-quality browser setting may produce a larger WebP. More bytes do not reconstruct the source detail that was lost earlier. Compare alternative quality and dimension choices, or keep the original when the new format offers no useful benefit.
Google WebP FAQ: quality, lossless conversion and larger resultsweb.dev: WebP image encoding
Check recorded orientation before adding your own rotation
The browser decodes with image orientation taken from the file. A camera photo may therefore appear upright even when its stored width and height describe the sideways pixel array. The tool then applies the selected clockwise quarter turn and flips; these controls operate on that decoded image.
A flip is applied along the output axes after the selected rotation. For example, a 90-degree turn followed by a horizontal flip is different from a horizontal flip followed by that turn. Check signs, faces and text in the preview, especially when the source already has an orientation tag. Applying orientation to pixels is separate from preserving that tag in the output.
Reduce dimensions proportionally without enlarging
The maximum-side control accepts 0 to keep dimensions, or a positive whole number no greater than 12000. A smaller maximum reduces both sides proportionally after rotation. It does not crop to a fixed rectangle, and a maximum larger than the image does not enlarge it.
Pixel dimensions and display dimensions are different. A photograph intended for a small card may not need its full camera resolution, but the original still has to pass the source limits before resizing begins. Keep a larger source copy when future uses may require more detail.
| Decoded source and rotation | Maximum side | Output dimensions |
|---|---|---|
| 4000 × 3000, no rotation | 0 | 4000 × 3000 |
| 4000 × 3000, no rotation | 1200 | 1200 × 900 |
| 4000 × 3000, 90 degrees | 1200 | 900 × 1200 |
| 600 × 400, 90 degrees | 1200 | 400 × 600; no enlargement |
Conversion does not remove a JPEG background
A JPEG photo has no alpha channel. Its white backdrop, sky or other background consists of ordinary image pixels. Saving those pixels in a format that supports transparency does not separate a subject or create transparent holes.
The shared JPG background control has no effect on this fixed WebP output. It is used when the target format is JPG in other image workflows. If you already have a transparent PNG, use the matching PNG converter; creating a cutout from a photograph requires a separate editing step.
MDN: JPEG image format and transparency supportweb.dev: WebP image encoding
Keep originals when metadata or color fidelity matters
This route draws decoded image pixels onto a canvas and encodes a new WebP. It does not copy the original JPEG EXIF, comments or embedded profile bytes. A browser may generate its own output profile data, so original-metadata omission does not mean that every output is completely free of all metadata.
Browser decoding and color conversion can affect appearance. Do not treat this as an archival color-management workflow or a way to preserve every camera tag. Compare skin tones and saturated colors in the destination application, and keep the original when provenance, precise color or metadata is important.
MDN: createImageBitmap orientation and color conversionMDN: OffscreenCanvas.convertToBlob and quality settings
Check the source limits before requesting a smaller output
File limits use decimal bytes: 25 MB here means 25,000,000 bytes. Pixel area and either-edge limits both apply to each source before resizing, and the decoded bitmap is checked again. A 6000 × 4000 source reaches the 24,000,000-pixel ceiling; 6001 × 4000 exceeds it even if the requested output is small.
The total input allowance and total encoded-image allowance are separate. A job can pass one and fail the other. ZIP container overhead is additional to the encoded image payloads. The worker also has a 60-second job deadline; selecting fewer or smaller accepted sources can help when a device struggles.
| Check | Allowance | Practical consequence |
|---|---|---|
| Files in one job | 1–20 | Add fewer files when the queue is full |
| Each source file | 25,000,000 bytes | Re-export an oversized source before selecting it |
| Each source image | 24,000,000 pixels and 12000 per side | Both bounds apply before requested resizing |
| All source files combined | 100,000,000 bytes | Split a large selection into smaller jobs |
| All encoded images combined | 100,000,000 bytes | Reduce dimensions, quality or batch size |
| Maximum-side choice | 0, or a whole number from 1 to 12000 | 0 retains dimensions; positive values do not enlarge |
| Conversion job | 60 seconds | A busy or limited device may need a smaller job |
Set the queue order and download the results
Add files up to the queue limit, move individual entries, sort by filename or reverse the order. Filename sorting uses the active language and numeric ordering, so numbered names are handled as names rather than plain character strings. Removing a file or changing the order clears previous results; convert the current queue again.
Output names use the current queue position, a sanitized source stem and the .webp extension, such as 01-photo.webp. Download individual files or use the ZIP button for several results. The ZIP stores the already encoded images without converting them again, but it adds container overhead. A displayed result is not an automatic save to your chosen folder.
Recover from rejected files without trusting the extension
The source must contain JPEG data that passes the header checks and can be decoded by the browser. A PNG renamed .jpg can still produce a generic preview but will fail this strict conversion route. If one file fails, the batch exposes no partial download set; remove or replace the offending input and run the remaining selection again.
The JPEG dimension scan examines only the first 1,048,576 bytes. Unusually large metadata before the dimension marker can cause a safe rejection even when the complete JPEG is otherwise decodable. Re-export a fresh ordinary JPEG from a trusted image application when dimensions cannot be read safely or an uncommon variant fails. If the browser cannot encode WebP, this route rejects the result instead of returning a mislabeled file; use a supported browser or a different conversion workflow.
JPEG committee: JPEG 1 overview and coding modesMDN: createImageBitmap orientation and color conversionMDN: OffscreenCanvas.convertToBlob and quality settings
Cancel, adjust and retry with the current settings
Cancel stops the conversion worker and retains the selected inputs for another attempt. The conversion is sequential, and a failure or cancellation does not deliver an unfinished set of results. Changing an option clears old results so they cannot be mistaken for the next conversion.
Clear files removes the queue but retains global choices such as quality, maximum side, rotation, flips and background. Check those choices before starting a different set of photographs. Invalid maximum-side values, unreadable inputs and oversized batches need an input or setting correction before retrying.
Separate local conversion from website delivery
The selected image bytes are processed on your device in a browser worker. ZIP packaging is also local, on the main browser thread. Opening the site still involves page and asset requests, and site analytics may make requests; local image processing is not a promise of zero network activity or permanent offline availability.
A downloaded WebP does not replace a photo on a website or update its responsive images automatically. Upload or install the chosen asset through your own publishing workflow, then check its appearance, dimensions and compatibility where visitors will see it. Related-tool handoff within the tab is temporary and should not replace downloading files you need to retain.
web.dev: WebP image encodingMDN: OffscreenCanvas.convertToBlob and quality settings
Common questions
How do I convert a JPG or JPEG photo to WebP?
Choose the source images, start with quality 90 and maximum side 0 if you want to retain dimensions, then choose Convert to WebP. Compare a downloaded sample before processing a larger batch.
Are JPG and JPEG different input formats here?
They are filename extensions for the same format. Both are offered by the picker, but the file must actually contain a JPEG that passes the header and browser decoder checks.
Will my WebP always be smaller?
No. Content, dimensions, the existing JPEG and browser encoding choices all affect the result. The tool exports WebP even when it is larger; compare the actual sizes before keeping it.
Can conversion repair JPEG compression damage?
No. Re-encoding cannot reconstruct detail already discarded by a previous lossy JPEG save. A high-quality setting can help avoid additional visible damage, but it cannot restore missing information.
Does quality 100 guarantee a lossless result?
No portable guarantee is provided. The browser receives a quality setting and chooses its encoding behavior; there is no explicit lossless selector. Earlier JPEG losses, decoding, color conversion and resizing still matter.
Will the photo retain its EXIF orientation?
The decoder requests orientation from the image, so the displayed pixels can be upright before your selected rotation or flips. The original EXIF tags are not copied into the WebP by this tool.
Can I keep camera metadata or an original color profile?
This workflow does not copy those original JPEG records. Browser color handling and newly generated output profiles may affect the result. Keep the original when metadata or precise color is important.
Can I remove the background or make a JPEG transparent?
No. A JPEG has no alpha channel, and conversion does not cut out a subject. Its background remains ordinary image pixels; the JPG background control does not change this WebP output.
Why did a file with a preview fail conversion?
The preview supports more image formats than the JPG-only conversion route. Wrong content, unreadable data, uncommon JPEG coding or a dimension marker beyond the bounded header scan can still cause rejection.
Does selecting a small maximum side bypass the source limits?
No. Per-file bytes, original dimensions and pixel area are checked before resizing. Reduce an oversized source in another suitable workflow first, then select the smaller JPEG.
How do I download several results, and are my photos uploaded?
Conversion and ZIP creation run locally in your browser; this workflow does not upload the selected photo bytes. Download the individual WebP files or the ZIP of completed results. Loading the site can still generate ordinary network requests.
What stays after I cancel or clear the files?
Cancel stops the job and keeps selected inputs. Clear files removes the queue while retaining global settings. Neither action saves a result automatically; download files you need before leaving or changing the job.
Sources and further reading
- Google WebP FAQ: quality, lossless conversion and larger results
- JPEG committee: JPEG 1 overview and coding modes
- web.dev: JPEG compression and progressive images
- web.dev: WebP image encoding
- MDN: createImageBitmap orientation and color conversion
- MDN: OffscreenCanvas.convertToBlob and quality settings
- MDN: JPEG image format and transparency support