Is it really free?
Yes. No account, no card, no quota. encodevideos.com is sponsored by EdProgress as a public utility — see
About.
Where does my video go?
Nowhere. The encoding runs entirely in your browser. We have no copy of your video, your filename, or anything in between. You can verify this yourself in your browser’s DevTools Network tab — drop a video, watch the network panel, and you won’t see a single upload request. Full story on the
Privacy page.
What do you track about my use?
Aggregate counts: page views, how many encodes ran, success rate, broad input-size buckets, error types. Never your filename, file content, exact size, or anything personally identifying. Full event list on the
Privacy page.
What video formats can I drop in?
MP4, MOV, AVI, MKV, WebM, FLV, WMV, M4V, 3GP, MPEG, MTS, and most other common containers. Output is always MP4 (H.264 + AAC) for video, or MP3 or WAV for audio extraction.
What's the maximum file size?
4 GB. Files over 1 GB show a “this will take a while and may not work on low-memory devices” warning — encoding very large files in a browser tab is real work, and your computer’s RAM is the binding constraint, not our servers.
Why does my output look worse than I expected?
Output quality is a function of two things: the quality of your source video, and how much we have to compress it to hit your target size. A clean source shrunk a little still looks great. A heavily compressed source (a screen recording re-encoded twice, a phone video already trimmed in another app) shrunk hard will show artifacts that no encoder can rescue — you can’t squeeze detail back into a frame that lost it earlier in its life.
The other lever is duration. The same target size split across a longer video gives every second a smaller bitrate budget, so a 30-minute talk compressed to 25 MB will look much worse than a 5-minute clip compressed to the same size.
Workaround: split a long video into pieces.
If you’re unhappy with the quality on a long source, use Edit Mode to trim the video into shorter chunks and encode each one separately. Two 25 MB halves of a one-hour talk look noticeably better than a single 25 MB encode of the whole hour, because each chunk gets the full bitrate budget for its own duration.
Why is my output a different size than I asked for?
The encoder gets very close to the target but rarely lands exactly on it. We build in a small safety margin (~5%) so a 25 MB target reliably comes in under 25 MB rather than slightly over. For platform presets we use the platform’s documented limit as the target.
Does it work on mobile?
Best on desktop. iOS Safari and Android Chrome can encode short clips, but the multithreaded encoder isn’t always available on mobile and large files may run out of memory mid-encode. If you have a choice, encode on a laptop.
Why no account?
You don’t need one. No login means nothing to remember, nothing to leak, no email list, no password reset emails. Privacy as a default.
Where can I report a bug or suggest a feature?
See also: Privacy · About