maddog107

Damn you good, I should hire you The issue was due to chunked uploads, so even though you are allowed to upload 256mb, nginx and IPB chunk the upload size into multiple little parts if its over 10mb and that path wasnt being used to convert to webp.

test123

test

test123

test

it should work just fine. Something like ffmpeg -i input.gif -c:v libwebp -loop 0 -q:v 82 output.webp Key flags: - -c:v libwebp — uses the libwebp encoder (supports animation) - -loop 0 — loop forever (like the original GIF) - -q:v — quality (0-100) That is what we are using for the conversion. You should just update your tools to the latest and everythign should work normally except it woudl now support webp.

That is even stranger, linux made for webp? What distribution are you using? Our server is RHEL based, but I have a ubuntu laptop. Can you be more specific on what exactly do you normally do? Like what is the workflow? What app(s) are you using that doesnt open webp? https://developers.google.com/speed/webp/download

Just tried a 32mb image. Looks like it worked ok, i still think its most likely the timing of the post. If you retry today, let me know if you see any issues and ill investigate furthur.

Huge test. 32mb.

You can try https://storage.googleapis.com/downloads.webmproject.org/releases/webp/WebpCodecSetup.exe on windows 8. According too the internet that should enable webp support in your filesystem on older windows machines.

Most likely during the whole machine rebooting a million times and packages missing. I will go through and manually fix those up at a later time.

Instagram switched to webp in 2021. We are 5 years behind the "major" players. Support is not an issue at all. https://caniuse.com/webp All green except for IE11 which if you are still using, im sure 99% of the websites out there dont even render correctly anymore. Compressions settings are equivalent to jpeg, I can adjust them up and down as needed, if you can show me a case where the webp is worse than the jpeg ill adjust my compression settings sitewide. Here is a summary of our findings during 2026 that shows that even on small images there is signifcant savings with imperceivable image loss: 2026 Q1 (Jan-Mar) — 440,646 modern photos, 133.7 GB → 60.3 GB (55% saved) - Thumbnails (< 50 KB): 247K files, 19 KB → 11 KB avg, 42% saved - Small (50-100 KB): 18K files, 76 KB → 30 KB avg, 61% saved - Medium (100-200 KB): 38K files, 149 KB → 72 KB avg, 52% saved - Large (200-500 KB): 72K files, 326 KB → 169 KB avg, 48% saved - XL (500 KB - 1 MB): 36K files, 703 KB → 366 KB avg, 48% saved - XXL (> 1 MB): 30K files, 2.7 MB → 1.1 MB avg, 60% saved Only 659 out of 440K files (0.15%) were skipped because WebP was larger. Every size bucket benefits.

What OS are you using? I assume you can simply use: https://apps.microsoft.com/detail/9pg2dk419drg?hl=en-US&gl=US If you dont alreayd have it installed. Windows should have native webp support since windows 10+. You can right click and say open with "photos" or whatever you normally use to view jpegs and it should work just the same.

Yes, our bandwidth bill is thousands a month, we have enabled some flags on our CDN provider to serve WEBP like the rest of the modern web.

ImageMagick got uninstalled during the upgrade so it was using gd which cant handle many images. Should work now. Keep the bug reports coming! thanks.