MP4 to F4V Converter

How to Convert MP4 to F4V Online

1. Upload Your MP4 File: Drag and drop or click "Add Files" to select MP4 or M4V files. Phone recordings, screen captures, downloaded clips, and exports from editing tools all work as input. Batch is supported.
2. Pick a Codec and Quality: Default is H.264 paired with AAC audio — the only combination Flash Player 9.0.115+ decodes inside an F4V container. Pick a quality preset (Highest → Lowest), target a percentage of the source size or an exact size in MB, set a constant or variable bitrate, or fine-tune with CRF on the 0–51 scale (18 = visually lossless, 23 = default, 28 = smaller). Most modern MP4s already carry H.264 + AAC, so the encoder can re-mux without re-encoding when settings are left at defaults.
3. Resize or Trim (Optional): Pick a fixed resolution preset (1920×1080, 1280×720, 854×480, 640×360), enter custom width × height, scale by percentage, or trim using start time + duration in seconds or HH:MM:SS.sss format. Older Flash deployments often expect 480p or 720p — downscale during conversion to match the legacy player window.
4. Convert and Download: Click Convert. Files process in your browser session — no sign-up, no watermark, no upload to a third-party server. The output .f4v is ready to drop into a legacy Flash CMS or an archive folder.

Why Convert MP4 to F4V?

MP4 (ISO base media file format) is the universal modern video container — phone cameras, editing software, screen recorders, and streaming platforms all output .mp4 by default. F4V is Adobe's MP4-style container designed for Flash Player streaming — the box structure is essentially identical to MP4, but the extension and a few Flash-specific metadata atoms differ. Adobe officially discontinued Flash Player on December 31, 2020 and modern browsers removed Flash plugin support in early 2021, so MP4 → F4V is a niche legacy workflow rather than a mainstream conversion.

• Feeding archived Flash CMS systems — Internal corporate training portals, legacy university LMS deployments, and government e-learning platforms built on Adobe Media Server or Wowza ingest pipelines that still expect .f4v filenames. Re-wrapping new MP4 recordings into F4V keeps the existing playlist database working without a backend rewrite.
• Standalone Flash projector playback — flashplayer_32_sa.exe and the macOS / Linux projector apps still run offline for kiosks, museums, and trade-show displays built around legacy .swf / .f4v content. F4V is the format the projector loads via NetStream.
• Adobe Animate timeline imports — Adobe Animate (formerly Flash Professional) still imports .f4v for timeline video tracks. Authors maintaining legacy .fla projects need the F4V variant rather than raw MP4.
• Matching an existing F4V archive — Educational publishers and broadcasters who recorded thousands of lectures or shows to F4V between 2008 and 2015 often standardise new uploads to the same container so a single playback shim handles every file in the library.
• Forcing a Flash-compatible H.264 profile — Many newer MP4s use H.264 High profile, H.265, or AV1, which Flash never supported. The conversion lets you re-encode to H.264 Baseline or Main profile so a Flash-era decoder can actually play it.
• For modern playback, keep MP4 instead — F4V and MP4 share the same underlying container. If the goal is browser, phone, or smart-TV playback in 2026, the MP4 already works everywhere — no conversion needed. Use F4V only when a legacy Flash target specifically requires the extension.

MP4 vs F4V — Format Comparison

Codec / Quality Quick Guide for F4V

Frequently Asked Questions

Why would anyone still convert MP4 to F4V in 2026?

Adobe Flash Player reached end-of-life on December 31, 2020 and modern browsers no longer load it, so F4V is not a format you'd choose for new web video. The remaining legitimate use cases are feeding archived Flash CMS pipelines that still expect .f4v filenames, matching an existing F4V archive for consistency, importing video into Adobe Animate timeline tracks, and standalone Flash projector playback on offline kiosks. For any browser, phone, or smart-TV target, the original MP4 already plays everywhere — keep it.

Can I just rename my .mp4 to .f4v?

Sometimes, but not reliably. Both formats are built on the ISO base media file format, so the byte structure is similar. F4V differs in two ways: it carries Adobe-specific metadata atoms used by Flash's NetStream, and Flash Player only honours certain codec/profile combinations (H.264 + AAC) inside it. If your MP4 is already H.264 Baseline or Main with AAC audio, a rename often works in Flash. If it's H.264 High profile, H.265, or AV1, Flash won't play it — a real conversion is needed.

Will the conversion re-encode or just re-mux my MP4?

It depends on the source. When the input MP4 already uses H.264 + AAC and you leave the codec settings at defaults, the encoder can re-mux into the F4V container quickly with no quality loss. If the source uses H.265, AV1, or an audio codec Flash doesn't support, a full re-encode runs to convert the streams to H.264 + AAC. Re-encoding takes longer but is the only way to make a non-H.264 source play in Flash.

Which H.264 profile should I pick — Baseline, Main, or High?

Baseline for the widest Flash compatibility — works on every Flash Player 9.0.115+ build from 2008 onward, including older mobile Flash. Main for slightly better compression with broad compatibility on Flash 10+. High profile only works on Flash 11+ runtimes, so avoid it if the target system is an older Flash deployment. Most legacy Flash CMS pipelines were built around Baseline or Main.

What audio codec does F4V support?

AAC is the standard pairing — the encoder emits AAC by default. MP3 also works in F4V containers and plays on Flash, but AAC is more efficient at the same bitrate and matches the codec used by virtually every Flash-era streaming workflow. The other audio codecs available in the encoder (AC-3, FLAC, Opus, Vorbis, WMA) are not supported by Flash Player and will not play in F4V.

Will subtitles or multi-audio tracks survive the conversion?

No — F4V has no native subtitle track support, and only one audio stream typically plays in Flash. Soft subtitles embedded in the source MP4 are dropped unless you burn them into the video before converting. Secondary audio tracks (commentary, alternate languages) are dropped — convert a separate F4V for each language if you need switchable audio in your Flash player.

Will the F4V be larger or smaller than the source MP4?

Usually nearly identical when the source is already H.264 + AAC and the encoder re-muxes — the container overhead is essentially the same. If the source MP4 holds H.265 or AV1, the F4V output will be 2-3× larger at the same visual quality because H.264 is less efficient than the newer codecs. Drop the bitrate or downscale to 720p / 480p if the output is too large for your archive target.

Can I trim the MP4 while converting to F4V?

Yes. Use the trim section to enter a start time and duration. Both fields accept seconds (12.5) or HH:MM:SS.sss format (00:01:30.500). Trim out intros, recaps, or post-credits before the F4V is written so the archive copy is the exact runtime you want.

My target system says "FLV", not "F4V" — are they the same thing?

No — FLV is the older Flash Video container (2002, Macromedia/Adobe) wrapping Sorenson Spark, VP6, or H.264 streams, while F4V (2007) is the newer MP4-based container Adobe introduced for Flash Player 9.0.115+. Most legacy systems labelled "Flash Video" accept both, but some older players only read FLV. If your target rejects the F4V output, convert MP4 to FLV for the older container instead.