bynder

Teams managing large asset libraries hit a wall with manual uploads. You normally download every image from a central library, then re-upload it to the Assets panel by hand. Your asset source has no version control, so outdated logos and expired campaign images stay live until someone notices. Across multiple brands and sites, that manual loop consumes hours every week.

Connecting Bynder with Webflow closes that loop. You search for brand-approved assets from inside Webflow and embed them directly from Bynder's CDN. When a new version lands in the DAM, CDN-linked assets update everywhere at once. A custom API build extends this further into an automated Webflow CMS sync.

This integration is for designers who want approved assets on the canvas and for marketers building landing pages without re-uploading files. It also gives brand managers a single source of truth. Agencies running multi-brand portfolios and enterprise web teams with governance requirements get the most out of it. Developers can go deeper with webhook-driven sync pipelines.

How to integrate Bynder with Webflow

What is Bynder? Bynder is a digital asset management (DAM) platform used by 4,000+ customers to store, organize, and deliver brand assets. It includes a configurable taxonomy, role-based access controls, approval workflows, and modules such as Brand Guidelines, Content Workflow, and Studio. Its Dynamic Asset Transformation (DAT) feature resizes and reformats images in real time through URL parameters.

Teams pair Bynder with Webflow when the website needs to pull from the same approved asset library as every other channel. Assets flow directly from Bynder into pages and skip the export-upload copy step. Version updates in Bynder automatically propagate to CDN-linked images on the site.

The Bynder-Webflow integration supports four approaches:

• The Bynder app handles asset search and embedding inside Webflow, plus syncing without writing code.
• Public URLs and embed codes let you place Bynder-hosted assets in Image elements or Code Embed elements.
• Zapier and viaSocket link Webflow to Content Workflow by Bynder, a separate Bynder product for content operations, via ready-made Zapier connectors.
• The Webflow Data API and Bynder APIs give you full control over automated asset-to-CMS sync and require server-side development.

Most implementations combine two or more of these methods depending on how much automation the site needs.

Install the Bynder app

The Bynder app in the Webflow Marketplace is a Designer Extension built by the agency Flowout. It runs inside Webflow. Bynder lists it as partner supported on its Bynder Marketplace. You authenticate with OAuth SSO and work with your Bynder library without leaving the canvas. Choose between two delivery modes for each asset. You can embed directly from Bynder's Amazon CloudFront CDN, or sync the file into the Webflow assets folder.

To set up the integration:

1. Install the Bynder app from its Webflow Marketplace listing.
2. Open the app inside Webflow and sign in to your Bynder portal with OAuth SSO.
3. Select an element on the canvas, pick an asset in the Bynder panel, and click Embed.

Once connected, the app lets you:

• Upload, search, tag, and manage Bynder assets and collections within Webflow
• Sync Bynder assets with the Webflow assets folder
• Embed assets directly from Bynder's CDN or from Webflow
• Narrow searches with Bynder Smartfilters

The app is a manual embedding tool. CDN-linked assets update automatically when new versions upload to Bynder. CMS item creation and updates require the API method covered below.

Embed Bynder assets with public URLs and Code Embed elements

Bynder generates public URLs and embed snippets that work in Webflow without the app. These methods suit content managers who need to place a specific asset or an entire collection on a page. The right path depends on your Webflow plan and how much of the library you want to expose.

Paste public asset URLs into Image elements

Users with the 'Mark assets as public' permission can generate public asset URLs in Bynder. The /asset/ structure is now Bynder's standard public link format, and legacy /m/ links keep working. This method works on every Webflow plan and requires no code.

To embed a public asset:

1. In Bynder, mark the asset as public and copy its /asset/ URL.
2. In Webflow, add an Image element and paste the URL into its source field.

Once an asset is public, it cannot revert to private, only deleted or archived. Derivatives stay private, so check each rendition you plan to use.

Add embed codes with Code Embed elements

Bynder generates embed snippets for individual assets and entire collections. Collection embeds display up to 250 assets and require the 'Embed collection' permission in Bynder. Pasting the snippet needs a Code Embed element, which requires a paid Webflow site plan.

To embed a Bynder asset or collection:

1. Generate the embed code in Bynder for the asset or collection.
2. In Webflow, go to Add panel > Advanced and add a Code Embed element to the canvas.
3. Paste the snippet, save, and publish the site.

Embedded collections become public to anyone visiting the page, including people without download rights in Bynder. Search engines do not index the embedded content.

Load Universal Compact View with custom code

Universal Compact View (UCV) is Bynder's pre-built UI component for searching and selecting DAM assets from within another system. Loading its JavaScript site-wide uses custom code in head and body tags, which also requires a paid site plan.

