Runway Mastery — Video Generation and AI Post-Production

Week 1 — meet the tool, get an account, and learn the screen before you learn the prompting.

1. Meet Runway — what it is and who makes it

   Runway is Runway's generative video and AI post-production studio. It is at its best at short, controlled shots and at the unglamorous fixes — removing an object, extending a shot, changing the background. It is at its weakest at long, coherent scenes with consistent characters, and at anything that needs precise timing — and knowing both halves is what separates somebody who uses it well from somebody who trusts it blindly.

   The lesson

   Runway is a generative video and AI post-production studio made by Runway. The models behind it are a set of video generation models plus editing tools that work on footage you already shot. None of that matters on its own — what matters is that you know what kind of worker you have hired. At short, controlled shots and at the unglamorous fixes — removing an object, extending a shot, changing the background is the job you hand it. At long, coherent scenes with consistent characters, and at anything that needs precise timing is the job you keep.

   Most people come to a course like this expecting a list of magic words. There is no such list. What there is, is a tool that produces short video clips and edits, usually three to ten seconds per generation, and produces it at a speed no human matches — which means the skill is not in writing the prompt, it is in knowing what a good answer looks like so you can tell the difference.

   Here is the first thing to try, worded the way you will word things for the rest of the course:

   PromptCopy

   I need a five-shot, forty-second title sequence for a student project about water quality. Give me a shot list with subject, camera, light and duration for each shot, using one reference still across all five.

   Read the answer twice. The first read is for the content; the second is for the shape — did it answer the question you asked, or the question it found easiest? That second read is the habit this whole course is built on.

   Example A plan rather than a prompt — which is the whole difference between a folder of experiments and a finished sequence.

   Practice Open Runway, ask it the one question you would normally put to a search engine about your own field, and write down two things: whether the answer was right, and whether it would have taken you longer to find it yourself.

2. Signing in: what is free, what is paid, and what you actually need

   You do not need the paid plan to finish this course. Start on the free tier — a free allowance of credits per month, enough to learn every technique here. Upgrade only when you hit a wall you can name: a longer file, a newer model, or a rate limit you keep meeting.

   The lesson

   Every one of these tools has a free tier that is good enough to learn on and a paid tier that removes a limit. paid plans add credits, higher resolution and the larger models. The mistake is buying the paid plan in week one, before you know which limit you hit — you end up paying to remove ceilings you were never going to touch.

   Work out your own honest usage first. How many questions a day do you actually ask? How big are the files you upload? Do you need the newest model, or the fast one? For revision, for drafting, for coursework, the answer is usually the free tier.

   If your college or workplace provides an account, use it: a team plan with shared assets and commercial terms is how most people in a job get access, and asking your placement cell whether one exists costs nothing.

   Example A few seconds of generated video per day is a realistic free-tier pace, which is why this course teaches planning before generating.

   Practice Create the account, find the plan page, and write down in one line which limit you would hit first in your own week. It is usually a message cap or a file-size cap, not the model.

3. The screen: where every control lives

   A tour of the interface you will live in — a gallery of your assets, a generation panel with a prompt box and reference frames, and a set of tools for cutting, masking, slowing and extending. Every panel has a reason to exist, and half of them are the difference between a chat and a system.

   The lesson

   The interface of Runway is a gallery of your assets, a generation panel with a prompt box and reference frames, and a set of tools for cutting, masking, slowing and extending. That sentence is worth slowing down on, because the single biggest cause of bad output is not a bad prompt — it is a good prompt typed into the wrong place.

   The history list is your memory of what worked. Name your conversations. The temporary or private mode is for anything you would not want in an account's history. The settings panel holds the personal instructions that apply to everything, which is where your context belongs rather than repeated at the top of every message.

   Do this once, properly: generate the same eight-second shot twice — once from text alone, once from a reference frame with a described camera move — and compare. It takes fifteen minutes and saves you those fifteen minutes every week after.

   Example The reference frame and camera-motion controls are where the craft is: a still you supply plus a described camera move beats a longer prompt every time.

   Practice Spend fifteen minutes doing nothing but clicking. Open every panel, rename one conversation, and save one setting you will want again. Fluency with the screen is what stops you re-explaining yourself every session.

