Runway ML Gen-3 Commercial Use 2026: License Rights, Client Work & Copyright Guide

To answer your subscription question from earlier in the thread: in my experience the commercial license attaches to the content you generated while you were on a paid plan, not to your account status forever. I upgraded for one project, generated my clips, and downgraded the next month. Nothing got revoked.

That said, I screenshot the relevant terms section on the day I generate, with the date visible. ToS changes constantly and you want a record of what the deal was when you actually made the asset. Not legal advice, just how I cover myself.

On the copyright ownership question nobody really wants to hear the honest answer, which is that purely AI-generated output may not be protectable by copyright at all in the US. The Copyright Office has been pretty consistent that human authorship is required, and a text prompt alone generally hasn't been treated as enough.

Practically that means your client may own the deliverable as a contractual matter (whatever your agreement says), but the raw AI clip itself might not have a copyright anyone can enforce against a copycat. Worth setting expectations on that before you pitch it as exclusive.

The img2vid question is the interesting one to me. If you start from an image you actually drew or shot yourself, you brought real human authorship into the pipeline. My understanding is that the human-authored parts can still be protected even if the AI motion on top is shakier.

I'd keep your source image, the layered file, anything that shows you made it. If a dispute ever comes up, being able to show the human input is what matters.

Disclosure to clients: I just put a line in my SOW now. Something like 'portions of the deliverable were produced using generative AI tools.' Takes ten seconds and it has saved me an awkward conversation twice already.

One client actually had a policy against AI in their brand assets and I never would have known if I hadn't asked. Better to surface it early than have them find out after launch.

OP here, this is all super helpful. The production company actually came back and asked me to confirm in writing that they'd own the final B-roll. I'm now realizing 'own' is doing a lot of work in that sentence given what mark_d_92 said about AI output maybe not being copyrightable.

How are people wording the ownership/assignment clause when the thing being assigned might not even carry a copyright? Feels like I'm assigning rights to something that may not exist.

Funny timing, I literally hit this last week. My contract lawyer reframed it from a pure copyright assignment to a broader 'assignment of all right, title and interest I have, if any, plus a license to use, modify and reproduce the deliverables.' The 'if any' and the license backstop cover you if the copyright turns out to be thin.

Not saying copy my wording, but the concept of pairing an assignment with a broad license helped a lot. The client gets practical certainty even where copyright is murky.

Adding a data point on Runway specifically: read the section about your inputs too, not just the outputs. When you do img2vid you're uploading your own image, and you want to be comfortable with what rights you're granting them to that upload. Most of these tools take a license to process your content, which is normal, but check the retention and training language.

If you're using a client's confidential storyboard frames as the seed image, that's a whole separate confidentiality issue with the client.

Has anyone dealt with the indemnification angle? Some of these platforms now offer a commercial indemnity (they'll back you if the output infringes someone's IP) but usually only on the higher enterprise tiers. For a solo freelancer on a mid plan you probably don't have that, which means you're the one holding the bag if a clip accidentally resembles something trademarked.

tara.nguyen is right and that indemnity gap is exactly why I bumped my own freelancer agreement to push that risk back where it belongs. I now carve out AI-generated elements from my warranty of non-infringement, because I genuinely cannot warrant that a model didn't reproduce something.

Clients push back sometimes but most accept it once you explain the tool doesn't give YOU that guarantee either.

Quick clarifying question for the people who've shipped client work: do you bill the AI tool subscription back to the client as a cost, or eat it as overhead? I'm trying to figure out if expensing it changes anything about who 'controls' the output. Probably overthinking it but curious how others structure it.

I just fold it into my rate as overhead, same as I do with my Adobe subscription. Whoever pays the $35 doesn't determine ownership, your contract does. I wouldn't read anything into the expense line.

The one time I itemized it the client got weird about 'why am I paying for AI' so now I just don't break it out.

