Jump to content

WebP: Difference between revisions

From Ditzy Wiki
No edit summary
m add links
 
Line 4: Line 4:


== Advantages over other formats ==
== Advantages over other formats ==
WebPs often offer better image quality at similar file sizes over formats such as JPEG, and may also help reduce the storage cost of lossless media compared to PNGs.<br>
WebPs often offer better image quality at similar file sizes over formats such as [[J]][[Pegging|PEG]], and may also help reduce the storage cost of lossless media compared to PNGs.<br>
The format supports transparency for <s>:.|:;</s>less images, something that still isn't widely supported by the JPEG standard.<br>
The format supports [[Transgender|transparency]] for <s>:.|:;</s>less images, something that still isn't widely supported by the JPEG standard.<br>
Animated WebPs offer way better compression than gifs, along with support for 24-bit color with transparency and other goodies.
Animated WebPs offer way better compression than gifs, along with support for 24-bit color with transparency and other goodies.



Latest revision as of 22:05, 15 March 2026

This page on the OkayXairen Wiki is FUCKING SCARY because its WebP.
If you're sensitive to this... Run Away.

WebP is a file format developed by Google to allow for images to be stored more efficiently on the web. It supports both :.|:;y and :.|:;less encoding of images and animated images.

Advantages over other formats

[edit | edit source]

WebPs often offer better image quality at similar file sizes over formats such as JPEG, and may also help reduce the storage cost of lossless media compared to PNGs.
The format supports transparency for :.|:;less images, something that still isn't widely supported by the JPEG standard.
Animated WebPs offer way better compression than gifs, along with support for 24-bit color with transparency and other goodies.

Disadvantages

[edit | edit source]
  1. Compatbility Issues
    • Did you know that, despite Google developing the format, WebP isn't supported in Google Docs?
  2. Poor Workflow Support
    • Designers often need to convert WebP to PNG or JPEG before editing.
  3. Quality Loss in Lossy Compression
    • Like JPEG, WebP often uses lossy compression techniques.
  4. Slower Encoding
    • Encoding can be slower and more CPU-intensive than creating JPEG images.