Description
Stop wondering where your images are used! Oxygen Media Usage Tracker Pro gives you instant visibility into media usage across your entire Oxygen-powered website. Perfect for developers, agencies, and site owners who want to optimize their media libraries and improve site performance.
Key Features
Instant Usage Detection
- See exactly which pages, templates, and reusable parts use each image
- Direct edit links to quickly update or remove media references
- Works with all Oxygen elements including galleries, backgrounds, and dynamic data
Smart Caching System
- Lightning-fast results with intelligent caching
- Automatic stale data detection (7-day freshness)
- Background batch processing prevents timeouts
Advanced Search Capabilities
- Standard Scan: Quick detection of direct media usage
- Deep Scan: Comprehensive search including:
- Generated thumbnail sizes
- Element-level CSS (Code Blocks, Advanced CSS)
- Escaped URLs in JSON data
- Dynamic featured images in repeaters
- Cached CSS from Oxygen components
- Custom Fields Scan: Detects images in ACF/Metabox fields including:
- ACF repeater fields and flexible content
- Metabox group fields and cloneable fields
- Image fields, gallery fields, and file fields
- All custom field types containing attachment IDs
Powerful Filtering
- "Only Unused" filter to quickly identify orphaned media
- Sortable usage column
- Batch operations for efficiency
Developer-Friendly
- Clean, modular code architecture
- Extensible code architecture
- WP-CLI compatible (coming soon)
- Debug mode for troubleshooting
Technical Specifications
- Requirements: WordPress 5.6+, PHP 7.4+, Oxygen Builder 3.0+
- Database Impact: Minimal - uses post meta for caching
- Performance: Processes 100+ images in under 10 seconds
- Compatibility: Works with Oxygen's repeaters, dynamic data, and conditions
Known Limitations
The plugin scans Oxygen's database-stored content (JSON data, cached CSS, templates). The following are not detected:
- Universal CSS (Settings → CSS): Oxygen compiles this to static files on the filesystem, not stored in the database
- Third-party plugins: CSS/JS files added by other plugins outside Oxygen's data structure
- Shortcode-rendered images: Images dynamically loaded by shortcodes (e.g., Ultimate Member, BuddyPress) are not detected because they're rendered at runtime and not stored in Oxygen's JSON structure
- Gutenberg/Classic Editor content: Images added to blog posts via the Gutenberg editor or Classic Editor are not detected as they're stored in post content, not in Oxygen's data structure
These limitations are by design to maintain performance and simplicity. Element-level CSS (Code Blocks, Advanced CSS) is fully supported.