I second that, a filter for the suffix would be great! i used a plugin that created myimage.jpg -> myimage.jpg.webp and i'm serving those images via url rewrite. So to be able to keep serving my existing images and create new ones with the performance lab plugin it would be handy to be able to to change the suffix of the generated files!

Thx paul

Thanks, Paul, for the comment.

Some background for the image extension. Plugin added the original image's extension to the WebP file name for its uniqueness in #444, for two or more images share the same file name but different mime types.

If you are aware of the rise of the same file name with different mime types issue, the filter is a good option for removing file name extensions.

Filter that adds an extension to the image name. The default value for this filter is true, so it doesn't affect the current behavior of the plugin.

/**
 * Filters whether image extensions are allowed for image names.
 *
 * By default the performance lab plugin will use the image extension for uniqueness 
 * purposes for the additional mime type image name.
 *
 * @since n.e.x.t
 *
 * @param bool $allowed_image_extension Add the image extension to the file name. Default true.
 */
$allowed_image_extension = apply_filters( 'webp_uploads_image_name_with_extention', true );

@felixarntz and @adamsilverstein, I would be interested to hear your thoughts on this?

Please review and suggest wording if I missed anything.

I'm open to the idea of introducing some developer control here, however we may want something broader to control naming overall.

We may want to hold and revisit this once we consider adjusting the approach in the plugin to match where we wound up in core.

How about selections between: filename.jpg to filename.jpg.webp or filename.webp
I need option: filename.jpg.webp.

@PaulSchiretz

I second that, a filter for the suffix would be great! i used a plugin that created myimage.jpg -> myimage.jpg.webp and i'm serving those images via url rewrite. So to be able to keep serving my existing images and create new ones with the performance lab plugin it would be handy to be able to to change the suffix of the generated files!

Thx paul

@kenny-nt

How about selections between: filename.jpg to filename.jpg.webp or filename.webp I need option: filename.jpg.webp.

That would be compatible with redirection convention used on most hosting providers, even WordOps is using it by default.

Current renaming convention is pure nonsense. I guess, someone was mislead or inspired with -cropped and -rotated suffix, but that was appropriate because it is for completely different purpose.

Anyways, I wonder what else could be purpose of WebP upload module keeping jpeg thumbnails than enabling redirection for WebP enabled/disabled browsers? Same convention should be implemented for original.jpg

@adamsilverstein

I'm open to the idea of introducing some developer control here, however we may want something broader to control naming overall.

We may want to hold and revisit this once we consider adjusting the approach in the plugin to match where we wound up in core.

Upload name is always checked for duplicate names and renamed. Thumbnails names just follow original / renamed file. That works without problems for decades. Same will work for .jpeg.webp because it will never be duplicate of original-name.jpeg. Even when .jpeg thumbnails are not generated (skipped).

@adamsilverstein

We may want to hold and revisit this once we consider adjusting the approach in the plugin to match where we wound up in core.

This "thing" should never "wound up in core". Image Editor Class is already capable of generating both media/types (when library supports), and is already capable to regenerate images. Which is not the case with WebP - upload module that does it's "thing" only on upload. All you have to do is to handle name and use _save method twice. That would enable generating and regenerating older images for JPEG and PNG formats.

Which is not the case with WebP - upload module that does it's "thing" only on upload.

@ddur are you sure about that? WebPs should be generated when regenerating images as well as at upload.