HandBrake is a free desktop video converter for Linux, macOS and Windows. It is useful when a recording is too large to share or will not play on the device you need. This guide takes you from an official download to one checked output file, then a small batch. It covers video conversion tasks that can otherwise require a paid encoder; it does not replace a complete editing timeline. The provider documentation was checked on October 14, 2026. AltStack has not installed or tested HandBrake on every supported operating system. Start with a short video you created or have permission to process, and keep the original.
1. Pricing and what you need before starting
The HandBrake project says everyone can use its video conversion software free of charge. The application uses GPL-2.0. This local workflow does not need a HandBrake subscription, paid AI credits or a hosted conversion allowance. Your computer, storage, electricity and any separate backup service still have their usual costs. A free application does not mean an old laptop can encode a long 4K recording quickly.
Prepare one short input clip, a folder for new files and enough free disk space to hold the original and the output together. Check the current System requirements page against your operating system, processor and memory before downloading. Requirements vary by release, so follow that page rather than a years-old installation tutorial. Decide where the result must play: a phone, a classroom computer, a television or a browser. That destination determines which preset is useful. Do not begin by converting your only copy of an important recording.
2. Download and install the official stable app
Open handbrake.fr and follow its Downloads link. Choose the stable graphical application for your operating system and processor. Beginners do not need a source checkout or a nightly build. The project publishes checksums for its downloads; compare the checksum of the downloaded file with the official one when you need to verify integrity. Stop if they differ.
On macOS, open the downloaded disk image and drag HandBrake into Applications. On Windows, open the official installer and follow its location and installation prompts. The current Windows instructions also require the matching Microsoft .NET Desktop Runtime; use the Microsoft link in the installation documentation if the app reports that dependency missing. On Linux, the project recommends its Flathub Flatpak for convenient installation and updates. Follow Flathub's setup for your distribution, then install the linked HandBrake package. Keep normal operating-system security protections enabled. If a warning appears, verify the release and its source instead of downloading a similarly named package from an advertisement.
3. Open a video you are allowed to convert
Launch HandBrake and use Open Source to select your input file. You can also drag a supported video into the main window. Wait for the scan to finish. If the source has several titles, select the intended one in the Title control. Check its duration before continuing; a short extra clip is easy to mistake for the main recording.
A phone recording or screen capture you made is a useful first example. HandBrake also understands a range of professional and disc-related formats, but support for a file container does not remove encryption or repair every damaged input. Its official documentation says it does not bypass copy protection or work with DRM-protected subscription video. This guide does not provide Netflix downloads, paid streaming catalogs or circumvention steps. If the input fails, test a different ordinary local recording and consult the supported-source documentation. Keep the input file separate from the folder you use for converted results.
4. Choose a preset for the destination
A preset is a saved group of conversion settings. After opening the source, select one that matches the device or use case you care about. For a first general-purpose test, the official documentation recommends Fast 1080p30 as a broadly compatible starting point. A device-specific preset may fit better when you know exactly where the file will be watched.
Treat the preset as a starting point, not a guarantee for every player. Read its name and check the selected output format before encoding. A preset with a resolution or frame-rate limit may change those aspects of your source, which matters for a high-frame-rate demonstration or fine screen text. Write down the chosen preset so another trial is comparable. Avoid switching several advanced controls at once. A sensible first goal is simply a file that plays on the intended device with readable detail and clear sound; you can optimize it further after confirming that baseline.
5. Adjust quality without chasing an arbitrary file size
Open the Video tab and begin with the preset's quality setting. Many presets use constant quality: the encoder aims for a chosen visual quality while file size varies with the content. Lower quality usually reduces size but can lose detail. For x264 and x265, the manual suggests RF 20–24 for 1080p as a starting range; a lower RF number means higher quality for those encoders.
Do not copy the same RF value into every encoder and expect the same result. Quality scales differ, and some hardware encoders reverse the direction of the numeric scale. Use the documentation for the encoder you select. Adjust in small steps and compare a short result before processing the full recording. Inspect slides, faces, movement and small text at the size people will actually watch. A screen tutorial may need different compromises from a landscape clip. If the upload service has a strict size limit, measure the finished test file; constant quality does not promise an exact number of megabytes.
6. Preview a short section before the full conversion
Select Preview in the toolbar. In the preview window, choose a starting position and a short duration, then use Live Preview to encode that sample. Wait for it to finish and play the result. Pick a difficult part of the recording, such as movement or small lettering, rather than only an easy static scene.
Check that the picture is not cropped unexpectedly, important text remains readable and sound is present. If the sample is poor, close the preview, adjust one setting and try again. Record the preset and quality value with your observations so you do not confuse two samples. Previewing saves time when a full video would take a long time to encode. It still uses your computer's resources and may not play exactly like every external device. Before a larger batch, also export one complete short clip and open it in the real player or service that matters to you.
7. Pick a new output path and start encoding
Find the Destination controls. Save As specifies the new file's name, and Browse lets you choose where it will be written. Use a distinct name such as lesson-small.mp4 in your output folder. Double-check both the folder and filename before selecting Start in the toolbar. HandBrake shows encoding progress; completion time depends on the input, settings and hardware.
Do not assume the file is missing just because it is not beside the original. Open the destination folder you selected. Play the finished file from beginning to end or spot-check the start, middle and final section before sharing it. Compare its duration and size with the original. Check the audio and any subtitles you need on the intended player. Retain the source until the result has been accepted for its real purpose. Conversion creates a new version and can discard information; the smaller file should not automatically become your only master copy.
8. Process several videos with the queue
For each input, choose its title, preset and destination, then select Add to Queue. Open Show Queue to review the pending jobs. Add another source the same way and give every output a unique filename. When the list is ready, start it with the queue's Start control or the main window's Start Queue control.
Begin with two jobs, rather than an entire archive. Check their output folders and filenames in the queue first. A batch is a collection of separate conversions, not a command to join clips into one video. The official interface differs slightly by operating system, so use its queue documentation for bulk title-selection and editing controls. If you edit a queued job, review its settings and add the revised job back when required by that workflow. Keep the computer powered and allow time for completion. Only expand the batch after confirming that the first outputs have the right content and do not overwrite one another.
9. Understand performance and the editing limits
Encoding speed depends on source duration, resolution, complexity, the chosen settings and the machine. Hardware encoders are available on supported systems, but the right choice also depends on output quality and compatibility. Follow the project's performance and hardware-encoder documentation before changing those settings. A faster run is useful only if its output still meets your needs.
For your own comparison, use the same short input and change one option at a time. Record elapsed time, output size and visible quality. This is a suggested exercise, not an AltStack benchmark or a promised speed improvement. HandBrake always converts the video stream; it is not a tool for lossless video pass-through. It also does not combine clips or provide a full multitrack editing project. For cuts, titles, animation or creative composition, complete that work in an appropriate editor before using HandBrake to create the delivery file. Keep the editing project and original media when you may need revisions.
10. Troubleshoot and keep files and logs private
If HandBrake will not launch, check that you installed the official stable release for your system. On Windows, check the documented .NET Desktop Runtime dependency and its processor architecture. Restarting and checking the current release guidance are better first steps than deleting settings. Back up custom presets before any reset or reinstall. If encoding fails, try a small ordinary video and note whether scanning or conversion is the failing stage.
The project's Activity Log is the useful starting point for support. Read it before posting: a log can reveal local folder paths, filenames and details about your media. Remove personal information from a public report while keeping the error and version information needed for diagnosis. This workflow converts local files rather than requiring an upload to a conversion website, but your backup, sharing and operating-system tools have their own privacy behavior. End the first session by storing the output and original in clearly named locations. Save the settings that worked so the next conversion begins from a known starting point.
Official instructions and sources
Official HandBrake downloadsFree software, capabilities and limitationsDownload and installation stepsCurrent system requirementsOpening a video sourceChoosing a presetQuality scales and recommended rangesPreview a short sampleDestination and starting an encodeUsing the queueCommon troubleshooting issuesPerformance and encoder tradeoffsActivity Log for supportSource and software licenseOriginal AltStack guide by Sushil Kumar Sah. Installation steps follow provider documentation; they do not imply testing on every supported device.