ResponsiveImageGenerator->generateResponsiveImage add media_library_original file to responsive-images folder

[kosee73]

Hi everyone,
I have a problem when I regenerate the image from the media library.
In addition to the regenerated responsive files in the "responsive-images" folder, other files are added that have the name "media_library_original".
and this significantly increases the size of folders.

The method that generates the files, generateResponsiveImages(), is in the class:
Spatie\MediaLibrary\ResponsiveImages\ResponsiveImageGenerator

How can you fix it? Can anyone help me?

thanks

[kosee73]

[monster010]

Hi Spatie team,

I would like to suggest improving the internal logic that adds the media_library_original part to responsive image filenames. This suffix seems unnecessary, as the image size is already clearly indicated by the dimensions in the filename.

Current behavior:

• Example filename: image___media_library_original_400_300.jpg
• The media_library_original suffix is added for responsive images generated from the original.

Proposed behavior:

• Example filename: image-400x300.jpg
• The media_library_original suffix is removed, as the dimensions already uniquely identify the image variant.

Current workaround:

You can bind a custom generator via the service container:

$this->app->bind(
    \Spatie\MediaLibrary\ResponsiveImages\ResponsiveImageGenerator::class,
    \App\MediaLibrary\CustomResponsiveImageGenerator::class
);

This allows removing the suffix from the filenames.
However, the media_library_original variable is used in multiple places internally, which makes this workaround somewhat cumbersome.

Proposed clean solution:

• The library could provide a configuration option (e.g., in config/medialibrary.php) that defines the suffix for responsive images generated from the original.
• The default could remain media_library_original, but users could disable or customize the suffix.

Rationale:

• Clarity: The image dimensions already uniquely identify the file.
• Consistency: A uniform naming scheme for all variants simplifies handling.
• Maintainability: Less redundant information makes the system easier to maintain and extend.
• Flexibility: Through a config option, each user can decide whether to include the suffix.

I look forward to your feedback and am happy to discuss further.

Thank you for your work on this excellent package!