Choose H.265 for a straightforward Mac export; consider AV1 when a comparison shows worthwhile upload savings. QuickTime Player exports HEVC, while HandBrake offers both codecs. This guide helps you choose and check one finished YouTube upload file.

Which codec fits your delivery task?

For a Mac user with a finished video, H.265—also called HEVC—is the practical starting point. Apple documents HEVC export in QuickTime Player, and YouTube explicitly lists HEVC among its supported upload formats. That provides a documented route from a desktop movie to an upload without requiring an AV1 encoder. Apple’s QuickTime export guide, YouTube’s supported file formats.

AV1 becomes worth evaluating when reducing the delivery file matters enough to justify testing another encode. HandBrake documents SVT-AV1 software encoding alongside its H.265 options. Its Mac VideoToolbox documentation lists H.264 and H.265 encoders, with no AV1 encoder in that list; do not assume an AV1 hardware option will appear because your Mac offers accelerated HEVC. HandBrake video codecs, Apple VideoToolbox support.

Use the following decision aid as a workflow recommendation, rather than a claim that one codec always produces better results.

Your situation Recommended starting point What to verify
You want a simple export using an included Mac app QuickTime Player HEVC Available resolution and exported appearance
You want accelerated HEVC encoding with more settings HandBrake H.265 VideoToolbox, when available Actual encode time and picture quality
Upload size is a recurring constraint Compare HandBrake AV1 with HEVC Similar visual quality, file size, and total time
You already have an acceptable HEVC delivery file Test that file before converting again Successful YouTube processing and playback
You are delivering HDR Follow the HDR requirements below Color information and metadata, alongside codec

YouTube’s general upload recommendations still specify H.264 video in MP4. Its HDR guidance separately recommends AV1 and HEVC, among other codecs. These documents describe different requirements: accepting a format does not make it the default recommendation for every upload. H.264 remains a documented alternative if either workflow proves troublesome. Recommended upload encoding settings, HDR upload guidance.

How do you export H.265 using QuickTime Player?

For an ordinary finished movie that QuickTime Player can open, Apple documents this export sequence:

  1. Open the movie in QuickTime Player.
  2. Choose File > Export As, then select 1080p or 4K, as appropriate for the source.
  3. In the Format pop-up menu, choose Smaller File Size to use HEVC. Greater Compatibility selects H.264.
  4. Enter a new filename, choose a destination, and click Save.
  5. To monitor the export, choose Window > Show Export Progress. QuickTime Player export instructions.

The boundaries matter. QuickTime exports these movies as .mov, not MP4, and its documented export choices do not include AV1. Apple lists H.264 alone for the 720p and 480p export options. Resolutions above the source are dimmed, and the resulting resolution and data rate depend on the original. This workflow therefore supplies a convenient HEVC export, without a documented numeric bitrate control in the instructions. QuickTime export formats and limitations.

YouTube lists both MOV and HEVC as supported, so QuickTime’s MOV output does not by itself require another conversion. Keep the original and give the delivery copy a distinct name, such as graphics-demo-hevc.mov. Supported YouTube file formats.

How do you compare H.265 and AV1 in HandBrake?

Use HandBrake when you want to evaluate both codecs from the same finished source. The example here is a synthetic graphics demonstration containing small labels, moving geometric shapes, and smooth gradients. Start both candidates from the same original file so the comparison answers a useful question: which delivery encode preserves this material adequately?

Open the source and select an appropriate preset

With HandBrake installed, click Open Source, or drag the video into its main window. If the source contains multiple titles, select the intended clip with the Title control. Choose a preset, then set a separate output filename and destination. HandBrake’s quick-start guide documents these controls and the toolbar Start button used for the final encode. HandBrake quick start.

The current preset documentation lists Fast 2160p60 4K AV1 and Fast 2160p60 4K HEVC, both using MP4 with AAC stereo audio. These provide comparable starting categories, rather than proof of equivalent visual quality. Preset names describe maximum resolution and frame rate; a preset can reduce a source that exceeds those limits. Check the resulting dimensions, frame rate, and audio selection before proceeding. HandBrake official presets.

For accelerated HEVC on a supported Mac, HandBrake also documents H.265 Apple VideoToolbox 2160P 4K and H.265 Apple VideoToolbox 1080p presets. The Video tab exposes available VideoToolbox encoders. If they are absent, use an available software encoder rather than assuming a hidden hardware switch exists. HandBrake Apple VideoToolbox documentation.

YouTube recommends retaining the recorded frame rate. For an SDR project, its recommended color space is BT.709. Preserve those characteristics when they match your finished source; changing codecs is not a reason to alter the project’s timing or color treatment. YouTube upload recommendations.

