How to strip the editor / encoder software stamp from video exports
- Step 1Confirm the stamp before you deliver — Open the export in any media-info viewer or run
ffprobeto see theencoder/ software string, the exportcreation_time, and any title/chapter markers. That tells you exactly what the scrub will remove from the file you're about to send. - Step 2Drop your export — Upload the finished deliverable — MP4, MOV, MKV, or WebM. The tool infers the container from the extension and keeps it on output, so the client receives the same container you exported. No format conversion happens.
- Step 3Choose Mode: all for a full white-label — The only control is a Mode select. default removes the encoder/software stamp, date, GPS, and device tags but keeps the title and chapter markers. all additionally runs
-map_chapters -1 -fflags +bitexact, wiping the project title and chapters and suppressing even FFmpeg's own version string. For a white-label deliverable, choose all so nothing about your tooling or project survives. - Step 4Run the scrub — FFmpeg runs
-i input -map_metadata -1 -c copy output(plus-map_chapters -1 -fflags +bitexactinallmode). Because it's a stream-copy, no codec runs — the encoded bytes pass straight through and only the metadata block is rewritten clean. - Step 5Hand off the clean file — Save the deliverable — same resolution, same bitrate, same frames, with no software stamp, no export date, and (in
allmode) no project title or chapters. The output keeps your export's container extension. - Step 6Record a delivery hash — For a clean handoff record, take a SHA-256 of the delivered file with multi-hash-fingerprinter so you can prove later exactly which file you sent. Confirm only the header changed against your master with file-integrity-monitor.
Editor / encoder stamps and how they're handled
Software identifiers different suites write into exports, and how -map_metadata -1 (plus +bitexact in all mode) handles each. These are all container metadata tags — none are part of the encoded picture — so removal is always lossless.
| Source | Stamp written | Removed? | Notes |
|---|---|---|---|
| Adobe Premiere / Media Encoder | encoder software name + version, export date | Removed | Goes with all other tags in one -map_metadata -1 pass |
| DaVinci Resolve | Software/encoder string, project metadata | Removed | Container tags only — wiped wholesale, not field-by-field |
| HandBrake | encoder stamp identifying HandBrake + libavformat | Removed | Cleared like any other tag |
| FFmpeg pipelines | Lavf<version> software tag | Removed (and suppressed in all) | Mode: all adds +bitexact so the scrubbing step writes no Lavf tag either |
| Project title / scene chapters | Title and chapters named after internal working files | Kept in default, removed in all | Mode: all runs -map_chapters -1 to wipe project-named chapters |
Mode option contract
The tool exposes exactly one control — a Mode select. There are no presets and no per-field toggles. These are the only two values and the exact FFmpeg arguments each produces.
| Mode | FFmpeg arguments | Suppresses FFmpeg's own stamp? | When to use |
|---|---|---|---|
default (default) | -map_metadata -1 -c copy | No — clears existing tags but writes its own muxer info | Strips the editor's stamp and date while keeping title and chapters as navigation |
all | -map_metadata -1 -map_chapters -1 -fflags +bitexact -c copy | Yes — +bitexact suppresses version/encoder strings | Full white-label: removes project title, chapters, and even FFmpeg's own identifier |
Formats, output, and tier limits
Real input formats and tier file-size limits. This security entry requires a Pro plan; processing runs through the Video Metadata Scrubber, so video-family streaming limits apply once the file is being scrubbed.
| Property | Value |
|---|---|
| Accepted containers | MP4, MOV, MKV, WebM (AVI, M4V, and TS extensions are also recognised) |
| Output | Same container as input (extension preserved); lossless stream-copy |
| Engine | FFmpeg compiled to WebAssembly, running in your browser tab — no upload |
| Minimum plan | Pro (this tool is not on the Free tier) |
| Pro file size | Up to 10 GB per file; up to 5 files |
| Pro-media file size | Up to 100 GB per file; up to 50 files |
| Developer file size | Up to 100 GB per file; unlimited batch |
Cookbook
Concrete recipes for white-labeling deliverables before handoff. The ffprobe-style listings show the metadata before and after the scrub; the footage itself is unchanged.
White-label a Premiere export with Mode: all
A finished MP4 carries Premiere's encoder stamp, an export date, and a project title naming the internal codename. For a client deliverable, Mode: all removes all of it and suppresses even FFmpeg's own version tag.
Before (ffprobe -show_format excerpt):
encoder : Lavf60.16.100 (Adobe Premiere Pro)
creation_time : 2026-06-09T11:30:00.000000Z
title : ACME_Q3_Spot_INTERNAL_v7
Scrub: Mode = all
ffmpeg -i deliverable.mp4 -map_metadata -1 -map_chapters -1 \
-fflags +bitexact -c copy deliverable-clean.mp4
After:
(no encoder/Lavf stamp, no creation_time, no title)
Video stream: bit-identical, full export qualityStrip the stamp but keep chapters (default)
A long-form tutorial export has useful chapter markers the client wants, but you still don't want your editing-suite stamp on it. Mode: default removes the encoder and date tags while keeping the chapters and title intact.
Before: encoder : HandBrake 1.8.0 Chapter #0: 00:00 'Setup' Chapter #1: 04:10 'Build' Scrub: Mode = default ffmpeg -i tutorial.mp4 -map_metadata -1 -c copy tutorial-out.mp4 After: (no encoder/HandBrake stamp) Chapters and title preserved as client-requested navigation
Remove the DaVinci stamp from a ProRes .MOV
A DaVinci Resolve master delivered as a ProRes .MOV carries the suite's software string. The scrub clears it without re-encoding the ProRes, so the master stays exactly as graded.
MOV (ProRes):
ffmpeg -i master.mov -map_metadata -1 -c copy master-clean.mov
-> DaVinci software/encoder string and project metadata removed
ProRes video stream copied untouched, grade unchanged
Note: output stays .MOV — the tool never converts the containerProve the deliverable wasn't re-encoded
To assure a client (or yourself) that white-labeling changed only metadata, compare the master and the clean file's streams with file-integrity-monitor — it reports byte-equality and the first-difference offset, which sits in the rewritten container header.
Workflow:
1. Scrub master.mp4 -> master-clean.mp4 (Mode: all)
2. file-integrity-monitor: drop master.mp4 (A) + master-clean.mp4 (B)
-> first-difference offset inside moov/header,
confirming the mdat (media payload) is unchanged
3. multi-hash-fingerprinter: SHA-256 the delivered file for recordsDeterministic re-runs for a delivery audit trail
When you need reproducible deliverables, Mode: all makes the output deterministic: the same input scrubbed twice yields byte-identical bytes, so a recorded hash always matches.
Run 1: ffmpeg -i spot.mp4 -map_metadata -1 -map_chapters -1 \
-fflags +bitexact -c copy out1.mp4
Run 2: (same command) -> out2.mp4
sha256(out1.mp4) == sha256(out2.mp4)
-> deterministic; safe to record one hash as the canonical deliveryEdge cases and what actually happens
Default mode still writes muxer info; use 'all' to suppress it
By designIn default mode FFmpeg clears the source's tags but the mux step can still write its own libavformat (Lavf) identifier. To suppress even that, use Mode: all, which adds -fflags +bitexact so no version/encoder string is written. For a true white-label deliverable, all is the right choice.
Burned-in studio bug / lower-third is not metadata
Not removedA logo, watermark, or lower-third rendered into the picture is part of the video frames, not the metadata block, so -map_metadata -1 cannot touch it. Removing a burned-in bug requires re-encoding with a crop or overlay tool, which is a different job than metadata scrubbing.
Audio and video streams are never altered
PreservedBecause the command is -c copy, the encoded picture (H.264/H.265/ProRes/VP9) and audio are copied byte-for-byte. The tool cannot transcode or re-grade — it only rewrites the metadata block. If you need to change the encode, that's a different video tool.
MKV / WebM are fully supported
SupportedThe underlying Video Metadata Scrubber accepts MP4, MOV, MKV, and WebM. -map_metadata -1 clears Matroska/WebM tags including WRITING_APP (the Matroska equivalent of an editor stamp) just like MP4-family atoms. The output keeps the same container.
Title and chapters survive in default mode
By designMode: default keeps the title and chapter markers, which is useful when a client asked for chapter navigation. If a chapter or title names an internal project, switch to Mode: all, which adds -map_chapters -1. There's no middle option to keep chapters but drop the title.
File over your tier's size limit
rejectedThis tool requires Pro. Pro allows up to 10 GB per file and 5 files; Pro-media up to 100 GB and 50 files; Developer up to 100 GB and unlimited batch. A high-bitrate master above your tier's ceiling is rejected before processing — upgrade or split. There's no Free-tier access.
Corrupt or incomplete export dropped
errorIf FFmpeg cannot demux the input — an export that was cancelled mid-write, a truncated transfer, or a renamed non-video — the run exits non-zero and the scrub fails with an error rather than producing a half-written deliverable. Re-export the master first.
Container is preserved, not converted
By designThe output uses the same extension as the input — a ProRes .MOV stays .MOV, an H.264 .MP4 stays .MP4. If a client needs a different container, scrub the metadata first, then run a separate format conversion; combining the two would change the encode.
Embedded poster frame / cover art
RemovedA poster-frame image embedded as a metadata attachment is part of the metadata block and is dropped by -map_metadata -1. If you want to inspect what thumbnails a deliverable hides before scrubbing, use hidden-thumbnail-extractor.
Re-running 'all' mode is deterministic
ExpectedMode: all adds -fflags +bitexact, suppressing FFmpeg's own version/encoder strings and timestamps. Scrubbing the same export twice yields byte-identical output, so a single recorded hash stays canonical for a delivery audit trail.
Frequently asked questions
Does this remove the editing-software name from a video?
Yes. The encoder / software stamp written by Premiere, DaVinci, HandBrake, and FFmpeg pipelines is a metadata tag, and -map_metadata -1 clears it along with every other tag. After scrubbing, a delivered file no longer names which suite produced it.
Will it also remove FFmpeg's own Lavf stamp?
Use Mode: all. In default mode the mux step can still write a libavformat (Lavf) identifier; all adds -fflags +bitexact, which suppresses FFmpeg's version/encoder strings so no Lavf tag is written. For a true white-label, choose all.
Does it remove project titles and chapter names?
In Mode: all, yes. default keeps the title and chapter markers (useful navigation); all adds -map_chapters -1 to wipe chapters and the title, which is what you want when they name an internal project or codename.
Is the deliverable re-encoded or re-graded?
No. The command is -c copy, a stream-copy. The encoded picture and audio are copied straight through; only the metadata block is rewritten. Your grade, bitrate, and frames are bit-identical to your master export.
Can it remove a burned-in logo or watermark?
No. A studio bug or watermark rendered into the picture is part of the frames, not the metadata block, so a metadata stripper cannot touch it. Removing a burned-in bug requires re-encoding with a crop or overlay, which is a different tool.
Does my client master get uploaded to a server?
No. FFmpeg runs as WebAssembly inside your browser tab. Your master never leaves the machine, which keeps confidential deliverables off third-party infrastructure.
Does it work on ProRes .MOV and MKV masters?
Yes. It accepts MP4, MOV, MKV, and WebM, and -c copy preserves ProRes, H.264, H.265, and VP9 streams untouched. For MKV it clears WRITING_APP and other Matroska tags. The output keeps the same container.
Why keep the same container instead of converting?
Converting the container would change the mux and potentially the encode; the scrub deliberately only rewrites the metadata block and preserves the extension so the deliverable is identical apart from the stripped tags. If a client needs a different container, convert separately afterward.
Can I make deliverables reproducible for an audit trail?
Yes. Mode: all adds -fflags +bitexact, so scrubbing the same input twice produces byte-identical output. Record one SHA-256 with multi-hash-fingerprinter and it stays canonical for your delivery records.
How can I prove white-labeling didn't change the footage?
Run the master and the clean file through file-integrity-monitor — it reports byte-equality and the first-difference offset, which lies inside the rewritten container header, confirming the media payload (mdat) is unchanged.
Can I batch-clean several deliverables at once?
Yes. Pro allows up to 5 files; Pro-media up to 50; Developer is unlimited. Each export is scrubbed independently and each output keeps its own container and quality.
What file sizes are allowed?
This tool requires Pro: up to 10 GB per file and 5 files. Pro-media allows up to 100 GB per file and 50 files; Developer allows up to 100 GB per file with unlimited batch. It's not on the Free tier, and files above your ceiling are rejected before processing.
Privacy first
Every JAD Security operation runs entirely in your browser. Files, passwords, and PGP private keys never leave your device — verified by zero outbound network requests during processing.