HandBrake Custom Preset Not Saving: How to Fix It

A HandBrake custom preset may appear to save but disappear after a restart, fail to apply when you open another source, or produce an encode that does not match the settings you expected. These symptoms usually come from one of four areas: the current settings were never saved as a new preset, HandBrake cannot write or retain its configuration files, the preset does not include a source-dependent choice, or the queue is still using settings captured earlier. The steps below isolate preset persistence and application without turning the process into a general video-quality investigation.

1. Confirm the Symptom With a Small Test Encode or Preview

Before changing permissions, drivers, or encoders, determine whether the preset is actually disappearing or whether it is being applied differently to a new source. HandBrake presets are collections of encoding settings. They do not guarantee that every displayed value will remain identical when the source has different tracks, dimensions, frame rates, or subtitle options.

1.1 Create a controlled test preset

Open a short, ordinary video file that you are authorized to process. Avoid an encrypted disc, unusual camera format, or damaged recording for this test. Choose a built-in preset, change one unmistakable setting such as the video encoder or quality value, and then save those current settings as a new custom preset.

1. Open a small source file.
2. Select a built-in preset as a starting point.
3. Change one clearly visible encoding setting.
4. Use the preset command that creates or saves a new preset.
5. Enter a unique name that cannot be confused with a built-in preset.
6. Place it in a custom category you can find easily.
7. Select another preset, then select your new preset again.

Success means the changed setting returns when you reselect the custom preset. If it does, the preset exists and can be applied during the current session. Stop changing unrelated encode options and continue with the restart test.

1.2 Test persistence after a full restart

Close HandBrake normally, wait for it to exit, and reopen it. Load the same source and look for the custom preset under the name and category you selected. Apply it and verify the distinctive setting.

If the preset survives the restart and the setting returns, preset persistence is working. Any remaining difference is likely connected to source analysis, track selection, the queue, or playback rather than saving. If the preset is gone after restart, concentrate on configuration-file permissions, portable installations, sync software, and competing HandBrake processes.

1.3 Distinguish saving from encoding

A preset can be saved correctly even if an encode fails. Conversely, an encode can complete while using settings other than the ones you meant to preserve. Use these definitions while troubleshooting:

• Not saved: The named custom preset disappears after HandBrake restarts.
• Not applied: The preset remains listed, but selecting it does not restore a setting it should contain.
• Source-dependent result: The preset applies, but HandBrake adjusts dimensions or track choices for the loaded source.
• Queue mismatch: The preset is correct now, but an older queue item retains earlier settings.
• Playback mismatch: The output is correct, but a player chooses a different audio or subtitle track.

2. Check the HandBrake Settings Directly Related to This Problem

2.1 Create a new preset instead of only modifying current settings

Changing controls in HandBrake changes the current job. It does not necessarily update the selected preset. A built-in preset also should not be treated as an editable storage slot. After making changes, explicitly create a new custom preset or use the available update command for an existing custom preset.

If you want to revise a preset, select it first, make the changes, and then explicitly update or replace that custom preset. Merely closing HandBrake after adjusting the current job is not a reliable way to preserve those adjustments.

Success means selecting a different preset and returning to yours restores the intended values. Once that works, do not keep recreating the preset. Move to the restart test.

2.2 Use a unique preset name and visible category

A duplicate or nearly identical name can make it look as if HandBrake ignored your changes. Give the test preset a short, unique name such as “Phone H264 Test” and place it in a clearly identified custom category. Expand collapsed preset categories before deciding that the preset disappeared.

If more than one preset has a similar name, rename or remove the obsolete copy after exporting a backup. Success means there is one identifiable preset, and selecting it produces predictable current settings.

2.3 Verify what the preset is expected to store

Presets primarily describe encoding behavior. Some choices depend on the scanned source and may not behave like fixed values. Cropping, resolution limits, anamorphic behavior, frame-rate handling, available audio languages, subtitle tracks, and pass-through compatibility can change when a new source is loaded.

For example, a preset cannot select a Spanish audio track if the new source does not contain one. It may instead follow the configured audio defaults or fall back according to the available tracks. Similarly, subtitle selection can depend on language rules, forced-subtitle detection, and whether the source includes a compatible track.

Success means stable encode settings return while source-specific fields sensibly reflect the source. At that point, stop trying to force every displayed field to match the previous file.

2.4 Configure audio and subtitle defaults inside the preset

If audio or subtitles appear to be missing when you apply the preset to a new source, inspect the preset’s audio and subtitle default behavior rather than relying only on tracks manually added for the current source. A track added to one job may refer to that source’s track list and may not translate directly to another file.

