Content Delivery Network (CDN)

A Content Delivery Network (CDN) is a system that helps make your media and assets load faster by spreading them out across multiple servers worldwide. When people access your content, they are directed to the closest server to them, which makes things load quicker. Bynder uses Amazon CloudFront as its default CDN provider, but you can use your own CDN if you want, like Akamai. Bynder's CDN also automatically updates assets whenever changes are made. Bynder has different data hosting regions in Frankfurt, the US East Coast & West Coast, and Tokyo, which helps deliver assets quickly with little delay. However, some clients may need even faster asset delivery in certain situations.

We can set up Bynder to upload your data to a specific region. See Data hosting regions supported by AWS and Bynder.

How to enable this feature in your portal?

Contact your Customer Success Manager to enable this feature in your portal and any associated costs.

Bynder uses Amazon Web Services' (AWS) CloudFront, a CDN network that ensures high availability with servers worldwide. CloudFront caches images across multiple endpoints, allowing for fast delivery. Bynder also utilizes flexible hosting and autoscaling from AWS, enabling easy and automatic scaling of server capacity. By default, Amazon CloudFront has a 24-hour expiry time for cached content. However, Bynder has implemented Automatic Invalidation, which automatically invalidates CloudFront CDN URLs when a new version of an asset is uploaded. This means that external integrations using CloudFront will always display the latest version of assets, without having to wait for the cache to expire.

Download and share private & public files through Bynder’s CDN

When you download assets from the asset library, you are using the CDN (Content Delivery Network). We can also customize Bynder so that you can use CDN with Bynder Express. This means that when you share files with Bynder Express, the recipients can download the files using CDN when they click on the download link in the notification they receive. If users have permission to download the original file, they can do so through CDN if the asset is marked as public on the Asset Detail Page. The link to the image is only available for a limited time for security reasons. Alternatively, if the asset is marked as public, you can retrieve a permanent link via the API. When assets are marked as public, all the thumbnails and web versions are also public in Bynder and can be distributed through CDN. If needed, we can customize your portal so that thumbnails become private. Their link will be signed and expire after a limited time.

Additional information on Bynder CDN provider (Amazon CloudFront)

  • The first download through CDN is usually slower, but then the speed increases. Download speed depends on a variety of factors, such as your internet speed, location, and other conditions that influence the connection between your device and Amazon CloudFront. Read more about Amazon CloudFront here. You can find more information on their quotas, previously known as limits, here.

  • When using CDN, the maximum file size you can download is 20GB.

  • Depending on the amount of traffic used you may be charged for CDN usage. Read more about our fair use policy here


    Our Support team can only assist with Amazon CloudFront-related questions.

Other CDN Providers

Bynder is also compatible with other CDN providers, such as Akamai. If you decide to use a provider other than Amazon CloudFront, you will need to set up and configure the CDN on your side. When it's up and running, please contact your Customer Success Manager to make the necessary updates on our end.


Configuring a custom CDN will not replace our Amazon CloudFront setup but work alongside it. Amazon CloudFront will be used for all portal activity, like downloading assets and displaying thumbnails. Your custom CDN will host your assets for web/API use.


Please see below for limitations you may experience when using Other CDN Providers

  • Cache invalidations: If you decide to delete an asset that should not be public, Bynder would need to manually invalidate the public link, as it would not occur automatically. If this occurs frequently we recommend building an integration to make this process automatic.

  • Assets versioning: Is invalidated. For example, when a new version of an asset is uploaded, it will not be automatically updated in your portal.

  • Usage tracking: Real-time metrics are a feature that allows you to keep up-to-date with what is happening in your portal, i.e., what assets are being viewed or downloaded by users. When using a custom CDN this feature will not work for DAT or public links.

If you’d like to make use of your own custom CDN and facilitate public assets, follow the setup below.

The below configuration page is from AWS. The wording may vary slightly on your side when setting this up for a different CDN provider.

  • Path pattern - This is the default URL path that we use for public assets. Fill in: /m/* For DAT use transform/*

  • Origin or origin group - Select the URL of your Bynder portal. For example

  • Viewer Protocol Policy- We only support the HTTPS protocol, so make sure to redirect HTTP to HTTPS.

  • Allowed HTTP Methods - Select GET and HEAD. Other HTTP methods are not necessary.

  • Whitelist Headers - Add Host and Origin. Optionally other headers can be added as well.

  • Minimum and Maximum TTL—You can configure the TTL values to determine when you want the cached asset to expire. Once it has expired, the asset must be requested from the server again.


Was this article helpful?

0 out of 0 found this helpful

We're sorry to hear that!

Find out more in our community

Have more questions? Find out more in our community