Free HeyGen AI Prompts for Cooking Tutorial Videos: Examples + How to Use Them

If you want a presenter-led recipe video without standing in front of a camera, HeyGen AI prompts for cooking tutorial videos can get you most of the way. HeyGen is built around AI avatars that speak a script you provide, so your real work is the script, scene notes and pacing. Be clear about a limit: an avatar cannot actually cook. You will need to combine it with real or stock footage of the dish, text overlays and step graphics, and you should check the tool's current features to see what it supports.

Two responsibilities apply. First, if you use an avatar or a cloned voice, only use ones you have consent and rights to, and tell viewers when a presenter is AI-generated. Second, verify every recipe step, temperature and allergen note yourself, since AI scripts can contain errors that matter in a kitchen.

How HeyGen Works for Cooking Videos

Typically you pick an avatar, paste or generate a script, choose a voice and language, set a background or layout, and add media. For cooking, the avatar works well as an intro host, a voice-over presenter in a corner, or a recap narrator, while footage carries the actual technique. Many prompt-based video tools respond to script text more reliably than to long scene descriptions, so write the script first.

The Prompt Formula

[Dish + skill level] + + [structure] + [spoken style] + [on-screen text cues] + [safety notes] + [what to avoid]

| Slot | Example | |—|—| | Dish and level | weeknight tomato soup, beginner | | Length | 90 seconds, about 220 spoken words | | Structure | hook, ingredients, steps, tip, call to action | | Safety | state internal temperatures only if I provide them |

A useful rule: roughly 130 to 160 spoken words per minute is a comfortable pace for most narration.

Basic vs Improved Prompt

Basic: Write a script for a cooking video.

Improved:

Write a 90-second spoken script for a beginner cooking tutorial on [DISH], for home cooks with [EQUIPMENT, e.g. one pot and a knife]. Structure: a 10-second hook naming the result, ingredient list with amounts from my recipe below, five numbered steps with one sentence each, one common mistake and its fix, and a closing line asking viewers to [ACTION]. Friendly, calm tone, short sentences, no jargon. Use only quantities and times from my recipe; mark anything missing as [CHECK]. Add [ON-SCREEN TEXT: ...] cues for each step. Recipe: [PASTE RECIPE]

It limits invention, which is the biggest risk with recipe content.

Script Prompts for Recipe Videos

Hook and intro

Write five alternative 8-second opening lines for a video on [DISH] aimed at [AUDIENCE, e.g. busy students]. Each should promise a specific payoff (time saved, one-pan cleanup, budget) using only facts from this recipe: [PASTE]. Vary the style: question, bold claim you can actually support, mini-story, myth-buster, countdown. Under 20 words each, no exaggeration.

Ingredient walk-through

Turn this ingredient list into a spoken 20-second segment plus matching on-screen text. Group items by when they are used ([GROUP 1], [GROUP 2]), mention one smart substitution only where the recipe allows it, and flag common allergens present (list them from the recipe, do not guess). Ingredients: [PASTE LIST]. Tone: warm and quick.

Step-by-step narration

Convert these recipe steps into narration for a presenter, one step per scene, each 8 to 12 seconds. Include the sensory cue to look for (color, sound, texture) only if it appears in my notes. Add a [B-ROLL: ...] suggestion for each step, such as close-up of onions softening. Steps: [PASTE STEPS]. Keep verbs active, avoid filler like "just" and "simply".

Mistake-proofing segment

Write a 15-second "avoid this mistake" segment for [DISH]: the mistake, why it happens, the fix. Base it on this experience: [YOUR NOTES, e.g. overcrowding the pan makes the mushrooms steam]. Confident but friendly tone. Do not add food-safety claims I did not give you.

Equipment and prep segment

Write a 20-second "before you start" segment for [DISH]: the equipment needed ([EQUIPMENT LIST]), what to prep in advance (chopping, measuring, preheating to [TEMPERATURE FROM MY RECIPE]), and one tip to save cleanup. Calm, organized tone. Use only my details and mark any gap as [CHECK]. Add an on-screen checklist with up to six items.

Starting with prep mirrors how cooks actually work and keeps viewers from missing a step.

Scene and Layout Prompts

Presenter layout

Suggest a scene layout for a 16:9 cooking video: presenter avatar in the lower-right corner at about 25 percent width, large area for step footage, lower-third text for each step title, ingredient list panel appearing at the start. Palette: [COLORS], font style: clean sans-serif. Provide a scene-by-scene table with duration, visual, narration and text overlay.

Vertical short version

Rewrite the script for a 9:16 short for [PLATFORM]: 35 seconds, hook in the first 3 seconds, three key steps, one finishing tip, and on-screen captions of up to 6 words each. Keep the same recipe facts. Add safe-zone guidance so captions avoid the bottom area where interface buttons appear.

Multi-language adaptation

Adapt this narration for [LANGUAGE] speakers in [REGION], using local ingredient names where equivalents exist and noting where measurements should be converted to [METRIC/US]. Do not change quantities unless I confirm the conversion. Flag any step that could change in meaning. Script: [PASTE]

Have a fluent speaker review translations before publishing.

Series and Content Planning

Plan a six-episode beginner series called [SERIES NAME] with one dish per episode that build skills: knife basics, sauteing, roasting, simple sauces, baking basics, meal prep. For each: dish, the single skill taught, estimated video length, and a hook line. Keep ingredients budget-friendly for [REGION].

A Multi-Step Workflow

1. Lock the recipe. Cook it yourself and write down exact amounts, times and temperatures.
2. Script prompt. Use the improved prompt with your recipe pasted in.
3. Fact check. Ask the model: List each quantity, time and temperature in this script and whether it appears in my recipe. Then verify by hand.
4. Scene table. Run the layout prompt to match narration with footage.
5. Build in HeyGen. Add the avatar, voice, footage, captions and lower-thirds.
6. Disclosure and review. Add a short note such as "Presented by an AI avatar" where appropriate, then watch the whole video once with sound off and once with sound on.

Tips and Common Mistakes

• Treating the avatar as the cook. Show real food; the avatar narrates.
• Unchecked temperatures. Safe cooking temperatures matter, so confirm them against authoritative food-safety guidance.
• Overlong scripts. Count words against your target runtime.
• Missing allergen notes. State allergens from your own recipe.
• Using someone else's likeness. Only use avatars and voices you have permission to use.
• No disclosure. Be upfront about AI-generated presenters.

For related video ideas, see Fliki AI prompts for social media reels and Kaiber AI prompts for travel vlogs.

FAQ

Can HeyGen show the dish being cooked?

Its avatars present and speak. Combine them with your own footage or stock clips for the cooking itself, and check current features for media options.

How long should a cooking tutorial be?

Short formats of 30 to 90 seconds suit social platforms, while detailed lessons can run longer. Match length to the platform and skill taught.

Do I need to disclose an AI presenter?

It is good practice and sometimes required by platform rules. Check the current policies where you publish.

Can AI write the recipe too?

It can draft one, but cook it yourself first and verify quantities, times and safety details.

Can I use my own face or voice?

Many tools offer this, subject to their consent steps. Check the current process and terms.

Conclusion

A strong HeyGen cooking video comes from a tested recipe, a tight script and honest framing. Use the prompts above to draft the narration, plan scenes, adapt for vertical and other languages, and always verify food details before you publish.