This feature allows you to control where WebP conversion should apply. Instead of converting every image globally, you can limit the conversion scope for better compatibility and performance control.
20.1 Overview #
By defining scope rules, you can decide exactly which content areas should generate and serve WebP images.
This is especially useful for:
- Large websites with many media files
- Testing WebP on selected sections
- Avoiding compatibility issues on specific pages
How It Works Internally #
- Checks the current post ID or post type
- Applies WebP conversion conditionally
- Skips conversion if content is outside defined scope
- Ensures fallback to original formats when needed
20.2 Settings #
Choose from the dropdown:
1️⃣ All Public Content #
Converts images across all posts, pages, and public post types.
- Applies site-wide
- Recommended for most websites
2️⃣ Specific Post IDs #
Enter post IDs separated by commas.
Example:
102, 114
Only those specific posts will have images converted.
3️⃣ Specific Post Types #
Select specific content types such as:
postpageproduct(WooCommerce)
Useful for optimizing only high-traffic sections like product pages.
20.3 Best Practice Recommendation #
- Use All Public Content for full-site optimization
- Use Specific Post Types for eCommerce performance tuning
- Use Specific Post IDs for controlled testing
- Clear cache after changing scope rules
Conversion Scope Rules provide granular control over image optimization behavior.
