Cooking & Food

Cooking & Recipe Video Script Template

A script template for recipe and cooking videos that transforms a dish into a story — with a written example using carbonara, format-specific anti-patterns, and creator archetype breakdowns.

Sample Hook

"Most recipes online get one specific thing wrong about this dish. Here's what it is, and the fix that actually changes the result."

Cooking & Recipe Video Script Template

Use for recipe videos, cooking tutorials, technique breakdowns, and "I tried making X" formats. Works for home cooking, restaurant-quality recreations, and food science content.


Creator Archetypes

Joshua Weissman

Weissman's "but better" format raises Outcome Debt immediately and specifically: viewers know the goal (beat the restaurant version), they know the benchmark (the original product), and they'll stay to see whether he actually achieves it. The specific challenge — "can homemade beat fast food?" — is a question most viewers have had and never answered themselves. His vulnerability about process is structural, not performative: "this took me three attempts" is trust-building because it signals the recipe has already been stress-tested. Viewers who have failed to recreate a dish at home recognize the cost being described and trust the process that followed it.

Ethan Chlebowski

Chlebowski runs the test himself before making any recommendation. He'll make four versions of a dish with one variable changed — fat type, salt timing, resting temperature — and taste them against each other. This makes his recommendations non-arbitrary in a format flooded with arbitrary claims. His structure follows hypothesis → test → result → application, which creates a specific kind of Knowledge Debt: viewers don't know what the test will find, and the finding is genuinely uncertain until he reveals it. The revelation is the retention mechanism, not the recipe itself.


Written Example: Carbonara

This section is written out in full — no brackets. Use it as a model for how to execute the hook, stakes, and critical technique sections.

The problem with most carbonara recipes isn't the technique. It's the eggs — specifically, the fact that almost every recipe undersells exactly how different the dish becomes depending on what happens to those eggs in the last 60 seconds.

Here's what carbonara actually is before we talk about how to make it: it's an emulsion. Not a cream sauce — there is no cream in carbonara, and if you've been told otherwise, you were making a different dish. The sauce is made entirely from egg yolks, aged cheese, rendered pork fat, and starchy pasta water. The emulsion is what makes it silky rather than scrambled. And it only forms in a narrow temperature window: hot enough to thicken, too hot and you get egg ribbons. The margin is about 15 seconds.

Every ingredient has a specific job, and substituting without understanding the job will change the dish in ways you'll feel before you can name.

The guanciale — cured pork cheek — renders slowly in a dry pan to produce fat with a specific flavor that pancetta and bacon can't replicate. The reason isn't tradition; it's chemistry. Cured jowl has lower water content than belly or back. Lower water content means the fat integrates into the emulsion instead of breaking it. You can use pancetta and the dish will be good. It won't be carbonara.

The cheese: equal parts Pecorino Romano and Parmigiano-Reggiano. Pecorino alone is sharp and salty. Parmigiano alone is nutty and mild. Combined, the sauce has both edges and depth. The balance becomes more noticeable as the dish cools — if you're using all Pecorino, the saltiness accumulates in a way that reads as harshness rather than seasoning. Use both.

The pasta water is your control variable. It has to be genuinely starchy, which means cooking pasta in less water than you think — the ratio on the package box is wrong for this dish — in the pan you'll use to finish the sauce, and you should save twice as much as you think you'll need. The starch is what stabilizes the emulsion when the temperature moves.

The eggs: three yolks and one whole egg per two servings. The yolk-to-white ratio changes both the richness and the stability. More yolks means richer sauce with a lower threshold for scrambling. This ratio gives you a sauce that coats the pasta and doesn't tighten into a clump as it cools.

The critical technique: take the pan off the heat before adding the egg mixture. The residual heat from the pasta, the rendered guanciale, and the hot pan is what sets the sauce. If the pan is still on a burner when the eggs go in, they will scramble. Off the heat, add the egg and cheese mixture, add a splash of pasta water, and agitate the pan constantly — tilting and rotating, not stirring — until the sauce ribbons slowly from a spoon. That consistency is the target. From there, serve immediately.


The Template


Hook (0:00–0:20)

Option A — The method claim:

"Most [dish] recipes online get [one specific technical element] wrong. The result is [flavor/texture problem]. Here's the version that fixes it."

