Screens in the Resource Hub

Capture or promote screens into the Resource Hub Screens Library, reuse them across templates, label and filter them, and push edits with Update in templates.

Updated Nov 5, 2026

Screens in the Resource Hub

The Resource Hub's Screens tab is your company's shared library of captured screens. Capture or promote a screen once, label and organize it, then pull it into as many templates as you like — without recapturing it each time.

Running several products, brands or partners from one workspace? See Screens Library: capture once, reuse across every product and brand for when to use the library and how it works with themes and presets.

Snapshot

Role Access: Editor, Admin, or Account Owner
Location: Resource Hub → Screens tab

Key features

A flat, company-wide library of screens that lives beside Media, Variables and Presets in the Resource Hub
Fill the library by capturing a screen with the Chrome extension, or Promote from template to pull a screen that already lives in a template
Reuse the same screen in any number of templates, in one click from the editor
Organize screens with Product and Feature labels, group by product and feature, creator or month
Filter by product, feature, creator, template a screen is used in, date added and last modified
Search by screen name across the entire library (case-insensitive, substring)
Switch between Grid and List views
Bulk-select to archive, label, or spin a new template out of a group of screens
A details side panel shows every template a screen is currently used in

Open the Screens tab

Click Resource Hub in the main navigation, then open the Screens tab. The counter next to the title shows how many screens the current filters match.

Fill the library

The header offers two ways to add screens:

Capture screens — opens the Walnut Chrome extension flow and brings new captures straight into the library (shown as Capture new when media import is available, which also lets you upload or import files from the same picker).
Promote from template — pick an existing template and the screens inside it to copy up into the library. The original screens in the template stay where they are; the library gets its own copies that can then be reused anywhere.

Both options are also offered from the empty state when the library has no screens yet.

Reuse a screen in a template

Inside a template editor, open the Add screen dialog and switch to the Screens Library tab. Pick one or more screens and confirm — Walnut copies them into the current template at the position you added them from.

A few things to know:

Pick order matters. Links between screens you pick together are repaired in the order you selected them, so the second-picked screen is the one the first-picked screen's buttons will land on.
Links to screens you didn't pick are cleared — the picker warns you about the links it can resolve so you can decide whether to pull the destination in too.
Variables on the screen bind to a company-wide variable of the same name and kind if one exists; otherwise a template-local variable of that name is created automatically. If the template already uses the name for a different kind of variable, the copy is stopped and the conflict is named.
Custom HTML snippets and screen text translations travel with the screen.

You can also create a new template directly from a selection in the Screens tab — see Bulk actions below.

Keep library screens and templates in sync

Library screens and the templates that use them can 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, that edit is kept and the copy is shown as 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 offers Update the library (the library screen takes this template's version) or Keep it local (your version is saved to the library as a screen of its own).
With approval on. If your workspace requires approval, updating the library sends a request to a reviewer you pick, and the library screen is unchanged until it is approved.

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

Organize with labels, grouping and sorting

Screens carry two kinds of labels — Product and Feature — assigned from the card menu, the details panel, or the bulk bar. The left panel exposes:

Group by — Product and feature, Creator, Month, or Ungrouped
Sort — order the grid or list
Filters — Product, Feature, Creator, Used in template, Date added, Last modified

Clicking a label chip on a card replaces the current label filter with that one — a quick jump to everything carrying the same label.

Filter choices are saved per browser, so the library opens with your last view.

Use the search box above the grid to find screens by name. Search runs on the server across the entire library — not just the current folder or the pages you've already scrolled through — and keeps the library's last-updated ordering.

If nothing matches, Walnut shows No screens in your library match that name with a Clear search button, instead of the empty-library state.

Switch between Grid and List

Use the toggle in the top-right to switch:

Grid view — thumbnail cards, grouped by whatever Group by is set to.
List view — a table with sortable columns, ideal for large libraries.

Bulk actions

Hover a screen to reveal its checkbox and select it. Select more than one, and a floating bar appears at the foot of the page with:

Select all / Deselect all — toggles every screen the grid currently shows.
Archive — removes the selected screens from the library.
Label — assigns a Product or Feature label to the selection.
Create template — opens the new-template modal pre-filled with the selected screens, copied in the order you selected them (same contract as the editor picker).

Selecting a whole group's heading selects every loaded screen in that group; if more of the group has yet to load, Walnut tells you so.

Per-screen actions and the details panel

Click a screen to open the details side panel. From the card menu or the panel you can:

Rename the screen (undo restores the previous name and name source — capture-generated, AI, or user).
Duplicate the screen in the library.
Archive the screen.

The panel's Used in list names every template currently using this screen. Archived templates, and archived copies inside live templates, are excluded.

Rename, archive, label and duplicate actions share a single undo/redo history for the whole page, so you can walk back the last change from the bulk bar, the card menu or the panel.

FAQs

Who can use the Screens tab?

Any team member with an Editor, Admin or Account Owner role.

Does editing a library screen update the templates already using it?

Not automatically. A screen copied from the library into a template is that template's own copy. To push a library edit, click Update in templates on the library screen and pick the templates. Copies a template has edited itself are left as they are.

What's the difference between the Screens tab and "Import screens" inside a template?

The Screens tab is a company-wide library you fill once and reuse. Import screens inside a template copies screens directly from one template to another without going through the library. See Import screens from the screens library for the template-to-template flow.

I added a screen but the destination of one of its buttons is empty.

That link pointed at a screen that isn't in your target template and wasn't included in the picker. Pull the destination screen in too and the link will resolve.

What happens to variables on a library screen when I copy it into a template?

If a company-wide variable with the same name and kind exists, the screen's binding is attached to it. Otherwise Walnut creates a template-local variable of that name in the destination template. If the template already owns a variable of that name under a different type, the copy stops and names the conflicting variable so you can rename one and try again.

Can I search inside a folder only?

Opening a folder with no search term shows only that folder's screens. Running a name search spans the entire library — the whole point of the search box is to find a screen wherever it lives.

What happens when I archive a screen?

The screen is removed from the Screens tab and no longer appears as a co-pick suggestion or in a template's Used in list. Templates that already contain a copy are unaffected — the copy inside the template is independent of the library.

Related to:

resource hub screens library screens templates labels capture promote variables

Was this helpful?