Skip to main content

Inside Frontify: January 2026

Product keynote

Updated this week

The future of brand operations is here: See how Frontify brings together governance, automation, and intelligence to help teams scale with clarity and confidence.

Watch the keynote:

Your questions from the live event, answered:

General

  1. Will the video recording of the presentation and Q&A be sent out via email or available via CSM? Yes, the recording is available on Youtube and on the Frontify website.


DAM:

  1. Just back to the beginning: I’d love to test motion templates. Is this already available?
    Motion templates is currently in closed beta for select customers. If you would like to join the beta for early testing and feedback, please reach out to your Customer Success Manager.

  2. Are we going to have libraries that are more universal that allow you to do more things that are currently only assigned to one library type currently? For example having a document library that allows you to have document categories, which allows for a visual sub divider on front end, but then allow for background colours to be set on something like a cut out image like a png. Currently we have to upload a jpeg of a cut image with a brand colour set behind for the visual and then add the PNG.
    There are no current plans to remove library types (Media, Document, Icon, etc.). However, we’re actively considering ways to improve and evolve library structures over time.


Automations:

  1. I saw openAI on the automations. Can I add other AI tools instead of openAI?
    At the moment, OpenAI is the only AI provider available as a dedicated Automation action, which can be installed via the Frontify Marketplace. That said, we are actively working on enabling the new action GET requests within Automations, allowing you to connect to external services and tools. This will open the door to integrating other AI tools or workflow platforms (e.g. Zapier or Make) you may already use. If you have a specific tool or use case in mind, please reach out to your Frontify contact so we can explore it together.

  2. If we could get Copilot integrated into Frontify as well, that would greatly assist my company’s broader team since our workflow is already involved with Copilot.
    There are two relevant angles here. First, with upcoming support for the new action GET requests in Automations, it will be possible to connect Automations to external services that already include AI capabilities, which could cover Copilot-based workflows.

    Second, Frontify can already be integrated with Microsoft Copilot via APIs: you can use the Asset Search API to retrieve assets from Frontify and the Guidelines Content API to answer questions or generate content based on your brand guidelines inside Copilot.

  3. So file name conventions can be scanned and their data attributed to custom metadata? For example, having ENG, DAN, CZE in the file name. Can Frontify scan the file name and attribute them to existing custom metadata like English, Danish, Czech, etc.?
    Yes. This is a common use case for Automations in Frontify. File names can be scanned for defined patterns (such as ENG, DAN, or CZE) and mapped to existing custom metadata values.

    It’s important to note that this isn’t automatic or generic language detection. Each abbreviation needs to be explicitly defined as a trigger in an individual Automation rule and then mapped to the corresponding metadata value (for example, ENGEnglish). Once set up, this allows consistent and scalable metadata assignment during asset ingestion, while avoiding manual tagging.

  4. When can we move automations between libraries? We really need this.
    Thanks for sharing this feedback, it’s great to see Automations being actively used for library metadata management. We know that the ability to copy or duplicate Automations across libraries would be a big time-saver, and it’s something we’re actively considering as part of our product roadmap.

    While we don’t have a timeline to share yet, feedback like this helps us prioritize what’s next.

  5. Would be great to apply an automation to another Library, especially when they are quite complex!
    This question can be understood in two ways.

    • First, reusing Automations across libraries: complex Automations are time-consuming to rebuild, and the ability to duplicate or transfer them between libraries would be valuable. This is on our radar, and we’ll share updates once timing is clearer.

    • Second, cross-library actions within an Automation: for example, triggering an Automation in one library that moves or affects assets in another. This is an interesting use case but adds complexity around permissions and metadata consistency. It’s not supported today, but it’s an area we’re considering for future workflows.

  6. Q: This is an AEM killer?
    Automations are definitely a powerful capability, and many customers already use them very extensively to scale how they manage and enrich assets in Frontify. We’re confident that Automations significantly reduce manual work and enable sophisticated workflows that, for many teams, cover a large portion of what they need - especially when working at scale. Compared to solutions like Adobe Experience Manager, we see strong adoption and momentum in how customers are using Automations today.


PIM integration:

  1. Is Akeneo in Frontify marketplace?
    Akeneo is a partner-built integration, so it’s not available directly in the Frontify Marketplace. To get access, you’ll need to reach out to your Customer Success Manager. The integration is set up collaboratively to ensure the data model, metadata, and sync workflows are properly configured for your specific use case.


