With Mediaflow CDN, you can publish files from Mediaflow and use them on a website, in an online store or in an app, for example. Each publication gets a public URL that your system uses to retrieve the file.
For images, you can set things like size and format directly in the link. If the source file behind a publication is replaced, the same URL keeps working. Within an hour, the content updates automatically everywhere the file is published, so you don’t have to change each link by hand. This makes it easier to keep images up to date and to manage published files from a single source.
What is a CDN?
CDN stands for Content Delivery Network. It’s a network of servers that caches published content and delivers it from a server closer to the visitor. This can shorten response times and help handle traffic spikes, because fewer requests have to go all the way to the origin server.
How it works
- The file is stored in Mediaflow.
- Your integration publishes the file through Mediaflow’s CDN API and receives a public URL.
- The integration saves the URL in the system where the file will be used.
-
When someone visits the website or uses the app, the file is retrieved through the CDN link.
The benefits of a CDN
- Potentially faster file delivery: the file is delivered and cached closer to the visitor, so it loads faster for them.
- Less manual work: replace a file in Mediaflow instead of tracking down and replacing copies in several places.
- Better control: published files have their own links and can be updated or unpublished.
- Works across channels: the same media bank can serve as the source for websites, e-commerce and newsletters, for example.
Supported file types
The CDN solution supports images, PDF, SVG, audio and video. Images can be delivered as JPEG, PNG, WebP or AVIF, and can be resized and converted on delivery. When the link specifies a size or format, or when the publication has default settings, Mediaflow automatically picks the format that works best in the visitor’s browser. Images without parameters are delivered as WebP. PDF, SVG, audio and video files are delivered without that kind of processing. Office documents and archives can’t be published through the CDN. For GIFs, the animation is lost if the image is processed with parameters or default settings.
To get started, you’ll need:
- A Mediaflow account with CDN enabled. Contact your account manager to get started.
- API access and an OAuth2 bearer token.
- The CDN ID for your configuration. Ask Mediaflow for the correct value.
- A developer who can set up and maintain the integration.
- A file that has been uploaded to Mediaflow.
To call the management API from your integration’s backend, not from the browser. That way, authentication and the publication lifecycle are handled on the server side.
Want more technical information about how our CDN works?Contact support@mediaflow.com.