Batch image preparation for WordPress
Drop in a hundred photos if you like — the tool will shrink them to the size you need, convert them to WebP and rename Cyrillic names into Latin script. The files never leave your computer: all processing happens in the browser.
Nothing has been processed yet. Drop the images into the area above — everything else is computed in this tab, without a single network request.
The images never leave your browser: decoding, resizing, re-encoding and even building the ZIP happen in the tab. Open DevTools → Network and see for yourself — not a single request.
Why images should be prepared before upload, not after
Optimisation plugins only start working after the file has reached the server. Until then it takes up space in the backups, and WordPress has already cut half a dozen intermediate sizes out of it — and each of those has to be stored somewhere too. A 4 MB photo from a phone turns into 5–8 files. The second reason is control. You see the result before uploading and can pick the quality by eye instead of trusting a plugin's preset. The third is file names. A Cyrillic name turns into a long percent-encoded string that breaks when the link is copied and looks unreadable in the media library. And the fourth, which people rarely think about: metadata. A phone photo contains EXIF with the exact GPS coordinates of where it was taken. Publishing it as is means publishing the coordinates too. Redrawing through canvas does not carry metadata over — so the cleanup happens automatically. As for width: most themes show images in a container of up to 1200 pixels. There is no point in uploading a 4000-pixel photo — the browser will scale it down anyway, having spent the user's bandwidth.