Free online ISMV to M2T converter

ISMV files are commonly produced for Microsoft Smooth Streaming, while many HDV editors, cameras, and transport-stream tools expect M2T. Converting the fragmented MP4 video to an MPEG transport stream makes it easier to open in those applications and preserve it in an MPEG-TS workflow.

What the ISMV format is

ISMV is a fragmented MP4 media format associated with Microsoft IIS Smooth Streaming. It stores separately fragmented video or audio segments for adaptive streaming rather than as one conventional MP4 file. Microsoft Expression Encoder, IIS Media Services workflows, and Smooth Streaming packagers can create .ismv files.

You may encounter ISMV files in a Smooth Streaming output directory alongside an .ism server manifest and a .ismc client manifest. The manifest is not the video itself; conversion requires the actual ISMV media file. FFmpeg can usually read a standalone ISMV file because it is based on fragmented ISO Base Media File Format.

What the M2T format is

M2T is a filename extension commonly used for an MPEG-2 transport stream, especially HDV recordings. It typically contains packetized video and audio with transport-stream metadata, allowing the stream to carry multiple elementary streams and remain usable when transmission or recording is interrupted.

M2T is useful in HDV capture, broadcast-oriented workflows, transport-stream analyzers, and older editing software. The extension does not by itself guarantee one codec combination: some applications expect MPEG-2 video with MPEG audio, while others accept H.264 and AAC inside an MPEG-TS container.

How to convert ISMV to M2T

FFmpeg is the most controllable desktop option. Install a current FFmpeg build, open a terminal in the folder containing the source file, and inspect its streams first:

ffprobe -hide_banner input.ismv

For a broadly compatible MPEG-2 transport stream, re-encode the video and audio:

ffmpeg -i input.ismv -map 0:v:0 -map 0:a? -c:v mpeg2video -b:v 25M -c:a mp2 -b:a 384k -f mpegts output.m2t

The optional audio mapping allows conversion to continue when the ISMV contains video only. Change -b:v 25M to match the required delivery bitrate; 25 Mb/s is a common HDV-style value, not a universal M2T requirement.

If the destination accepts the source codecs inside MPEG-TS, avoid re-encoding with:

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

Stream copying is faster and preserves the encoded samples, but it can produce a file that an HDV-only editor rejects if the ISMV uses H.264 video, AAC audio, unsupported frame dimensions, or incompatible timing. In that case, use the re-encoding command and select the required frame size, frame rate, aspect ratio, and audio rate explicitly.

For a no-installation conversion, upload the ISMV file to 101convert.com, choose M2T as the output format, and download the resulting file. Check the service's size limits and avoid uploading confidential recordings.

Quality and compatibility limits

Changing the container with -c copy does not improve quality and may retain codecs that the target program cannot decode. Re-encoding to MPEG-2 introduces generation loss; use a bitrate at least as high as the source's effective bitrate when compatibility matters more than file size.

Inspect the output with ffprobe output.m2t. Confirm that the video codec, frame rate, resolution, audio codec, and bitrate match the receiving device. A Smooth Streaming package may contain multiple quality levels or short media fragments; converting one ISMV file converts only that file, not the complete adaptive presentation. To reconstruct a continuous program, identify and process the required fragments in playback order using the original manifest or packaging workflow.