Guidelines and AI:

  1. Is it planned to enable localized alt texts?
    At the moment, AI translations in Frontify focus on visible guideline content. Alt texts are primarily used for accessibility and SEO and are not directly visible in guidelines, which is why they are not currently included in the localization scope.

    That said, we recognize the value of localized alt texts, especially for global and accessibility-focused teams, and this is something we’re considering for the product roadmap. We’ll share updates as soon as timelines or concrete plans become available.

  2. Do you plan to integrate graphical AI aggregation platforms into Frontify?
    Frontify is expanding Automations to support custom requests and connections to external services, making it possible to link the AI or workflow tools you already use, including graphical AI platforms, into your Frontify processes.

    For more direct or deeper integrations with a specific graphical AI aggregation platform, Frontify’s Apps SDK can be used to build a dedicated app tailored to your needs.

    If you have a particular tool or use case in mind, we recommend reaching out to your Frontify contact so we can help identify the best integration approach.

  3. Q: When will the Copilot integration be available?
    Frontify can already be integrated with Microsoft Copilot today using our APIs. The Asset Search API allows Copilot to retrieve assets from the DAM, while the Guidelines Content API enables Copilot to answer questions or generate content based on your brand guidelines. Many customers implement these integrations using their own engineering resources. A pre-built Copilot integration is not yet available. However, it is on our roadmap and currently planned for the second half of 2026. We’ll share more details as we get closer to release.
    Resources:

Media Delivery

  1. On the dynamic CDN, if you change the asset, how do you ensure that the asset’s focus points are correct in each of the derivatives?
    The focus point defined in the Frontify backend is a metadata returned separately. If this value is dynamically integrated into the target integration, for example, a website or an app, any change to the focus point will be applied instantly and will result in the creation of a new rendition.
    Note that the Media Processing API also offers a Smart Focus feature, which allows Frontify to manage the focus point automatically. This feature is especially useful for user-generated content or large image catalogs.

  2. I can see the usability of dynamic CDN on web, but would this also work with emails or SoMe channels?
    Yes, dynamic CDN works well beyond websites, including email and social media (SoMe) channels. For emails in particular, this is a strong use case. Using the Media Processing API, you can dynamically resize, crop, or optimize images specifically for email without duplicating assets. This helps ensure faster load times and better performance across different devices and email clients. The same approach can be applied to social media channels, where different formats and dimensions are required, while still relying on a single source asset in Frontify.

  3. Is it possible to upload two versions of the same image (a desktop and a mobile version) in Frontify and deliver them through a single dynamic CDN link? And if so, will the front end automatically select the most suitable version based on the user’s device?
    Not yet. But a very similar feature is in the works. Stay tuned!


Frontify Kitchen:

  1. I saw Specs in the Keynote, can I try it or get access to it?
    Specs is something Frontify is currently exploring internally. What you saw in the Keynote was an early prototype that gives a glimpse into how we’re thinking about the future of AI in brand governance and creative workflows.
    While Specs isn’t available to customers today, it reflects the problems we’re actively investing in and the experiences we’re excited to shape over time. As we continue learning and iterating, we’ll share updates if and when there’s something ready to bring to customers.

  2. Where is Specs on Frontify? Can’t see it in the marketplace.
    Specs is currently not available in the Frontify Marketplace. It’s part of an early product initiative where we’re exploring how AI can support creative workflows and brand compliance. Availability and access will be shared as we move closer to a broader rollout.

  3. Is Specs in beta or early access?
    No. Specs is not in beta or early access. It’s still in development, and customers can’t use it yet. We’re validating the concept and experience before defining any beta or rollout plans.

  4. Is this AI tool (Specs) approved for use in China where LLM tools are controlled by the government? This has been an issue with us being unable to use the Brand Assistant.
    Our goal is to make Specs available globally, including regions with specific regulatory requirements. Specs is designed with flexibility in mind, including support for different underlying models where possible.

    Performance and availability may vary by region, and we’re happy to discuss specific compliance or deployment needs. If you have requirements related to China or other regulated markets, please reach out to your Frontify contact so we can review options together.

  5. Can you turn off Specs’ ability to use what it’s learned in your space to train its model?
    Yes. Specs is an opt-in feature, and you’ll have control over what content it can access and how it’s used. Customer data is not used to train shared or external models by default.

    For any capabilities that require processing by third-party providers, you’ll have transparency and control over whether those features are enabled.

  6. So Specs can read and see graphics?
    Yes. Specs can analyze both text and visual elements within graphics.

    It uses vision-language models to understand things like logos and their placement, text content, colors, fonts, and overall layout. This allows Specs to check whether assets follow your brand guidelines, for example, verifying logo usage, color accuracy, font consistency, and text rules.

  7. Can Specs also review visual content, like photos, to double check that they follow brand standards?
    Yes. Specs can review visual content, including photos, to help ensure they align with your brand standards.

    It can analyze imagery against your guidelines and flag potential issues, such as unsuitable subject matter, visual style mismatches, or other defined criteria, as part of your review workflows. This helps surface visual compliance issues earlier, before manual review is needed, similar to how Specs supports checks for logos, fonts, and colors.

  8. Are the Specs features and workflows final?
    No. Specs is still evolving. The capabilities and workflows shared today reflect our current direction, but functionality, scope, and availability may change as development continues.


If you have further questions or would like to explore a specific use case, please reach out to your Frontify contact. We’re happy to help you find the best solution.

Did this answer your question?