Is NowConverter uploading my video?
No. All video data stays inside this browser tab. The conversion library downloads from a public CDN when needed.
Video converter
WebM uses lightweight browser-native encoding. Other formats may use an experimental FFmpeg engine. Your video stays on your device.
Drag a video here or choose a file below.
MP4 · MOV · WebM · MKV · AVI and more · 120 MB maximum
Audio extraction requires an audio track in your source video.
For GIF, choose an end time no more than 12 seconds after the start. The GIF is limited to 480px width and 10 FPS, without sound.
Choose a video to get started.
WebM (and MP4 if your browser supports H.264/AAC recording) converts locally without a large download, at approximately real-time speed. MOV, GIF, MP3, WAV and unsupported MP4 require experimental FFmpeg (~32 MB) and are limited to 25 MB inputs; those conversions can fail on memory-limited devices.
Technical status
About this tool
Convert videos directly in your browser
Choose a video and convert it to MP4, WebM or MOV. You can also extract MP3 or WAV audio, or turn a short video clip into an animated GIF. Optional trimming, resolution and quality controls help tailor the result.
Privacy and performance
WebM uses your browser’s native video encoder. MP4 uses it only where H.264/AAC recording is available. Additional formats use an experimental FFmpeg WebAssembly engine downloaded from a public CDN only when needed. Your video is never uploaded. Native conversion runs at approximately real-time speed; the FFmpeg engine can exceed memory limits.
Can I convert any size video?
The general input limit is 120 MB. Experimental FFmpeg conversions are limited to 25 MB; small clips are recommended.
Will every codec work?
No. Input and output support depends on the codecs built into our FFmpeg WebAssembly engine. For unsupported files, try a smaller MP4 or WebM clip.
Video conversion depends on both the container and the codec
A filename such as .mp4 or .webm identifies a container, but playback also depends on the audio and video codecs stored inside it. Two MP4 files can therefore behave differently in the same application. Browser conversion is especially dependent on which encoders and decoders the current browser exposes or which local WebAssembly components can be loaded.
Transcoding is computationally expensive and is usually lossy, so avoid unnecessary repeated conversions. Decide whether your priority is compatibility, size, editing or web playback, then create a delivery copy from the best source available. For long or high-resolution media, a desktop editor or command-line encoder may offer more control and faster hardware acceleration.
Practical checks
- Keep the highest-quality original as your master.
- Test the exported file in the actual destination app or browser.
- Avoid converting the same compressed output repeatedly.
Practical walkthrough · video converter
Deliver a short clip in a compatible format
Example task: A collaborator asks for an MP4 version of a clip currently in a different supported container.
Try this workflow
- Choose a source the browser and converter can decode.
- Select MP4, WebM or GIF as appropriate and set the output options.
- Export a short sample first and verify audio sync, duration and playback in the recipient’s app.
What to expect
Containers and codecs are different: an MP4 file can still use a codec unsupported by the destination.
When to take extra care
Long or high-resolution videos can exhaust browser memory. GIF generally has no audio and may become very large.