Translation: your video editor sucks.

There's a difference between whether or not a file format supports features and a software supporting the file format. A tractor can have loads of features and still not be the right fit for you if it does fit in your barn. Doesn't mean the tractor doesn't have those features. DDR5 can be better then DDR4 and yet not all motherboards support it. It is trivial to convert from webp to the file format you need for your unique situation. Its supported baseline by browsers and use on the web is its best case. I make websites that allow people to customize SOLIDWORKS CAD files. SOLIDWORKS doesn't support webp: I still use it on the website wherever possible and if someone uploads in webp I just convert to jpg before inserting into SOLIDWORKS.

and how many images are above 16k x 16k pixels?

If you have an optimisation for 99% of all online images, then that's dope - You can use more niche or older compressions for your very high pixel files

At these resolutions, I'd rather use OpenEXR or TIFF, because it's very likely something beyond usual photography or casual internet pictures, such as astronomical/medical imagery or 3D scene imagery/textures, both of which benefit from multichannel and full precision multilayer capabilities due to being likely a composition of different wavelengths for the first or different aspects/passes for a 3D scene (diffuse light, roughness, emissive light, etc).

memes@lemmy.world

I weep for the web server that has to serve those size images. I can typically cut webserver bandwidth in half by converting all non svg images to webp. Have had one project where this cut the network fee by 80% and allowed us to downgrade the rented server space.