Convert 3GPP to DV — Free Online Tool
Convert 3GPP mobile video files to DV format, re-encoding the H.264 or MJPEG video stream to intra-frame DCT-compressed dvvideo and the AAC or MP3 audio to uncompressed PCM 16-bit audio. This is particularly useful for importing mobile-captured footage into legacy broadcast editing workflows and camcorder-era software that natively reads DV.
to
FFmpeg Command
Copy this command to run the same conversion locally with FFmpeg on your desktop. Download FFmpeg
Drop your 3GPP file here
or click to browse
Free — no uploads, no signups. Your files never leave your browser.
Settings
Note: Browser-based encoding uses approximate quality targets. For precise CRF compression, copy the FFmpeg command above and run it on your desktop.
Estimated output:
Conversion Complete!
DownloadHow It Works
This conversion is a full transcode — no stream copying occurs. The 3GPP container, designed for 3G mobile delivery with highly compressed H.264 video and AAC audio at low bitrates, must be entirely re-encoded to meet DV's strict format requirements. The video is decoded from its mobile-optimized codec and re-encoded using the dvvideo codec, which uses intra-frame DCT compression (every frame is independently compressed, with no inter-frame prediction). This contrasts sharply with H.264's GOP-based compression and means the output DV file will be significantly larger than the input 3GPP file. The audio is transcoded from compressed AAC (or MP3) to pcm_s16le — raw, uncompressed 16-bit little-endian PCM — which is the only audio format DV supports. The output is a flat .dv file with no support for chapters, subtitles, or multiple audio tracks.
What Each Flag Does
| Flag | What it does |
|---|---|
ffmpeg
|
Invokes the FFmpeg binary, the open-source multimedia processing engine that handles the full transcode pipeline from 3GPP demuxing through dvvideo encoding. |
-i input.3gp
|
Specifies the input 3GPP file. FFmpeg will demux the MP4-based 3GPP container and decode the H.264 (or MJPEG) video and AAC (or MP3) audio streams for re-encoding. |
-c:v dvvideo
|
Instructs FFmpeg to encode the video output using the dvvideo codec, implementing the DV25 intra-frame DCT compression standard used in MiniDV camcorders and broadcast editing workflows. |
-c:a pcm_s16le
|
Decodes the compressed AAC or MP3 audio from the 3GPP file and re-encodes it as raw uncompressed 16-bit signed little-endian PCM, which is the only audio format the DV container supports. |
output.dv
|
Defines the output filename with the .dv extension, telling FFmpeg to write a raw DV stream file compatible with legacy NLEs, DV decks, and broadcast editing software that reads the DV format natively. |
Common Use Cases
- Importing old mobile phone video clips into Final Cut Pro 7 or Avid Media Composer legacy projects that require DV-format media for timeline compatibility
- Migrating 3GPP footage captured on early Nokia or Sony Ericsson phones into a DV-based archive workflow where all video is stored as broadcast-quality intra-frame files
- Feeding mobile-captured 3GPP video into a hardware DV deck or tape dubbing chain that accepts DV file input for output to MiniDV tape
- Standardizing a mixed-format video project to a single DV codec baseline so that a legacy NLE can handle all clips without proxy generation
- Converting 3GPP footage from a dashcam or security device that recorded in mobile format into DV for frame-accurate editing without GOP decoding overhead
- Producing DV files from 3GPP source material for use with older DVD authoring software that accepts DV input but not H.264 or 3GPP containers
Frequently Asked Questions
No — this conversion cannot recover quality lost during the original 3GPP encoding. The 3GPP file was encoded with H.264 at a low mobile bitrate, and that lossy compression is permanent. Re-encoding to dvvideo introduces a second generation of lossy compression on top of the first, so the output DV file will have at minimum the same quality as the source, and potentially slightly less due to the additional encode step. DV's intra-frame structure offers more predictable quality per frame but not higher fidelity than the source.
3GPP files use H.264 with inter-frame compression, which achieves very high compression by storing only the differences between frames — resulting in very small file sizes optimized for mobile delivery over 3G networks. DV uses intra-frame compression, meaning every frame is encoded independently as a full image without referencing neighboring frames. This approach is far less space-efficient but more edit-friendly. Additionally, the audio is converted from compressed AAC to fully uncompressed PCM, adding further to the file size. A typical DV file runs around 13GB per hour of video.
DV is a strictly defined format with limited resolution and frame rate options: it supports 720x480 at 29.97fps (NTSC) or 720x576 at 25fps (PAL). If your 3GPP file was recorded at a non-standard mobile resolution such as 176x144, 320x240, or 640x480, FFmpeg will need to scale and potentially pad the video to fit one of these DV frame sizes. If the frame rate does not match, FFmpeg will perform frame rate conversion. You may want to explicitly specify the target frame rate and resolution with additional flags if the defaults do not suit your project.
DV exclusively uses uncompressed PCM audio, specifically pcm_s16le (16-bit signed little-endian), at either 48kHz or 32kHz. The AAC or MP3 audio in your 3GPP file will be fully decoded and re-encoded as raw PCM — this means no further lossy compression is applied to the audio in the output file. However, any quality lost during the original AAC or MP3 encoding of the 3GPP file cannot be recovered. DV does not support multiple audio tracks, so only the first audio stream from the 3GPP file will be included.
The command shown processes a single file, but you can batch process using a shell loop. On Linux or macOS, run: for f in *.3gp; do ffmpeg -i "$f" -c:v dvvideo -c:a pcm_s16le "${f%.3gp}.dv"; done. On Windows Command Prompt, use: for %f in (*.3gp) do ffmpeg -i "%f" -c:v dvvideo -c:a pcm_s16le "%~nf.dv". Each file will be transcoded sequentially. Be aware that this conversion is computationally intensive due to the full re-encode of both video and audio streams.
No. DV is a bare-bones format with no structured metadata container — it does not support GPS coordinates, device information, creation timestamps, or any of the rich metadata that 3GPP files can carry in their MP4-based container atoms. All such metadata will be discarded during conversion. If preserving this information is important, extract it from the 3GPP file using a tool like ExifTool or MediaInfo before converting, and store it separately.
Technical Notes
The dvvideo codec in FFmpeg implements the DV25 standard (approximately 25 Mbps for NTSC, 25 Mbps for PAL), which is the standard definition camcorder DV format. Because DV is constrained to specific resolutions (720x480 NTSC, 720x576 PAL) and chroma subsampling (4:1:1 for NTSC, 4:2:0 for PAL), any 3GPP source with non-standard dimensions will be automatically scaled by FFmpeg, potentially introducing letterboxing or stretching depending on the aspect ratio of the source. 3GPP files commonly use 4:2:0 chroma, which is compatible with PAL DV chroma but will be converted to 4:1:1 for NTSC DV — a chroma quality reduction. The DV format has no configurable quality parameter because the bitrate is fixed by the standard, so the command has no -crf or -b:v flag. PCM audio in the output requires no quality configuration either. The output .dv file uses a raw DV stream container with no index or seeking metadata, which means some players may not support random seeking. DV files are not suitable for web delivery or mobile playback and are intended exclusively for professional editing and archival workflows.