What should you configure before saving?

Set only the options you expect the preset to represent. For example, a delivery preset might specify container, codec, resolution, frame rate, audio format, and file naming. Those are illustrative choices, not a recommended export recipe; the right combination depends on the delivery requirement.

Don't add variables merely because they are visible. If one delivery uses a different resolution or audio layout, decide whether that deserves a separate preset rather than repeatedly changing a general-purpose one. A focused name such as Client Review H264 or Archive ProRes makes the intended use easier to spot. Those names are examples, not built-in Resolve presets.

The most useful first confirmation is simple: after saving, can you find the preset by name and select it? If yes, the preset exists. The next check is whether its loaded settings match the job you wanted. If the preset isn't visible at all, don't diagnose its codec values yet; return to the save command, selected render mode, and menu you used.

How can I tell that the save worked?

A save is verified when the named preset appears in the Render Settings controls and selecting it restores the expected render options. A successful dialog close alone isn't enough to confirm that the preset is listed and usable.

Use a small verification pass:

• Open the preset list or preset controls on Deliver.
• Find the name you entered.
• Select the preset.
• Review the visible video, audio, and file settings.
• Check the destination separately.
• Only then add the job to the render queue.

This check distinguishes two failures that can look alike. The preset may not have been saved at all, or it may have been saved correctly but not contain the option you expected. If selecting the preset changes some values but not others, compare the settings you edited with the exact controls represented in the current mode. Don't infer that Resolve is ignoring a saved preset until you have confirmed the selected preset and current render mode.

Why does my custom render preset disappear after I close a project?

A missing preset after a project change doesn't automatically mean the preset was stored inside that project or that it has been deleted. First check the selected preset in Deliver, then confirm whether the preset is available in the Resolve installation and library you're currently using.

The essential distinction is between the preset and the project. A render preset is a reusable configuration selected from Deliver. Project settings describe the current project. A saved render configuration should not be mistaken for a project backup, a timeline export, or a record of every choice made for a specific job.

If you switch projects and can't find the preset, work through this order:

1. Confirm you're in the intended Resolve installation and version.
2. Open the intended project library and go to Deliver.
3. Open the Render Settings preset controls and look for the exact name.
4. If it appears, select it and check the loaded settings.
5. If it does not appear, try importing a known exported copy of the preset.
6. If no exported copy exists, recreate it from the intended settings and save it again.

This is a diagnostic sequence, not a claim that every installation stores presets in a particular way or that changing a library always causes loss. The purpose is to avoid destructive steps while you determine where the missing item went. Don't delete preference folders or reset the application as a first response; doing so may remove useful configuration without resolving a mistaken expectation about project state.

A render preset, a project, and an export folder are separate pieces of the workflow.

What if I was expecting the whole Deliver page to remember my last job?

A preset and the current Deliver page state are not the same promise. A named preset is for recalling a saved combination of render settings; the exact job you last prepared may also include a different timeline, destination, filename, or range.

For example, suppose you used one preset for a short review video, but then changed the output folder and filename for a client delivery. Later, you select the same preset. The codec-related configuration may be what you intended to recall, while the job-specific location or name still needs attention. Treat the selected preset as one ingredient in the next render, not as a complete snapshot of every project and queue detail.

Before rendering, compare the current job with the delivery brief. Check timeline, render mode, destination, name, range, video settings, and audio settings. Use the DaVinci Resolve export settings guide for broader help choosing delivery options, and the stuck or failed render guide if the preset loads but the render itself fails.

Does a DaVinci Resolve render preset save the export folder?

Do not assume a saved render preset will restore the export folder you used for another job. Set or confirm the current destination in the Deliver page's render-location controls before adding the job to the queue.

This distinction matters because a user often says “my preset didn't save” when the format looks right but the file goes to an unexpected folder. The preset and the current destination answer different questions:

• Preset: What combination of render options should Resolve recall?
• Destination: Where should this render job write its output?
• Filename: What should the output file be called?
• Queue item: Which configured job is waiting to render?

If the format and codec are correct but the location is not, the evidence points to a destination issue, not necessarily a missing preset. Browse to the intended folder, check the displayed path, and review the job before rendering. If you use removable storage or a network location, confirm it is available in the operating system and that you chose the intended mounted volume. Those are sensible checks for any file-writing workflow, not a claim about a special Resolve preset defect.

What if the saved preset appears but the folder is wrong?

Select the correct folder for the current job and inspect the full path before you render. If you expect that folder to be recalled every time, test that expectation explicitly rather than treating it as part of the preset.

A useful worked example:

• You create a preset called Review H264.
• You set the destination to a temporary review folder for today's export.
• On another day, you select Review H264 but want to deliver to a dated client folder.
• You choose the new destination, check the path, and then add the job to the queue.

The example illustrates why a saved preset can work while the job's destination differs. It isn't a report of a test or a guarantee of which values every Resolve version stores.

Why can't I save an Individual Clips render preset?

Blackmagic's Resolve 20 guide states that custom render presets can be made from Single Clip settings, not Individual Clips settings. If your intended configuration uses Individual Clips, switch to Single Clip to create a reusable preset, then configure the individual-clip job separately where needed.

