Runway exports carry container metadata — creation timestamps, encoder strings, software tags inside the MP4 or MOV. Here's what's there and how to clean it.

TL;DR: A Runway video export is an ordinary container — MP4 (H.264) on Basic and Standard plans, with ProRes 4444 added on Pro and Unlimited. The identifying data lives in the moov movie box: mvhd stores creation and modification timestamps as seconds since 1 January 1904 UTC, and the udta / meta sub-atoms hold encoder and software strings (the ©too atom), plus any XMP packet. Runway does not currently embed C2PA Content Credentials or a SynthID-style watermark in its files, so the removable layer is just the container metadata. Opening the file in Metadata Cleaner and clicking Clean rewrites that container — timestamps, encoder tags, XMP — without touching a single frame. What it cannot remove: a free-plan visible watermark burned into the pixels, or anything Runway keeps server-side.

So you generated a clip in Runway, downloaded it, and assumed the file was a clean slate. It mostly is — but "mostly" is doing some work in that sentence, and we'd rather show you the bytes than wave our hands.

This post covers what Runway actually writes into an export, whether any of it is C2PA Content Credentials, the thirty-second clean, how to verify it worked, and — the part most guides skip — what stripping metadata does not fix.

What Runway Actually Writes Into Your Video File

Runway hands you a standard container, not a proprietary format. Per Runway's own export documentation, Basic and Standard projects export to MP4 (H.264) only, while Pro and Unlimited add formats such as ProRes 4444. Both MP4 and MOV are flavors of the same ISO Base Media File Format / QuickTime structure, which means the metadata lives in the same place and reads the same way regardless of which plan produced the file.

That structure is a tree of boxes, also called atoms. The one that matters for metadata is the moov box — the "movie box," which acts as the table of contents for the whole file. Inside it:

mvhd (movie header). Holds the file's two most basic timestamps: creation_time and modification_time, both stored as the number of seconds elapsed since midnight UTC on 1 January 1904. This is the field that quietly tells a reader when the export was rendered, down to the second.
udta (user data) and meta. These sub-atoms carry the descriptive tags. The ©too atom names the encoder or muxing software that wrote the file. On Apple-flavored MOV files you may also see keys like com.apple.quicktime.creationdate and com.apple.quicktime.software.
XMP packet. Some pipelines attach an XMP block — Adobe's XML metadata wrapper — that can mirror creation dates and tool names. If a Runway clip is round-tripped through an editor before you export it, this is where editing-history tags tend to accumulate.

Worth being precise here, because it's where most "Runway stamps its name on your file" claims fall apart: the ©too / software string usually records the muxing library, not the marketing name of the model. A clip that passed through a standard MP4 muxer typically shows a generic encoder string rather than the word "Runway." We're not going to assert a specific atom value we haven't seen in your specific file — the honest claim is that the container carries timestamps and an encoder/software tag, all of them editable, none of them pixel data. (We broke down what AI-generated files carry in general here.)

Dark screen filled with rows of green hexadecimal and numeric data Photo by Tibe De Kort on Pexels.

Does Runway Embed C2PA Content Credentials?

This is the question worth slowing down on, because the answer is changing and a lot of writing about it is out of date.

C2PA — the Coalition for Content Provenance and Authenticity — is the cross-industry standard for cryptographically signed provenance. Its specification does cover video: a C2PA manifest can be embedded in an MP4 as a signed data structure that records what tool made the file and what was done to it. Adobe's Content Credentials, several camera makers, and Google's Veo pipeline are among the implementations shipping today.

Runway is a different story. As of this writing, Runway does not embed C2PA Content Credentials in its standard exports. There is no signed manifest in the moov box to remove, because there's nothing being signed at export time. That makes the current state simpler than the AI-image world, where a Photoshop "Generative Fill" export or a Content Credentials-enabled tool genuinely does write a JUMBF manifest you have to strip deliberately.

We're flagging this as a moving target on purpose. C2PA video support exists in the spec and is being adopted across the industry; if Runway turns it on in a future release, the removable surface grows to include a signed manifest, and a plain container rewrite may need a C2PA-aware pass to clear it. For now, cleaning a Runway file means clearing ordinary container metadata. (Our full explainer on what C2PA is and how it travels is here.)

How to Clean Runway Video Metadata

The clean itself is short. Metadata Cleaner runs entirely in your browser — the file's bytes pass through the tab's memory and back to disk without ever being uploaded to a server, which is the same architecture behind our browser-only video tool.

Open Metadata Cleaner in any browser. Desktop or mobile both work; there's no login and nothing to install.
Drag your Runway MP4 or MOV into the drop zone, or tap to pick it on a phone. The file loads into the tab's memory.
Click Clean. The tool walks the container, drops the udta / meta user-data atoms, neutralizes the mvhd creation and modification timestamps, removes any XMP packet, and writes a fresh file. The video and audio streams are copied through untouched — no re-encode, no quality loss.
Click Download. The cleaned file lands back in your downloads or camera roll.

