Figma Make buying guide: You can rename the copied button. Did its interaction come along?
Bring a Make preview into Figma Design to keep working on its appearance. Use three fictional state cards to distinguish editable layers from behavior that needs its own handoff.
Design colleagues who receive a preview may assume they all received the same thing. One wants to change a heading; another wants to know what a button does in an edge case. The official announcement for Figma Make describes bringing previews into Figma Design as editable layers. The official help documentation makes a further distinction: copied layers are a snapshot of that moment and do not retain their original interactions in Design. Editing them does not update the Make prototype either. They suit layout changes; a handoff of functional rules needs separate evidence.
Ask the recipient to explain the empty, success, and return states
Sketch a “Check legend” panel for a fictional paper-art exhibition. Empty input should leave the user at a hint; selecting a symbol should show its explanation; returning from the explanation should restore the previous selection. Separately draw the success state, with a button and heading that can be edited independently. Give those two paper drafts to a colleague separately. The visual alone shows where the button sits and how to change the text, but does not tell them whether empty input shows a hint or what survives on return. Next, change “Check legend” to “View symbols” only on the visual and ask what the original behavior notes still call it. If each person relies on their own version, the editable visual and behavior notes have drifted apart at handoff. This is a hand-drawn exercise, with no prototype run, connected, or published.
Decide what the handoff must answer before copying layers
For a review limited to spacing, wording, or layout, an editable snapshot is more useful than a plain screenshot. If you need to judge transitions, keep a table of “starting state | action | expected state” and put the confirmed revision beside the behavior notes. Use the copied layers as visual material, not as a reason to skip the record. If the team only needs to discuss one static composition, editing the existing Design draft may be simpler than maintaining an extra Make preview. Check that the plan offers the copying permissions you need; even with permission, the two materials do not become one interactive deliverable.
Content note:This article is based on publicly available information and is intended as a reference for evaluating tools. Features, pricing, and related policies may change at any time; please refer to the latest official information.
Original source:www.figma.com