F4V to MKV
Convert F4V to MKV in your browser. Nothing's uploaded.
Runs in this tab. The file stays here.
This runs in your browser. Nothing is uploaded. Longer clips take longer here than they would on a fast server. That's the trade-off for not sending the file.
Format hubs: F4V · MKV · Convert
About F4V to MKV
Converts F4V to MKV in your browser. Flash MP4 relative used by older Adobe tooling. Output is MKV. Nothing is uploaded.
F4V is flash MP4 relative used by older Adobe tooling. MKV is matroska container. Decode and encode via ffmpeg.wasm. This page is only that pair. It isn't a generic dump box that guesses the destination after an upload. If you have a different container, use that format's hub instead of forcing the file through the wrong decoder.
The clip is read into memory and converted with FFmpeg compiled to WebAssembly, loaded from this origin once (~30 MB) and then cached. You can open the network tab first: you should see this origin load, and on the first video or audio visit a local ffmpeg-core.wasm, not a POST of the file. After the page (and encoder, if this is media) has loaded, wifi can go off. That's the whole product, not a badge.
MKV is a lossless or uncompressed target. It won't restore detail a lossy F4V file already threw away. It stores the current samples or pixels more honestly, usually in a larger file. That's useful when the next tool in a chain insists on MKV, not when you're trying to “improve” a compressed original.
Related conversions sit on this same origin. F4V to another destination, or another source into MKV, are separate pages so the titles stay specific. The F4V hub and the MKV hub list every pair I actually ship. Missing pairs are missing because the encoder or decoder isn't here, not because they are paid.
Start from the F4V hub if you're leaving this format, or the MKV hub if you need to arrive in it. Those pages are indexes, not upload forms. A generic dropdown still exists under Video convert and Audio convert when you would rather pick the destination after you drop the file. Stills use jSquash or canvas; clips and recordings share the same FFmpeg core as the rest of the media tools. You can disconnect after that core has loaded.
How to use F4V to MKV
- 1Drop a F4V file. The in-browser encoder loads from this site the first time you open a video or audio tool.
- 2Click Convert. Encoding a long clip can take a while on a phone; that wait is local CPU, not an upload bar.
- 3Download the MKV result. It was never on my disk.
What it won't do
- Input is F4V (video/mp4,.f4v). A different container belongs on its own pair.
- The encoder is GPL FFmpeg in WebAssembly, single-thread, from this origin. Exotic codecs inside a familiar extension can still fail.
Common questions
Does converting F4V to MKV upload the file?
No. This is a static page. The clip stays in the tab. The network panel should show this origin, not a POST of your F4V file.
Will F4V to MKV look or sound the same?
Pixels or samples that are already in the F4V file are kept. Anything F4V already discarded is gone. MKV won't invent it back.
Why is there a separate F4V to MKV page instead of one converter?
Searchers type this pair. A generic convert tool with a dropdown is easy to build and easy to bury. Each pair is its own URL, its own title, and a file picker that expects F4V. The generic pickers still live at video convert and audio convert if you want a dropdown.
Can I convert MKV back to F4V on this site?
Yes: that's /convert/mkv-to-f4v. Going back and forth through a lossy codec twice is how you make mud. Do it once if you must.
Related tools
Why this one doesn't upload your file
There is no server to upload to. This page is a static file, and the work happens in your browser using the same graphics and WebAssembly code that renders every other site you visit. Your file is read from disk into memory, processed, and handed back as a download. Once the page has loaded you can disconnect from the network entirely and it keeps working. The longer explanation