Update from my own project since people shared theirs: delivered a 45-second product video with maybe 8 seconds of Runway-generated transitions. Disclosed it in the SOW, client signed off, no issues. The only friction was the client's ad agency asking whether the clips were 'cleared,' which I took to mean cleared of third-party IP. I told them honestly that AI output comes with no clearance guarantee and they decided to keep those shots as abstract enough that it didn't matter.

The 'cleared' question outoftheloop_22 mentioned is going to come up constantly with agency clients. They're used to stock footage and music that comes with a license and a clearance. AI output breaks that mental model because there's no rights holder vouching for it.

I've started just saying upfront: this is generated, not licensed stock, treat it as original-ish content that you should review for any obvious resemblance before it airs.

Does the analysis change at all for broadcast or paid-ad use versus organic social? My gut says the exposure is higher when there's a media buy behind it because more eyes and more money means more incentive for someone to claim infringement. But I don't know if the actual legal standard differs.

Thank you Counsel_Adrian, the 'risk is a function of exposure' framing is the clearest way I've seen this put. I'm going to use that with my next nervous client.

Follow-up: if the raw clip may not be copyrightable, does editing it heavily (compositing, color, layering my own footage, retiming) create enough human authorship to claim copyright in the finished sequence? Or am I still standing on sand?

Not a lawyer but from everything I've read the editing/compositing angle is exactly where the human authorship lives. The selection, arrangement, and creative editing of clips has long been protectable even when individual elements aren't yours. A heavily edited sequence is a different thing than a raw drop of a generated clip.

The catch is your protection covers your creative contributions, not the underlying generated frames themselves. So someone could maybe regenerate a similar raw clip, just not copy your exact edit.

