Frontify Media Delivery is the system that powers how assets are processed, stored, and delivered through our Content Delivery Network (CDN). It ensures faster load times, optimized previews, and a more scalable approach to managing media.
To enhance performance and reliability, we are transitioning all customers to an upgraded version of Media Delivery. This article provides guidance on what’s changing, what to expect, and how to ensure a seamless transition.
What is changing?
Frontify is upgrading how assets are served through our Content Delivery Network (CDN). This update happens behind the scenes and improves performance, preview quality, and URL structure.
Important: The upgraded Media Delivery system is fully backward compatible. Existing asset URLs, legacy transformations, and API parameters will continue to work after the transition. No customer action is required to maintain existing links or integrations in most cases.
However, some custom integrations, security settings, or firewall configurations may need adjustments to ensure continued access to assets in specific networks or environments.
Why are we making this change?
This upgrade allows Frontify to:
Improve performance and reliability across regions
Simplify and standardize CDN URLs
Enable advanced media capabilities, such as dynamic CDN links and real-time asset transformations
Scale media delivery more efficiently for large asset libraries
Some of these newer capabilities will only be available on the upgraded Media Delivery system.
What will we do?
We are migrating customers gradually in controlled phases to minimize risk and ensure stability.
The transition will happen in phases, ensuring stability and minimizing disruptions.
Legacy URLs and existing transformations will continue to function, so there is no immediate impact on accessibility.
Once enabled, all new media transformations and previews will use the optimized delivery system automatically.
Once enabled, all new media transformations and previews will automatically use the upgraded delivery system.
How to ensure a smooth transition
For most users, the transition will be seamless. However, if your organization has custom integrations, security policies, or internal network configurations, follow these steps to ensure uninterrupted media delivery:
1. Check if your integrations use hardcoded CDN links
If your organization uses custom integrations, middleware, or third-party systems that fetch Frontify assets, check whether they:
Rely on hardcoded CDN domains
Enforce strict URL validation
Proxy or cache media through custom infrastructure
Legacy URLs will continue to work, but new media and transformations will use the updated CDN structure.
2. Ensure network security settings allow the new URLs
If your organization uses firewalls, proxies, or domain allowlists, ensure the new Media Delivery domain is accessible.
Action required (if applicable):
Confirm with your IT team whether outbound requests to new domains are restricted
Allow traffic from
https://media.ffycdn.net
If the new domain is blocked, assets may not load in restricted environments.
3. Test media access and performance (Optional)
Open and preview assets in your Frontify Libraries and Style Guides to ensure everything loads as expected.
If you rely on automated processes, verify that media transformations, previews, and embedded assets work correctly.
How can I test the new CDN URLs to see if your network configuration will block the media from loading?
To test the new URLs in your network, you can take any existing CDN URL you find in your Frontify platform, for example:
https://cdn-assets-eu.frontify.com/s3/frontify-enterprise-files-eu/eyJwYXRoIjoiZmVybVwvZmlsZVwvMjVVOEtGTmVUZWN6MzJkMkpCZjkucG5nIn0:ferm:Yi0Fo_Akkv_tqJJYWQ5zygGfMQwZGg3UNL_Mwc0zu6w
and build the new CDN URL based on the old one, combined with the new domain. From the legacy CDN URL domain, you’ll need to extract everything from 'eu/ey' to the end of the URL.
With this information, you can build your new CDN URL. You’ll just need to extract the region (in this example eu), the instance (in this case: ferm) from the encoded path (between the two colon characters ::) and the whole encoded path itself.
In this example:
eyJwYXRoIjoiZmVybVwvZmlsZVwvMjVVOEtGTmVUZWN6MzJkMkpCZjkucG5nIn0:ferm:Yi0Fo_Akkv_tqJJYWQ5zygGfMQwZGg3UNL_Mwc0zu6w
With this information you can compose the new CDN URL that should work and deliver your media preview even before the rollout. In this case, it should look something like this:
https://media.ffycdn.net/eu/ferm/eyJwYXRoIjoiZmVybVwvZmlsZVwvMjVVOEtGTmVUZWN6MzJkMkpCZjkucG5nIn0:ferm:Yi0Fo_Akkv_tqJJYWQ5zygGfMQwZGg3UNL_Mwc0zu6w
What to do if you experience issues
While we don’t anticipate disruptions, some configurations may require minor adjustments. If you notice:
Missing or broken images: Check if security settings are blocking
https://media.ffycdn.net.Delays in previewing updated files: Some caching differences may temporarily affect how recently uploaded assets appear.
Custom integrations not displaying media correctly: Ensure that any hardcoded CDN URLs are updated to support the new URL format.
Need help?
If you experience issues, contact Frontify Support for troubleshooting assistance. If necessary, we can temporarily revert the change while resolving the problem.