.svg){kind=logo}
Aligning everyone on design delivery
Centralize your design documentation. Stakeholders can view fixed designs without a Zeplin login.
Confluence users can see Zeplin resources with full context on Confluence pages without logging in to Zeplin. All stakeholders can offer input and value at design handoff, so that designers can make sure their products are solving the right problems.
Try Zeplin for Confluence Pro.webp)
Blend the power of Confluence and Zeplin to create a design system that’s accessible, scalable, and easy to maintain. Embed screens, scenes & components from Zeplin, which users can view and download directly from Confluence.
Display fixed assets in your design system with full version control. Changes in Zeplin won’t propagate to Confluence unless the designer updates the version. This helps users keep track of changes to the design system and maintains the integrity of the documentation.
Resources are pinned to your Confluence page and won’t automatically change. Confluence users can switch between versions to see how designs have evolved over time. You also have the option of disabling this feature so that the latest version is always shown.
Embed resources using different display types. A collapsible panel, the frameless view when space is limited (e.g. in a table column) or the native Zeplin embedder view (requires logging in to Zeplin).
Use the full-screen interactive viewer to drag and zoom in on a resource. Scale to the actual size when you need specific dimensions. You can also open an information panel containing extra details (version, dimensions, link ect) about the resource.
Anyone with access to the Confluence page is able to see the embedded Zeplin resources. No Zeplin logging required!
Zeplin for Confluence Pro works with Confluence Cloud and Confluence Data Center.
The app is aimed at designers who use Confluence to create and share design documentation with other teams. Embedding Zeplin resources in Confluence pages, lets stakeholders who don’t have a Zeplin license collaborate on designs and offer feedback to design teams.
It’s also aimed at designers, developers, and other stakeholders who want to use Confluence as their design system. It lets users view and download components and brand assets directly from Confluence rather than Zeplin.
We mean that when you embed a Zeplin resource in a Confluence page using our app, the design shown is permanently displayed and changes made in Zeplin won’t reflect in Confluence. It is only by selecting and pinning a new version that the design will change.
It would impact the integrity of your design documentation and make it harder for stakeholders to use and rely on it. Constantly changing assets can lead to, for example, different versions of a logo being used in the same sales campaign.
Yes. We don’t believe Zeplin is the right place for creating design documentation or building design systems. Zeplin is a designer’s tool; it’s not a general team workspace. It’s also very expensive to buy Zeplin licenses for team members who hardly ever work in Zeplin. Confluence is a neutral, central space for creating and storing general team documentation and collaborating on it. So if you create your design documentation there, and embed Zeplin resources with our app, people are more likely to engage with it.
Yes, you can embed public and private resources. A key benefit of our app is that Confluence users can access private resources without logging in.
Only one user needs to have a Zeplin account with access to the resources to be embedded. This user needs to authenticate the app to enable other users to view resources without logging in.
Our documentation offers step-by-step instructions for the Zeplin for Confluence authentication method.
Of course! Just ask.