image-optimizer

You can convert large PNG and JPG images to WebP by scanning your project directory and batch converting qualifying static assets, which reduces storage and build size for front-end repositories.

Yes, you can run a scan-only mode to find large static images while skipping heavy directories like node_modules, allowing you to review qualifying files before performing any WebP conversion.

The best way to optimize Next.js static assets is to scan for oversized screenshots and convert them to WebP using a configurable minimum size threshold and quality level to reduce payload size before deployment.

Yes, Pillow supports batch processing for WebP conversion in Python by scanning specified directories for large image files and applying a configurable quality level to report before and after size savings.

You can configure minimum file size and quality for batch image optimization by setting a path, minimum size threshold, and WebP quality level, while excluding common directories and reporting detailed savings per file.

Your front-end bundle size increases after adding screenshots because oversized static image files slow down builds and hurt page load performance, which can be resolved by converting large PNG and JPG assets to WebP.