This page is the bytes job. The disk is full. A camera dump ate a folder. A screen recording is a brick and you want a copy that actually fits. Open Explorer, read the size, encode a lighter file, read the size again. The original stays until you are sure. The generic encode walk sits on Compress video. Writing an MP4 as the box sits on Mp4 compressor. Making a clip small enough that Discord will send it sits on Discord video compressor.
This is HandBrake. GPL-2.0. The HandBrake Team publishes it. We did not make it. Official files live on GitHub Releases. The repo is HandBrake/HandBrake. This site does not host the installer. Skip Softonic, CNET, and unofficial wrappers.
The button on this page goes to Install on the home page. Trust notes sit on Video compressor download safe.
Install so a video size reducer can run
Paste this into Windows Terminal or Command Prompt:
winget install -e --id HandBrake.HandBrakeCopy
If winget is missing, install App Installer from Microsoft, then paste again. Official Microsoft links only. The id is HandBrake.HandBrake. Do not paste a lookalike id from a comment thread.
HandBrake also needs .NET Desktop Runtime 10 from Microsoft. If the app will not open, or if the installer says the runtime is missing, install that runtime from Microsoft, then open HandBrake again. We do not host the runtime. We do not invent a Microsoft URL here.
The other path is GitHub Releases. Open tag V1.11.2. For most PCs take HandBrake-1.11.2-x86_64-Win_GUI.exe. On ARM Windows take HandBrake-1.11.2-arm64-Win_GUI.exe. A zip also sits on that release if you want a zip. Do not invent a newer tag here. File notes sit on Video compressor releases. LICENSE sits on Video compressor GitHub.
How to reduce video size
- Install HandBrake with the command on this page, or take
HandBrake-1.11.2-x86_64-Win_GUI.exefrom GitHub Releases (ARM:HandBrake-1.11.2-arm64-Win_GUI.exe). Add .NET Desktop Runtime 10 from Microsoft if needed. - Open HandBrake. You should get a window, not a browser tab.
- Open the video you already have. Pick a file on this disk: Documents, Downloads, a camera card, a recording you stored.
- Pick a smaller size in the app. Use the size controls HandBrake actually shows. We will not invent a preset title or an RF number.
- Start encode. Wait until the new file finishes writing.
- Check the new file has fewer bytes than the source. Right-click, Properties, read Size. If it is not lighter, pick a smaller size and encode again.
That list is the video size reducer path. The test is the byte count. Play the copy once so you know the picture still holds. Then decide whether the original can leave the disk.
Bytes are the metric
Video size reducer means fewer bytes. Not a new story. Not a new title card. The same clip, lighter on disk. Explorer Properties is the scoreboard. Size on disk and Size can differ a little on some volumes. Compare the same field on both files. If the copy is larger, you did not pick a smaller size.
A folder of camera files can hide the problem. Sort by size. The one file that is a brick is the one to open first. Reducing a small clip while a huge dump sits next to it will not free the drive. Open the heavy file. Encode that.
Free space in This PC is the other read. If the drive is already full, HandBrake cannot write the copy. Delete junk that is not the source, empty Recycle Bin, then encode. Do not delete the source until the copy plays.
Read the size before you encode
Right-click the source. Properties. Write the size down or leave the window open. After encode, Properties on the new file. If you skip the before number, you will guess. Guessing is how people keep a copy that barely moved.
Name the copy so you can tell it from the source. lecture-small.mp4 next to lecture.mp4 is clear. Overwriting the source is how a bad encode eats the only take. Browse a folder you control. Documents is fine. Do not point the destination at the same path as the source.
Date modified should be now. If you are staring at last week's file, you opened the source. Sort by date. Open the new name. Then read Properties.
Levers that actually cut bytes
Frame size is a hard lever. A 4K screen recording of a settings panel is wasted pixels if you only need to read the text. Drop the frame size in the app when the picture is far larger than you will watch. That cut is usually the biggest byte drop on a desktop capture.
Video rate is the other lever. If the frame size is already the size you need and the file is still heavy, drop the rate in the controls HandBrake shows. We will not print a number. Watch a short section of the copy. If faces smear, raise a step. If the file is still a brick, drop a step. Two or three passes on a one-minute slice teach you the trade before you spend an hour on the full file.
Audio adds weight. A talking-head clip does not need six channels. Leave a simple stereo track. If the source is silent, leave audio off. Extra commentary tracks you will never play are bytes you can drop in the app.
A smaller copy can look softer. That is the trade. Watch the result once on the screen you will use. A laptop screen hides softness that a TV will show. Judge on the device that matters, then keep or encode again.
Long files, short tests
A two-hour lecture is a long encode. Do not learn the size controls on that file. Cut a one-minute test if you have a way to cut, or pick a short clip from the same camera and match those controls. Then open the long file and use the same smaller size. The test file is the cheap lesson.
Duration is time, not a size control. An hour-long source stays an hour-long copy unless you open a shorter file. If you only needed the middle five minutes, make that shorter file first, then reduce that. This page still encodes the file you open. It does not cut time for you.
Queue several jobs if you have a folder of dumps. Add one, set a smaller size, add the next, start the queue. Do not open three copies of the program to race one disk. One queue, one machine. Watch the first job finish and check bytes before you trust the rest.
Keep the original until the copy is real
Start encode writes a new file. Closing the window mid-job can leave a half-written output. That stub is not the reduced file. Delete the stub and encode again. Let the job finish, or pause in the app if it offers a pause.
Play the copy in a player you already trust. If audio is missing, look at the audio track in HandBrake and encode again. If the picture is black, the source may be a type the app could not decode, or the destination path failed. Try a short known-good clip first, then return to the heavy file.
When the copy plays and Properties shows fewer bytes, you can copy the light file off the machine or delete the source. Deleting first is how people lose a take. The source is the backup until you say otherwise.
Disks, labs, and the Windows files
A USB stick that holds the source needs to stay plugged in for the read. Copy the source to the internal disk if the stick is leaving. Encoding onto a nearly full stick can fail the write. Prefer an internal folder with room, then copy the light file back if you need it on the stick.
A lab image may block winget and unknown installers. Then this install is closed for that hour. Do not fetch a wrapper to get around policy. Use a compressor already on the image, or wait until you control the PC. A borrowed laptop you return in twenty minutes is a bad place to leave HandBrake-1.11.2-x86_64-Win_GUI.exe.
After install, open HandBrake once. If Windows shows a SmartScreen prompt on a first exe, read the publisher. Prefer the GitHub asset. Winget skips some of that path because Microsoft already listed the package. Add .NET Desktop Runtime 10 from Microsoft if the window will not start.
Usual Windows pick is HandBrake-1.11.2-x86_64-Win_GUI.exe. ARM is HandBrake-1.11.2-arm64-Win_GUI.exe. Zip is on the same V1.11.2 release. Do not invent a newer tag. Pick one package. Do not run the installer and unpack the zip on top of each other. The install pointer is Install on the home page.
When the new file is not lighter
You did not pick a smaller size, or you compared the wrong file. Open the output folder. Sort by date. Properties on the new name. If that copy is still huge, pick a smaller size in HandBrake and encode again. Keep the original.
A zero-byte output is a failed write. Disk full is the usual cause. Free space, then encode again. A file that is actually a still image renamed to a video type will not become a light movie. Look at the real type. Save a real video, then open that.
If the app reports the source is damaged, try a second copy of the same clip if you have one. This page will not repair bytes. It will not host a recovery tool. If the copy in email still opens on another machine, save a fresh copy here.
What this video size reducer will not do
It will not pick an MP4 box as the whole job. That sits on Mp4 compressor. It will not promise a Discord upload will go through. That sits on Discord video compressor. It will not replace the generic compress walk. That sits on Compress video.
It will not host the installer. It will not be a star rating. It will not invent a preset title. It will not pull a clip from a website for you. Save the file first. It will not cut time off the source. Open a shorter file if you need a shorter file.
How do I reduce video size?
Install with winget install -e --id HandBrake.HandBrake or the Windows exe from GitHub Releases. Add .NET Desktop Runtime 10 from Microsoft if needed. Open HandBrake. Open the video you already have. Pick a smaller size in the app. Start encode. Check Properties. The new file should have fewer bytes. The install pointer is Install on the home page.
How do I know it worked?
Properties on the source, then Properties on the copy. The copy should be lighter and it should play. If it is not lighter, pick a smaller size and encode again. If it does not play, the write failed or you opened the wrong file.
Can I delete the original?
After the copy plays and the byte count dropped. Not before. The source is the backup. Uninstall is a separate step in Apps if you want HandBrake gone. Quitting the window does not uninstall and does not delete your files.
Did you make this video size reducer?
No. The HandBrake Team publishes HandBrake under GPL-2.0. Official files live on GitHub Releases. This site only points at that page. We do not host the installer. Back home if you want the short version.