Cache-Control for CDN

  • Updated

If you are using your own Content Delivery Network (CDN) and want to have control over when the caching of your Bynder assets expires, you can use cache-control. By implementing cache-control, you can specify the expiration time for your cached Bynder assets. Learn more about cache-control below.

What is cache-control?

If your CDN is not set up by Bynder, you can make use of cache-control to configure the cache expiry time of your assets. When your users request a Bynder asset, the asset will be cached on your CDN. During this request the cache expiry time will also be returned to your CDN via the response header. Due to the cache-control the CDN knows that it can no longer use the cached image when the asset is requested for the first time after the cache has expired. The cached image will be invalidated and the latest version will be retrieved from Bynder.

When should I use cache-control?

When your CDN is not set up by Bynder, but you still want to control when the Bynder assets cached on your CDN expire, you can make use of cache-control.

How to set up cache-control?

Decide on the expiry time for your assets and contact your Customer Success Manager, who can help you setting this up.


  • Cache-control can only be set up for the original file and cannot be configured for (OTF) derivatives.

  • The configured expiry date will apply to all Bynder assets. It is not possible to set up an expiry time for assets individually.

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