johnghiz

Hello,

Currently, the ‘-scaled’ suffix cannot be removed from uploaded image titles.

The ‘-scaled’ suffix was introduced in WordPress 5.3 as part of the ‘Big Image Threshold’ mechanism. When an uploaded image exceeds a certain size (defaulting to 2560px), WordPress automatically generates a version optimized for web display and treats it as the ‘Full’ size image.

Currently, the ‘Max Dimensions’ feature in CompressX generates a resized version of the primary image and appends the ‘-scaled’ suffix, consistent with WordPress core behavior. This approach preserves the original high-resolution image, prevents overwriting, and avoids potential caching or compatibility issues. We do not currently offer an option to remove the ‘-scaled’ tag, as doing so would risk overwriting original files or causing caching conflicts.

When ‘Max dimensions’ is enabled and an uploaded image exceeds the threshold (e.g., 2560px), the plugin automatically generates a resized version of the main image. This serves several purposes:

• Optimizes Performance: Reduces frontend file size and improves loading speeds.
• Prevents Server Errors: Avoids memory exhaustion or timeouts when generating thumbnails, WebP, or AVIF files from oversized originals.
• Stability: Maintains consistent ‘Full Size’ image handling within the WordPress Media Library.

The ‘-scaled’ suffix is simply a filename marker indicating that this is the resized primary image. The original large file is still preserved and recorded in the metadata.

This logic is identical to how WordPress handles large images natively. CompressX simply incorporates this threshold and behavior into its own resize functionality.

Kind regards.

Hello @ziobond

Support for pro version is not permitted in this forum, for any questions regarding the pro version, please feel free to contact us via this form. We would be happy to assist you further there.

All the best,

Hello @chrisesch

Thanks for your feedback.

To clarify, CompressX automatically serves the WebP/AVIF version on your website once it has been converted.

The description text you see (showing the size savings) confirms that the WebP version has been successfully created and is being used.

To verify that your site is correctly serving the WebP images to your visitors, please follow the steps in this detailed guide: How to verify if WebP/AVIF is effective

All the best,

Hello,

Thank you so much for the ’10-star’ love! ❤️ We truly appreciate the support from the developer community and smaller site owners. We are committed to keeping CompressX accessible and powerful for users like you. Your feedback keeps us motivated to keep improving!

Have a nice day.

Hello @yhthn

Thanks for your feedback.

We have confirmed that this is a bug caused by the V2 interface failing to save this specific setting. Our team will include a permanent fix for this in the next public release.

To resolve this immediately, you can temporarily switch back to the V1 interface by going to General Settings, selecting Change Style, choosing Old Style, and clicking Save Changes. Once in the V1 interface, enable the option to Remove ‘Header always set Cache-Control “private”‘ from .htaccess file. Once you have saved the change in V1, you can switch back to the V2 interface and the setting will remain active.

All the best,

Hello @sheldonng

Thank you for the update. It is great to hear that you found a solid workaround to resolve the compatibility issues.

If you run into any other questions while optimizing your newly converted JPEG library, feel free to reach out.

All the best,

Hello:

1. The status ‘Not supported (Convert)’ is not caused by the image dimensions. It is very likely because the MIME type saved in the database does not match any of the following supported types:

image/jpg, image/jpeg, image/png, image/webp, or image/avif. Based on your description, the type stored in your database is likely HEIF.

2. The ImageMagick version displayed depends on the PHP ImageMagick extension library, not the version installed on the server itself. Therefore, to upgrade the version correctly, you must upgrade the server’s ImageMagick and ensure the corresponding PHP extension is updated to match it.

Kind regards.

Hello @queno1809

Thank you for your feedback and information.

Regarding CloudFront compatibility, we would like to clarify that Amazon CloudFront is not yet supported as a natively integrated CDN in CompressX. Currently, our “CDN Integration” feature is optimized specifically for Cloudflare, and Bunny CDN (in pro version).

However, we are considering adding broader CDN support, including CloudFront, in our future roadmap.

We appreciate your patience as we continue to improve the plugin. Please let us know if you have any other questions.

All the best,