Set language preferences, fallback behavior, pass-through rules, burn-in choices, and track-selection rules appropriate to your workflow. Then save or update the custom preset again and test it with two different sources.

Success means the preset chooses tracks according to your rules when those tracks exist. It does not mean every source produces an identical track list.

2.5 Remove stale queue items

HandBrake queue items generally preserve the job settings captured when they were added. Updating a preset afterward does not necessarily rewrite jobs already in the queue. Remove the test item from the queue, apply the corrected preset to the source again, and add a fresh job.

Success means the new queue entry reflects the corrected encoder, quality, audio, subtitle, and destination choices. Do not use an old queued job to judge whether a newly updated preset works.

3. Check Configuration, Source, Encoder, and Destination Factors

3.1 Confirm HandBrake can retain its configuration files

If all custom presets disappear after every restart, HandBrake may be unable to write its user configuration. This can happen when the configuration location is read-only, owned by another account, blocked by security software, restored by a profile-management system, or damaged.

Run HandBrake under your normal user account and create a uniquely named test preset. Close it normally and reopen it. If your operating system provides folder security or controlled-access notifications, check whether HandBrake was denied access. Avoid making broad security exclusions. Grant access only through trusted operating-system controls and only to the legitimate HandBrake installation.

On a managed computer, an administrator may intentionally reset application data at sign-out. If the preset remains during one session but vanishes after signing out or rebooting, ask whether user application settings are redirected or restored.

3.2 Inspect portable and nonstandard installations

A portable copy may store or seek settings differently from a normal installation, depending on how it was packaged and launched. Problems arise when the application resides in a protected system folder, removable drive, network share, read-only image, or directory where the current user lacks write permission.

Move a trusted portable installation to a user-writable local folder, or install the official package normally. Do not run two copies that use different settings locations and assume they share presets.

Success means a test preset survives a restart from the same executable. If it appears in one installation but not another, the issue is separate configuration stores rather than a failed save.

3.3 Pause sync and cleanup tools during the test

Cloud-sync utilities, roaming-profile systems, backup restoration, privacy cleaners, and automated maintenance tools can replace a newer settings file with an older copy. Temporarily pause the relevant tool, create a test preset, restart HandBrake, and check again.

If the preset now survives, adjust the tool’s conflict or exclusion rules carefully. Preserve the newest valid configuration instead of repeatedly deleting all HandBrake data. Exporting the preset first gives you a safer recovery path.

3.4 Separate source behavior from preset behavior

Test with a short local MP4 or similar ordinary file. Optical media, complex Blu-ray structures, variable-frame-rate phone recordings, screen captures, and camera files can expose source-specific choices that make a preset look inconsistent. Only process discs and files that you have the legal right to use, and do not attempt to bypass access controls.

If the preset works with the simple local file but not with one source, it is probably being saved. Investigate the source scan, available tracks, dimensions, and timestamps instead of deleting the preset.

3.5 Treat hardware encoder and driver errors as a separate layer

A hardware encoder can be present in a saved preset but unavailable when the job starts because of unsupported hardware, a driver problem, remote-session limitations, or a changed system configuration. That does not necessarily mean the preset failed to save.

Confirm that selecting the preset still displays the intended encoder. If the encode then fails, test the same job with a software encoder. A successful software encode indicates that persistence is working and the hardware path needs separate troubleshooting. Update drivers from the operating-system or hardware vendor’s official channel rather than using third-party driver tools.

3.6 Verify the destination independently

The output folder and filename are job-specific concerns and may not be preserved in the way you expect from an encoding preset. Check that the destination exists, is writable, has enough free space, and is not a disconnected removable or network location.

If the job encodes successfully to a simple local test folder, the preset is probably not the cause of the earlier destination failure. Stop editing preset settings and correct the output path or permissions.

3.7 Check the player before changing the preset

An output can contain the expected audio and subtitle tracks while a playback application selects a different default or hides subtitles. Inspect the finished file with another capable player or media-information tool. Manually switch tracks during playback.

If the expected tracks are present, the HandBrake preset did its job. Adjust player defaults or track dispositions as needed rather than rebuilding the preset from scratch.

4. Use the Activity Log to Separate Guesswork From Evidence

HandBrake’s Activity Log records source scanning, selected encoders, track handling, filters, output paths, warnings, and encode failures. It is most useful when a preset remains visible but the resulting job does not behave as expected.

4.1 What to look for in the log

• The source path and detected title or file.
• The video encoder actually initialized for the job.
• The input and output dimensions.
• The selected audio and subtitle tracks.
• The destination path.
• Permission, file-access, muxing, or encoder initialization errors.
• Warnings showing that a requested feature was unavailable or changed.