Render mode matters because these are different output workflows. Single Clip produces the selected timeline range as one file. Individual Clips creates separate outputs for source clips in the selected range. The settings available to a job can depend on which mode you've chosen, so a preset-saving instruction from a tutorial may fail if you are following it in the wrong mode.

Here's a careful workaround:

1. On Deliver, select Custom Export.
2. Change the render mode to Single Clip.
3. Set the options you want to reuse.
4. Save the named preset from the three-dot menu.
5. Select the preset and check its values.
6. For an Individual Clips delivery, switch modes and configure the job separately.
7. Review the job's available settings before adding it to the queue.

This workaround follows the documented limitation in the Resolve 20 New Features Guide. Blackmagic may revise controls or documentation in later versions, so consult the current manual if Resolve 21.1 behaves differently. The official support page provides the Resolve 21.1 manual listing.

Don't save a Single Clip preset and assume it will convert an Individual Clips job into the same deliverable. A saved preset isn't a substitute for checking the selected render mode. Likewise, don't conclude that saving is broken simply because the menu is unavailable while a different mode is selected.

Single Clip is the documented starting point for a custom render preset.

When should I use a separate preset instead?

Create separate named presets when you have recurring delivery types that require meaningfully different settings and the workflow supports saving them. Keep each name tied to a use, not a vague label like Custom 2.

For instance, a small team might distinguish a review copy from a high-quality master. That doesn't mean the same codec, color handling, or sound settings fit every project. Write down the delivery requirement first, configure the relevant controls, then verify the result before using it on an important handoff.

If the deliverable is unusual, such as a broadcaster, post house, or client-specific specification, ask the recipient for the delivery requirements. A preset can make a known workflow repeatable; it cannot establish which specifications the recipient expects.

How do I update a saved render preset without losing the old settings?

To revise a saved preset, select it, make the intended changes, and use the current preset's update command in the Render Settings menu if that option is available. If you want to preserve the original configuration, save the changed settings as a new preset instead.

There are two decisions here: replace or preserve. Updating a preset changes what that named configuration recalls. Saving a new preset gives you another named configuration and lets you keep the previous one available.

Use this simple decision table:

Blackmagic's older Resolve documentation describes updating a custom preset through the Render Settings options menu. The menu wording can differ across releases, so use the command displayed by your installed version rather than relying on a tutorial recorded for an older build. The Resolve 21.1 manual is listed in Blackmagic support.

After an update, select the preset again and check the controls that matter. Don't use the preset's name as proof that its contents are correct. If a new configuration has replaced the old one by mistake, restoring a copy may be possible only if you exported it or kept a separate version. That's why a second, descriptive preset is the better choice when you're still deciding.

How should I name presets to avoid confusing them?

Choose names that identify the destination or task, then distinguish variants when necessary. For example, Review H264 - 1080p and Review H264 - 4K are more informative than Preset A and Preset B.

Names should describe the configuration, not make promises. Avoid embedding a client name or date if the preset is intended for general reuse. For a one-off client deliverable, you can use a distinct temporary name, but review it before you later choose the preset for another project.

A short naming system also helps diagnose whether you're selecting the configuration you meant. If two presets differ only in a number or suffix, make that difference explicit. Keep a written note of the essential settings if the delivery is critical, and confirm them inside Resolve before rendering.

How do I use the same custom render preset on another computer?

Export the custom render preset from the Deliver page, transfer the resulting preset file, and import it on the other Resolve installation. After importing, select the preset and verify its settings and destination instead of assuming the second workstation is identical.

The DaVinci Resolve 20 New Features Guide documents options to export and import custom render presets. Use the current version's menu labels where they differ. A practical transfer sequence is:

1. On the original workstation, open the Deliver page.
2. Open the Render Settings options menu.
3. Choose the custom preset you want to export.
4. Use the export option and save the preset file somewhere you can identify.
5. Transfer the file using your normal approved method.
6. On the other workstation, open Deliver and choose the import option.
7. Select the transferred preset file.
8. Find the imported preset, select it, and inspect the options.
9. Set the desired render folder on the second workstation.

Preset transfer and project transfer are not interchangeable. If the project itself must move, use the project-transfer or archive workflow appropriate to your situation. A render preset only addresses the saved render configuration. It doesn't package source media, relink files, or deliver the project database.

Why verify the preset after importing it?

The other workstation may have a different version, operating system, available codec, storage layout, or delivery context. Even when the preset imports, those differences can affect whether the configuration is useful there. This is a reason to verify, not a claim that imported presets always fail across systems.

Confirm the imported preset's name and core values, then set the destination path for that workstation. If a required option isn't available, consult the current manual or the relevant codec documentation before choosing a substitute. Don't silently change the delivery specification just to make the preset appear to work.

An imported preset still needs a destination check on the receiving workstation.

Why does the menu in my tutorial look different?

The Deliver page instructions can look different when the tutorial uses another Resolve version, another render mode, or a different preset-selection workflow. Check your installed version and the manual linked from Blackmagic support before following old menu-by-menu directions.

