StripShot vs FFmpeg vs HandBrake: Which Removes Video Metadata Best?
Published April 2026
When you search for how to remove metadata from a video, three tools come up consistently: FFmpeg, HandBrake, and StripShot. All three can modify video files. Only one actually removes AI-specific metadata like C2PA credentials without degrading your video quality. The differences matter, and they are not obvious from the documentation.
This comparison covers what each tool actually does to your file, why re-encoding is a problem for metadata removal, and which tool to use depending on what you actually need.
Full Feature Comparison
| Feature | StripShot | FFmpeg | HandBrake |
|---|---|---|---|
| Zero quality loss | Yes | No (re-encodes by default) | No (always re-encodes) |
| Removes C2PA UUID atom | Yes | No | No |
| Removes AI software strings | Yes | Partial | No |
| Removes ByteDance / CapCut fields | Yes | No | No |
| No installation needed | Yes | No | No |
| Free tier available | Yes | Yes (open source) | Yes (open source) |
| Batch processing | Yes (Pro) | Yes (CLI scripting) | No |
| Browser-based | Yes | No | No |
| Removes GPS / timestamps | Yes | Partial | No |
| Processes on your device | Yes (browser) | Yes (local CLI) | Yes (local app) |
FFmpeg: Powerful but Re-Encodes
FFmpeg is the most capable open-source multimedia toolkit available. For format conversion, stream manipulation, and filter processing, it is unmatched. For metadata-only removal with zero quality loss, it has significant limitations.
The common FFmpeg command for metadata stripping is:
Basic metadata strip (re-encodes video):
ffmpeg -i input.mp4 -map_metadata -1 output.mp4
Attempting copy-stream with metadata strip:
ffmpeg -i input.mp4 -map_metadata -1 -c:v copy -c:a copy output.mp4
Problem: -c:v copy prevents video re-encoding but does not remove the C2PA UUID atom. The UUID box is treated as an unknown top-level box and preserved in the output container.
The fundamental issue is that FFmpeg does not have specific awareness of the C2PA UUID identifier. It strips metadata tracks (moov udta, XMP) but leaves unknown UUID boxes intact. Sora videos processed through FFmpeg with -map_metadata -1 -c:v copystill trigger Instagram's "Made with AI" label because the C2PA UUID box survives the operation unchanged.
HandBrake: Re-Encodes by Design
HandBrake is a video transcoder. It was designed to decode source video and re-encode it at a different quality level, size, or format. There is no "pass-through container" mode that preserves the original bitstream while only modifying metadata.
Every HandBrake export involves a full decode-encode pipeline through libavcodec. The output file is a new video, not a modified version of the original. This means:
- Quality loss is unavoidable, even at maximum quality settings (CRF 0 or RF 0 still produces generational loss)
- File size changes (usually gets larger at high quality settings)
- All metadata is rewritten from HandBrake defaults, not surgically removed
- The C2PA UUID atom, ironically, does not survive HandBrake (it is stripped because the container is rebuilt from scratch), but neither does your original video quality
HandBrake is an excellent tool for its intended purpose: compressing large source files for distribution. It is the wrong tool for metadata-only removal because the side effects (quality loss, bitstream change) are inherent to its architecture.
StripShot: Binary-Level, No Re-Encoding
StripShot approaches video metadata removal as a binary file editing problem, not a transcoding problem. The video bitstream is never decoded. The audio stream is never touched. StripShot reads the ISOBMFF box structure of your MP4, identifies metadata containers by their box type identifiers, and writes the output file with those boxes excluded.
For C2PA specifically, StripShot targets the UUID box by its 16-byte identifier (d8fec3d6-1b0e-483c-9297-5828877ec481) and removes it entirely. For software strings, it nullifies the ©swr and ©too atoms in the moov header. For CapCut / ByteDance metadata, it removes the com.bytedance.* proprietary atoms.
The output file has the same video quality as the input. Not visually similar. Byte-for-byte identical video and audio data. The only difference is the metadata containers that were removed. Processing happens in your browser via WebAssembly, so no file is ever uploaded to any server.
When to Use Each Tool
Use StripShot when
- You need to remove AI metadata (C2PA, software strings, ByteDance fields) before uploading
- You need zero quality loss
- You want browser-based processing with no installation
- You need to remove GPS, timestamps, or device data without touching video quality
Use FFmpeg when
- You are already re-encoding for format conversion or resolution change
- You need batch processing via CLI scripting
- You need format features not supported by browser-based tools
- C2PA removal is not a requirement (or you use StripShot first, then FFmpeg)
Use HandBrake when
- You need to compress a large file for storage or distribution
- File size reduction is more important than preserving original quality
- You are transcoding to a different codec (H.265, AV1)
- Metadata is not a concern (or run StripShot on the source first)
FAQ
Can FFmpeg remove C2PA metadata from video?
Not reliably. FFmpeg's -map_metadata -1 flag strips standard metadata tracks (moov udta atoms, XMP data) but does not specifically target the C2PA UUID box in the ISOBMFF container. The UUID box is treated as an unknown top-level box and may survive even an explicit metadata strip. Testing confirms that Sora videos processed with FFmpeg -map_metadata -1 -c:v copy still trigger the Instagram 'Made with AI' label because the C2PA UUID atom remains intact.
Does -c:v copy in FFmpeg prevent quality loss?
The -c:v copy flag tells FFmpeg to copy the video stream without re-encoding, which preserves quality for the video stream itself. However, even with -c:v copy, FFmpeg may re-mux the container in ways that alter atom ordering and do not remove the C2PA UUID box. You get a re-muxed file, not a binary-identical file, and the C2PA metadata often survives.
Why does HandBrake always re-encode?
HandBrake is a transcoder, not a metadata editor. Its entire architecture is built around decoding and re-encoding video through libavcodec. There is no pass-through mode that preserves the original bitstream. Every HandBrake export involves full decode and re-encode, which changes the bitrate, introduces encoding artifacts at the chosen quality setting, and resets all metadata to HandBrake defaults. It is not the right tool for metadata-only removal.
Is StripShot processing done on my device or on a server?
StripShot processes entirely in your browser using WebAssembly. Your video file never leaves your device. The ISOBMFF parsing, UUID box identification, and file writing all happen locally in the browser sandbox. This is possible because binary-level box removal does not require server-side video decoding.
When should I still use FFmpeg over StripShot?
Use FFmpeg when you need format conversion (MP4 to WebM, for example), need to change codec or resolution, or are already re-encoding for another reason and want to strip metadata in the same pass. In those cases, quality loss from re-encoding is unavoidable anyway. If you only need metadata removed and want zero quality impact, StripShot is the correct tool.