Option B — The result-first hook:

"I've made [dish] probably a hundred times. This is the version I'll make for the rest of my life. Here's what's different about it."

Option C — The challenge hook:

"I tried to recreate [famous restaurant/brand]'s [dish] at home. It took [X attempts]. Here's what I figured out on the third try that made it work."


Stakes (0:20–0:50)

State the specific problem with the way most people make this dish — not vaguely, but the exact point of failure.

"The specific issue with most [dish] recipes is [technical problem]. The result is [sensory problem — too bland, too dry, the sauce breaks]. What I'm showing you today fixes [that specific problem] without [common tradeoff people accept]."


Ingredient Overview (0:50–2:00)

Don't list ingredients — explain what each one is doing. Every ingredient earns its place.

"[Ingredient] does [specific job] in this dish. Most recipes use [common substitute], but [your ingredient] gives you [specific outcome] that [substitute] can't. Here's why: [brief mechanism]."

This creates micro-engagement through the setup phase. Viewers who understand the why behind each ingredient feel like they're learning, not just watching a list.


Method: Section 1 — Prep and Setup

Step-by-step with reasoning embedded:

"Start by [step]. The reason you do this before [other step] is [explanation]. The thing most people skip here is [critical detail] — and skipping it causes [specific problem] at the end."

Bridge: "Once you have that done, here's where most people make the mistake that affects the whole dish..."


Method: Section 2 — The Critical Technique

Every dish has one step where the difference between good and genuinely great happens. This is your highest-retention section — give it the most time.

"This is the step that changes everything. [Technique]. Here's the mechanism: [specific science or process explanation]. What you're watching for is [specific visual/audio/tactile cue]. When you see that, [what to do next]."

Show close-up footage. Show what the right version looks like and, if possible, what the wrong version looks like. The contrast is the teaching.


Method: Section 3 — Cooking and Assembly

Narrate the sensory cues rather than just the steps:

"You're looking for [visual cue]. When you see [cue], that means [what's happening chemically or physically], and it's time to [next action]."


The Reveal (Final 90 Seconds)

The plating, tasting, and genuine reaction. This is the highest-retention section because viewers have been anticipating it since the hook.

"[Taste reaction — specific, not performative.] What you're getting there is [specific flavor note]. That's directly from [specific technique or ingredient from earlier in the video]."

Close the loops you opened in the hook. If you said a specific thing was wrong with most recipes, show that your version doesn't have that problem.


CTA

"If you want to make [related dish that uses a similar technique], I've got that video [here / linked below]. And if you make this one, send me a photo — I'm serious, I want to see it."


What Kills This Format

1. Listing ingredients without explaining the why. "Add 150g of guanciale" tells the viewer what to do but not why guanciale rather than pancetta, not why 150g rather than 100g. A recipe without reasoning is just instructions. A recipe with reasoning is education. Viewers who understand the mechanism can adapt when they don't have the exact ingredient — and they trust you more for treating them as someone who can understand the reason.

2. Skipping the failure point. Every dish has one step where most people fail. Most recipe videos rush past it or note it with "be careful here." Name the failure mode explicitly: "this is where you will scramble the eggs if you're not paying attention, and here's specifically what to watch for." The "what to watch for" is what makes the warning actionable rather than just anxiety-producing.

3. Ending before the real taste reaction. The reveal — the moment you taste the finished dish — is the payoff the viewer came for. Everything before it is setup. If you cut away after plating, or if your taste reaction is perfunctory ("mmm, that's good"), you've squandered the moment that makes the whole video feel worth watching. The taste reaction should be specific: name the flavor note, name the texture, connect it back to something you did earlier in the video. "That richness is from taking the pan off the heat before adding the eggs" closes the loop the recipe opened.


Quick Reference

  • Recipe videos rank in Google as well as YouTube — write your description with the full recipe in it, including quantities and times
  • "Easy [dish] recipe" and "the best [dish]" are your highest-volume title formats
  • Tasting reactions filmed genuinely outperform performed reactions — viewers can tell the difference

Want this written for your specific video?

YouScript uses this structure to write a complete script in your voice — with your hook, your transitions, and your CTA. Takes 15 minutes.

Generate my script free →

First 3 scripts free. No credit card required.