Free online TRP to M2T converter

Some HDV editors, video ingest tools, and archival workflows expect MPEG-2 transport streams with an .m2t extension rather than a receiver-generated .trp file. Converting between them is often a container change, so the video can usually be preserved without re-encoding.

What the TRP format is

In the Video category, TRP generally denotes an MPEG-2 transport-stream recording created by a digital television receiver, satellite or cable set-top box, personal video recorder, or HDTV capture application. The file can contain MPEG-2 or H.264 video, one or more audio streams, subtitles, program metadata, and transport-stream timing information.

TRP is not a single codec specification. Its exact stream contents depend on the recording device, and some devices split long recordings into multiple TRP segments or add proprietary indexing. A TRP file may therefore play in VLC or a broadcast-stream utility while failing in a consumer editor.

What the M2T format is

M2T is a filename extension commonly used for an MPEG-2 transport stream, especially HDV camcorder footage and transport streams prepared for video-editing software. It is suited to sequential video transfer and editing workflows because it retains packetized audio, video, timestamps, and multiple elementary streams in one file.

The .m2t extension does not guarantee a particular resolution, frame rate, audio codec, or video codec. Many M2T files contain HDV-style MPEG-2 video, but an M2T output made from a TRP recording can retain another codec if the conversion only remuxes the streams.

How to convert TRP to M2T

Using FFmpeg without re-encoding

FFmpeg is the most controllable desktop method. First inspect the source:

ffprobe -hide_banner input.trp

If the file contains standard playable streams, remux it into an MPEG transport stream:

ffmpeg -i input.trp -map 0:v:0 -map 0:a? -c copy -f mpegts output.m2t

-c copy copies the audio and video packets, so this process avoids generation loss and is substantially faster than transcoding. The optional audio mapping keeps the command working when the recording has no audio stream. To retain all streams, including subtitles or additional audio tracks, use:

ffmpeg -i input.trp -map 0 -c copy -f mpegts output.m2t

Open output.m2t in the target editor or player and check video, audio synchronization, subtitles, and the complete duration. If the source contains damaged timestamps, FFmpeg may report continuity or decoding errors; remuxing cannot repair missing or encrypted content.

When re-encoding is required

Use transcoding when the target application rejects the source codec, the TRP stream is malformed, or the editor specifically requires HDV-compatible MPEG-2. A general MPEG-2 transport-stream conversion is:

ffmpeg -i input.trp -map 0:v:0 -map 0:a:0? -c:v mpeg2video -q:v 2 -c:a mp2 -b:a 384k -ar 48000 -f mpegts output.m2t

This creates new video and audio streams, so quality, file size, aspect ratio, interlacing, and frame rate should be checked afterward. HDV-specific applications may require fixed parameters such as 1440×1080 interlaced video and a 25 Mb/s video rate; select those values only when the receiving workflow documents them.

Using the online converter

You can convert the file on 101convert.com for free without installing software. Upload the TRP file, select M2T as the output format, start the conversion, and download the resulting file. This option is practical for ordinary, non-encrypted recordings; large files, protected broadcasts, unsupported codecs, and provider-specific TRP variants may require FFmpeg or the original receiver software.

Quality and compatibility limits

Remuxing changes the container and filename convention, not the encoded picture. It does not increase resolution, remove broadcast compression, restore missing frames, or make a proprietary or encrypted recording editable. If the source is already MPEG-2 transport stream data, stream copying is normally the preferred first attempt.

Use a direct conversion rather than simply renaming input.trp to input.m2t; the extension alone does not rewrite container metadata or repair packet structure. Some DVRs store incomplete final segments, proprietary encryption, or nonstandard timestamps, and these files may need to be finalized or exported by the recording device before conversion.