What a QuickTime file contains
MOV is the container associated with Apple QuickTime. It can package different kinds of encoded video and audio, so the extension alone does not identify the compression or image quality. Phone recordings and editing exports can both use MOV while containing very different tracks. Before converting an important recording, keep the original and check which codecs it uses. A browser that opens one QuickTime clip may still be unable to decode another.
What goes into the MP4 copy
This page writes an MP4 container with H.264 video and AAC audio when sound is present. The engine handles the primary tracks only. Existing H.264 video can be copied, and existing AAC audio can be copied independently. For example, a compatible picture track does not need to be encoded again just because the audio needs conversion. Extra soundtracks, embedded subtitles and attachments are not included, so keep the source for a complete archive.
Why the result may not be smaller
Repackaging compatible tracks changes their container without reducing their encoded picture or sound data. That can solve a format requirement, but it is not a size reduction setting. When a different supported codec needs conversion, the engine targets 8 Mbps for video and 192 kbps for audio. The new copy can therefore be larger than an already compact source. Compare size and playback after conversion, and use compression separately if your main problem is a heavy file.
Check camera formats before a handoff
HEVC and ProRes sources are not guaranteed to decode in this browser workflow. An unreadable track produces an error, even if the original plays in a desktop application. This output also makes no promise to retain HDR or transparency. For a client handoff, confirm that H.264 MP4 meets the request, then review the beginning, ending and sound in the converted copy. Retain a dedicated camera or editing export when special image properties are required.