Technical specifications for interfaces

Last updated on Aug 7, 2026

Learn about the technical specifications for the Interfaces feature in Adobe Firefly.

   Interfaces is a beta feature in Adobe Firefly now available for testing and feedback.

Supported nodes

All nodes are supported in interfaces except these:

  • Nodes that are in Alpha or marked for deprecation.
  • Nodes and workflows requiring XMP files as defaults are currently unsupported and will be supported in the future.
  • Preview and Output text nodes, as they are not relevant for interfaces.

Unsupported workflow capabilities in interfaces

Workflow capability

Scope and recommendation

Any action the interface user takes that changes the ports and connections in the underlying node graph, such as:

  • Changing data merge templates
  • Changing models in the Generate image and Modify image nodes
  • Changing parameters in some custom nodes.

Unsupported, and it's recommended that the interface author hide all such nodes and node options.

Sending output files to different file locations

If multiple output types, such as .indd and .jpg files, are produced by the interface, it's recommended to send all of them to the same location.

Multiple independent node graphs in an interface

Only one interconnected node graph is accepted per interface, and multiple independent subgraphs in the same interface are not supported.

Best practices for interface authors

  • Add a name, description, and cover image when creating an interface. If you don't add a cover image, users will see a default image.
  • Clear all the Output file nodes to the default Your files location, and add the node to the interface before publishing to avoid storage permission issues.
  • Make changes only in the Workflow tab. The Interface (Beta) tab is for viewing the final user experience only.
  • Save workflow .json files before publishing interfaces, as there's no way to edit an existing interface. You must unpublish the old interface, create the workflow, and publish a new interface. Saving the workflow .json file helps you avoid starting from scratch.
  • Test the underlying workflow before publishing an interface. After publishing the interface, test the interface to confirm it runs correctly.
  • Before publishing an interface, remove any assets from the workflow node graph you don't want users to see as defaults.
  • Unpublish interfaces that your organization no longer needs to keep the home page clean.