Video Converter

Video conversion sounds like it should be simple — swap the extension, get a smaller file, move on. In practice, every conversion involves two independent decisions: the container (the "box" that wraps everything — MP4, MOV, MKV, WebM) and the codec (the algorithm that actually encodes the pixels — H.264, H.265/HEVC, VP9, AV1). Getting either wrong means a file that plays badly, plays not at all, or bloats to ten times the size it needed to be.

This primer covers what happens inside a video conversion so you can make deliberate choices for streaming, editing, archiving, or just getting a file to open on a specific device.

Container vs. codec — the split that trips everyone

A file called video.mp4 tells you almost nothing about what's inside. An MP4 container can hold H.264 video, H.265 video, or AV1 video — three completely different codecs with completely different quality-per-byte behaviour. Same story for MOV (usually H.264 or ProRes), MKV (anything), and WebM (usually VP9 or AV1).

When a video won't play, it's almost always the codec, not the container. When a video is huge, it's almost always the codec. When you convert MP4 to MP4 and the file shrinks by 60%, what you actually did was re-encode with a more efficient codec inside the same container.

The common formats at a glance

Bitrate — where file size actually comes from

The single biggest lever on video file size isn't the codec or the container — it's the bitrate. Bitrate is how many bits per second the encoder is allowed to spend describing the video. A 1080p video at 8 Mbps looks visibly better than the same clip at 2 Mbps. The same 1080p clip at 12 Mbps looks nearly identical to 8 Mbps but uses 50% more space.

Sensible defaults for H.264 video at 30 fps: 3-5 Mbps for 720p, 6-10 Mbps for 1080p, 25-40 Mbps for 4K. H.265 and AV1 achieve the same quality at roughly 60% of those bitrates, which is why modern streaming services have moved to them.

Choosing a target — a short decision tree

• Uploading to YouTube, Instagram, LinkedIn, or a website? Convert to MP4 with H.264. It's the universal safe target — nothing else needs installing.
• Editing in Final Cut, Premiere, or DaVinci? Keep the source in MOV / ProRes or convert to it. The editor will re-encode on export.
• Delivering to a modern web player with efficient streaming? WebM/VP9 or MP4/H.265 — both cut bitrate roughly 40% at the same quality.
• Archiving a family video collection? MKV with H.265. It handles multi-track audio and subtitles, and the file size stays reasonable.
• Sharing a short reaction clip? MP4/H.264. GIF looks tempting but plays back at a fraction of the quality for 10× the file size.
• Just want the file to play on grandma's Windows 10 laptop? MP4/H.264. Nothing else is that safe.

Resolution, framerate, and audio — the settings people forget

Converting a 4K master to a 720p delivery cuts file size by roughly 75% before you touch anything else. Similarly, 30 fps content doesn't need to be exported at 60 fps just because the source device supports it — half the frames at half the storage. Audio bitrate matters less than video (AAC at 128-160 kbps is inaudible from lossless for most content), but if the source has 5.1 surround, converting to stereo cuts more space.

What every iFormat video converter does the same way

All the tools listed below process video on isolated per-request workers, with TLS-encrypted uploads and 30-minute auto-delete on both source and output. No watermarks on paid tiers, no ads on any tier. Long video jobs (over a minute of source at 1080p) require sign-in on the free plan — this is server compute, not browser processing, and the sign-in keeps the queue orderly for everyone else.