Quick answer

Open your AVI in HandBrake, start from the Fast 1080p30 preset, then set: Video encoder H.264, Framerate Same as source, Quality CRF 20–23, and on the Dimensions tab keep the source resolution (848×560 on a 450D, 768×512 on a 1000D — do not upscale). Hit Start. Expect roughly a 10× smaller file at quality you cannot distinguish from the original.

Step 1 — Install HandBrake

Download it from handbrake.fr (Windows 10/11 installer) and run through the setup. No plugins or extra codecs are needed — HandBrake reads MJPEG AVI files out of the box.

Step 2 — Open your source file

Drag an eos-movrec AVI into the HandBrake window, or use File → Open Source. After a few seconds of scanning, the title bar shows the clip’s resolution and frame rate — confirm it matches your camera (848×560 for the 450D, 768×512 for the 1000D, around 17–22 fps). If HandBrake refuses a file, convert that one with FFmpeg instead; severely non-standard AVIs occasionally trip the scanner.

Step 3 — Pick the right starting preset

In the Presets panel, choose Fast 1080p30 under General. Do not be alarmed by the “1080p” in the name — we are about to override the resolution. Starting here just gives us sensible H.264 defaults; the Dimensions tab is where we lock the real output size.

Step 4 — Video settings: H.264, same frame rate, CRF 20–23

On the Video tab, check these four things:

• Video Encoder: H.264 (x264). This is the efficient modern codec that shrinks MJPEG so dramatically.
• Framerate: Same as source with Variable Framerate. eos-movrec footage runs at roughly 17–22 fps depending on the body and USB conditions; forcing it to 30 fps would just duplicate frames and waste bits.
• Quality: Constant Quality, RF 20 to 23. RF 20 is near-transparent; RF 23 is a touch smaller with quality still fine for YouTube. Think of RF as “lower number = better looking, bigger file”.
• Encoder Preset: Fast is fine. Slower presets (Slow, Very Slow) squeeze out a few percent more compression but take much longer — rarely worth it for this footage.

Step 5 — Dimensions: keep the native resolution

On the Dimensions tab, make sure the output size equals the source: 848×560 (450D) or 768×512 (1000D). Set Anamorphic to None and modulus to 2. Do not upscale to 720p or 1080p here — upscaling inside the encoder just bloats the file without adding real detail. If you want a larger frame for YouTube, do it properly afterwards with our free upscaling guide.

Step 6 — Audio and subtitles: nothing to do

eos-movrec AVIs contain no audio track, so the Audio tab will be empty — that is expected, not an error. Leave Subtitles off as well. (Need sound in your final video? Record it separately and sync it in the editor — see our no-audio guide.)

Step 7 — Queue a batch and encode

Set the destination filename (use .mp4), then click Add to Queue instead of Start. Repeat for every clip, then open the Queue window and hit Start Queue — HandBrake will work through the whole list unattended. A typical eos-movrec clip encodes at several times real-time speed on a modern PC.

The “41 MB for 11 seconds” reality check

That 41 MB figure comes from real 40D footage: MJPEG stores every frame as its own JPEG photo, so the bitrate lands around 30 Mbps. After HandBrake at RF 20, the same 11 seconds typically drops to roughly 3–5 MB — small enough to upload, share, or keep. If a file comes out much bigger than that, double-check that the encoder is H.264 (not MPEG-4) and that you did not accidentally upscale the resolution.

Want it fully automated?

HandBrake’s queue is fine for a handful of clips, but if you have folders full of AVIs, a one-line script wins: our FFmpeg guide includes a Windows batch file that converts an entire folder — subfolders included — with a double-click.

Frequently asked questions

Which RF/CRF value should I actually use — 20, 23, or something else?

Start at RF 20. It is near-transparent for eos-movrec footage: side by side with the original AVI, you will not see a difference. If the files are still bigger than you would like, try RF 23 — slightly smaller, still perfectly fine for YouTube. Only go beyond 25 if file size matters more than quality, because softness and banding start to show.

HandBrake won’t open my AVI. What now?

First, confirm the file plays in VLC — if VLC cannot play it either, the recording itself is corrupt. If VLC plays it but HandBrake’s scanner hangs, the AVI headers are probably non-standard; convert that file with FFmpeg, which tolerates malformed AVIs far better, then continue from the MP4.

Should I upscale to 1080p in HandBrake’s Dimensions tab?

No. Upscaling at encode time just spends bits describing a bigger picture with no new detail — the file gets larger and YouTube gains nothing. Keep the native 848×560 / 768×512 here. If you genuinely want a larger output frame, upscale as a separate, deliberate step afterwards — our free upscaling guide shows how.

Can HandBrake convert a whole folder at once?

Yes, via the queue: add each file with Add to Queue, then Start Queue and walk away. There is no built-in “watch folder”, so for dozens of clips across subfolders the FFmpeg batch script is the faster tool.

YouTube re-compresses everything anyway — why bother compressing first?

Two reasons: upload time and upload reliability. A 41 MB original versus a 4 MB encode is the difference between a two-minute upload and a twenty-minute one — and a failed upload hurts ten times less when the file is small. YouTube’s re-encode of a clean H.264 source at RF 20 looks essentially identical to one made from the giant AVI.

My output looks blocky. What went wrong?

Almost certainly the quality setting: RF values above ~26 get visibly blocky on this footage. Re-encode at RF 20. If it still looks bad, check the Dimensions tab — an accidental upscale combined with a high RF is the classic double mistake.