Compare the log from one successful minimal encode with the failing job. If both show the intended encoder and track rules, the preset is being applied and the difference lies later in the workflow. If the failing log shows an old encoder or old track configuration, recreate the queue item after applying the preset.

4.2 What the Activity Log cannot prove

The encode log is not always the best evidence for why a preset vanished between application launches. A disappearance points more directly to configuration persistence, installation location, synchronization, or application shutdown. Use the log to verify the resulting job, then use the restart test to verify saving.

5. Run a Clean Temporary Encode With Minimal Settings

A controlled encode provides a clear stopping point and prevents multiple variables from being changed at once.

1. Restart HandBrake and clear or ignore old queue entries.
2. Open a short local video stored in a writable folder.
3. Select a standard built-in preset.
4. Change one visible video setting.
5. Save the current settings as a uniquely named custom preset.
6. Select another preset, then reapply the custom preset.
7. Choose a new local output filename.
8. Add the job to the queue and confirm the queue summary.
9. Run the encode and inspect the Activity Log.
10. Close HandBrake normally, reopen it, and apply the preset again.

The test is successful if the preset remains after restart, restores the changed setting, creates a new queue job with that setting, and completes the encode. Once all four conditions are met, stop changing HandBrake’s configuration. Reintroduce your normal source, hardware encoder, audio rules, subtitles, and destination one at a time.

If the preset disappears only after restart, focus exclusively on configuration-file access or replacement. If it survives but the job differs, focus on source-dependent selections and queue capture. If the job settings are correct but the encode fails, troubleshoot the encoder or destination. If the encode succeeds but playback looks wrong, inspect the output tracks and playback device.

6. Export Presets Before Resetting Anything

Export important custom presets to a file before reinstalling HandBrake, clearing application data, testing another package, or allowing a support technician to reset the configuration. Store the exported file outside the HandBrake configuration area so that a cleanup tool cannot remove both copies.

After exporting, test whether the file can be imported into the same or another trusted installation. Use export as a backup, not as proof that every source-dependent choice will produce identical tracks.

A reinstall should not be the first step. Reinstalling application files may leave the same user configuration untouched, while deleting configuration data can remove the presets you wanted to recover. The controlled restart test and exported backup make any reset safer and more informative.

7. Quick Fix Checklist

• Save current settings as a new custom preset instead of only adjusting the job.
• Use a unique preset name and a clearly visible custom category.
• Select another preset and return to yours to test immediate application.
• Close and reopen HandBrake to test persistence.
• Confirm HandBrake can write and retain user configuration files.
• Move portable copies out of protected, network, or read-only folders.
• Check whether sync, cleanup, or profile tools restore older settings.
• Configure audio and subtitle defaults rather than relying on one source’s tracks.
• Remove stale queue items and add a fresh job after updating the preset.
• Use a short local source and writable local destination for the control test.
• Read the Activity Log before changing drivers or encoders.
• Export important custom presets before resetting configuration or reinstalling.

8. Frequently Asked Questions

8.1 Why does my HandBrake custom preset disappear after restart?

The preset may not have been explicitly created, or HandBrake may be unable to retain its configuration. Other common causes include launching a different installation, using a portable copy in a protected folder, or having synchronization or cleanup software restore an older settings file. Create a uniquely named preset, restart immediately, and test before changing encode settings.

8.2 Why does selecting my preset not restore every field?

Some displayed choices depend on the current source. Dimensions, cropping, audio tracks, subtitles, and compatibility decisions can change after a new scan. Verify stable settings such as the intended encoder and quality mode, then evaluate source-dependent selections according to the available tracks and preset defaults.

8.3 Does changing current settings automatically update the selected preset?

No. Treat current job settings and stored custom presets as separate things. After making changes, explicitly save a new custom preset or update the existing custom preset using the relevant preset command. Then switch away and back to confirm the update.

8.4 Why is an old queue item ignoring my updated preset?

The queue item likely retained the settings it had when it was added. Remove it, apply the updated preset to the source, verify the tabs, and add a new queue item. The new entry is the correct test of the updated preset.

8.5 Can a hardware encoder make a saved preset look broken?

Yes, but usually at encode time rather than save time. The preset can retain a hardware encoder that the current computer or driver cannot initialize. If the preset still displays the intended encoder after restart, persistence works. Test a software encoder to isolate the hardware path.

8.6 When should I stop troubleshooting the preset?

Stop changing the preset when it survives a restart, restores its stable settings, appears correctly in a newly created queue item, and completes a controlled encode. Any remaining issue should then be investigated in the source, destination, encoder, track rules, output file, or playback device.