How to use
- Open bars-32x16.jpg.
- Write WebP at quality 80, then at 60.
- Do not expect a transparent pixel to appear.
Formula / how it works
bars-32x16.jpg becomes a 32 by 16 WebP. Quality 80 and quality 60 both keep the grid. The flat bars barely change size between those settings. A noisy photograph will. JPEG had no alpha, so the WebP will not grow a transparent pixel. The encoder is the browser. A browser that cannot write WebP stops.
This is the path when a page wants WebP and you only have JPEG. It is not a restoration of detail the JPEG already discarded. Decode, then encode. Two generations, the second of them WebP.
Use WebP to PNG when you need a lossless container after this. Use the image compressor when you also need a max width.
bars-32x16.jpg becomes a 32 by 16 WebP. Quality 80 and quality 60 keep that grid. The flat bars may not shrink between those settings. A noisy photograph will, and the size line is how you tell. No transparent pixel appears, because the JPEG had none. The browser encodes the WebP. A missing encoder stops the page. Detail the JPEG already lost stays lost. This is a second encode, not a restoration.
The WebP is 32 by 16 because the JPEG was 32 by 16. Quality changes the weights, not the grid, on this page. Flat bars hide that. A street photograph will not. No hole becomes transparent. If you need a hole, you needed a PNG source on the PNG to WebP page, not a JPEG. The encoder is the browser you are sitting in, which is also why a very old browser is told to stop.
The JPEG bars become a 32 by 16 WebP. Quality changes the encode, not the grid. Flat red and blue may not shrink. A noisy photo will, and the size line is the only honest report. No transparent pixel is created. The browser does the encode. An old browser that cannot write WebP is told to stop. Detail the JPEG already lost is still lost. This is not a repair.
Keep the JPEG. The WebP is a second generation at 32 by 16, not a replacement that recovered anything. If the WebP is larger than the JPEG on a photograph, the quality was too high or the JPEG was already small. The size line will say which. Flat bars are a bad teacher for that lesson. A street photo is a better one. The bars WebP is 32 by 16, same as the JPEG, and that match is the check for this icon. Quality did not change the grid. It would change a photograph. Read that line before you delete the JPEG. The bars check is the 32 by 16 grid, not a claim that every WebP is smaller. Delete the JPEG only after the WebP opens and the size line is the one you wanted. The bars file is 32 by 16 in both containers. A street photograph is the file that can disappoint you on size, not these flat bars.
A PNG container after this is WebP to PNG. Scaling as well is image compressor.
Worked examples
JPEG bars at WebP quality 80
Inputs: j2w-f: bars-32x16.jpg | j2w-q: 80
On this page, take bars-32x16.jpg, then 80 and press Convert. JPEG had no alpha, so the WebP will not grow one.
Result: JPG to WEBP: 32×16. 0.6 KB
JPEG bars at WebP quality 60
Inputs: j2w-f: bars-32x16.jpg | j2w-q: 60
On this page, take bars-32x16.jpg, then 60 and press Convert. JPEG had no alpha, so the WebP will not grow one.
Result: JPG to WEBP: 32×16. 0.6 KB
Use cases
- Feeding a WebP-only slot from a JPEG.
- Keeping the 32 by 16 grid.
- Accepting that JPEG detail already lost stays lost.
- Stopping if the browser cannot encode WebP.
Tips & limitations
- Flat bars may not shrink between 80 and 60.
- A photograph will.
- No alpha is created.
- The size line is the check.
FAQ
What size is the WebP?
32 by 16, the same grid as bars-32x16.jpg.
Does WebP restore JPEG detail?
No. The browser decodes the JPEG and encodes WebP.
Can the WebP be transparent?
Not from this JPEG. There was no alpha channel.
Who encodes it?
The browser. A missing encoder stops the page.
Will quality 60 always be smaller?
Not on these flat bars. Read the size line on a photograph.
Is the JPEG uploaded?
No.
32 by 16 is bars-32x16.jpg written as WebP. A camera JPEG will not match this icon’s size.