Runway's ownership language does not, by itself, settle whether every element of your video is cleared or whether a particular output receives copyright protection. Treat it as one layer of a rights review, not a certificate covering the whole production.
What the ownership statement covers
Runway states: “As between you and Runway, you retain ownership and all your rights to content that you upload and generate on Runway.” The limiting phrase matters: the statement describes the relationship between you and Runway.
It does not establish what permissions a photographer, performer, composer or brand has granted you. Nor does this supplied passage answer jurisdiction-specific questions about copyright protection or enforceability. Indian creators delivering overseas campaigns should identify the relevant territories rather than assume one answer travels everywhere.
Build a four-layer rights worksheet
Use one page per project, with these editorial review fields:
- Provider relationship: Save the ownership wording, source and review date. Record exactly which proposition you are relying on.
- Input permissions: List each asset, its owner, permission evidence and whether the planned transformation has been addressed.
- Output clearance: Identify recognisable people, marks, music or other elements requiring further review, including anything unexpected in the finished scene.
- Protection and delivery: Record what the client expects to own, the intended jurisdictions and questions requiring qualified advice.
For each layer, assign an owner and a status: documented, unresolved or excluded. Do not let a documented provider statement automatically turn the other layers green.
Hypothetical example: a festival teaser
Suppose an independent Pune creator plans a 15-second teaser using their own abstract drawing, a purchased photograph and a separately licensed soundtrack. The intended uses are a website and paid social advertising for three months in India.
The drawing has a documented creator. The photograph's purchase receipt exists, but its transformation permissions are unclear. The soundtrack licence mentions a different distribution context.
Evaluate the project by checking those two unresolved permissions against the actual proposed uses. Runway's ownership statement does not resolve either gap. A useful alternative is to replace the uncertain assets before production rather than carry ambiguity into client delivery.
Stop at the unresolved layer
Pause publication when a necessary permission remains unverified. Continue with an asset-free storyboard or clearly cleared substitutes while seeking clarification. Ask a qualified adviser about copyright or contractual conclusions you intend to promise.
If access procurement is also pending, compare the AI tools catalog, checking access format and saving offer terms before buying. Marketplace account/code/token offers are not proof of official subscription equivalence, and seller terms are separate from Runway documentation.
Sources and scope
Runway usage rights establishes the quoted ownership language. Source material checked 29 October 2026; features/policies may change. The layered worksheet and example are practical editorial advice, not legal conclusions.