A malformed (attacker crafted) webp file could cause Chrome (or other Chrome based browsers) to execute arbitrary code when rendering it. The file might be embedded in a web page you view. Other applications that use Skia for graphics are theoretically affected too.
SVG is for vector graphics, i.e. anything that can be described with lines and shapes, like logos or most icons.
WebP on the other hand is for raster graphics. For example, cameras create raster graphics.
So, while SVG may be able to replace WebP for some use-cases, it makes no sense to generally switch to SVG.
A suitable, better replacement for WebP is JPEG XL.
JPEG XL is just a new standard from the Joint Photographic Experts Group. It doesn’t have much to do with the original JPEG standard from 1992. For example, JPEG XL also supports lossless compression, which PNG was traditionally used for.
And yes, WebP was developed to supersede JPEG, however it was developed at Google without much input from the industry. As such, it never gained particularly widespread support.
JPEG XL is a newer standard compared to WebP, developed in a joint venture by more of the industry (including Google), and from what I’ve heard, it makes several significant improvements compared to WebP.
It is a very new standard, so it probably is still behind WebP in terms of adoption, but I’d expect that to flip pretty soon.
Personal opinion: I just think WebP is poop.
You can have images with huge resolutions that still look incredibly blurry.
Honestly, I have no idea. It sounds like AVIF also has wide industry support and is generally quite proficient.
But JPEG XL likely wouldn’t have been created, if AVIF was perfect. Wikipedia says:
The [JPEG XL] standard is expected to outperform the still image compression performance shown by HEIC, AVIF, WebP, and JPEG 2000. It also provides efficient lossless recompression options for images in the traditional/legacy JPEG format.
I’m guessing, AVIF was created, because it basically already existed. It’s using the AV1 video codec to encode a single-frame video and that just happened to be better than the competition.
JPEG XL being more focused on those still images could obviously still outperform it. I guess, we’ll have to see.
For right now, though, yeah, JPEG XL might still be too young and AVIF therefore the better choice.
A malformed (attacker crafted) webp file could cause Chrome (or other Chrome based browsers) to execute arbitrary code when rendering it. The file might be embedded in a web page you view. Other applications that use Skia for graphics are theoretically affected too.
The internet needs to switch to .svg
SVG is for vector graphics, i.e. anything that can be described with lines and shapes, like logos or most icons.
WebP on the other hand is for raster graphics. For example, cameras create raster graphics.
So, while SVG may be able to replace WebP for some use-cases, it makes no sense to generally switch to SVG.
A suitable, better replacement for WebP is JPEG XL.
What does jpeg XL differ from normal jpeg? Wansn’t webp introduced to replace jpeg?
JPEG XL is just a new standard from the Joint Photographic Experts Group. It doesn’t have much to do with the original JPEG standard from 1992. For example, JPEG XL also supports lossless compression, which PNG was traditionally used for.
And yes, WebP was developed to supersede JPEG, however it was developed at Google without much input from the industry. As such, it never gained particularly widespread support.
JPEG XL is a newer standard compared to WebP, developed in a joint venture by more of the industry (including Google), and from what I’ve heard, it makes several significant improvements compared to WebP.
It is a very new standard, so it probably is still behind WebP in terms of adoption, but I’d expect that to flip pretty soon.
Personal opinion: I just think WebP is poop.
You can have images with huge resolutions that still look incredibly blurry.
What’s better? Avif or jepg xl?
Honestly, I have no idea. It sounds like AVIF also has wide industry support and is generally quite proficient.
But JPEG XL likely wouldn’t have been created, if AVIF was perfect. Wikipedia says:
I’m guessing, AVIF was created, because it basically already existed. It’s using the AV1 video codec to encode a single-frame video and that just happened to be better than the competition.
JPEG XL being more focused on those still images could obviously still outperform it. I guess, we’ll have to see.
For right now, though, yeah, JPEG XL might still be too young and AVIF therefore the better choice.