To set up UCV:

1. Confirm your portal runs on the Bynder CDN, the prerequisite listed in the UCV quick start guide.
2. Follow the Integrate Universal Compact View instructions and add the script through site settings custom code.

Custom code supports HTML, CSS in <style> tags, and JavaScript in <script> tags. Server-side languages like PHP or Python are unsupported.

Connect Content Workflow by Bynder with Zapier or viaSocket

Bynder DAM has no connector on Zapier, Make, n8n, or IFTTT. Zapier and viaSocket offer a connector for Content Workflow by Bynder, a separate Bynder product for content creation workflows that include review and approval. If your team runs editorial or web content production through Content Workflow, the Zapier Webflow integration links the two directly.

Documented flows connect the two directly. A new Webflow form submission can create a project or an item in Content Workflow, and when a Content Workflow item changes status, the flow can create or update a live item in the Webflow CMS. viaSocket documents a variant where a new Webflow order opens a Content Workflow project.

These automations only move content tasks and status changes. For syncing images and files from Bynder DAM into Webflow, the API path below is the only automated option.

Build with the Webflow and Bynder APIs

Automated sync between Bynder DAM and Webflow CMS collections requires a custom API integration. This path suits developers building an automated pipeline. Asset changes in Bynder propagate to CMS items without manual work. Bynder API access uses OAuth 2.0 with JWT-format bearer tokens. You register an OAuth app yourself in your Bynder portal under Settings, Advanced Settings, Portal settings, OAuth Apps. For machine-to-machine setups that need no user interaction, Bynder also offers permanent tokens that never expire, a feature Bynder Customer Support enables. Flowout built its own Bynder-Webflow app on a Node.js server, a practical reference architecture for this pattern.

A full pipeline draws on several APIs:

• Bynder's media API handles asset search and retrieval. It includes metadata and derivatives via GET /api/v4/media/?includeMediaItems=true.
• Bynder's Dynamic Asset Transformation endpoint transforms images at GET /transform/{id}/{name} with operations such as crop, fit, rotate, and scale, plus focuspoint, format, and quality parameters. It outputs JPG, PNG, and WebP, with WebP as the default.
• Webflow's Data API handles CMS collections and items, plus asset uploads.
• Bynder webhooks push real-time asset events to your server via Amazon SNS.

A full DAM integration needs the Webflow scopes assets:read, assets:write, cms:read, cms:write, and sites:write.

Sync Bynder assets to the CMS with webhooks

Bynder fires webhook events for asset lifecycle changes, including asset_bank.media.create, asset_bank.media.updated, asset_bank.media.meta_updated, asset_bank.media.archived, and asset_bank.media.deleted. Delivery authentication is limited to Basic Auth over HTTPS.

To build the sync pipeline:

1. Configure a Bynder webhook for asset_bank.media.create and asset_bank.media.updated pointing at your server endpoint.
2. On receipt, wait 2–5 seconds. Then call GET /api/v4/media/{id} to fetch the processed asset's metadata and URL. The webhook payload does not include the CDN URL.
3. Create or update the CMS item with POST https://api.webflow.com/v2/collections/{collection_id}/items or PATCH on the same path. In the image field, pass the Bynder DAT or CDN URL as { "url": "<bynder-url>" }.
4. Publish with POST https://api.webflow.com/v2/collections/{collection_id}/items/publish.

Webflow does not generate responsive srcset variants for externally hosted image URLs, so pair this pattern with DAT parameters for sizing. Flowout notes that some Bynder features sit outside the public API, so validate your required endpoints before committing to an architecture.

What you can build with the Bynder Webflow integration

Integrating Bynder with Webflow lets you publish brand-approved assets across your sites without downloading files from the DAM and re-uploading them by hand.

• Multi-brand web properties: Manage several brand sites from one DAM with permission-based access controls, so each site's team only touches its own approved assets. A parent company can run distinct product brand sites from a single Bynder portal.
• Campaign landing pages with transformed images: Use DAT URLs to serve WebP renditions cropped and scaled per breakpoint. A seasonal campaign page pulls one master asset from Bynder and displays the right variant everywhere.
• Auto-updating product catalogs: CDN-linked product images update on the live site when a new version uploads to Bynder, since automatic CloudFront invalidation clears stale URLs. A retailer's catalog pages stay current without republishing.
• Brand portal microsites: Embed a Bynder collection of up to 250 assets as a press kit or partner resource page, or render synced assets in a Collection List for a searchable media library.

For more control over automated CMS sync and asset lifecycle handling, the API integration path covers those cases. Explore how to serve responsive images on a Webflow site to reuse the same delivery pattern with Bynder's DAT renditions.