Compress MPEG Online — Free File Size Reducer
Compress MPEG files in your browser by re-encoding with MPEG-2 video and MP2 audio at adjustable quality settings. Ideal for reducing file sizes of legacy broadcast or DVD-compatible footage while keeping output in the universally readable MPEG container.
to
FFmpeg Command
Copy this command to run the same conversion locally with FFmpeg on your desktop. Download FFmpeg
Drop your MPEG 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
Unlike simple remuxing, compressing an MPEG file requires full re-encoding of both the video and audio streams. The video is decoded from its original MPEG-1 or MPEG-2 stream and re-encoded using the MPEG-2 video codec with a quantization scale factor (-q:v) that controls compression aggressiveness — lower values mean higher quality and larger files, higher values mean smaller files with more visible compression artifacts. The audio is similarly decoded and re-encoded as MP2 (MPEG-1 Audio Layer II) at a target bitrate. Because MPEG is a lossy format and this is a lossy-to-lossy transcode, each generation of re-encoding introduces some quality degradation, so the goal is to find the lowest -q:v value that achieves your target file size without unacceptable quality loss.
What Each Flag Does
| Flag | What it does |
|---|---|
ffmpeg
|
Invokes the FFmpeg binary. In the browser tool, this runs via FFmpeg.wasm compiled to WebAssembly; on the desktop, this calls your locally installed FFmpeg executable. |
-i input.mpeg
|
Specifies the input MPEG file. FFmpeg will detect whether it contains an MPEG-1 or MPEG-2 video stream and decode it accordingly before re-encoding. |
-c:v mpeg2video
|
Sets the video encoder to MPEG-2, ensuring the output remains in a format compatible with DVD players, broadcast hardware, and legacy media software that require MPEG-2 video streams. |
-q:v 2
|
Sets the MPEG-2 quantization scale to 2 (the highest quality end of the 1–31 range), producing the smallest amount of additional compression artifacts. Increase this value to compress the video more aggressively at the cost of visible blockiness. |
-c:a mp2
|
Encodes the audio as MP2 (MPEG-1 Audio Layer II), the native and most widely compatible audio codec for MPEG-1 and MPEG-2 containers, required for DVD and broadcast MPEG-2 compliance. |
-b:a 192k
|
Sets the MP2 audio bitrate to 192 kilobits per second, a standard broadcast-quality bitrate for stereo MP2 audio that balances file size and fidelity. Lower this to 128k or 96k to reduce the audio portion of the file size. |
output.mpeg
|
Defines the output filename and container. The .mpeg extension tells FFmpeg to write an MPEG Program Stream, preserving compatibility with devices and software that expect standard MPEG-2 files. |
Common Use Cases
- Reducing the file size of archived MPEG-2 broadcast recordings before transferring them to legacy DVD players or set-top boxes that have limited storage or slow read speeds
- Shrinking large MPEG captures from VHS or LaserDisc digitization rigs to a manageable size for long-term archival without changing the container format required by older editing software
- Compressing MPEG footage from older camcorders or satellite receivers so it fits on FAT32-formatted media (SD cards, USB drives) with a 4GB file size limit
- Preparing smaller MPEG files for streaming over low-bandwidth connections or embedding in legacy media servers that specifically require MPEG-1 or MPEG-2 streams
- Batch-reducing the size of a large MPEG-2 video library captured from broadcast TV before uploading to a network-attached storage device with limited capacity
- Generating a lower-quality MPEG proxy copy of broadcast footage for offline editing or review, keeping the output in the native MPEG format expected by broadcast editing workflows
Frequently Asked Questions
Yes, some quality loss is unavoidable because both the input and output are lossy MPEG formats. Every time you re-encode, the MPEG-2 codec introduces new compression artifacts on top of any already present in the source. Using -q:v 2 (the default) preserves the most quality possible, while values above 5 will produce progressively more visible blockiness and detail loss, especially in high-motion scenes. If your goal is maximum quality, use the lowest -q:v value that still achieves your target file size.
-q:v sets the MPEG-2 quantization scale, where 1 is the highest quality (largest file) and 31 is the lowest quality (smallest file). At -q:v 2, the encoder uses very fine quantization steps, preserving fine detail and producing files that may only be marginally smaller than the input. At -q:v 31, quantization is very coarse, causing heavy blocking artifacts and color banding but yielding files that can be 10x smaller or more. For broadcast-quality output, values between 2 and 6 are typical; values above 15 are generally only acceptable for thumbnail previews or very low-bandwidth delivery.
MP2 (MPEG-1 Audio Layer II) is the native audio codec for MPEG-1 and MPEG-2 containers and is required for DVD and broadcast MPEG-2 compliance. While AAC and MP3 (via libmp3lame) are technically supported in the MPEG container by some encoders, MP2 ensures the widest compatibility with hardware DVD players, set-top boxes, and legacy broadcast equipment that strictly validate the audio stream type. If your target device or system specifically requires MP3 or AAC audio, you would need to modify the -c:a flag accordingly.
To increase video compression, raise the -q:v value in the command — for example, change '-q:v 2' to '-q:v 8' for a noticeably smaller file at the cost of some quality. To reduce audio file size, lower the -b:a value, such as changing '-b:a 192k' to '-b:a 96k' or '-b:a 64k'; note that MP2 audio at 64k will sound noticeably degraded for music but may be acceptable for speech. You can combine both changes: 'ffmpeg -i input.mpeg -c:v mpeg2video -q:v 10 -c:a mp2 -b:a 96k output.mpeg' for an aggressively compressed file.
Yes. On Linux or macOS, you can use a shell loop: 'for f in *.mpeg; do ffmpeg -i "$f" -c:v mpeg2video -q:v 2 -c:a mp2 -b:a 192k "compressed_$f"; done'. On Windows Command Prompt, use: 'for %f in (*.mpeg) do ffmpeg -i "%f" -c:v mpeg2video -q:v 2 -c:a mp2 -b:a 192k "compressed_%f"'. The browser-based tool processes one file at a time, so the FFmpeg desktop command is the recommended approach for compressing large collections of MPEG files.
No. The MPEG container format does not support subtitles, chapter markers, or multiple audio tracks in the way that MKV or MP4 do, and this compression command maps only the primary video and audio streams to the output. Any secondary audio tracks embedded in the source MPEG will be dropped. If your source has DVD-style subtitle streams (VOB subtitles), these are also not carried over. For multi-track or subtitle-rich sources, consider converting to an MKV or MP4 container instead.
Technical Notes
MPEG compression is a generation-loss operation: because the input is already lossy MPEG-1 or MPEG-2 video, re-encoding with mpeg2video adds a second round of DCT-based quantization artifacts. The -q:v parameter in FFmpeg's mpeg2video encoder maps to the MPEG quantization scale (qscale), which is not directly comparable to CRF values used in H.264 or H.265 encoders — there is no constant-rate-factor mode for MPEG-2, so bitrate control is less predictable and depends heavily on scene complexity. The output will always be a valid MPEG-2 Program Stream (.mpeg), compatible with DVD players and broadcast hardware that require MPEG-2 compliance. Note that MPEG does not support transparency, embedded subtitles, chapters, or multiple audio tracks, so none of these features can be preserved regardless of what the source file contains. The MP2 audio codec is fixed at CBR (constant bitrate), making the -b:a value a reliable predictor of audio stream size. Files processed in the browser via FFmpeg.wasm are handled entirely client-side — no data leaves your machine.