Skip to content
SynthIDX

Strip the Metadata From a Runway Export

Runway Metadata Remover

Strips container metadata from Runway exports. The Runway visible mark is not in our removal registry, so this page does not promise to remove it.

What a Runway export leaves in the file

Runway is a generative video platform at runway.com, and its video models include Gen-4.5, Gen-4, Gen-4 Turbo and the Aleph 2.0 editor. The export help article says MP4 is the default format, that ProRes arrives as a .mov file with PCM audio, and that a PNG sequence ships as a zip of single frames (https://help.runwayml.com/hc/en-us/articles/54396547993491-Exporting-Videos-in-ProRes-and-PNG-Sequence-Formats). The same article notes that Workflows and Agent generations are delivered as MP4, and that the format is fixed when the generation runs. In everyday use, then, the file you download is a container rather than a pile of raw frames.

An MP4 or a MOV belongs to the ISO Base Media File Format, a tree of boxes where each box carries a size and a four character type. The MP4 Registration Authority keeps the list of box and atom types at https://mp4ra.org/registered-types/boxes. The coded picture sits in the media data box, while the track list, the sample table and the descriptive entries sit in the movie box beside it. That layout is why a metadata pass can change the record around the footage without decoding the footage itself.

Runway documents its provenance work at the policy level. The safety page states that Runway implements C2PA so AI-generated content can be traced back to its source (https://runway.com/safety). A research post from October 2024 goes further: Runway says it adopted the C2PA provenance standards and adds invisible watermarks to every generation, keeping evidence in the metadata that the output is AI-made (https://runway.com/research/foundations-for-safe-generative-media). The safety site also hosts a verifier that inspects C2PA manifests in images, videos and audio (https://runway.com/safety/verify).

What Runway does not publish matters just as much. There is no per-field table for its exports, no manifest schema, no list of which models or plans attach a credential and no statement about the signer. The C2PA technical specification describes the manifest store and the ISO Base Media File Format embedding in general terms (https://spec.c2pa.org/specifications/specifications/2.5/specs/C2PA_Specification.html), but it cannot tell you what a given Runway file holds. This page therefore targets the provenance records and the recognized generator fields a container can carry, and makes no claim about a specific field that nobody has documented.

Beyond a signed manifest, a Runway export can hold the ordinary record that any MP4 or MOV pipeline writes. Creation and modification times live in the movie header, an encoder or software name can sit in the user data and metadata boxes, the handler names describe the tracks, and an XMP packet or app export key can name the tool that wrote the file. Those entries are the second half of the strip target. A pass that leaves the sample table valid has to be selective, so this page does not describe the operation as a full sweep of every container tag.

Why the visible Runway mark is outside this page

A Runway clip can show a Runway mark in the corner. The Free plan help article is explicit: all videos generated on a Free plan feature a Runway watermark, and a Standard plan or above generates without one (https://help.runwayml.com/hc/en-us/articles/50404627334547-Free-plan-details). That makes the mark a plan artifact rather than a render setting. A clip you already exported on the Free plan keeps the mark, while a new export on a paid plan is a different file.

The mark itself is drawn into the pixel values inside the media data box. The container record sits in separate boxes that describe the file rather than depict it. Rewriting a box can change what a verifier reads; it cannot repaint a frame. A metadata strip can turn a provenance box into an empty one and still leave the corner logo untouched, so the two layers have to be discussed apart. In short, this page does not remove anything that lives in the picture.

Our removal registry lists the visible marks the frame level pipeline is configured to target, and the Runway mark is not on that list. That is why the first screen says this page does not promise to remove it, and why no paragraph here claims otherwise. The AI Video Watermark Remover page describes the mark families its tracker handles, and Runway is not among them, so that page is context on the visible layer rather than a Runway fix. If the visible mark is the obstacle, the supported route is a fresh generation on a plan Runway says produces clean output, or a crop that accepts the loss of the edge.

Keep the two outcomes apart. Re-generating on a paid plan replaces the file, while a metadata strip returns a cleaned copy of the file you uploaded. Neither one repaints an existing frame, and a Free plan clip that already carries the mark will still carry it after any container pass.

How to keep the record out of a Runway export

  • Begin with the workspace download

    The copy in your Runway assets is the fullest version of the file. A browser save of the preview, a screen recording or a clip pulled from a shared page can drop boxes and pick up a new encoder string from the app that handled it. Download from your own asset list so the strip starts from a known file. Runway also notes that the output format is chosen at generation, so re-run the generation if you need a different container.

  • Strip after the last edit

    Every converter, trim and cloud sync between the strip and the upload is a chance for a new software string or a fresh provenance entry to appear. Clean the file at the end of the workflow and send it straight to the destination. If you must resize or trim afterwards, run the strip one more time, because the editor can attach its own tags.

  • Inspect what stayed

    Play the result and open it in a metadata viewer. The picture and the soundtrack should be unchanged, and the provenance entries should be gone. On MP4 and MOV an ordinary title, author or creation time can remain because the pass keeps box offsets valid, so check the fields you care about instead of trusting a blank report.

  • Respect the plan and the rights

    Runway sets the watermark rule by plan and can change it, and the Free plan clause is a policy statement rather than a promise about an old file. Stripping a provenance record is an edit to output you made. It does not transfer ownership or override Runway terms, so keep the workflow on clips you generated or are licensed to change.

How it works

How to strip the metadata from a Runway clip

  1. Step 1: Upload the clip

    Choose an MP4, MOV, WebM or MKV clip and drop it on the panel below, or browse for it. Your browser sends the file to processing storage, and the upload is never published. Until you start a run, nothing changes the source file on your disk.

    Tip

    Start from the download in your Runway assets rather than a shared link or a screen capture, because a re-saved copy can lose fields before it reaches this page.

  2. Step 2: Run the metadata strip

    The panel loads one video metadata operation with removal switched on, so there is nothing to configure. Press run and the job reads the container, clears the provenance records and the recognized AI generator fields, and writes a new file. On MP4 and MOV the coded streams are copied rather than encoded again. On WebM and MKV the job remuxes with a stream copy and drops the tag list.

    Tip

    Credits are spent only when a strip actually runs.

  3. Step 3: Download and check

    When the job ends, download the cleaned file and play it once. The footage and the audio should match what you uploaded. Open it in a metadata viewer if you need to confirm which entries left. Signed out, the page asks you to sign in and then returns you to the panel.

    Tip

    Send the cleaned file to the next platform directly. A converter or editor run afterwards can write fresh metadata into it.

Limitations and honest expectations

The visible Runway mark is not in our removal registry

Our registry names the visible marks the frame level pipeline can target, and the Runway mark is not one of them. A mark drawn into the frames stays in the picture after a container pass, because the pass never repaints a pixel. The first screen says so and no answer here contradicts it. Runway says a Free plan generation carries the mark and a Standard plan or above does not, so a clean re-generation is the supported route when the file can be replaced.

Runway publishes no per-field export map

The safety page and the research post state that Runway implements C2PA and adds an invisible watermark. They do not list the fields a Runway export contains, the manifest schema, the signer or the models and plans covered. We therefore cannot promise that one named field will be cleared, only that provenance bearing records and recognized AI generator fields are the target. Where Runway publishes nothing specific, this page says nothing specific either.

Ordinary container tags can survive

The MP4 and MOV path edits provenance fields where they sit and leaves the box lengths as they were, which keeps every absolute offset in the sample table correct. Because of that constraint, a plain title, author or creation time can stay when it holds no AI provenance. If you need ordinary tags gone too, reach for a general editor and verify its output.

This is not a privacy scrubber

This pass works on provenance bearing records and on AI generator fields it can recognize, and it stops there. It makes no claim about removing GPS coordinates, device identifiers or personal data as a category, and it is not a general container cleaner. A privacy cleanup on media you own belongs on a dedicated metadata page, where you can check the result field by field.

A signal inside the coded stream is another layer

Runway says it adds invisible watermarks to every generation and keeps evidence in the metadata, but it does not name the scheme or say whether the signal lives in a container box or in the frames. A container pass can blank a known tag; it cannot confirm a payload it cannot read. Treat a clean container as one layer removed, not as proof about every artifact in the file.

The destination can add its own record

After you hand the file over, any service that re-encodes or republishes the clip can write new metadata of its own. It can also decide to show an AI label based on its own systems or on the disclosure you provide at posting time. Cleaning a file before upload takes away one signal, but it cannot reach a classifier, a reviewer or a badge that a published post already shows.

The Free plan rule is Runway’s to change

Runway states that Free plan videos carry a watermark and that Standard and above do not. Plans, models and export formats change, and a shared page can serve a different file from the one in your workspace. Check the file you actually hold rather than a policy line from an older article, and re-export from your own workspace when you need a fresh copy.

Stripping provenance is a decision about authorship

Provenance records carry who made a piece of media and how it was edited. Clearing them from your own output is routine. Clearing them from a clip that belongs to someone else hides its origin and can breach their terms or the law. Keep the workflow to footage you produced or are licensed to change.

Identity and official documents are not supported

This tool is not for passports, identity cards, driver licenses, visas, certificates, statements, or other official documents, whether the document is real, generated by AI, or put together from a template. Editing one of these can be document fraud, and we close accounts that try. Use the tool on other images you generated or have the right to edit.

Where to go next

The right page depends on which layer you need to alter. If the container is the target, the Video Metadata Remover lays out C2PA boxes, tag lists and the coded stream boundary together. If a mark in the frames is the target, the AI Video Watermark Remover explains a frame level pass across the marks its tracker knows, and Runway is outside that set. To see the same container strip on another video generator, the Pika Metadata Remover covers Pika exports and where its visible mark boundary sits.

The facts here come from first party pages and the C2PA specification. Runway’s export formats are documented at https://help.runwayml.com/hc/en-us/articles/54396547993491-Exporting-Videos-in-ProRes-and-PNG-Sequence-Formats, and the Free plan watermark rule is at https://help.runwayml.com/hc/en-us/articles/50404627334547-Free-plan-details. The C2PA commitment appears at https://runway.com/safety, the verifier at https://runway.com/safety/verify, and the October 2024 research post at https://runway.com/research/foundations-for-safe-generative-media. The C2PA technical specification is at https://spec.c2pa.org/specifications/specifications/2.5/specs/C2PA_Specification.html, and the MP4 Registration Authority lists box types at https://mp4ra.org/registered-types/boxes. Runway does not publish a metadata field map, and this page does not invent one.

Sign in to run. Free credits included.

FAQ

Frequently asked questions

Short answers about Runway exports, from the container record to the visible mark this page does not promise to remove.

Explore more tools

AI Video Watermark Remover

A frame level pass over the visible marks its tracker supports, and the reason Runway is not one of them.

Open tool

Video Metadata Remover

The general container page, from C2PA boxes to the tag and chapter lists a stream copy drops.

Open tool

Pika Metadata Remover

The same container strip applied to Pika exports, with the same boundary drawn around the visible mark.

Open tool

C2PA Remover

The container credential record that travels with a Runway export.

Open tool

Luma Metadata Remover

The same video metadata page for Luma Dream Machine, with the visible mark left alone.

Open tool

All tools

Every remover and detector on one page, grouped by what each one cleans or checks.

Open tool

Strip the Runway metadata before you share the clip

One pass clears the provenance records and the recognized generator fields in a Runway file. The footage comes back as it went in.