Adjust quality independently for each encoder

Begin with the selected preset’s quality setting. HandBrake recommends constant quality for ordinary use, and its documented starting ranges for software encoding differ: at 1080p, x265 uses RF 20–24, while SVT-AV1 uses RF 25–35. These are testing ranges, not YouTube requirements. HandBrake quality guidance.

Do not match the RF numbers between codecs. HandBrake explicitly says quality values are not comparable across encoders. Lower RF means higher quality for x265 and SVT-AV1; VideoToolbox uses the opposite numerical direction. In HandBrake’s interface, moving the quality control to the right increases quality regardless of encoder. Understanding HandBrake’s quality scales.

Choose a quality level separately for each candidate, then compare the resulting pictures. For the synthetic demonstration, examine whether small lettering stays readable, moving edges retain their shape, and gradients remain smooth. A smaller file only meets the task if it also passes those checks.

Preview before encoding the full movie

Click Preview on the toolbar. HandBrake documents Position and Duration controls for choosing the test segment, followed by Live Preview to encode it. The resulting preview provides playback controls. Use a segment with both fine detail and movement, then repeat with the other codec. Previewing your settings.

For a fair comparison, use the same segment and duration, retain the same intended dimensions and frame rate, and record each candidate’s settings. Once both look acceptable, encode complete delivery copies with different filenames. Keep the original available until the chosen file has passed the upload check.

Does AV1 save enough upload time to justify its encode time?

Compare the complete delivery effort, rather than file size alone. A useful planning estimate is: local encode time + upload time. YouTube processing adds another stage, but its duration varies with format, length, frame rate, quality, and traffic, so treat it separately from this calculation. YouTube processing guidance.

The following numbers are explicitly illustrative, not measurements of HandBrake or a particular Mac. Suppose equally acceptable candidates produce these results, and the sustained upload rate is 20 Mbps. Using decimal gigabytes, estimated upload minutes equal file size in GB × 8,000 ÷ upload Mbps ÷ 60.

Illustrative candidate Encode time File size Estimated upload Encode + upload
HEVC 6 minutes 3.0 GB 20 minutes 26 minutes
AV1 22 minutes 1.8 GB 12 minutes 34 minutes

Here, AV1 saves eight upload minutes but requires sixteen additional encoding minutes. HEVC reaches the end of upload eight minutes sooner. With these particular inputs, the break-even upload rate is 10 Mbps: below that, the smaller AV1 file saves more upload time than its additional encoding cost. The estimate excludes transfer overhead, interruptions, and YouTube processing.

Substitute your own observed times and sizes. If encoding runs while you are away, you may value the smaller upload more than the additional local wait. If you need the file delivered promptly, total elapsed time may be the better criterion. Neither preference requires a universal claim about codec efficiency.

What changes when the source is HDR?

HDR requires a separate check before applying the ordinary SDR comparison. YouTube specifies 10- or 12-bit color, Rec.2020 primaries, Rec.2020 non-constant-luminance matrix coefficients, and a PQ or HLG transfer function. Correct HDR metadata must be present in the codec or container. Selecting a 10-bit encoder alone does not establish that these requirements are met. YouTube HDR requirements.

YouTube’s HDR documentation recommends both AV1 and HEVC and lists MOV, MP4, and MKV as tested containers. For an existing HDR project, use an authoring export path that preserves its required metadata, then verify the processed result. Do not apply the SDR comparison as an HDR conversion recipe. YouTube produces HDR versions for compatible devices and an SDR downconversion for other viewers; HDR playback displays an HDR label alongside quality options. Upload High Dynamic Range (HDR) videos.

How do you check the finished YouTube result?

Before uploading, review the complete delivery copy for duration, image framing, readable text, audio, and synchronization. A successful short preview cannot establish that the entire output is correct.

To upload from the Mac, sign in to YouTube Studio, choose CREATE > Upload videos, and select the delivery file. This is the documented desktop upload path; neither QuickTime’s export controls nor HandBrake’s encoder selection supplies a control over the codec YouTube ultimately serves to viewers. Treat the local file as the input to YouTube’s processing workflow. Upload YouTube videos.

Wait for the intended viewing quality before judging the result. YouTube processes low quality first, and higher resolutions can take longer to appear. Open the watch page, select the player’s Settings > Quality, and check whether the expected resolution is available. Then inspect the same text, motion, and gradient segments used in the local comparison. Checking quality after upload.

Choose the delivery file that preserves the source adequately and fits your measured time and size constraints. HEVC offers a documented QuickTime export path and optional HandBrake hardware encoding; AV1 earns its place when your own comparison demonstrates a useful saving. Keep the successful settings with the project so the next delivery starts from evidence.

Sources