Week 2 — how Runway reads text, the four-part prompt, your own work, and what to do when the answer is wrong.

1. How Runway reads what you type

   Context, instructions and roles. It works in short clips, so continuity has to be built by you: the same reference frame, the same described light, the same lens. Understanding what the model can see — and what it has already forgotten — explains almost every disappointing answer you will get.

   The lesson

   It works in short clips, so continuity has to be built by you: the same reference frame, the same described light, the same lens. This is the machinery. A model does not remember your last conversation the way a person does; it is handed text and asked to continue it well. Everything you want it to know has to be in that text, in the same window.

   There is a difference between a system instruction — the standing context, set once — and a message, which is this request. Put your standing context in the standing place. "I am a final-year mechanical engineering student applying for data roles" belongs in your profile, not typed again at the start of every chat.

   And there is a hard limit. When a conversation gets long enough, the earliest turns fall out of view. Symptoms: it contradicts an instruction you gave ten messages ago, or forgets the file you uploaded. The fix is a new conversation with a written summary of where you got to, not a longer argument.

   Example Keeping one reference image across six shots is what makes them feel like one place, and it is the single technique worth practising.

   Practice Ask the same question twice: once on its own, once after a short paragraph of setup about who you are and what you need. Compare the two answers and write down the difference. That gap is the thing you are learning to control.

2. The four-part prompt: role, task, context, format

   Almost every good prompt has four parts: who the model should be, what it must do, the facts it must use, and the shape of the answer you want. Leave out the fourth and you get an essay when you wanted a table.

   The lesson

   Write the four parts as four lines, in this order. ROLE: who it should answer as. TASK: the single thing you want done, as an instruction, not a wish. CONTEXT: the facts, pasted, not referred to. FORMAT: the exact shape of the answer — "a table with three columns", "five bullets, no more than twelve words each".

   FORMAT is the part everybody skips and the part that saves the most time. An answer you have to restructure by hand was not really an answer. Ask for the shape you are going to use: if it is going into a slide, ask for slide bullets; if it is going into a spreadsheet, ask for rows.

   Here is the same request done both ways — first as people usually write it, then in four parts:

   PromptCopy

   Weak:  tell me about data analyst jobs
   
   Strong:
   ROLE:    A hiring manager for entry-level analytics roles in India.
   TASK:    List what you screen for in a fresher's first 30 seconds.
   CONTEXT: I am a 2026 B.Com graduate with Excel, basic SQL and one
            dashboard project. No internship yet.
   FORMAT:  A table: skill | what a fresher shows | what most get wrong.
            Five rows maximum. No introduction.

   The second prompt is not longer because long is good. It is longer because it contains four things the model cannot guess, and the guess is where the useless answer came from.

   Example Describing the camera — "slow push in, handheld, 35mm" — changes the result more than describing the subject again.

   Practice Take a task you did last week without AI and write the prompt in four labelled lines. Then run it, and rewrite only the part that failed — not the whole prompt.

3. Runway for the work you actually have

   Assignments, revision, email, applications, meeting notes. A five-shot title sequence for a project video, a background you could not film, or a shot where something distracting had to be removed. The test of a tool is whether it removes an hour from your week, not whether the demo looked clever.

   The lesson

   The highest-value use of Runway for a student or a fresher is not writing essays. It is compression: turning a 40-page chapter into the six things you actually have to remember, turning a messy set of notes into a revision sheet, turning a job description into a list of what to prove.

   The second highest is structure: given a blank page, ask for three possible outlines and pick one. Being stuck is usually a problem of options, not of effort.

   Here is a prompt worth keeping verbatim — it is the one that turns a document into something you can study:

   PromptCopy

   Shot list format — one block per shot, five shots for a 40-second piece.
   
     SHOT 1
     SUBJECT   what is in frame, plainly
     CAMERA    how it moves: static, slow push in, pan left, handheld
     LIGHT     where it comes from and what colour
     DURATION  4s
     REFERENCE the file or frame that keeps the light and palette consistent
   
   Rules:
     - nothing longer than 8 seconds
     - the same reference frame on every shot
     - describe the camera before you describe the subject again
     - plan the cuts on paper; the generation is the easy part

   Notice the last line. Asking for the gaps is asking the tool to mark its own work, and it is the single most useful line you can add to a study prompt: the material it could not summarise is the material you have not understood yet.

   Example For each shot, write one line of subject, one of camera, one of light, and one of duration.

   Practice Pick the one task you repeat every week — the one that is boring rather than hard — and rebuild it in Runway today. Time it. Then keep the prompt that worked, saved and named.