Version context matters in October 2026. Blackmagic announced Resolve 21.1 on September 8, 2026, and its support page lists the corresponding 21.1 manual. A tutorial for Resolve 20 may still explain the basic idea of saving a custom preset, but its menu labels, dialog layout, or extra Quick Export controls may not match your installation.

When the interface differs, use this order:

1. Identify your installed version from Resolve's About information.
2. Check whether you're using Deliver or a Quick Export dialog.
3. Confirm Custom Export and Single Clip are selected for the preset-creation workflow.
4. Look for the Render Settings options menu.
5. Match the command name to your version's manual.
6. Avoid following instructions for project settings if you're trying to save a Deliver preset.

Resolve 20's guide describes adding a custom user preset to Quick Export, while the Resolve 21 New Features Guide covers changes introduced in 21. Since a feature guide isn't necessarily a complete manual, use Blackmagic's support page for the full 21.1 reference when you need the exact current interface.

Should I update Resolve just to make presets save?

Don't update solely on the assumption that a newer version will recover a preset or fix a configuration misunderstanding. First confirm that you used the save command, the supported render mode, and the correct installation. If you decide to update for another reason, back up important projects before changing versions.

Blackmagic's support page lists software downloads and manuals. The official backup guide in our catalog covers project preparation before an update. The main point here is narrower: an update isn't the first diagnostic step for a preset that wasn't explicitly saved or whose destination was expected to persist.

If the current build is behaving differently from its manual, note the exact Resolve version, operating system, selected render mode, and steps that reproduce the issue. Blackmagic's community forum is an official place to ask Resolve questions. Include only the relevant details and avoid posting private project material.

What should I check if the preset still won't appear?

If the preset remains missing after you save it from Custom Export in Single Clip mode, repeat the save once with a distinct name and verify the visible list. If it still doesn't appear, collect version and workflow details and consult the current manual or Blackmagic's support community rather than deleting application data.

Use this troubleshooting order:

1. Did you choose the save command?

Changing codec, resolution, or audio controls doesn't create a named preset by itself. Return to the Render Settings three-dot menu and choose Save as New Preset. Enter a new name so you can distinguish the attempt from existing presets.

2. Are you in Single Clip mode?

Blackmagic's Resolve 20 guide documents the custom-preset limitation for Individual Clips. Switch to Single Clip for the preset setup, then configure the separate clip-render job as needed.

3. Are you looking in the right place?

A custom preset created from Deliver may also be available through the custom preset controls in Quick Export, depending on the Resolve version and save options. Blackmagic's Resolve 20 guide documents custom Quick Export presets for that version. Don't conclude that a preset is gone until you check both Deliver's preset controls and the relevant Quick Export list.

4. Are you in the intended Resolve version and setup?

If you have more than one Resolve installation or are working across machines, verify the application version and where you imported the preset. The support page lists Resolve 21.1 resources. Record the exact version if reporting a problem.

5. Is the preset present but not recalling what you expect?

Select it and compare its loaded options with your intended configuration. Then check the destination, filename, timeline, and range separately. A preset can be present while the current job differs in a job-specific setting.

6. Does Resolve show a warning or refuse a particular option?

Write down the exact message and which control you were using. A codec or delivery constraint is a different problem from saving a preset. Don't treat a failed render or unsupported export option as proof that the preset was not stored.

7. Does it only happen after an update or on one workstation?

Keep the comparison controlled. Record Resolve version, operating system, render mode, whether the preset was created or imported, and the steps that make it disappear. If the issue is reproducible, share those details with Blackmagic's support forum. Avoid broad resets until you know which user settings or preferences they might affect.

A missing preset and a failed render are different problems with different fixes.

For a render job that stalls, aborts, or produces an error after the preset is selected, use the separate DaVinci Resolve render troubleshooting guide. For a preset that appears and loads correctly, but produces the wrong delivery, compare the settings with the recipient's requirements and use the export settings reference.

Can TryUncle help me find the right control?

If you know the goal but can't locate a menu in your current Resolve layout, on-screen guidance can help you identify the relevant control while you stay in charge of the steps. TryUncle is the on-screen assistant for DaVinci Resolve on Mac and Windows - ask in plain words and Uncle points at the exact control on your screen.

That can be useful when your tutorial uses a different version or the Resolve interface is unfamiliar. It doesn't replace the preset checks above, guarantee a fix, or choose export settings for you. First confirm the workflow: Deliver, Custom Export, Single Clip, configure, then save the preset. If you want help navigating those controls, TryUncle is the product page for current availability and details.

What should I do before the next render?

Before rendering, select the preset you intend to use, confirm it loads the expected options, and set the destination for the current job. Then check the filename, selected timeline or range, and render mode.

If the named preset still doesn't appear, repeat the documented save sequence once in Single Clip mode and check the list again. If Resolve 21.1 still behaves differently from Blackmagic's manual, gather the exact version and reproduction steps and ask through Blackmagic's support community. Don't reset the application or rebuild a project until you've separated the preset problem from the folder, project, or render-job problem.