How to convert MOV to MP4 on Windows 11 without installing software

You do not need to install anything. Open your MOV in the MOV to MP4 converter, which runs inside this browser tab on your Windows 11 PC, and save the MP4. Most MOV files from a phone or a camera already contain H.264 video and AAC audio, which are legal inside an MP4, so the tool copies the streams into a new container instead of re-encoding them. That takes seconds and the picture is bit-for-bit identical.

What does not work is renaming the file. Changing .mov to .mp4 in File Explorer changes the label on the box, not the box. Sometimes the result plays anyway, which is worse than failing, because you now have a file that some programs accept and others reject for no visible reason.

Why renaming .mov to .mp4 sometimes appears to work

MOV and MP4 are close relatives. QuickTime's MOV format came first, and when MPEG designed MP4 they built it on the same underlying structure — the ISO base media file format, a tree of nested boxes with four-letter names. That shared ancestry is the reason a renamed file often plays: a tolerant player such as VLC ignores the extension entirely, sniffs the first few bytes, recognises the box structure and gets on with it.

Strict software does not. A file's ftyp box near the start declares which specification it follows — qt   for QuickTime, isom, mp42 or similar for MP4 — and plenty of programs read that brand and refuse anything that does not match the extension. Worse, MOV is allowed to hold things MP4 is not: ProRes video, uncompressed PCM audio, timecode tracks, alpha channels, and QuickTime-only metadata atoms. Rename one of those and no amount of tolerance will help, because the contents are genuinely illegal in an MP4.

A real conversion rewrites the container: it reads the tracks out of the MOV structure, writes fresh MP4 boxes around them and fixes up the index so a player can seek. When the codecs inside are already MP4-legal, that is all that happens — no frame is decoded, no quality is lost. That operation is called a remux, and it is what you want.

Convert it in the browser, with nothing installed

This site's converter is FFmpeg compiled to WebAssembly, downloaded once and run in a background thread inside your tab. Your file is read from disk by the page and never leaves the machine — there is no upload and no server involved, which also means nothing to be retained or breached later. Once the page has loaded, it keeps working with the network switched off.

1. Open the MOV to MP4 tool and drop your file on it, or pick it with the file chooser.
2. Read the summary it shows you: container, video codec and profile, resolution, frame rate, duration, audio codec. This is what is actually inside the file, not what the extension claims.
3. Check the line that says whether it will copy the streams or re-encode them. For an ordinary H.264 MOV it will say copy.
4. Press Convert and save the MP4 where you want it.

Two limits are worth knowing before you start. Files above 2 GB are refused outright — a 32-bit WebAssembly heap cannot address them. Above roughly 300 MB the page warns you, because the work needs something like three times the file size in free memory. Subtitle tracks and any second audio track are dropped, and the tool tells you when that is about to happen.

What Windows 11 already gives you, and why it is slower

Windows 11 ships with Clipchamp, Microsoft's video editor, and it does accept MOV on import and export MP4 at 480p, 720p, 1080p or 4K. It is a genuine option if you have nothing else. But it is an editor, not a converter: it lays your clip on a timeline and renders the whole thing out again, which means every frame is decoded and re-encoded. That is slower than a remux and it is lossy by definition, however high you set the export quality. You also give up the original resolution unless it happens to match one of the presets.

The Media Player app is not a converter at all. It has had its codec coverage widened over the years and will open many MOV files, but it cannot save one as anything else, and MOV files carrying HEVC or ProRes are exactly the ones it tends to stumble on. If your real problem is that the file will not open, start with why MOV files fail to play on Windows instead — the fix may be simpler than a conversion.

When it will not be instant

A remux is near-instant no matter how long the clip is, because nothing is decoded. A re-encode is a different job, and the browser build here is single-threaded: think roughly real-time for 720p, slower than real-time for 1080p, and several times worse again if you ask for H.265 or VP9 output. A twenty-minute 1080p clip is an afternoon-coffee job, not a two-second one.

You will be re-encoding rather than copying when the MOV holds something MP4 cannot carry as-is, or something your destination cannot read:

• ProRes, from a camera or a Mac edit. It is not legal in an MP4 and has to be encoded to H.264 or H.265.
• Uncompressed PCM audio, common in camera MOVs. The picture can still be copied; only the audio needs re-encoding to AAC.
• HEVC from an iPhone, which is legal in an MP4 but may not play on the PC you are sending it to. That is a codec problem rather than a container one, and it has its own page: HEVC video that will not play on Windows 11.

If you want the reasoning behind picking a quality setting for the cases where a re-encode is unavoidable, converting MOV to MP4 without losing quality covers what "lossless" honestly means and when you can actually get it.

Find out what is inside the file first

Windows tells you almost nothing useful about a video. Right-click → Properties → Details gives you frame width, height, data rate and sometimes a codec name that is wrong or blank, because the shell relies on registered decoders to fill those fields in. It cannot tell you the H.264 profile, the audio channel layout, or whether the file is variable frame rate.

Loading a file into the converter shows you all of that without converting anything, and you can walk away afterwards. There is a dedicated page for that job too: check a video's codec in the browser. Knowing the codec turns "it does not work" into a specific question with a specific answer, and it takes about five seconds.

If the MP4 still misbehaves afterwards

A container swap fixes container problems. It does not fix everything, so match the symptom to the cause:

• Video plays, no sound. Usually the audio codec, not the container — camera MOVs with PCM audio and iPhone clips with multichannel tracks are the usual suspects. See video plays but there is no sound.
• An editor still refuses it. Editors are pickier than players, particularly about variable frame rate footage from phones and screen recorders. Converting variable frame rate to constant frame rate explains what they are actually objecting to.
• It is too big to send. A remux barely changes the file size, because the video data is unchanged. To make it smaller you have to re-encode; sending a video that is too large to email works through the sizes involved.

Why "no upload" is the part that matters

Most results for this search are either an installer or an upload. The installer route is closed to you on a work or school machine where you have no administrator rights, which is a large share of the people typing "without software" into a search box. The upload route works, but your footage then sits on somebody else's disk for as long as their retention policy says, and a big file crawls over a home upstream connection before any converting begins.

Running the encoder in the tab avoids both. The cost is worth stating plainly: your own CPU does the work, so a genuine re-encode is slower here than on a server farm, and very large files are out of scope. For the common case — an H.264 MOV that needs the right container around it — none of that applies, because there is nothing to encode. Are online video converters safe lays out what actually happens to a file you upload.