Free online ISMV to F4V converter

A player, editor, or archive workflow may require Adobe F4V instead of the Microsoft Smooth Streaming fragments stored in an ISMV file. Converting the container can preserve H.264 video and AAC audio without re-encoding when the streams are compatible.

What the ISMV format is

ISMV is a fragmented ISO Base Media File Format container used by Microsoft Smooth Streaming. It normally contains a segmented H.264 video track; the matching audio is often stored separately in an .isma file. Smooth Streaming packages also commonly include an .ism server manifest and an .ismc client manifest.

Microsoft IIS Media Services, IIS Smooth Streaming publishing workflows, and Microsoft Expression Encoder can create ISMV media. You may encounter these files in archived adaptive-streaming packages, old Windows-based media servers, and downloaded Smooth Streaming content. A single ISMV may represent one bitrate track rather than a complete presentation, so converting it does not automatically combine alternate video qualities or separately stored audio.

What the F4V format is

F4V is Adobe's ISO Base Media Format container for H.264 video and AAC or other supported MPEG-4 audio. It was designed for Flash Player playback, Flash Media Server delivery, and progressive download, unlike the older FLV container commonly associated with Sorenson Spark or VP6 video.

F4V is useful when legacy Adobe video software or a media workflow explicitly requires the .f4v extension. It can store standard MP4-style H.264/AAC streams, but current web browsers and many modern players generally provide better support for ordinary .mp4 files than for F4V.

How to actually convert ISMV to F4V

Using the 101convert online converter

You can convert the file on the 101convert.com website for free without installing software. Select the video conversion option, upload the ISMV file, choose F4V as the output format, start the conversion, and download the resulting file when processing finishes. If the audio is in a separate ISMA file, combine the streams with desktop software first; uploading only the ISMV will normally produce video without that audio.

Using FFmpeg

FFmpeg is suitable when the ISMV is readable and its codecs are accepted by the F4V muxer. Inspect the streams first:

ffprobe input.ismv

For compatible H.264 video and AAC audio, use stream copying to avoid generation loss:

ffmpeg -i input.ismv -map 0:v:0 -map 0:a? -c copy -f f4v output.f4v

The optional audio mapping keeps the command working when the ISMV contains video only. If the audio is in a separate ISMA file, provide both inputs and map their streams:

ffmpeg -i input.ismv -i input.isma -map 0:v:0 -map 1:a:0 -c copy -f f4v output.f4v

If stream copying fails because of an unsupported codec, timestamp structure, or incompatible track metadata, re-encode:

ffmpeg -i input.ismv -map 0:v:0 -map 0:a? -c:v libx264 -preset medium -crf 20 -c:a aac -b:a 128k -movflags +faststart -f f4v output.f4v

Lower CRF values increase H.264 quality and file size; values around 18–23 are typical starting points. Remove -c:a aac -b:a 128k only when the source audio is already compatible and you are using -c copy.

Quality, compatibility, and limitations

Stream copying preserves the encoded picture and audio exactly, but it does not repair damaged fragments, missing segments, encryption, or incompatible codec parameters. Re-encoding reduces quality and requires enough processing time for the selected resolution and frame rate.

ISMV files protected with Microsoft PlayReady or another DRM system cannot be converted by FFmpeg unless the content has been legally decrypted through the original playback or delivery system. A fragmented ISMV may also be only one segment or one bitrate representation; a successful conversion can therefore be shorter, silent, or lower quality than the complete streamed presentation.

F4V is a container, not a video codec. H.264/AAC sources are the best candidates, while VC-1, MPEG-2, or unusual Smooth Streaming tracks usually require re-encoding. Test the output in the application that requires F4V because some legacy Flash-based software expects specific H.264 profiles, AAC settings, or non-fragmented metadata.