Skip to main content

Build a demo from screenshots

Updated Oct 13, 2026

Build a demo from screenshots

Overview​

Build a Walnut demo straight from a batch of screenshots. Drop the images into the import flow and each one becomes a Walnut screen, in the order you picked them. Walnut then connects the screens with hotspots so the demo already clicks through end to end — no need to place links by hand before you start editing.

Where Walnut can tell what changed between two consecutive screenshots, it uses that difference to guess where the click happened on the first screen and anchors the hotspot there. Screens that look identical are left unlinked, and so are pairs where the change doesn't look like a single click target — you add those links yourself.

Import Screenshots Into a Demo​

The screenshot importer lives in the editor's import flow, alongside the Figma and PowerPoint sources.

  1. Open a demo (or create a new one) and open the import flow.
  2. Pick screenshots or a recording as the source.
  3. Drop in your image files, or pick them from your machine. Supported formats: PNG, JPG, WebP.
  4. Review the list of files Walnut picked up. Remove anything you don't want to import, and reorder files so the sequence matches the flow a viewer should click through.
  5. Pick a target section for the imported screens — either an existing section in the demo, or let Walnut create a new one in place.
  6. Confirm the import. Screens appear in the editor as soon as they are created, and the first ready screen opens so you can start editing while the rest finish in the background.

Each image is uploaded, converted into a Walnut screen, and placed in the chosen section in the order you picked.

Automatic Hotspots Between Screens​

Once the screens are in, Walnut walks the imported sequence and tries to add a hotspot on each screen that links to the next one:

  • For every consecutive pair, Walnut compares the two images and finds the region that changed.
  • When the change looks like a single clickable UI element (a button, link, tab, menu item, field), Walnut asks a vision model to box that element on the first screen and anchors a hotspot there pointing to the next screen.
  • When the two screens look the same, no link is added — there's nothing to click.
  • When the change is spread across the whole screen (a full-page navigation, several things moving at once) and the model can't single out one target, Walnut skips that pair rather than guess, so you can place the hotspot yourself.
  • A screen that already has a custom element on it from a previous edit is left alone.

Automatic hotspots use the same AI budget as other AI features in Walnut — track usage in AI Control Center → Usage.

Edit the Imported Screens Like Any Other Screen​

Once the screens land, each one behaves like any other Walnut screen:

  • Reorder, rename, or move screens between sections.
  • Edit, move, resize, or delete the automatic hotspots, or add new ones.
  • Add guides and annotations on top of the screenshot.
  • Attach sticky notes for reviewers.
  • Personalize with variables.

Screenshot screens are flat images, so there is no editable HTML text on them. To make a specific element editable, use Make editable on the screen to convert the image region into an interactive element.

Import Limits​

  • Up to 100 images per import.
  • Each image can be up to 50 MB.
  • A video imports on its own, one per import — if you include a video, upload the screenshots in a separate import.
  • Images that fail validation (wrong file type, too large, over the batch cap) are listed in the review step with the reason, and the rest of the batch still imports.

FAQs​

Which file types can I upload?​

Images: PNG, JPG / JPEG, WebP. Videos (uploaded separately): MP4, MOV, WebM.

In what order do the screens appear?​

In the order you picked them in the review step. Reorder files there before confirming to control the sequence a viewer will click through.

Can I mix screenshots with other kinds of screens in the same demo?​

Yes. Imported screenshot screens live alongside captured screens, Figma-imported screens, and PowerPoint / PDF slides in the same demo.

Walnut didn't add a hotspot between two of my screens. Why?​

Either the two screenshots look identical to Walnut, or the change between them is spread too wide to point at a single click target. In both cases Walnut leaves the pair unlinked — add the hotspot yourself in the editor.

The hotspot landed in the wrong place. Can I fix it?​

Yes. Automatic hotspots are regular Walnut hotspots — select the hotspot and drag it to the right element, resize it, or delete it and draw a new one.

Was this helpful?