Skip to main content

Screens Library: capture once, reuse across every product and brand

Use the Screens Library to capture each product screen once, label it by product and feature, and reuse it across every product, brand and audience in three steps.

Updated Oct 21, 2026

Screens Library: capture once, reuse across every product and brand

One Library. Every Product, Every Brand.​

The Screens Library in the Resource Hub is your company's single source of product screens. Capture a screen once, label it by product and feature, and pull it into any template. Teams stop recapturing the same dashboard for every demo.

It pays off most when one workspace serves several products, brands or partners. Every team builds from the same up-to-date screens. Each demo still gets its own look from a theme and its own story from a preset.

When to use the Screens Library​

  • Multiple products or product lines. Label each screen with its product and feature. Each product team then finds its own screens in seconds, and shared screens (login, settings, admin) are captured once for everyone.
  • Multiple brands on the same product. If several brands sell the same product, they share its screens. Build each brand's templates from the same library screens and give each template that brand's theme.
  • Partners and resellers. Partners build from your official screens instead of capturing their own, so what they show stays accurate.
  • A product UI change. Update the screen once in the library and push it to every template that uses it.

If you only have one product and a handful of templates, importing screens from template to template may be enough. The library is for when you're reusing the same screens across many templates.

Set it up in 3 steps​

1. Fill the library and label it​

  1. Go to Resource Hub → Screens.
  2. Click Capture screens to capture with the Chrome extension, or Promote from template to copy screens you already have into the library.
  3. Label each screen with a Product and a Feature. Walnut prompts you to label screens after you capture or promote them, and you can label many at once from the bulk bar.

Labels are what make one library work for many products. Use Group by → Product and feature to see each product's screens together, and the Used in template filter to see what's actually in use.

2. Build templates from library screens​

  • Start a new template: select screens in the library and click Create template. Walnut can put them in sections by product and feature, in the order you selected them.
  • Add to an existing template: in the editor, open Add screen and switch to the Screens Library tab.

Then make the template right for its audience:

  • Brand: give the template a theme, such as your core brand, a sub-brand or a partner co-brand. Templates built from the same screens can each carry a different theme.
  • Story: put customer names, logos and sample data in variables. A library screen's variables bind to the company-wide variable of the same name and kind, so presets can fill them in for each account or vertical.

3. Keep every template in sync​

Library screens and the templates that use them can now be updated in both directions.

  • From the library to templates. Open a library screen in its own editor and make your change. Then click Update in templates and choose which templates that use it get the new version. If a template changed its own copy of the screen, Walnut keeps that edit and labels the copy Left as edited here. If a template you update is live, anyone with its link sees the new version straight away.
  • From a template to the library. When a template's copy of a library screen has changed, the editor header lets you Update the library with that version. Or choose Keep it local, which saves your version to the library as a screen of its own: handy for a brand- or product-specific variant.
  • With approval on. If your workspace requires approval, updating the library sends a request to a reviewer you pick. The library screen stays unchanged until they approve.

Library screens keep their own version history, so you can restore an earlier version.

Good to know​

  • Who can use it: Editors, Admins and Account Owners.
  • Archiving a library screen doesn't touch templates. Templates that already contain a copy keep it.
  • Links between screens: when you add several screens at once, pick them in flow order. Links to screens you didn't add are cleared, so pull the destination screen in too.

For every tab, filter and action, see Screens in the Resource Hub.

FAQ​

Do I need a separate library for each product or brand? No. Use one library and label screens by product and feature. Brand comes from the template's theme, not from the screen.

If I update a library screen, do templates change automatically? Only when you choose Update in templates and pick the templates. Copies that a template has edited itself are left as they are.

Can a partner have their own version of a screen? Yes. Edit the screen in the partner's template and choose Keep it local. Their version is saved to the library as its own screen, and the original stays as it is.

How does this relate to themes and presets? The library supplies the screens, a theme supplies the look, and a preset supplies the account-specific values. Together, one set of screens covers every product, brand and audience.

Was this helpful?