TL;DR: WebP exports are now properly sized and honor your quality settings. PNG exports got a small efficiency bump for opaque images. Installer SHA-256 hashes are now published on the docs page so you can verify every download.

🐛 What’s fixed

WebP export file sizes are now correct. On opaque photos, WebP output is now in the expected 200–400 KB range at quality 82, instead of the multi-megabyte files some of you saw.

WebP quality slider now applies. The quality control on the sidebar now affects the actual encode — previous builds produced lossless output regardless of where you set the slider.

PNG export is smaller for opaque images. When the source image has no transparency, the alpha channel is stripped from PNG output. Modest size reduction, no visible difference.

🔧 Under the hood

The export pipeline was audited end-to-end. JPEG and AVIF paths were already correct and didn’t need changes. The WebP fix was isolated to a single encode function — no changes to your settings, presets, or conversion history. Existing Pro licenses continue to work normally.

🔒 Installer verification

SHA-256 hashes for both the .exe and .msi installers are now published on the documentation page, in the new Installer Verification section. If you want to confirm the file you downloaded matches what we published, you can now verify it in one PowerShell command:

Get-FileHash ImageSmasher_1.0.1_x64-setup.exe

The output should match the hash on the docs page exactly. This stays in place until Microsoft Trusted Signing is fully set up on our end, after which the SmartScreen warning will also go away.

📥 How to update

Download the new installer from the Download page and run it over your existing installation. Your settings, license, and conversion history are preserved.

Pro users: No need to reactivate. Your license carries over automatically.

🛣️ What’s next

A few things on the roadmap worth calling out:

• Code signing via Microsoft Trusted Signing — eliminates the SmartScreen warning on first install. Setup is in progress; we’ll announce here when it’s live.
• More batch-processing presets — a few of you have asked for additional out-of-the-box presets for common workflows. On the list.
• Continued format-specific polish — the audit flagged a few small efficiency improvements worth picking up in future releases. None affect output correctness, just file-size optimization on edge cases.

💬 Found something?

If you notice anything weird after updating — unexpected file sizes, conversion failures, anything that doesn’t match what you saw in 1.0.0 — please reply to this thread or open a new one in the bug reports section. Include:

• Input image format and approximate dimensions
• Output format and preset used
• What you expected vs. what happened

That level of detail helps us reproduce and fix things quickly.

Thanks to everyone who’s reported issues, asked questions, or just stuck with us through the early releases. The feedback is what drives this work. — LXB Studio

`