a lot of the specifics here (exact tier names, indemnity terms, what's covered) change as the platforms update their terms, so treat dated posts as a snapshot. Always confirm the current ToS before you rely on anything.

One thing I haven't seen mentioned: model and likeness issues. If you generate something that ends up looking like a real recognizable person, that's a separate can of worms (right of publicity) that has nothing to do with copyright. Happened to a colleague where a generated 'spokesperson' looked uncomfortably close to a B-list actor and the client legal team killed the shot.

Abstract B-roll like the OP's case is way lower risk on this. Faces are where it gets dicey.

Reporting back on my bakery reel from earlier. I upgraded to the paid tier for the month, generated the transitions, delivered, and downgraded. Everything still plays and the client posted it weeks ago with no problem.

deeptone_editor's advice to screenshot the terms on generation day was clutch, by the way. I did it and it gave me peace of mind even though I never needed it. Cheap insurance.

On nina_codes's likeness point, this is the one that scares me most for ad work because right of publicity varies a ton by state and some states are aggressive about it. A generated face that resembles a real person in the wrong state could be a real problem even if you never intended it.

I now run any generated face past the client with an explicit 'this is synthetic, does it resemble anyone you're aware of' note. Pushes some of that judgment to the people who'd know their own market.

Beginner question, sorry if obvious: when people say 'check the current ToS,' where in Runway's terms do you actually find the commercial use language? I open the terms page and it's a wall. Is it under a specific heading or do I need to read the whole thing?

It's usually split across two places: the main Terms of Service (look for sections on 'your content,' 'ownership,' or 'license') and the plan/pricing page which spells out what each tier includes commercially. The pricing page often has the cleaner answer on whether commercial use is allowed on your specific plan.

If the two ever seem to conflict, that's exactly when you'd want a second set of eyes. They're not always perfectly consistent.

rachelg's point about keeping prompt history is underrated. I started exporting my generation log per project into the client folder. It's saved me twice when someone assumed I'd 'just downloaded something off the internet.'

It also helps on the authorship side honestly, it documents the human creative choices that went into the piece.

Anyone know how this plays out for international clients? Half my work is for a company based in the EU. I keep reading that the US human-authorship rule is one thing but other countries treat AI output differently. Does the client's location change what I should put in my contract?

Good question, general info only. Copyright is territorial, so protection and the treatment of AI-assisted works can differ country by country, and several jurisdictions handle authorship and AI output differently than the US does. That's one reason contracts often specify a governing law and a forum, so you're not guessing which country's rules apply if there's a dispute.

For a cross-border engagement, the practical move is usually to make the contract itself carry the weight (clear assignment plus license, clear governing law, clear allocation of infringement risk) rather than relying on copyright defaults that vary by territory. Worth having someone look at the governing-law clause specifically when the counterparty is overseas. None of this is advice for your particular deal.

Practical tip that's saved me money and grief: don't generate client work on a free trial 'just to test' and then plan to 'regenerate it properly later.' Learned that the hard way. Spent an afternoon trying to recreate a transition I made on the free tier and never got it back, because the seed randomness means it almost never comes back identical. You also may not have commercial rights to that trial output anyway.

Now my rule is: the moment a generated clip might survive into the final cut, it gets made on the licensed plan. No exceptions.

Question about work-for-hire framing. If I'm a contractor and my agreement says everything I produce is 'work made for hire,' does that even function for AI output that might not be copyrightable? Feels like work-for-hire assumes there's a copyright to transfer in the first place.

Not a lawyer but that's exactly why the better contracts I've seen don't rely on work-for-hire alone. They stack it: work-for-hire to the extent it applies, plus an assignment of any rights that exist, plus a broad license as the fallback. Belt, suspenders, and a second belt.

If your current contract only says 'work made for hire' and stops there, that's probably the weak spot to fix.

Following up on the indemnity subthread. I checked and the commercial indemnity on the tool I use really is limited to enterprise plans and even then it's capped and has a bunch of conditions (you have to use the service as intended, not modify outputs in certain ways, etc). So even 'covered' users aren't fully covered. Read the conditions, not just the headline 'we indemnify you.'

Result to share: client asked me to add an AI-disclosure line to the video credits itself, not just the contract. A small 'contains AI-generated elements' in the end card. Honestly it was a non-event for viewers and the client felt covered. Might become standard for the cautious brands.

Side note, some advertising rules in certain markets are starting to lean toward disclosure of synthetic or manipulated content, so I suspect their legal team was getting ahead of that. Would not surprise me if on-screen disclosure becomes expected for ads in the next couple years.

Late to this but bookmarking the whole thread. The consensus I'm taking away: paid plan from the start, keep your prompts and generation dates, disclose to the client in writing, lean on contract language (assignment + license) instead of assuming copyright, and watch out for faces/likeness. Did I miss anything important?

OP closing the loop. The corporate video shipped. I generated the B-roll on the paid plan, disclosed it in the SOW, kept my prompt logs, and used an assignment-plus-license clause a contract attorney tweaked for me. The production company was happy and the 'futuristic' shots cost me an afternoon instead of a week in After Effects.

gina_makes that summary nails it. The one thing I'd add from my experience: have someone actually look at your ownership clause before the first AI job, not after. Reusing it across every project after that was the real time-saver. Thanks everyone, this thread basically wrote my workflow.

Reviving briefly to ask a narrow one: if my client wants exclusivity ('no one else can use this exact clip'), can I even promise that with AI output? I can promise I won't reuse my generated clip, but I obviously can't stop the platform or another user from generating something similar. How are people wording the exclusivity promise honestly?

Exactly the right instinct. You can commit to exclusivity over YOUR deliverables (I won't license or reuse these clips elsewhere) but you should not promise the output is globally unique or that no similar clip can ever exist. My contract distinguishes between 'I grant you exclusive rights in the delivered work' and an explicit note that 'generative outputs are not guaranteed to be unique.'

Clients generally accept that once you explain how the tech works. The honest framing also protects you from a breach claim if a lookalike clip surfaces somewhere you had nothing to do with.