WebP Optimizer
WebP Optimizer creates smaller modern image versions where compatible, helping reduce image transfer size without asking you to manually convert every catalog image.
- 1Open the WebP settings and use conservative quality settings; save before generating or changing caches.
- 2Open a product page that contains an existing JPG/PNG product image.
- 3In browser Developer Tools → Network → Img, inspect the returned image format and compare visually.
Where browser/server conditions allow WebP output, supported images are delivered in a modern format without appearing broken. The original file is not overwritten by normal delivery.
Remember: A JPEG/PNG response alone does not prove a failure: check browser support, server capability, caching and optimization settings. Frontend verification guide →
Recommended setup
- Run the conversion test first.
- If the test passes, enable WebP globally.
- Use quality around 82 as a practical starting point.
- Leave cache handling at the default unless troubleshooting.
Why is there no Store dropdown?
WebP conversion works on the shared OpenCart image/cache filesystem. A separate quality value per store would be misleading because the same original image and generated derivative may be used by multiple stores. HuntBee therefore keeps WebP status and quality global.
But what if different stores use different themes?
Theme compatibility is still checked per store at runtime.
Recommended quality
A quality around 82 is a sensible balance for most ecommerce stores: noticeably smaller files without an obvious loss of product-image quality in normal viewing.
| Quality range | What to expect |
|---|---|
| 75–80 | Smaller files; inspect detailed product photography carefully. |
| 82 | Practical general starting point. |
| 85–90+ | More visual preservation but larger files; diminishing size benefit. |
There is no single perfect number. Use the conversion test and inspect representative product images on desktop and mobile.
What does the cache do?
HuntBee generates/serves WebP derivatives through the image pipeline and uses cached files so the same image does not need to be converted on every request.
When should I clear the cache?
- After changing WebP quality and wanting existing derivatives rebuilt.
- After replacing source images but seeing an old derivative.
- While troubleshooting a conversion/display problem.
You do not need to clear it routinely just because the store receives orders or products are viewed.
Recommended settings
| Setting | Recommended |
|---|---|
| Status | Enable after conversion test passes. |
| Quality | Start around 82. |
| Store selector | None — configuration is global by design. |
| Theme compatibility | Let HuntBee detect the active theme per store. |
| Cache clear | Use after quality/source changes or troubleshooting, not as daily maintenance. |
WebP vs Image Organizer
- WebP Optimizer changes the delivered image format/size.
- Image Organizer improves filenames/folder organization and image references.
They solve different problems and can be used independently.
Troubleshooting
- Conversion test fails: check PHP image library support and permissions before enabling.
- Journal3 store behaves differently: that can be intentional; HuntBee avoids interfering with incompatible/custom theme image pipelines.
- Quality change is not visible: clear the WebP cache and reload a representative image.
- Some images are not converted: confirm the source format/path is handled by the OpenCart image pipeline.