Runway Tutorial: Your First 10 Minutes

So you signed up for Runway, opened the dashboard, and immediately felt a little lost. I did too the first time. There are buttons everywhere, the model names sound like robot serial numbers, and your credits start ticking the moment you press generate. This Runway tutorial is the version I wish someone had handed me on day one, written so you can make a real video clip in your first 10 minutes without wasting half your credits on accidents.

I'm going to keep this practical. No theory, no fluff. Just the exact steps, what each part means, and the small mistakes that cost beginners money.

What you actually get on the free plan

Runway's free plan gives you a one-time batch of credits (around 125 as of early 2026), which is enough to test the tool but not enough to make much. One second of the newest Gen-4.5 model costs roughly 25 credits, so that free pile disappears fast if you go straight for the fanciest option. If you decide you like it, the Standard plan runs about $12 a month billed annually (closer to $15 month-to-month) and gives you 625 credits monthly.

Here's the catch I want you to know upfront: credits do not roll over. Whatever you don't use that month is gone. So there's no point hoarding them.

Step one: start with the right model

From the dashboard, click Generate Video. In the bottom left you'll see a model selector. You'll be tempted to pick the highest number you see. Don't, not yet.

• Start with Gen-4 Turbo. It's cheaper per second and renders faster, which is exactly what you want while you're still figuring out prompts.
• Only switch to Gen-4 or Gen-4.5 once a Turbo result is close and you want the quality bump.
• Treat Turbo as your sketchpad and the pricier models as your final draft.

This single habit will save you more credits than any other tip in this Runway tutorial.

Step two: give it a starting image

The Gen-4 video models work best when you hand them a first frame. You can upload your own photo or generate one inside Runway first. The input image sets the entire look of your clip: the subject, the colors, the lighting, the style. It becomes the literal first frame of your video.

If you don't have an image, click into the image generator, type a description of the scene you want (not the motion, just the scene), and make one. Then carry that image into the video step. This is the part beginners skip, and it's why their clips come out looking random.

Step three: write a prompt about motion, not the scene

This is the thing that clicks for everyone eventually, so let me save you the trial and error. Since your image already shows what things look like, your text prompt should mostly describe what moves and how.

Instead of writing "a woman in a red coat on a rainy street," which your image already covers, write something like: "she turns her head slowly toward the camera, rain falls, neon reflections shimmer on the wet pavement, slow camera push-in." Describe the action, the camera, the pacing. That's where Runway listens hardest.

Step four: set duration and aspect ratio before you hit go

Right before generating, you'll choose a length (usually 5 or 10 seconds) and an aspect ratio. Pick 9:16 for TikTok or Reels, 16:9 for YouTube, 1:1 for a feed post. Set this now, because regenerating later because you forgot is just paying twice for the same idea.

Start with 5 seconds. A 5-second clip costs half what a 10-second one does, and for testing a prompt that's plenty. Once the motion looks right, regenerate at 10 seconds if you need the length.

Step five: generate, then judge it honestly

Hit Generate. Your clip renders in the session and you can preview it, download it as an MP4 or GIF, or send it back in for another pass. When you watch it back, ask three questions:

• Did the motion match what I asked for, or did it do its own thing?
• Did faces or hands warp partway through? (That's the classic AI tell.)
• Is the pacing too fast or too slow for the vibe I wanted?

If something's off, tweak one part of the prompt and try again in Turbo. Change the motion words, or simplify them. Small edits beat rewriting the whole thing.

Writing prompts that actually work

Since prompting is where most of your results live or die, let me give you a simple structure I lean on every time. Think of your motion prompt in three parts: the subject's action, the environment's movement, and the camera. You don't need all three, but naming them keeps your prompt focused instead of vague.

• Subject action: what the main thing does. "She smiles and tilts her head," "the dog leaps forward," "the coffee swirls."
• Environment motion: what moves around it. "Leaves drift past," "steam rises," "crowd blurs in the background."
• Camera move: how the lens behaves. "Slow push-in," "gentle pan left," "locked-off static shot."

One more tip: keep it under a few sentences. Long, overstuffed prompts confuse the model and you get muddier results. Short and specific beats long and detailed almost every time. And avoid contradicting your image; if your picture is calm and moody, don't ask for frantic chaotic motion, because the model has to fight itself and usually loses.

A quick word on Workflows

Once you're comfortable, Runway has a node-based Workflows editor where you can chain steps together: text becomes an image, the image becomes a video, all in one canvas you press Run on. It's genuinely handy for repeatable stuff, especially when you find a recipe that works and want to reuse it without rebuilding each step by hand. But honestly, ignore it for your first day. Learn the basic generate loop first, then graduate to Workflows when single clips feel slow.

What to expect from your very first clip

Let me set your expectations honestly, because disappointment usually comes from the wrong ones. Your first clip probably won't be perfect. It might have a slightly weird hand, a face that drifts a little, or motion that's faster than you pictured. That's normal, and it doesn't mean you did anything wrong or that the tool is broken.

The people who make stunning Runway clips aren't getting them on the first try either. They're iterating: generate, watch, adjust one thing, generate again. Treat your first 10 minutes as learning the rhythm of that loop rather than producing a masterpiece. Once the loop feels natural, the quality climbs fast, and you'll be surprised how quickly you go from "that's a bit off" to "wait, that actually looks good." Give yourself permission to make a few throwaway clips while you learn what the model responds to.

The mistakes that cost beginners credits

Let me list the ones I see over and over, so you can skip them:

• Jumping straight to Gen-4.5 for tests. Use Turbo to experiment.
• Generating at 10 seconds before the motion is even right.
• Cramming scene details into the prompt when the image already handles that.
• Forgetting the aspect ratio and re-rendering the whole thing.
• Expecting realism on the first try. Two or three passes is normal, even for experienced people.

The Bottom Line

Your first 10 minutes in Runway should be cheap and a little messy, and that's fine. Start in Gen-4 Turbo, give it a strong first image, write prompts that focus on motion, test at 5 seconds, and only spend real credits once a clip is close. Do that and you'll get a usable result on your first session instead of burning through your free credits with nothing to show. Runway has a learning curve, but it's a short one, and most of it is just knowing which buttons not to press yet.