# Use prompt recipes for common videos Source: https://www.ngram.com/docs/prompt-recipes Published: 2026-08-06T00:00:00Z Updated: 2026-10-19T00:00:00Z Use privacy-safe prompt templates for product demos, explainers, updates, social clips, training, and presenter videos. Start here Start with a fill-in brief for a demo, explainer, update, social clip, training video, or presenter-led story—then replace every bracket with your own approved information. Use a recipe to create a product demo from screenshots and a recording, or an explainer from a deck and a public product page. [Try a recipe](https://www.ngram.com/app) [All docs](https://www.ngram.com/docs) ## Read before this Read these direct prerequisites in order. Each guide lists any earlier context it assumes. 1. [1 Write better prompts Brief the goal, audience, sources, format, and constraints.](https://www.ngram.com/docs/writing-better-prompts) 2. [2 Sources and attachments Ground videos in URLs, documents, images, audio, and recordings.](https://www.ngram.com/docs/sources-and-attachments) [Choose from five finished video examples and adaptable briefs](https://www.ngram.com/docs/video-examples-and-briefs) ## Use this when you need a complete starting brief Use a recipe when you know the video outcome but are unsure how to describe the audience, source priority, structure, visuals, length, and call to action. For a product demo or explainer, you can ground the brief in a screen recording, ordered screenshots, a deck, a public URL, approved product assets, or a combination with clearly assigned roles. ## Before you start You can prepare the brief while signed out. To follow the workflow in Studio, sign in, open Home, and use an account or team context where you are allowed to create. Have approved source material ready before you submit a factual video. ## Before you paste a recipe Replace every bracketed placeholder. Attach the referenced files, remove instructions you do not need, and never paste secrets or material you are not permitted to process. These are newly written generic recipes, not customer prompts. ## Product demo from recordings, screenshots, decks, URLs, or assets Create a \[45–90\]-second 16:9 product demo for \[audience\]. Use \[recording or ordered screenshots\] as the visual source, \[deck, document, or public URL\] as the factual source, and \[approved product assets\] only where they support the real workflow. Show the workflow in \[number\] steps, zoom in when an important control is used, remove dead time, and keep the narration \[tone\]. Preserve the actual order of actions. End with \[CTA\]. ## Explainer from a URL or document Create a \[duration\] explainer for \[audience\] who need to understand \[topic\]. Use \[attached file or public URL\] as the source of truth. Open with \[problem\], explain \[three key ideas\], and close with \[next step\]. Use a \[visual direction\] style in \[aspect ratio\]. Do not add claims that are not supported by the source. ## Product update or launch Create a \[duration\] update video for current users. Use the attached release notes and approved screenshots. Explain what changed, who benefits, and how to use it in \[number\] steps. Prioritize \[must-show change\]. Keep \[secondary detail\] brief. Use a direct, useful tone and end with \[CTA\]. ## Short social video Create a \[15–45\]-second \[9:16 or 1:1\] social video for \[audience\]. The single takeaway is \[message\]. Start with \[hook\], use concise on-screen text that works without sound, and end with \[CTA\]. Use \[source\] for facts and \[approved assets\] for visuals. Keep the pacing energetic without cutting away from information before it can be read. ## Training or how-to video Create a \[duration\] training video for \[role and experience level\]. By the end, the viewer should be able to \[observable task\]. Use \[source\] and teach the workflow in this order: \[steps\]. Define unfamiliar terms, show each required action, include \[warning or checkpoint\], and finish with a short recap. ## Presenter or avatar video Create a \[duration\] presenter-led video for \[audience\]. The presenter should sound \[tone\] and explain \[message\] in \[number\] sections. Use \[source\] for facts, pronounce \[terms\] as written, and support the presenter with \[graphics, captions, or product footage\]. End with \[CTA\]. Use only the voice and likeness I am authorized to publish. ## Run the recipe 1. Choose the recipe closest to the outcome, not merely the subject. 2. Replace every placeholder and delete unused clauses. 3. Open Home, choose Prompt to video, paste the completed recipe into Video brief, and attach the named sources. Review Model, Voice, Presenter, Length, and Format before choosing Create video. 4. Review the Script and Production details in the plan. Request any changes, then choose Approve plan when the direction is right. 5. Review the result against the audience, outcome, source, must-haves, and CTA before revising local details. ## Expected result The plan should identify the intended audience, follow the requested structure, use the named sources for their assigned roles, and end with the requested call to action. Review those decisions before generating the video or asking for a replacement. ## If the recipe misses the brief Keep the current project and compare it with the audience, outcome, source priority, must-show steps, and CTA in your filled recipe. Correct the single missing decision and retry only the smallest affected step or scene once. Use Fix a prompt for a working result that needs better direction. Contact Support when an attached source repeatedly cannot be read, an instruction still does not apply after that targeted retry, or a technical failure blocks the workflow; include the project URL, approximate time, affected source type, and last visible state. ## A product walkthrough with browser handoff Browse \[product-url\] and show \[workflow\] for \[audience\] using the real interface. I will sign in when asked. After I choose Done, capture the relevant screens. Use \[approved-facts\] for the explanation and end with \[next-step\]. ## A question-and-answer conversation Create a scripted conversation about \[topic\] for \[audience\]. Let \[questioner\] ask \[questions\] and \[expert\] explain \[approved-answers\] from \[source\]. Use distinct voices and the source visuals that support each answer. End with \[next-step\]. ## Explain an existing recording Use \[recording\] and keep \[selected-passage\]. Preserve the original speech. Add labels for \[key-terms\] and a short diagram for \[concept\], then return to the footage in sync. Keep the other passages clean. ## A mechanical explanation Use Machine anatomy to explain \[mechanism\] for \[audience\]. Use \[technical-source\] for the facts, label \[parts\] and show \[movement-or-flow\] in order. Review the terminology and relationships against the reference. ## Presenter emphasis for a short video Create a presenter explanation of \[idea\]. Keep the presenter large and place \[key-words\] behind the head and shoulders at selected moments. Use \[source\] for facts and end with \[CTA\]. Keep ordinary subtitles \[on/off\]. ## Prompt recipe FAQ ### Can I create a product demo from screenshots instead of a recording? Yes. Put the screenshots in workflow order, identify them as the visual source, and use a document, deck, or public URL for facts when the screenshots do not contain enough explanation. ### Can I make an explainer from a slide deck or website? Yes. Attach the deck or provide a public URL, state that it is the factual source, and name the audience, key ideas, target length, and next action. Review extracted facts before generating the final video. ### How should I combine a recording, deck, URL, and product assets? Assign one role to each source: for example, the recording controls the workflow, the deck or URL controls facts and structure, and approved assets supply visuals. State which source wins if they disagree. ### What should I do if the result ignores part of the recipe? Keep the current project, restate the single missing priority, and retry only the affected step or scene once. Contact Support if the same explicit instruction or readable source is ignored again. ## Keep going [Write a better video prompt Write prompts that produce stronger scripts, visuals, pacing, and revisions.](https://www.ngram.com/docs/writing-better-prompts) [Use sources and attachments Add URLs, documents, images, recordings, and other reference material to a video request.](https://www.ngram.com/docs/sources-and-attachments) [Create your first video Create a first ngram video from the current Home and agentic workflow.](https://www.ngram.com/docs/creating-your-first-video) [Fix a prompt that missed the brief Diagnose a weak result and improve the prompt, sources, storyboard, or targeted revision.](https://www.ngram.com/docs/fix-a-prompt) [Five video examples and briefs Choose a structure from finished ngram examples.](https://www.ngram.com/docs/video-examples-and-briefs) ## Continue in ngram Open the relevant Studio surface and follow the current controls shown in your account. [Try a recipe](https://www.ngram.com/app)