Convert WMV to MP4 on Windows

WMV files still live in enterprise training libraries, old screen recordings, and camcorder archives. Modern upload forms, phones, and web players expect MP4 with H.264 instead. You hit the wall when SharePoint rejects the attachment, a client portal lists accepted formats in small print, or Teams shows a generic playback error. Converting locally avoids re-recording, keeps internal footage off third-party upload sites, and lets you trim or resize when the portal also caps megabytes.

WMV vs MP4

WMV (Windows Media Video) grew out of the Windows Media stack. MP4 is the default container for web uploads, mobile devices, and most editors today. Both hold compressed video, but MP4 with H.264 and AAC is what portals, LMS tools, and ad review systems accept by default.

	WMV	MP4
Common source	Windows Media exports, old camcorders, HR training archives	Web, phones, modern editors
Built-in Windows apps	Plays in some legacy apps	Widely accepted everywhere
Upload forms	Increasingly rejected	Usually accepted
Best first step	Re-encode to H.264 MP4	Already compatible

In practice, WMV appears in onboarding videos, vendor demos from years ago, and screen captures exported before MP4 became standard. MP4 is what you send for Slack, Teams, CMS uploads, and client review links. If the clip plays but the extension blocks upload, export is enough. If the portal also caps megabytes, trim first and consider lower resolution.

See the video compression guide when file size is the real blocker.

Export in Clipchamp

Clipchamp (built into Windows 11) handles one or two WMV clips when you do not need batch queues or exact megabyte targets.

1. Open the WMV in Clipchamp.
2. Trim the timeline to remove dead air at the start and end.
3. Export at 1080p (or 720p for email and chat attachments).

That gives you H.264 in an MP4-friendly file. Screen recordings with small UI text benefit from 1080p. Talking-head clips that play in a small embed often look fine at 720p with much smaller files.

Situation	Export choice
One clip for a ticket	720p after trim
Client review in OneDrive	1080p
Portal with a hard MB cap	Trim first, then compress further

Clipchamp does not batch twenty files or set a megabyte target. When export one-by-one gets old, use FFmpeg or GetCompress. For Apple-origin containers, see MOV to MP4 on Windows .

Convert with FFmpeg

FFmpeg in PowerShell handles batch archive migrations and codec control. Install with winget:

winget install --id Gyan.FFmpeg -e

Standard re-encode for sharing:

ffmpeg -i input.wmv -c:v libx264 -crf 22 -preset medium `
  -c:a aac -b:a 128k -movflags +faststart output.mp4

Flag	Plain meaning
-crf 22	Quality (lower = better, bigger; try 20 to 26)
-preset medium	Speed vs compression tradeoff
-movflags +faststart	Better for web playback start

Batch every WMV in a folder:

mkdir mp4-out
Get-ChildItem *.wmv | ForEach-Object {
  ffmpeg -i $_.Name -c:v libx264 -crf 22 -preset medium `
    -c:a aac -b:a 128k -movflags +faststart `
    "mp4-out\$($_.BaseName).mp4"
}

Older WMV files may use WMA audio. If the output has no sound, re-encode audio with -c:a aac instead of -c copy. When upload still fails, add -movflags +faststart and confirm H.264 video.

For MKV sources, see MKV to MP4 on Windows .

Using GetCompress

GetCompress fits recurring convert WMV to MP4 on Windows work when Clipchamp export per file is too slow or when an upload form enforces a megabyte cap.

Drop WMV training clips, legacy screen recordings, or a whole folder into the app. Choose MP4 output, set resolution and quality, or use target file size when the portal states a limit. Trim in the preview before export if the recording includes idle time at the start.

Useful workflow pieces in GetCompress:

• Batch queue: process an entire archive folder without opening each file in Clipchamp.
• Presets: save “1080p client review” or “720p ticket video” and reuse next week.
• Preview and trim: confirm UI text stays readable before sending a walkthrough.
• Folder monitoring: watch an imports folder and auto-convert new WMV files when your team drops legacy exports there regularly.
• Local processing: keep internal training and NDA footage on your machine instead of uploading to online converters.
• Target file size: when SharePoint or a client portal states a megabyte limit, hit the cap without guessing CRF values in PowerShell.

After conversion, if the MP4 is still too large, adjust quality or resolution in the same window rather than starting over in PowerShell.