Reference Glossary
Connector / plugin (DAM)
A pre-built integration, usually installed inside a third-party tool (CMS, design app, Slack, PowerPoint), that lets that tool search, insert, or sync assets from a DAM without custom development.
Why it matters in a DAM
Connectors are what determine whether a DAM actually gets used day-to-day or gets bypassed: a designer who has to leave Photoshop, log into a separate DAM website, download a file, and re-import it will often just reuse a local copy sitting on their desktop instead. A DAM with a real Photoshop or Figma plugin lets that same designer search and pull the current, correctly licensed asset without leaving their tool, which is usually the difference between a DAM adoption effort succeeding or quietly failing.
A worked example
Common mistake
Evaluating a DAM primarily on its own interface while barely testing the connectors for the specific tools the team actually works in daily — a DAM with an excellent web UI but a broken or nonexistent Figma plugin will still get bypassed by designers who default back to local files.
A DAM connector or plugin is a pre-built integration that runs inside another application — a design tool, a CMS, an office suite, a chat platform — and lets users search and insert assets from the DAM without leaving that application or writing custom integration code themselves.
The reason connectors matter more than they might seem to on paper is adoption behavior. A DAM’s value only materializes if people actually pull assets from it instead of reusing whatever local copy is sitting on their desktop or in an old email attachment. Every extra step between ‘I need this logo’ and ‘I have this logo’ is a point where someone defaults back to a local file instead — which is exactly how outdated or unlicensed assets keep circulating even after a DAM is in place. A connector for the specific tools a team lives in daily (Photoshop, Figma, PowerPoint, the CMS) removes that friction directly at the point of use.
Connector quality varies widely between ‘search and insert’ (functional but basic) and deeper integrations that also sync updates, respect rights and expiry status, and pull the correctly sized rendition automatically for that context. It’s worth testing the actual connector for a team’s specific toolset before buying, rather than trusting a vendor’s general integration marketing page.
Frequently asked
Why do DAM connectors matter more than the DAM's own web interface?
Because a DAM's value only materializes if people actually pull assets from it -- every extra step between needing an asset and having it is a point where someone defaults back to a local desktop copy instead. A connector removes that friction directly at the point of use, like inside Photoshop or Figma.
What's the risk of evaluating a DAM only by its own interface?
A DAM with an excellent web UI but a broken or nonexistent Figma plugin will still get bypassed by designers who default back to local files -- the connectors for the specific tools a team actually works in matter as much as the DAM's own UI.
What's the difference between basic and deeper DAM connectors?
Basic connectors offer "search and insert" functionality; deeper integrations also sync updates, respect rights and expiry status, and pull the correctly sized rendition automatically for that context.
What tools commonly get DAM connectors?
Adobe Creative Cloud, Figma, PowerPoint/Office, WordPress, Slack, and Microsoft Teams are common examples of applications with pre-built DAM connectors.
What happens without a connector for a team's daily tools?
Users keep local desktop copies instead of pulling from the DAM, which is exactly how outdated or unlicensed assets keep circulating even after a DAM is in place.
How should a team evaluate connector quality before buying a DAM?
By testing the actual connector for their specific toolset directly, rather than trusting a vendor's general integration marketing page, since connector depth varies widely between vendors.