Drupal Developer Needed – Image Styles Causing High Disk Usage

We are looking for an experienced Drupal developer to investigate and fix excessive disk usage caused by generated image derivatives.

Our `sites/default/files/styles` directory contains **20,000+ images** and keeps growing. The website uses Drupal Feeds, Image Styles, ImageAPI Optimize/WebP, Drush queues, and cron jobs.

Tasks:
- Identify why so many image derivatives are continuously generated.
- Review Drupal Image Styles and remove/optimize unnecessary styles.
- Review Feeds/import processes and image processing.
- Check ImageAPI Optimize/WebP configuration.
- Safely clean up unnecessary existing derivatives.
- Implement an automatic cleanup/retention solution.
- Review relevant cron/Drush queue jobs.
- Prevent disk usage from continuously increasing.

Important:
We do not want a cron job that blindly deletes the entire `styles` directory. The solution must be Drupal-aware and must not cause broken images or unnecessary regeneration.

Please explain your proposed approach and provide examples of similar Drupal performance/storage issues you have solved.



WHAT WE DISCOVERED UNTILL NOW:
We also traced the image_api_optimize_* files to the Drupal ImageAPI Optimize module. Its configuration confirms that the module is enabled and that the wimage pipeline uses the WebP processor at quality 70:

status: true
name: wimage
label: Wimage

processors:
id: webp_webp
data:
quality: 70

The Drupal configuration also shows that the news_feed_image style uses this image optimization pipeline:

config/sync/image.style.news_feed_image.yml:
pipeline: wimage