Video Steganography Hider
Conceal data within video files using Frame LSB, Audio Track, or Metadata embedding.
Drop your video here
MP4, AVI, MKV, MOV, WebM
Up to 500 MB
How to Hide Data in a Video (5 steps)
- Upload your carrier video (MP4, AVI, MKV, MOV, WebM — up to 500MB on desktop, 50MB on mobile)
- Enter your secret message or upload a file — optionally encrypt with AES-256-GCM
- Choose your encoding method — Frame LSB for high capacity, Audio Track for transcoding resistance, Metadata for instant lightweight embedding
- Configure bit depth, frame selection strategy, and optional Reed-Solomon error correction
- Click Encode — the output video looks and plays identically but carries your hidden payload
Video Steganography Methods — Algorithm Comparison
| Method | Description | Capacity | Best For |
|---|---|---|---|
| Frame LSB | Replaces least significant bits of pixel RGB values across video frames | High capacity (2–8 MB/min at 1080p 1-bit). Not compression-safe — use with lossless/direct transfer only | CTF challenges, lossless video watermarking, direct file transfer |
| Audio Track Embedding | Encodes payload in the LSB of audio samples in the video's audio channel | Medium capacity (~0.5 MB/min at 44kHz stereo). Survives video transcoding since audio codec is separate | Videos that will be transcoded or re-encoded while preserving audio |
| Metadata | Appends payload as a base64-encoded comment marker in the video file | ~4KB maximum. Survives direct file transfer. Stripped by video hosting platforms | Small messages, copyright metadata, direct peer-to-peer transfer |
| AES-256-GCM Encryption | PBKDF2 (100k iterations) + random salt + 12-byte IV applied before encoding | +44 byte overhead | Add password to make payload unreadable even if extracted |
| Reed-Solomon Error Correction | RS-10/20/30 — adds parity shards so payload survives partial frame corruption | +11–43% overhead | Payloads that must survive re-encoding, partial corruption, or lossy transcoding |
Frequently Asked Questions
Will the encoded video look different?
No. Frame LSB at 1-bit depth produces a PSNR above 40 dB — completely imperceptible to the human eye. The encoder shows PSNR per frame after encoding so you can verify quality.
Which method is best for videos shared on YouTube or WhatsApp?
None — YouTube and WhatsApp re-encode uploaded videos which destroys frame LSB and audio track steganography. Use steganography only for videos transferred directly (file share, email attachment, USB). Metadata-only survives on direct transfer only.
What is Frame LSB?
Frame LSB (Least Significant Bit) replaces the lowest 1–4 bits of each pixel's RGB values across video frames. A 1-bit change in a pixel value from, say, 200 to 201, is completely invisible but stores one hidden bit per channel per pixel. At 1920×1080, 30fps, that's over 1 billion bits per minute of video.
Does this work on mobile?
Frame LSB encoding is limited to 50MB videos on mobile due to processing constraints. For large videos on mobile, use the Metadata method (instant) or use a desktop browser.
What is Reed-Solomon error correction?
RS adds redundant parity data so the payload can be reconstructed even if some video frames are corrupted. RS-20 survives 20% frame data corruption. Recommended when the video may be partially edited, cropped, or re-encoded.
Is my video uploaded anywhere?
Never. All encoding runs 100% in your browser using Canvas API and Web Crypto API. Your video bytes never leave your device.