Zuperix DAM

Developer	Zuperix
Version	v1.1.5
Active Installs	0 +
Requires / Tested	6.3 / 6.9.4
Last Updated	2026-05-18 8:06pm GMT
Official Link	View Details →

Zuperix DAM is the official WordPress connector for the Zuperix Digital Asset Management platform.

Managing brand assets across multiple WordPress sites, social media, and marketing tools often leads to “asset fragmentation”—where files are stored in multiple places, version control is lost, and storage costs spiral. A Digital Asset Management (DAM) system solves this by providing a single, centralized source of truth for all your media.

This plugin bridges the gap between your centralized Zuperix library and your WordPress workflow. Instead of uploading and storing files locally inside wp-content/uploads on every site, this connector allows you to:

• Centralize Storage: Upload once to Zuperix and use everywhere.
• Eliminate Duplicates: Stop maintaining the same image in multiple WordPress media libraries.
• Unified Workflow: Browse, search, and insert assets from your global DAM directly within the Gutenberg editor or classic media modal.
• Global CDN: Serve assets directly from the Zuperix CDN for maximum performance without taxing your WordPress host.

Features:

• One-click connection via API key — no OAuth flow needed
• Automatic upload interception — files are forwarded to the DAM transparently
• Fallback to local storage if the DAM is unavailable (toggle in settings)
• Full Gutenberg block editor support — a “Zuperix DAM” sidebar panel lets you browse and insert assets without leaving the editor
• Classic media modal tab — a “Zuperix DAM” tab is added to the standard WordPress media picker
• Paginated asset grid with live search (powered by Zuperix search API)
• Zero local file storage — WordPress stores only a ghost attachment pointing to the DAM CDN URL
• Nonce-protected AJAX endpoints for all browser→PHP communication
• Sanitised and validated inputs throughout

How it works:

1. Configure your DAM API URL and API Key in Settings → Zuperix DAM.
2. When a user uploads a media file, wp_handle_upload fires and the plugin intercepts the file before WordPress writes it to disk (or immediately after), sends it to the DAM, and replaces the URL with the CDN link returned.
3. The WordPress attachment post is created as usual but its guid and all URL filters point to the CDN URL.
4. Images inserted into posts use the CDN URL directly — no local file is ever served.