4. When the answer is wrong: iterate instead of restarting

   A bad answer is information. The failure is a beautiful shot that does not cut with the one before it — different light, different lens, a character who changed face. Keep the conversation, name the fault, and correct one thing at a time — restarting from scratch throws away everything the model has already got right.

   The lesson

   There are four things that usually went wrong, and each has a different fix. It answered a different question — restate the TASK as one sentence. It made things up — supply the facts yourself and say "use only these". It wrote too much — ask for the length first. It sounded like a machine — ask it to rewrite for one specific reader and cut every third word.

   Say the fault out loud, in the message. "This is too long for a WhatsApp message and it sounds like a brochure." A model cannot fix a problem you have not named, and naming the problem is also how you find out what you actually wanted.

   Follow-ups that work: "shorter", "only the parts that are true for a fresher", "rewrite the second sentence three ways", "what would you have to check before I send this?". That last one is worth using before anything goes out with your name on it.

   Example If two shots do not sit together, regenerate the second from the first one's last frame instead of rewriting the prompt.

   Practice Take the worst answer you have received this week and correct it in three follow-up messages without retyping the original prompt. Notice how much faster it converges.

Week 3 — documents and tables, Reference frames, camera control and the fix-up tools, the API, and one boring task automated.

1. Files, tables and long documents

   Uploading a PDF, a spreadsheet or a screenshot and asking questions about it: You can bring your own footage and stills, and the editing tools work on your material as well as on generated clips. This is where these tools stop being a chat and start being work, and where the failure modes are worth knowing.

   The lesson

   You can bring your own footage and stills, and the editing tools work on your material as well as on generated clips. The two failures to expect are the ones nobody warns you about: a long document is summarised as it is read, so a detail on page 60 can be missed; and a table with merged cells or a scanned page is likely to be read wrongly.

   So the working method is: ask narrow questions, and ask the tool to quote the line it is answering from. "From the attached file only, what does clause 4.2 let me do? Quote the sentence." If it cannot quote it, it did not read it.

   For a spreadsheet, ask for the formula and an explanation instead of the computed column — write the duration and the frame rate down before you generate, not after — then you can fix it yourself next month when the columns change.

   Example Removing a bag from the corner of a real interview clip is a two-minute fix with these tools and a reshooting problem otherwise.

   Practice Upload one real document you already own — a syllabus, a marksheet, a project report — and ask three questions whose answers you already know. When it gets one wrong, read the passage it quoted before you blame the file.

2. Reference frames, camera control and the fix-up tools — Runway's own feature

   Supply a still as the first frame and the shot starts from what you already approved. Describe the camera and the shot moves like one. Then use the editing tools — inpaint, extend, slow down — on footage you shot yourself, which is where the time actually gets saved.

   The lesson

   Because planning is what separates usable video from a folder of experiments. Generation is per-shot and short, so the skill is in the shot list, the reference frames and the cut — the same skills a film editor uses, applied to material you did not have to film.

   Write the shot list first, in blocks, with a duration on each one. Keep one reference image across the whole piece. Generate short, cut tight, and never regenerate a whole sequence to fix one shot. Then assemble and add sound — silence is what makes generated video look generated.

   Here is the shape of it, in the form you will actually use:

   Plain textCopy

   SHOT LIST - 40 second project demo
   
   SHOT 1   4s   static, wide      a desk at night, one lamp from the left, notebook open
   SHOT 2   5s   slow push in      the same desk, hands typing, same lamp
   SHOT 3   4s   handheld, close   the screen, out of focus text, screen glow on the face
   SHOT 4   6s   pan left          the same desk from the side, coffee going cold
   SHOT 5   5s   static, wide      window, morning light replacing the lamp
   
   RULES
     - one reference still for every shot (same lamp, same palette)
     - nothing longer than 8 seconds, ever
     - cut on movement, not on a pause
     - room tone under the whole piece; a music bed alone sounds synthetic

   The mistake is generating a twenty-second continuous shot and hoping it holds together. It will not — plan in shots of five to eight seconds and cut between them.

   Example A shot that a location would not allow — a rooftop at dawn — becomes a still you generated, then an eight-second move with a slow push in.

   Practice Take one real clip you already have and fix three things: remove an object, extend the end by two seconds, and change the background. Then generate one new shot to match its light.

