Image Organizer
Safely rename and organise OpenCart catalog images with previews, templates and conservative orphan handling.
Preview, rename and organise OpenCart image paths using consistent SEO-friendly patterns.
What does it do?
The Image Organizer can improve messy file names and folder organisation. It can work with product, category, manufacturer and option images. Because image paths are real files used by your store, this is a feature to use carefully and with a backup.
Safe beginner rule
Settings
| Setting | What it means | Recommended for beginners | Change it when… |
|---|---|---|---|
| Status | Enables Image Organizer services. | Enabled is fine; this does not mean every batch action runs automatically. | Temporary troubleshooting. |
| Auto Rename on Save | Renames supported entity images when saved. Default off. | Keep off until you have tested your naming patterns. | You trust the patterns and want new/edited items handled automatically. |
| Include Options in Auto Rename | Includes option images in automatic rename. Default off. | Keep off initially. | You use option images heavily and have tested naming uniqueness. |
| Folder Organisation | Organises images into configured folders. Default on. | Keep on for preview/planned batch work. | Your theme/integration requires a different fixed path approach. |
| Product Option Images | Includes product option images in relevant operations. Default off. | Leave off until you explicitly want to reorganise option images. | You have backed up and tested option-image behaviour. |
| Normalize JPEG Extension | Normalises JPEG extension to .jpg. It renames the extension; it does not convert image encoding. Default on. | Keep on. | A third-party system requires a different literal extension. |
| Product Folder Strategy | Controls how product image folders are built. Default uses category hierarchy. | Keep category hierarchy if your catalog structure is stable. | Your catalog needs a different folder scheme. |
| Product Root | Default catalog/products/. | Keep default. | You have an intentional custom media structure. |
| Option Root | Default catalog/options/. | Keep default. | Intentional custom media structure. |
| Category Root | Default catalog/categories/. | Keep default. | Intentional custom media structure. |
| Manufacturer Root | Default catalog/manufacturers/. | Keep default. | Intentional custom media structure. |
| Custom Folder Template | Default {category} when custom strategy is used. | Do not customise until you understand generated paths. | A stable custom organisation pattern is needed. |
| Main Product Filename | Default {product}. | Keep simple product-based naming. | Duplicate naming requires a stable differentiator. |
| Additional Product Filename | Default {product}-{index}. | Keep. | You need another stable sequence. |
| Option Filename | Default {product}-{option}. | Keep if/when option images are included. | Your option naming needs another unique pattern. |
| Category Filename | Default {category}. | Keep. | You need a different naming rule. |
| Manufacturer Filename | Default {manufacturer}. | Keep. | You need a different naming rule. |
How shared images are handled
Images that are shared by more than one catalog entity are risky to move casually. HuntBee takes a cautious approach and can skip shared images rather than creating broken references.
Orphan image candidates
An “orphan candidate” means HuntBee did not find a normal catalog reference. It does not prove the file is safe to delete. Themes, custom code, banners, content editors or external integrations may still use it. Review manually; do not treat an orphan report as an automatic delete list.
Cron options
The Cron Manager can run image rename/organise batches and image audits. They are disabled by default. Keep them off until manual preview/batch behaviour is confirmed.