Ask Lemmy

Jpg is lossy and throws away information every time it is used, that’s why you get the “deep fried effect” when you re-encode something repeatedly. PNG is lossless so it’s a perfect replica of whatever image you encode with it. It does take up more space however.

JPEG is for real life photos and document scans, using it for anything else is just lossy compression.

whereas png is better for graphics type elements with defined colors and edges?

The reason for that is rather surprising, but PNGs are basically zipped BMPs with an optional filter step to arrange the pixels in a way that compresses better.

And that's why if you give it a photo with lots of details, it's not very effective and just gives you a rather big file. PNG barely does anything compared to JPEG and other formats. That's also why it's great for small things like icons: it decompresses fast and still manages a fairly good compression ratio when a good chunk of the image is transparent or flat background.

Jpg is better for photographs. Png is better when there are a lot of homogeneous pixels, like cartoons or rasterized vector graphics.

PNG is lossless and JPEG is not. JPEG is about a sliding scale of "quality" (at the cost of file size) and minimizing how much it fucks with the visual end result.

Jpg is really bad for anything with sharp lines, such as text. It also doesn't support alpha channel (transparency) which is reasonably important in modern web design.

PNG is loseless, which is great for... anything other than storage/bandwidth due to file size. There's even an animated PNG standard, similar to animated GIF, but you never see that used anywhere.

(I accidentally responded to the wrong comment before.)

Yes, that’s exactly right.

You're not wrong of course, but I really need people to understand that this level of detail is not what a top-level reply to a lower-end technical question is aiming for. Maybe this will be helpful to someone, but I already knew it and didn't need it sent to me, and it's going to go above OP's head. For the average end user, this is abstracted somewhere in the "host stuff" layer, and that's fine.

So sad that the poor management at Meta can't find the money to add webp support to one of the most used chatting apps in the world 🥺

Wanna hear something funny? So iirc webp is a Google format. The other day I was preparing slides for class with my friends. Anyway, we were on Google slides. I tried to upload this image, but it says it's unsupported. So i checked the format and whaddaya know? webp. So a Google service doesn't even support a Google file format. LOL

I've literally only run into 1 program that couldn't handle webp and that was a FOMOD creation tool for Bethesda game modding, and even then it worked but just tossed an unknown extension error

Though if you're using Facebook messenger that's probably the issue right there lol

I still hoping JpegXL will get some traction. The fact that it was removed from Chrome looks bad but they'll most likely add it again if it does. It's by far the best of all of them.