If a downscaled video looks softer, first check whether the same detail is already soft in the source. If it becomes softer only after conversion, compare scaling paths before adding sharpening. HandBrake specifically documents that its VideoToolbox scaler uses a different algorithm from its software scaler and produces a less sharp output. That statement concerns VideoToolbox, not every hardware encoder. Sharpening can change the appearance of edges; it cannot restore detail that the source never contained.
Diagnose the source, then compare paths
Use a frame with stable, fine detail, such as text, a roofline, or fabric texture. Compare the source at its original dimensions with the converted video at its intended viewing size. Do not judge from a player preview alone: use the same frame and inspect the actual output file. If the feature is already soft in the source, the scaling choice is not the first issue to solve. If it looks clear in the source but softer after resizing, a scaling-path comparison is useful.
- Open the source in HandBrake and note its dimensions and the output dimensions you need. Keep the crop and output size the same across comparisons.
- Make a VideoToolbox encode if that encoder is available on your system. HandBrake lists VideoToolbox encoders for supported Macs; availability depends on the computer and software support.
- Make a second encode using HandBrake’s software scaling path, if your workflow permits it. Keep source, output dimensions, crop, and other relevant settings consistent. This is an author-recommended comparison method, not a claim that the two paths are otherwise identical in every encoding detail.
- Compare the same frame and the same feature in the source and both output files at their intended viewing size. If one output is acceptably clear, use that path without sharpening. If both remain soft, consider whether the source itself or another processing step is responsible before changing more settings.
HandBrake’s VideoToolbox documentation also notes that hardware encoding does not mean the entire workflow runs on the GPU: processing outside the listed accelerated stages may still involve the CPU. Keep this distinction in mind when comparing the path, but do not treat a speed difference as proof of a particular image-quality cause. See HandBrake’s Apple VideoToolbox documentation.
Record a small acceptance comparison
The table below is a hypothetical example of what a creator might observe; it is not a measured result or an output guaranteed by HandBrake. Use observations from your own files, and record the same detail at the same display size.
| Version | Hypothetical observation | Decision |
|---|---|---|
| Source, original dimensions | Small label text is already slightly soft | Do not expect scaling or sharpening to recover missing source detail |
| VideoToolbox, same output size | Text is legible, but the edge looks softer than the source | Compare with software scaling before applying a filter |
| Software scaling, same output size | Text appears clearer in this hypothetical comparison | Prefer this path if its output meets the delivery requirement |
| Sharpened candidate | Edge looks stronger, but a bright outline appears beside dark text | Reject or reduce sharpening; the outline is a warning sign, not added source detail |
For each real comparison, note the frame time, feature inspected, output dimensions, encoder or scaling path, and whether halos, ringing, or brittle texture are visible. The goal is a usable output at its delivery size, not maximum crispness in an extreme zoom.
Know the limits and what to try next
HandBrake’s filter documentation lists sharpening filters, including Unsharp and Lapsharp, and says available filters depend on the workflow. That establishes that sharpening filters exist; it does not promise that they will improve a particular clip. If both scaling paths look soft, test a restrained sharpening option only after the path comparison, then inspect high-contrast edges for halos and ringing. Keep it only if the result looks better at the intended viewing size without making noise or texture objectionable. See HandBrake’s filter summary.
If the source itself lacks the detail you need, return to a higher-quality source if one is available. If the source is clear but both outputs lose acceptable detail, check that crop and output dimensions are actually comparable and review other processing settings one at a time. Upscaling changes pixel dimensions; it is not evidence that new real-world detail has been recovered. If neither path meets the requirement, accept a softer result or revise the delivery size rather than sharpening until artifacts dominate.
Common questions
Does VideoToolbox always make video soft? No. HandBrake’s documentation describes its VideoToolbox scaler as less sharp than its software scaler. It does not say that every hardware encoder uses that scaler or produces the same result.
Should I sharpen before changing the scaler? Not as the first diagnostic step. Compare the source and available scaling paths first so that a filter does not obscure where the softness entered.
Can upscaling restore lost detail? No. Increasing output dimensions does not establish that missing source detail has returned. Judge the result by the information visible in the output, not by its pixel dimensions.
Sources and next step
This guide interprets public documentation and uses explicitly hypothetical acceptance examples, not application tests. Controls and availability can change; verify the cited manual against your installed version.
For work created in Imagild, carry the input requirements and acceptance checklist into the film workspace. The external software controls discussed above belong to their respective products.