Share and use a reusable recipe

A recipe shares a way of working: graph structure, supported settings and the selected reusable configurations. It is not a transfer of the author’s whole account, private media library or generated results.

Prepare a recipe to share

Open the studio’s recipe-sharing flow for a working project. Review the proposed graph and every included configuration. Image and Text generator configurations can carry their selected prompt and settings as a snapshot. Review those texts before sharing: a hand-written prompt can contain project-specific content too.

Built-in Elements can be referenced where supported. Personal characters, locations, objects and source files become needs the recipient must supply. Personal skills and restricted settings may be excluded. Read the listed exclusions and incomplete input rows; do not assume an omitted dependency will appear for the recipient.

A source file node (image, video or audio file) that holds one of your studio files shows Give my file with the recipe under its row. It is off by default. Turn it on only for files that are the basis of the recipe, such as the clip the recipe transforms. Anyone who opens the link and builds the project receives that file in their own materials. Files you leave unchecked stay yours, and their nodes arrive empty for the recipient’s own file. Your choice is remembered when you reopen the sharing flow to update the same link.

Restricted administrative workflow cards and their studio-owned step instructions stay out of the recipe layout and attachments. Review any connections listed as excluded; the recipient will not receive those links. Publishing a payload that still contains these protected steps is refused.

Use an example image or description that you intend to share. Keep private names, account material and unrelated project details out of the public recipe. Inspect the final preview and open the resulting recipe link to check what it actually contains.

Use a received recipe

Read its goal, included settings and required inputs first. Choose your own library Element for each role, or follow the offered route to make a new one. Provide your own required media files and an idea where requested. A file the author chose to give is marked as arriving with the project. It is attached to its node when you build and added to your project materials, and you can replace it with your own file on the canvas.

Review the plan before building. Building the graph does not generate the finished media. Inspect the resulting nodes, connections, chosen models and missing inputs, then quote and approve generation steps separately.

A shared generator configuration is a snapshot of the author’s selected settings. A later change to a built-in original does not automatically update that snapshot. Check model availability and current input limits before running an older recipe.

Check the result and keep work independent

Verify that the recipient’s Element names, references and files are connected in the intended places. Review every intermediate image before making video and watch the full finished output.

Through MCP, an agent can inspect the built graph, discover library items, apply supported operations and run supported nodes. MCP has no recipe-publication tool in the current catalogue. Use the browser for the sharing and recipient-choice flow, then use the agent on the resulting project.

See libraries and lore, graph edits and your first video.

Last checked: 22 October 2026. A recipe’s structure and included settings are reusable; availability and generation quality still need current checks.