The frames are byte-identical before and after. Stripping container metadata does not re-compress the H.264 or ProRes stream; it only edits the boxes that sit alongside the picture data. A typical short clip cleans in well under a second.

Video editing timeline open on a laptop in a dim room Photo by Muhammed Çetinkaya on Pexels.

How to Verify the Metadata Is Gone

Trusting a tool is fine; verifying it is better. Three ways to confirm the clean worked, in rising order of thoroughness:

ExifTool. Phil Harvey's exiftool reads QuickTime/MP4 tags. The one-liner exiftool -G1 -a -u clean.mp4 dumps every group and every duplicate; the -u flag forces unknown tags to print. After a clean, the Encoder, Software, and CreateDate fields should be absent rather than blanked.
MediaInfo. The free MediaInfo app (GUI or mediainfo on the command line) shows a "General" section with Encoded date, Writing application, and Writing library. On a cleaned file those lines drop out.
Right-click → Properties / Get Info. The OS-level inspector is the shallowest check — it surfaces creation dates and sometimes the encoder — but it's the fastest sanity pass before you upload.

A quick word on what "creation date" means after a clean: your operating system stamps a filesystem timestamp the moment the cleaned file is written to disk, and that is not the same as the in-file mvhd timestamp. The filesystem date is local to your machine and travels with nothing; the mvhd date is what travels inside the file to whoever receives it. The clean targets the second one.

What Stripping Doesn't Touch (Honest Limits)

Removing container metadata is real, but it is not a cloak of invisibility, and anyone who tells you otherwise is selling something. Four things a metadata clean does not do.

It doesn't remove a visible watermark. Runway's free plan burns a visible watermark into the exported frames. That mark is part of the picture — it lives in the pixel values, not the moov box — so no metadata strip can touch it. The only ways to get a clean frame are a paid plan that exports without the mark, or cropping, which degrades the image. Don't confuse "no metadata" with "no watermark."

It doesn't remove pixel-domain AI watermarks. A growing share of AI video carries an invisible watermark encoded into the pixel values themselves — Google's SynthID, which marks Veo output, is the most widely deployed example, designed to survive compression, cropping, and re-encoding. Runway is not known to embed one today, but the broader point holds for the category: a signal living in the samples is not in the header, so a container clean cannot reach it. This is the same header-versus-signal split we explained for audio in metadata versus watermarks.

It doesn't erase server-side records. Whatever Runway logs about a generation — the prompt, the account, the timestamp — lives on Runway's side, independent of what's in your downloaded file. Cleaning the file you hold does nothing to records you don't.

It doesn't change how platforms classify the upload. TikTok, Instagram, and YouTube run their own analysis at upload time and increasingly read provenance signals where they exist. A clean container removes one input to that process; it is not a guarantee of how a platform labels or distributes the clip. (We covered platform-side detection in depth here.)

The honest framing: cleaning a Runway export reliably clears the timestamps and tool strings in the container, which is the part that quietly travels with the file to every recipient. It is one clean layer, not the whole stack.

Audience in a dark cinema watching a glowing screen Photo by Bence Szemerey on Pexels.

FAQ

Does cleaning Runway metadata change the video quality?

No. The clean rewrites the container boxes only — it copies the encoded video and audio streams through without re-encoding. The moov box and the picture data are separate; editing one leaves the other byte-identical. Resolution, bitrate, frame rate, and color are all preserved.

Will the cleaned file still upload to TikTok, Instagram, and YouTube?

Yes. MP4 (H.264) and MOV are accepted everywhere regardless of whether they carry metadata. A cleaned file behaves like any other at upload, just a few kilobytes smaller.

Does Runway add C2PA Content Credentials to exports?

Not currently. The C2PA specification supports video, but Runway does not embed a signed manifest in its standard exports as of this writing. If that changes in a future release, a container clean would need a C2PA-aware pass to remove the manifest. The state today is ordinary container metadata only.

Can I clean a Runway video on my phone?

Yes. Metadata Cleaner is browser-only and runs on mobile Safari, Chrome on Android, and Firefox mobile. Drag-and-drop becomes tap-to-pick, and the cleaned file saves to Files or your camera roll.

Will cleaning metadata remove the free-plan watermark?

No. The free-plan watermark is rendered into the frames, not stored in metadata. Removing it requires a paid Runway plan that exports without the mark; a metadata strip cannot affect the pixels.

Is removing video metadata legal?

Yes. Container metadata is data you control on a file you own. No jurisdiction requires civilians to preserve creation timestamps or encoder tags. Narrow professional contexts with chain-of-custody requirements are the exception; outside those, stripping is your call.

Generated a clip you're about to post? Clear the timestamps and tool tags before it leaves your machine. Try Metadata Cleaner free — drop the file, hit Clean, download. The frames are yours; the paper trail in the container doesn't have to come along.