3. Automating clips and your own pipeline and your first script

   Generation is offered through the studio and, on paid tiers, through an API for scripting; the useful automation is the pipeline around it — shot list, naming, assembly. You do not need this to finish the course, and you do not need it for a fresher job either — but an afternoon here is what turns "I have used Runway" into "I have built with it", which is a different sentence in an interview.

   The lesson

   Generation is offered through the studio and, on paid tiers, through an API for scripting; the useful automation is the pipeline around it — shot list, naming, assembly. The idea is simple: the same model you have been chatting with also answers a web request, so you can put it inside a script, a spreadsheet or a page. A key identifies you; a request sends the text; a response comes back as data.

   The reason to try it once, even if you never build anything: it makes the chat version less mysterious. You see that the whole conversation is text in and text out, that your instructions are literally lines of a request, and that "the model" is one parameter among several.

   A first call looks like this:

   TerminalCopy

   # The pipeline, and the parts no model does for you:
   #
   #  1. Write the shot list (subject / camera / light / duration).
   #  2. Generate one reference still you are happy with. Keep it.
   #  3. Generate each shot from that still, named shot-01.mp4 ...
   #  4. Assemble in an editor: cut on movement, not on the beat of the music.
   #  5. Add sound: room tone first, then a music bed, then narration last.
   #
   # Step 5 is why most generated video looks generated. Silent or
   # music-only video reads as a demo; room tone makes it read as footage.
   #
   # ffmpeg, if you want the two-second version of "add room tone":
   #   ffmpeg -i shots.mp4 -i room.wav -shortest -c:v copy out.mp4

   The mistake is generating at the lowest quality to save credits and then trying to fix it in the edit. Resolution is not recoverable; credits are.

   Example A script that renders each row of a shot list in one pass is a realistic automation, and it is how a five-shot sequence gets made in an evening instead of a week.

   Practice Get a key, run one request that works, and change one word in it to see the answer change. That is the whole of the first afternoon.

4. Automate one boring task with Runway

   Automation is not about building a system. It is about doing one repetitive job the same way every time, in less time than last time, and being able to do it again next month.

   The lesson

   Pick the task by how often it happens, not by how impressive it would be. A weekly report you can half-generate beats a clever pipeline you build once and never open again.

   A title sequence regenerated every month from the same shot list with a new reference still, or a batch of short clips for a set of posts.. Whatever you choose, write the steps back out in plain English afterwards — "Step 1, open the sheet, Step 2, paste the names —" because the written steps are what you follow when the tool changes next quarter.

   And keep a copy of the prompt next to the task. A prompt that lives only in your chat history is a prompt you will rewrite from scratch in March.

   Example One shot list, five shots, three minutes of assembly — a two-week content set produced in an afternoon.

   Practice Name the task you repeat most often that involves typing, then write the prompt for it and run it three weeks in a row from the same saved place. Three runs is the point at which you know whether it is genuinely automated.

Week 4 — a finished portfolio project, the privacy rules, the limits, and the Runway certification paths.

