What a Luma export writes into the container
Luma’s consumer video generator became widely known as Dream Machine, and the clips it hands back are MP4 downloads. The developer documentation at https://docs.lumalabs.ai/docs/video-generation shows the same pattern: a generation completes with a video URL, and the example downloads that URL as an MP4. The model names have moved on. That page lists Ray 2 and Ray 2 Flash, while Luma’s official information page at https://lumalabs.ai/llm-info names Ray3.2 as the current video model and calls Dream Machine an older, deprecated name. The container mechanics do not depend on which label is on the generation.
An MP4 is a box tree. Every box carries a size and a four character type, and boxes nest inside one another. The MP4 Registration Authority publishes the registry of box and atom types, and its user data table lists codes such as swre for the software that wrote the movie, auth for the author, cprt for copyright, date for a creation time and loci for location, at https://mp4ra.org/registered-types/boxes. The footage sits in a media data box, and the movie box holds the track descriptions and the sample table that lets a player seek through the file. Metadata lives in those descriptive boxes, apart from the coded frames.
What Luma publishes about its own output is narrower than people expect. The licensing page at https://lumalabs.ai/learning-hub/licensing covers plans, watermarks and commercial rights. The API FAQ at https://docs.lumalabs.ai/docs/faq adds that images and videos made through the API have no watermarks of any sorts. Neither page publishes a metadata field map, a list of provenance keys or a C2PA statement for Dream Machine or Ray downloads. Some third party pages assert that a Luma MP4 carries a signed Content Credential, but Luma itself says nothing there we could verify, so this page does not repeat that claim as fact.
A Luma file can still carry the ordinary record that any MP4 pipeline writes. That includes creation and modification times in the movie header, a software string in the swre user data code, the stream handler names, possibly an XMP packet, and app export keys that name the tool. If a generation stage attached a C2PA manifest store, it sits in a top level box of the same tree. The C2PA technical specification at https://spec.c2pa.org/specifications/specifications/2.5/specs/C2PA_Specification.html lists the ISO Base Media File Format among the formats it can be embedded in and describes the manifest store and the hard binding that ties it to the media.
The strip works on the provenance bearing parts of that record, not on every box. It reads the container for the provenance entries and generator signatures it knows, and a video pass cannot rewrite the whole tree without breaking the sample table and the media offsets. An ordinary title, author or creation time entry that carries no provenance can survive, and the limitations below say so in full. That restriction is the honest shape of this tool rather than an unfinished feature.
Why the visible Luma mark is outside this page
The licensing page draws a line by plan. It says content generated on the Free and Lite plans includes a watermark that cannot be removed, even if the subscription is upgraded later, and that those generations stay personal use only. Plus, Unlimited and Enterprise output carries commercial rights and no watermark. The API FAQ adds a separate channel rule: videos made through the API have no watermarks of any sorts. Luma ties these rights to the plan that was active when the clip was generated, not to the plan in force when someone opens the file.
A visible mark is not a box. It is drawn into the pixel values inside the media data box, so it travels with the frames through every copy, conversion and republish. Rewriting a container record changes what a verifier reads about the file. It does not repaint a single frame. That is why a metadata strip cannot take a corner wordmark off a Free or Lite clip, however clean the box tree becomes afterwards.
Our removal registry lists the visible marks that the frame level pipeline is configured to handle, and the Luma mark is absent from that list. The first screen therefore says this page will not remove the visible Luma mark, and nothing below contradicts it. The AI Video Watermark Remover runs a different pipeline over its own supported mark set, which also leaves Luma out, so it is background on the visible layer rather than a Luma fix.
For a clip that already shows the mark, the licensed route is a new generation on a plan Luma documents as watermark free, or through the API where the FAQ says output has none. A crop can cut the mark out of the frame, but that is a destructive edit outside this page. Neither route changes the file you already hold, and neither one is a metadata operation. This page stays on the metadata side and leaves the visible layer to the pages above.
How to keep provenance data out of a Luma export
Start from the download Luma gave you
The file that comes straight out of Dream Machine or the API is the fullest record of the job. A copy saved from a chat thread, a screen recording or a repost may already have lost fields, and it can also carry a new software string from whichever app touched it. Begin with the download from your own workspace so the strip has a known starting point.
Strip after the last edit, not before
A converter, an editor or a cloud sync that touches the file before upload can write a software string or a provenance entry of its own. Clean the clip once the edits are finished, then send that file straight to the destination. If you trim or resize later, run the strip again, because the app saving the new version may add tags.
Inspect what actually stayed
Play the finished file once, then read its container record with a viewer. The frames and the soundtrack should match the source, and the provenance entries should no longer appear. Some ordinary fields may remain when they carried no provenance, because the MP4 and MOV path keeps the box offsets in place. Use the job report as a hint and confirm in the file itself.
Check the rights before you run it
Luma’s terms reserve the right to embed watermarks, content credentials and provenance metadata, and they say customers may not remove, alter, obscure or circumvent them. Whether a strip is permitted depends on your agreement and the law where you operate. Work on files you generated or are licensed to edit, and read the terms before you touch a Luma export.
How it works
How to strip the metadata from a Luma clip
Step 1: Upload the clip
Choose an MP4, MOV, WebM or MKV clip and add it through the panel below, or click to browse. Your browser sends the file straight to processing storage; nothing is published. Until a strip runs, the copy on your disk is unchanged, so you can compare the two afterwards.
Tip
Start from the download Luma gave you, not a copy saved from a chat, because that copy may carry a different record.
Step 2: Run the metadata strip
The panel loads a single video metadata operation with removal enabled, so there is nothing to configure. On MP4 and MOV the job reads the box tree and replaces the provenance boxes and the generator entries it recognizes in place. Box lengths and byte offsets stay valid, so the audio and video samples pass through without a second encode. On WebM and MKV it remuxes with a stream copy and drops the tag list and the chapter list. The result is a new file, and the upload is never overwritten.
Tip
Credits are used only when a strip actually runs.
Step 3: Download and check
Once the run completes, download the cleaned clip and play it through before sharing. Picture and sound should match the original. If you want to confirm exactly which entries disappeared, load the output into a metadata viewer. If you were signed out, signing in brings the panel back where you left it.
Tip
Upload the cleaned file directly to the next platform. A converter or editor run afterwards can write new metadata into it.
Limitations and what a Luma export keeps
Where to go next
Choose by the layer you need changed. The Video Metadata Remover covers the container layer on any video, including C2PA boxes, tag lists and the coded stream boundary. The AI Video Watermark Remover covers the visible layer, but only across its own supported mark set, which does not include Luma. The Runway Metadata Remover applies the container strip to a different video generator and draws the same line on the visible mark.
The facts here come from official pages. The licensing guide at https://lumalabs.ai/learning-hub/licensing states the watermark and commercial rights position by plan, and the API FAQ at https://docs.lumalabs.ai/docs/faq covers the API channel and its watermark position. The terms of service at https://lumalabs.ai/legal/terms-of-service reserve the right to embed provenance and restrict its removal. The video generation documentation at https://docs.lumalabs.ai/docs/video-generation shows the MP4 download path. The C2PA technical specification at https://spec.c2pa.org/specifications/specifications/2.5/specs/C2PA_Specification.html describes the manifest store and its ISO Base Media File Format embedding, and the MP4 Registration Authority lists box and user data types at https://mp4ra.org/registered-types/boxes. Luma 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 Luma exports, from the container record to the visible mark this page does not promise to remove.
Explore more tools
AI Video Watermark Remover
The visible layer explained: how a frame level pass works over its supported marks, and why Luma is not in that set.
Video Metadata Remover
The container layer in depth, from C2PA boxes to the tag and chapter lists a stream copy drops.
Runway Metadata Remover
The same container strip applied to another video generator, with the same boundary on the visible mark.
C2PA Remover
The credential record inside a video container, explained on its own.
Pika Metadata Remover
A second platform checked for video container metadata, with the visible mark out of scope.
All tools
Every remover and detector on one page, grouped by what each one cleans or checks.
Strip the metadata before the clip leaves your hands
One pass clears the provenance boxes and recognized generator entries a Luma file can carry, while the footage and the soundtrack stay as they were.