Most likely you understand my point, and we don't necessarily need to argue about it more if you don't want to.
To transition into something more positive... I wrote a PowerShell script that people can use to convert images.
I chose PowerShell because I'm assuming that most of you are using Windows and while I would prefer python myself, installing python and the needed dependencies is maybe a bit hard for some.
Basically save this to a file and name it "script.ps1"
param (
[Parameter(Mandatory=$true, Position=0)]
[ValidateScript({Test-Path $_ -PathType 'Container'})]
[string]$InputDirectory,
[Parameter(Mandatory=$true, Position=1)]
[string]$OutputDirectory
)
New-Item -ItemType Directory -Force -Path $OutputDirectory | Out-Null
$webpFiles = Get-ChildItem -Path $InputDirectory -Filter "*.webp" -File
foreach ($webpFile in $webpFiles) {
$outputPath = Join-Path -Path $OutputDirectory -ChildPath ($webpFile.BaseName + ".png")
$webpImage = [System.Drawing.Image]::FromFile($webpFile.FullName)
$webpImage.Save($outputPath, [System.Drawing.Imaging.ImageFormat]::Png)
Write-Host "Converted $($webpFile.Name) to PNG."
}
Write-Host "Conversion completed."
Then the way you use this is like this, from command line
.\script.ps1 -InputDirectory "C:\path\to\input\directory" -OutputDirectory "c:\path\to\output\directory"
If anyone needs help with using this, I would be happy to help you and you will never have to deal with webp again :P
It's also true that this could probably be improved in a lot of ways, but I figured this is a good starting point for someone who wants to solve problems like this with scripts.