1. Build the portfolio project: a five-shot title sequence for a real project

   Build a forty-second open for a project or channel: five shots, one reference still, a cut on movement, and sound underneath it. It is the thing you will talk about in the interview, so it has to be small enough to finish in a fortnight and concrete enough to show a person in one minute.

   The lesson

   Build a forty-second open for a project or channel: five shots, one reference still, a cut on movement, and sound underneath it. Finish it before you start the next one. A half-built idea shows nothing; a small finished thing shows that you can finish.

   Use the tool as a collaborator, not an author: ask it for a plan, a critique and a checklist, and write the work yourself. In the interview the questions will be about the decisions — why this, why not that — and only the work you did yourself has answers.

   Write one paragraph beside the project: what problem it solves, what you used, and what you would do differently next time. That paragraph is the interview.

   Example Finished, it is a video file with a stable visual language, usable at the start of any demo or presentation.

   Practice Show it muted to somebody and ask what the project is about. If they cannot tell, the cut order is the problem, not the footage.

2. Ethics, privacy and what never to paste

   These tools send what you type to somebody else's computer and keep it in a history. Never paste passwords, government ID numbers, bank or card details, medical records, or another person's private data — and never paste a company's confidential document.

   The lesson

   There is no version of this tool where your text stays on your laptop. Everything you type is sent to a server, kept in a history you can usually see, and may be reviewed or used to improve the product depending on the plan.

   Do not generate a likeness of a real person, and do not upload footage you were given access to but not the right to reuse. A clip of a lecture is not yours to publish because it was shared with you.

   The practical rule for a fresher: replace the real thing with a stand-in. "Client A", "my friend's phone number", "the amount in the offer letter". The tool rarely needs the real value to do the work, and the stand-in costs you nothing.

   And the professional rule: if footage was given to you for review, it is not footage you can publish. If your employer has an approved plan or a policy, that policy is the answer, not your judgement about how sensitive a file really is.

   Example Generated video of a recognisable real person, a real location you did not film, or a company's own footage carries the same permissions problem as an image

   Practice Go through your last five conversations and delete anything containing a real phone number, a client name, or a document you did not write. If you cannot find the delete button, that is the lesson.

3. Limits, hallucinations and how to check

   These tools predict plausible text. Short clips only, characters that change between shots, and text inside a frame that will be wrong That is a mechanism, not a moral failing — and the habit it demands is the habit of asking "where did this come from?" out loud, every time, before you use an answer.

   The lesson

   A model does not look things up unless it has been given a way to look things up, and even then it can attach a real number to the wrong claim. Short clips only, characters that change between shots, and text inside a frame that will be wrong

   So the rule is: numbers, dates, names, citations and legal or medical claims get checked in a primary source before they leave your hands. Everything else — drafts, structure, explanations, practice — is fair game.

   Three questions to ask before you trust an answer. Where did this come from? What would make it false? Who is the original source, and can I open it? If the third one has no answer, you have writing material, not facts.

   Watch the whole thing muted, then with your eyes closed. If either pass loses the story, something is out of order.

   Example Any writing in a generated shot will be garbled. Add the text in your editor, over the footage, where it will also be crisper.

   Practice Ask for one statistic with its source, then open the source. Sometimes it exists. Sometimes the citation is invented, and the number is close enough to a real one to be dangerous. Either way you will remember the exercise.

4. Get certified: the official Runway paths

   A Way2Fresher certificate for this course is free and lives on this site. Beyond it, Runway publishes its own learning and certification material — and the rail on this course page links to it.

   The lesson

   There are two things called a certificate and they are not the same. The one this site issues records that you finished a structured course and built the project at the end of it — it is free, and it is yours to print. The ones Runway issues record that you passed their own material.

   Runway publishes its own academy and documentation, which is the honest entry point for the tools; there is no vendor certification for this area, and the reel is the credential.

   Get both, in that order. The project is what an interviewer asks about; the certificate is what gets past a filter that looks for keywords. The links to the official paths are in the rail beside this lesson, each labelled with who issues it.

   And put the work on the certificate, not the other way round: a certificate with no project behind it is a line on a resume, and it lasts exactly until the first technical question.

   Example A finished forty-second sequence with a real shot list behind it demonstrates planning, which is what an editor or content team actually hires for.

   Practice Finish every lesson here, take your Way2Fresher certificate, then open one official path and work through it with the project you have already built. Being certified in the tool you can already use is a small additional step.