How do I check whether I have 21.1?

Use the About dialog inside Resolve rather than relying on the project file name or a downloaded installer sitting in your Downloads folder. The version displayed by the running application determines whether the 21.1 Inspector preset feature is present.

On desktop, open the Help menu and choose About DaVinci Resolve. Read the full version number, including the point release. If it reads 21.1 or a later 21.x version, continue with the new preset workflow. If it reads 21.0, you are on the release family before the feature. On macOS, the application menu may contain the About item; menu placement can differ across operating systems, but the About dialog remains the place to verify the running build.

Resolve's support page is the authoritative place to locate current installers and manuals. Blackmagic listed DaVinci Resolve 21.1 and its manual as separate support entries, and the 21.0 manual remains available there too. Avoid installing a point release in the middle of a deadline without your normal project backup and compatibility check. (Blackmagic Design Support Center)

Updating the editor and opening the project are separate steps. A project that was created in 21.0 can be opened in 21.1, but before changing a production project, preserve the version you can return to. If you share projects with other editors, agree on the Resolve version first. A colleague still running 21.0 will not see 21.1's Inspector preset interface, even if they receive the same timeline project.

The support page may list a newer 21.x build than the version named in an older tutorial. That does not make the tutorial useless; it means you should map its terminology to the current interface. A control that has moved, gained an icon, or changed its menu label is a reason to check the manual and release notes, not to guess at a potentially destructive action.

Does DaVinci Resolve 21.0 have the same save-settings menu?

No. Blackmagic introduced the Inspector preset feature in 21.1, so a Resolve 21.0 user should not expect the same Inspector preset control. Older Resolve builds offered other forms of presets, but those menus served different jobs.

This matters because Resolve uses the word “preset” across multiple features. A preset can describe an export configuration, a project configuration, a Fusion macro, a transition, an effect, a workspace layout, a color grade, a Fairlight processor, or now an Inspector parameter set. The shared label does not mean these objects save the same data or can be applied in the same way.

If an online answer says “click the three dots and save a preset,” ask what kind of preset it means and what Resolve version it was written for. Project Settings has its own preset menu. Workspace layout presets save interface arrangement. Fusion effects can have their own preset or macro workflow. Resolve 21.1 adds Inspector presets to reuse parameter values. Those actions can look similar because they use familiar menu patterns, but their scope is different.

For a project on 21.0, use the workaround that matches the thing you need to repeat. Copy and paste clip attributes when the task is moving selected timeline properties from one clip to another. Keep a sample clip in a Power Bin when you need a reusable timeline object. Use a Fusion macro or effect preset for a Fusion-based design. Use a Project Settings preset only when the desired settings are project-wide. Do not rename one kind of preset and assume Resolve has converted it to another.

Resolve 21.0 project presets and Resolve 21.1 Inspector presets solve different problems.

Should I save one parameter or a group preset?

Save one parameter when you want a narrow, predictable adjustment; save a group when the full combination should travel together. The smaller preset is usually easier to apply safely, while a group reduces repeated setup when the full package is intentional.

For instance, you might save a transform value for a recurring punch-in, but not the clip's crop, stabilization, and rotation. You might save a title treatment as a group if the font, size, tracking, shadow, and position are meant to stay together across a series. The right scope follows the editorial decision, not the number of controls visible in the Inspector.

The table is a decision aid, not a claim that one technique duplicates every other one. Blackmagic's product update says Inspector presets cover video, audio, transitions, and transforms, but the official announcement does not enumerate every individual parameter, whether animation curves are captured in every case, or how the feature's preset storage is organized. Treat the actual control's tooltip and visible menu as the authority for the exact setting you are saving. (Blackmagic Design 21.1 announcement)

An individual preset is easier to inspect mentally. If a clip needs the same scale but a different position, saving and applying only scale avoids unintentionally moving the image to an old composition. If you always use scale and position together for a standardized frame, a group can be appropriate. The preset does not know your artistic intention; you supply that intention through the name and the decision to apply it.

Group presets can also hide more than you intended. A value that appears harmless on the source clip might be wrong for a new shot. Imagine a title whose shadow is tuned for white text over a dark background. If the next title is dark text on a pale background, the saved shadow could reduce contrast. Imagine a clip with a pleasing transform but a different camera crop. Reusing the group's full setup may clip a face or push important action outside frame.

Use the smallest useful set of controls for presets you will apply broadly. Use a group when those values form a coherent recipe, not because saving a group feels more complete. The same logic applies to audio. A dialog clip and a music clip may both expose audio controls, but the right treatment differs. Keep speech cleanup and music shaping as separate named ideas rather than one vague “good audio” preset.

What should a useful Inspector preset name include?

A useful preset name tells you the object, purpose, and any important boundary. “Vertical interview punch-in, 9:16, mild” carries more meaning than “Preset 1,” while “Client A look” may become unclear after the project ends.

You do not need a complicated naming taxonomy. Start with a repeatable pattern such as Object - purpose - version or Parameter - context - strength. Examples include Transform - vertical talking head - tight, Title - lower third - two line, or Audio - dialogue EQ - light. These names are examples, not recommended technical values. The relevant numbers should come from the footage, delivery spec, or approved graphic design, not from a universal setting.

Avoid putting an entire client brief in the preset name. Keep operational notes in a project document or a marker where collaborators can find them. The name should help you distinguish related variants in a menu. If a preset is only safe for a particular frame shape, color pipeline, or clip type, say so briefly. A name such as Transform - 9x16 center crop immediately warns you not to apply it blindly to a landscape interview.

Add a date or version only if you actively maintain multiple revisions. A suffix like v2 is useful when the old and new treatments coexist during a review. It is clutter when you have one current preset. When a treatment changes permanently, update the existing preset if the application supports that action and the replacement should be canonical, or remove the stale entry if you no longer want it available. Do not leave several nearly identical presets with names like “final,” “final 2,” and “final new.”

Keep names portable across projects and teams. A preset labeled Marius project 04 will mean little outside that one context. A label like Subtitles - two-line caption - high contrast describes what the preset is for, even if you share the project months later. When an exact client style guide dictates the wording, use a client code plus the role of the preset, and keep any confidential information out of a broadly shared name.

What is a safe worked example for a transform preset?

A transform preset is useful when several clips need the same framing recipe, but it should be tested against each new shot because subject placement and source aspect ratio vary. Use a duplicate or a non-critical clip to establish and inspect the result before applying it to a final sequence.

Suppose you are cutting several vertical social clips from a landscape interview. You have already set the timeline format and identified a framing treatment that keeps the speaker's face and hands in frame. Choose a representative clip, adjust the relevant Inspector transform values, and create a clearly named preset for that specific treatment. Do not include unrelated stabilization or crop settings unless the same choices belong in every reuse case.

Next choose a second clip that has a different starting composition. Apply the preset and inspect both the viewer and the clip at normal playback size. Check whether the eyes remain in a comfortable position, whether hand gestures stay inside frame, and whether the camera movement remains tolerable. If the result misses the subject, the preset may still be valid for the original shot type; it simply isn't a universal framing command.

Then try a third clip with a different focal length or source crop. A preset copies numbers, not subject detection. It cannot know that the speaker leaned to one side, that a second person entered the frame, or that the useful action starts near the edge. Adjust the new shot where needed. The benefit is a consistent starting point, not a promise that every shot will be finished without judgment.

This example avoids prescribing an exact scale or position. The correct values depend on timeline format, source dimensions, crop mode, subject placement, and the delivery's safe area. A number that works for one 16:9 source could be wrong for another camera's framing. Use the transform controls to make the decision for the clip you are actually editing, then name the preset for that use.

If you repeatedly need several frame shapes, create distinct presets instead of overloading one. For example, keep separate choices for a centered vertical interview, an off-center speaker, and a screen recording with important UI near the edges. The exact set depends on your output patterns. Do not make a preset for every clip; make one when the same decision returns often enough that a named starting point is useful.

How do I apply a saved Inspector preset to another clip?

Select the destination clip, open the relevant Inspector controls, and choose the saved preset intended for that parameter or group. Then inspect the viewer and the timeline result before moving on, because copied values do not adapt themselves to different footage or design constraints.

An efficient repeat loop is: select target, apply preset, play through the affected range, adjust exceptions, and continue. For a transform, look at the full shot and the cut on either side. For a title, check spelling, wrapping, line breaks, and overlap with important action. For audio, listen at the same monitoring level you use to judge the edit. For an effect, toggle or bypass it to compare the processed and original image.

If you are applying the same preset to several clips, select a manageable group and confirm that the parameter type is compatible before making a broad change. The 21.1 release adds preset support, but the release announcement does not state every multi-selection behavior. Confirm the actual result on a small selection first. This is especially important for clips with different source sizes, text contents, channel layouts, or effect stacks.

Keep an untouched reference if you are unsure what changed. You can duplicate a clip, create a timeline version, or use an undoable test before committing a large batch. A saved preset is not inherently destructive, but an incorrect broad application can create many small mismatches that take longer to discover later. Inspecting a representative target first is cheaper than auditing a whole timeline after the fact.

When the preset lands correctly on one clip but not another, diagnose the difference before changing the preset. Is the target clip a different type? Does it have another effect already applied? Is the input frame shape or text length different? Is one clip keyframed and the other static? Are you applying a parameter preset or a group? The answer helps decide whether to edit the preset, save a second variant, or make a one-off adjustment on the target.

Use names that make matching fast. In the Inspector menu, a list of generic names forces you to remember which item contains what. If you have only a few useful presets, clear labels are enough. If you have many, group their names by parameter family or use a consistent prefix so related choices sit together when alphabetized. Do not rely only on color or icon differences if teammates use different display settings or accessibility needs.

How do I save a group of video settings together?

Set the intended video values on the selected clip, then use the Inspector options menu to save a group preset if the menu offers that action for the active Inspector context. Apply that group to a compatible clip and inspect which values it changes.

Start with a deliberate checklist. If you are creating a title treatment, decide whether the group should include font, size, tracking, line spacing, position, and shadow, or only a subset. If you are making an image treatment, decide whether stabilization belongs with transform and crop. There is no universal correct grouping. The test is whether a future use should receive all those values together.

Use a source clip that represents the target use well. A lower third placed over an interview is a poor source for a preset intended for full-screen title cards if the layout and timing differ. A group built from a shot with a special crop may not be appropriate for a montage. The more varied the intended targets, the narrower each saved combination should be.

After saving, apply the group to a second clip and check for hidden mismatches. Group application is especially worth checking when text content differs, when one clip has a different frame shape, or when the source has another effect or keyframe state. If the group contains more than you meant, create a more focused preset rather than repeatedly correcting every target.

Keep the number of group presets small enough that you can choose confidently. Each preset represents a bundle of decisions. If you create a large menu full of near duplicates, the time spent deciding which one to use may exceed the time saved. Retire stale versions and keep meaningful alternatives, such as “clean title” and “title with shadow,” only when you actually need both.

The release announcement confirms group-like recall of favorite parameter configurations, while detailed UI labels can evolve in point releases. If your menu wording differs, consult the manual associated with your installed build on Blackmagic's Support Center rather than assuming a tutorial's label is exact. (Blackmagic Design Support Center)

Can I save a title or text preset?

DaVinci Resolve 21.1's Inspector preset system is intended to save parameter configurations, and titles expose Inspector parameters on the Edit page. You can use the available control to save a relevant setting or group, then verify the result on a title with different copy.

Text is a special case because content changes. A title preset that includes the source text itself may be less reusable than a style bundle, depending on the exact controls the preset captures. Check the destination title after application. Confirm the words, font, line breaks, alignment, position, and background contrast. Never assume the preset only affects typography because that is what you intended when you saved it.

The official Blackmagic Editors Guide describes selecting a title on the Edit page and adjusting its controls in the Inspector. It also distinguishes the title asset in the Effects Library from the parameters that appear after the title is selected. That is a useful mental model: the graphic object and its exposed controls are related but not identical. (DaVinci Resolve Editors Guide)

For a series of lower thirds, create one title object, establish the visual style, and save only the settings that should repeat. Apply the result to another title and replace the copy. Then check the longest name in the series, not just the short example. A line that fits “Sam Lee” may wrap or collide when the next person has a longer name. Decide whether you need a second layout variant for long titles.

If you need to reuse an entire designed title with its animation and media dependencies, a reusable Fusion title, macro, or saved timeline asset may be a better fit than Inspector values alone. Use an Inspector preset for the values it captures. Use a reusable graphic when the full object is the thing you want to carry forward. They can complement each other, but one is not a guaranteed substitute for the other.

Can I save transition settings from the Inspector?

Blackmagic lists transitions among the parameter families supported by Inspector presets in Resolve 21.1. Select the transition itself, inspect its available parameters, save the values you want to reuse, and test the saved choice on another compatible transition.

Transitions sit between clips rather than behaving like ordinary source clips. Their duration and the edit points around them affect how they play. A preset may help reproduce transition settings, but it does not make every cut suitable for the same transition. Check handles, timing, motion direction, and whether the transition obscures an important moment.

Use a transition preset where the repeated treatment is intentional, such as a consistent dissolve style in a specific segment. Avoid applying a decorative transition everywhere just because it is now easy to save. A clean cut can be the right choice. A preset saves a decision; it does not make the decision editorially correct.

If the transition control does not show the option you expect, select the transition object rather than one of the adjacent clips. The Inspector content changes with the selected item. A common source of confusion is clicking a clip, seeing clip controls, and searching for an option that only appears when the transition is selected.

Can I save audio settings in the Inspector?

Blackmagic includes audio among the Inspector preset categories described for Resolve 21.1. Select the audio clip or relevant timeline object, adjust the intended controls, save the available parameter or group preset, and listen to the result on a second clip before using it broadly.

Audio presets need context just as image presets do. A dialogue clip, room tone, music bed, and sound effect may have different roles. A setting that makes one voice clearer can make another voice harsh. A music clip may need different control than dialogue because it sits under speech. Use the preset as a repeatable starting point, then listen for the target's actual level, noise, tone, and dynamics.

Preserve headroom and avoid assuming that one preset establishes a complete mix. Loudness targets depend on destination and delivery requirements. The same parameter values can produce different perceived results across recordings. A quiet lavalier track and a close studio microphone are not interchangeable inputs just because both are speech.

Name audio presets by the job and intensity, not a vague promise like “perfect voice.” For example, Dialogue - light cleanup says what it is meant to do without claiming that every voice needs identical processing. Keep music and effects in separate categories where their treatment differs. After application, audition the clip in the sequence, because the surrounding sounds determine whether the settings work in context.

If the saved settings do not appear on the destination, confirm that you are looking at the right Inspector section and object. Resolve has audio controls in multiple places, including the Edit page Inspector and Fairlight mixing tools. A Fairlight processor preset or an equalizer's own preset menu may not be the same thing as an Inspector preset. The labels can overlap; check which control owns the saved data.

Why can't I see the Inspector preset button?

The most likely reason is that the running application is Resolve 21.0 or earlier, because Blackmagic says the Inspector preset feature arrived in 21.1. Also check that a timeline object is selected and the Inspector panel is showing the correct controls.

Use this diagnostic order:

1. Check Help > About DaVinci Resolve for the full version number.
2. Confirm that the project is open and you are on the Edit page.
3. Select a clip, title, effect, or transition in the timeline.
4. Open the Inspector and look at the controls for that selected object.
5. Check whether the control has an associated preset action or whether the options menu applies to the whole group.
6. Consult the manual for the installed version if the interface differs from a tutorial.

If you are on 21.1 and still cannot see it, change the selection. The Inspector is contextual: it shows the settings for the selected object. Selecting the viewer, a track header, or a different timeline item may leave you looking at another context. The feature's availability on a category does not mean that every object exposes the same set of values.

Also separate three controls people often confuse: the Inspector visibility button, the Inspector options menu, and the preset control associated with a parameter. Opening the panel only reveals the controls. The menu may manage a group. A parameter's own save action may live closer to that setting. If the button looks unfamiliar, hover for a tooltip before clicking. Avoid assuming that a nearby three-dot icon saves everything.

Resolve 21.1 may have multiple builds and later point updates. If a current manual or release note names a changed control, trust the documentation for your installed point release. The Support Center lists product versions and manuals, including distinct entries for DaVinci Resolve 21 and 21.1. That versioned documentation is safer than an unlabelled tutorial video or forum answer. (Blackmagic Design Support Center)

If an update is not possible, choose a workaround based on the settings you need to preserve. Copy and paste attributes for selective clip-to-clip transfer. Keep a sample object in a Power Bin for a reusable timeline asset. Use an effect's own preset or a Fusion macro when the effect workflow supports it. These methods can bridge the gap, but they are not proof that the 21.1 feature exists in your earlier build.

Why does the preset appear to save, then disappear?

First determine whether the preset was actually saved, where Resolve stores that kind of preset, and whether you reopened the same application user and project environment. The official public 21.1 announcement confirms save-and-recall behavior but does not specify the preset's storage scope or cross-system portability.

Check the menu again while the same type of control is active. Some preset menus are contextual, so an item may appear only when the relevant parameter or object is selected. If the item is not listed, verify that the save command completed and that you are using the same Resolve version. Make a small test preset with an unmistakable name, close and reopen the project, and check again before relying on it for a client workflow.

Do not infer a storage guarantee from the fact that a preset survives a page change or remains visible in one project. It may be stored at the user, application, project, database, or another scope. Blackmagic's concise 21.1 public note doesn't document that distinction. Until you have verified how your installation behaves, treat a custom preset as a convenience rather than your only copy of a critical design or effect.

If you work across two machines, test the transfer before a deadline. Save the preset on machine A, then see whether machine B can access it after opening the same project or signing into the same user environment. If it cannot, transfer the underlying timeline object, effect, macro, project template, or documented numeric recipe instead. The right fallback depends on whether you need the values, the effect itself, or the whole graphic.

A community post can alert you to a possible issue, but it is not a verified product specification. For instance, Blackmagic's feature-request forum contains older requests for Inspector presets; those explain why the 21.1 addition matters, but they predate the feature. (Blackmagic Design feature request) If a current build behaves unexpectedly, gather the precise Resolve version, operating system, selected object, menu path, and a minimal reproduction before asking the official community.

Why does applying the preset change more than I expected?

You may have applied a group preset where an individual parameter preset would be safer, or the saved combination may include controls you did not intend to reuse. Recheck the source clip and compare its controls with the target before editing the preset.

To isolate the cause, undo once if the change is still recent, then inspect the same target before and after applying the preset. Look for unexpected position, crop, keyframe, effect, title, or audio changes. If the interface lets you save a smaller parameter selection, make that narrow version and test it again. If you need the full group for some clips, keep two clearly named variants instead of weakening the useful preset for every case.

Do not repeatedly adjust the target and save over the preset unless that target represents the intended standard. It is easy to turn a reusable recipe into a one-off exception by updating it from a clip with unusual framing or text. Keep the source for a canonical preset consistent, or duplicate it before experimenting.

Use timeline context as part of the inspection. A title may look fine over a dark shot and disappear over a bright shot. A transform may frame the subject but make the cut feel jumpy. An audio treatment may sound reasonable in solo and wrong under music. Preset correctness is not only “did the numbers apply?” It is “does the edit still work?”

If a setting repeatedly misbehaves across targets, inspect whether the difference comes from source properties or the preset's scope. A scale value has a different visible effect on different source dimensions. A text size can fit one title length and overflow another. Audio processing responds to the source signal. Those are normal differences, not evidence that the preset failed to save.

A saved Inspector preset is a reusable starting point, not a substitute for checking the shot, title, or sound.

A preset copies a setting; the editor still decides whether that setting fits the new clip.

Why don't all my keyframes transfer with the preset?

Do not assume that an Inspector preset captures every keyframe, curve, or animation detail unless the control and your installed version make that scope clear. Test with a short duplicate clip and inspect the keyframe editor before using it in a finished sequence.

Parameter values and animation data are related but distinct. A scale value can be static, or it can change over time. A title can have fixed font and position values, plus animated opacity or movement. A saved setting may reproduce the visible value without reproducing the exact motion. The official announcement does not publish a field-by-field list of what is serialized by each preset type, so we should not promise that it carries every animated state.

For a motion recipe, build a controlled test. Duplicate a clip, set an obvious animated change, save the preset, and apply it to a second duplicate. Scrub through the same time span and compare the keyframe markers and the result. If the animation did not transfer, use a method designed to copy attributes or reuse the complete effect or title object. The check costs little and prevents a false assumption from spreading through a sequence.

The same caution applies to source-relative behavior. Some effects depend on image boundaries, clip duration, or the point at which they are applied. A preset that works on a long clip may not behave identically on a short one. A transition's timing depends on adjacent edit points and available handles. Test motion and timing in the real context, not only on a static viewer frame.

When a result must match exactly, keep a known-good source clip in the project and label it as a reference. That can be a timeline clip disabled from export, a duplicate timeline, or a reusable item in a bin, depending on the project structure. Make clear to collaborators that it is a reference object, not a shot intended to appear in the final program.

Why doesn't the preset transfer between projects or computers?

Resolve's 21.1 announcement confirms that Inspector presets can be saved and recalled, but it does not promise that every preset is automatically shared across projects, user profiles, databases, or computers. Verify the storage scope in your own setup before planning a handoff around it.

If the preset is missing in a different project on the same machine, select the same kind of parameter and check its preset menu. If missing on another computer, compare Resolve versions and user accounts first. The second machine may run 21.0, a different point release, or a different operating-system user. A shared project database does not automatically prove that all application-level preferences or locally stored resources are shared.

For a team handoff, include a stable alternative. A labeled example clip can show the intended values. A screenshot is useful for internal notes, although the post's illustration slots are not screenshots. A short text recipe with the relevant control names and values can help a teammate reconstruct a look. For a complete graphic, include the reusable title or macro and its dependencies where licensing and project policy allow. Choose a method that preserves the object you actually need.

If you rely on Blackmagic Cloud or shared project libraries, distinguish shared project content from local application configuration. The project can synchronize timelines and media organization while a local preset list may remain tied to the running user's installation. Do not assume either behavior without checking the current documentation or performing a controlled test. Save a disposable sample, open the same work on the second account or workstation, and confirm what appears.

When preparing a handoff, write down the source version, any required plugins or fonts, and whether the preset is essential or merely convenient. If the receiving editor cannot access a custom preset, they should still be able to finish the edit from the saved project elements and clear instructions. That is more reliable than “it should be in your presets.”

What should I use if I need to reuse more than Inspector values?

Use a different Resolve feature when your real goal is copying selected clip properties, reusing an entire effect, preserving a full graphic, sharing a color grade, or standardizing a project. Inspector presets are the right tool only when the reusable unit is a parameter or parameter group in the Inspector.

Blackmagic's Editors Guide documents Edit page workflows for titles and transitions, and Resolve's forum discussions show common earlier workarounds such as Power Bins and copying attributes. Those workarounds were useful before native Inspector presets and still make sense when the reusable object is broader than Inspector values. (Editors Guide, Blackmagic forum discussion)

When is Paste Attributes better than an Inspector preset?

Paste Attributes is better when you already have a source clip and want to choose which of its supported properties to copy to one or more destination clips. Inspector presets are better when you want a named, reusable value or group that you can recall later without treating a particular timeline clip as the source.

The source clip is the reference in a Paste Attributes workflow. Copy it, choose the target, open the paste-attributes dialog, and inspect the available categories before confirming. That makes the operation useful for a one-time batch: copy a grade-related clip property, a transform, or audio attribute when the interface offers it. The exact categories depend on the selected media and Resolve version, so inspect the actual dialog.

Paste Attributes can be more selective than a wide group preset, but it is also easier to copy an accidental property if you accept every default checkbox without reading. If the destination clip has intentional keyframes or an existing adjustment, verify that your selection will not replace something you need. Apply it to one representative clip first, then scale to the rest.

Inspector presets are more convenient when the same settings recur across separate sessions and you want them named independently from a source clip. They can be faster to discover than searching a long timeline for the clip that contained the “right” settings. Still, the new preset feature does not remove Paste Attributes from the toolbox; the workflows answer different needs.

For a full walkthrough of keyframe copying issues and version-specific behavior, use the related guide on DaVinci Resolve 21 keyframe copy and paste problems.

When is a Power Bin or reusable clip a better fit?

A Power Bin or reusable clip is a better fit when you need to carry a whole timeline object, such as an adjustment clip, title, or composed graphic, rather than only a set of Inspector values. Keep the object available in a shared project context and make its dependencies clear.

An adjustment clip can hold effects that you want to place above other footage. It has a different behavior from applying a setting directly to each underlying clip. It affects clips beneath it over its duration, which may be ideal for an overall treatment and wrong for isolated shot changes. Test how it interacts with transitions, layered tracks, and clips that overlap its range.

A reusable title may include a designed layout, animation, and graphic structure. An Inspector preset may capture reusable control values, but that does not necessarily recreate the whole title object. If you need the entire construction, store the construction. If you only need a few values for new titles, an Inspector preset is more direct.

The Power Bin approach also has practical costs. The reusable item may rely on media, fonts, plugins, or a library shared with collaborators. A bin entry that looks present on your system can be offline or incomplete on another. Check the object in the receiving project, not just the bin label. Keep a small readme or descriptive name when the intended use is not obvious.

The older Blackmagic forum conversation on FX presets includes users describing adjustment clips and Power Bins as workarounds. That is useful historical context, but it predates the native 21.1 feature and should not be treated as the current step-by-step guide for Inspector presets. (Blackmagic Design forum discussion)

When should I make a Fusion macro instead?

Use a Fusion macro when the reusable item is a node-based effect or title construction with multiple connected tools, not merely a few ordinary Edit page Inspector values. A macro can package a more complete design or effect workflow, but it introduces its own dependency and compatibility questions.

Fusion is built around node graphs. If your intended result depends on a set of nodes, masks, merges, and exposed controls, a macro can preserve the structure more naturally than an Inspector preset. If all you want is a repeated scale value, building a macro would be unnecessary overhead. Match the tool to the object.

Before sharing a macro, test it on a second clip and a clean project. Check whether the macro uses fonts, third-party tools, media, or version-specific nodes. A teammate who does not have a required component may see a missing tool or a different result. Put the dependency list alongside the macro and do not promise portability until you have tested the target environment.

For a simple built-in effect, check whether the effect already exposes a preset workflow of its own. Some effects and processors have dedicated preset controls that existed before 21.1. Those local controls are not the same as the new Inspector preset feature, even when the practical result is similar. Save from the effect's own menu when that is the documented path for the selected effect.

Are Inspector presets the same as color PowerGrades?

No. Inspector presets reuse Edit page parameter configurations, while PowerGrades are gallery stills that store color grading node work for reuse on other shots. Choose based on whether the settings live in the Inspector or in the Color page node graph.

If you want to repeat a transform, title value, audio setting, or supported transition configuration, the Inspector preset is the relevant family. If you want to reuse a node tree for a color look, use a gallery still or PowerGrade workflow. Applying a PowerGrade and applying a transform preset may both change the picture, but they operate in different parts of Resolve and preserve different structures.

This boundary matters when building a reusable look. A grade is not a magic universal recipe. It responds to the camera source, exposure, white balance, color space, and the creative intention. Keep a good reference shot, apply the grade to a second shot, and balance it in context. A PowerGrade can provide a starting node graph; it cannot make different source footage identical.

If you are building a color workflow, see how to use PowerGrades in DaVinci Resolve. That guide covers the gallery-based reuse mechanism, which is distinct from Inspector presets introduced in Resolve 21.1.

What should I do before using presets across a project?

Decide the reuse boundary, make a representative test, name the preset clearly, and inspect a second target before applying it broadly. This four-part habit keeps a speed tool from turning into a timeline-wide cleanup job.

Start by defining what you want to repeat. Is it one value, a group of values, an effect, a grade, or a complete graphic? If you cannot state the object in one sentence, pause before saving. You may be reaching for an Inspector preset when another reusable asset would fit better.

Choose the source clip carefully. Use footage that represents the common case, not an unusual exception. If the preset is for vertical interviews, do not build it from a clip whose subject is already at the edge. If it is for titles, do not use the one title with a logo and an unusual three-line name. A preset built from an edge case can encode the wrong assumptions for the rest of the sequence.

Save a narrow setting where possible. The narrow version is easier to understand and safer to reapply. Broaden it only when the full combination needs to travel together. This approach also helps you debug later: if one parameter behaves incorrectly, you know which reusable action caused it.

Apply it to a second clip before creating a batch. The second target should differ in at least one meaningful way, such as subject position, text length, or source framing. If the result still makes sense, your preset may be broad enough for that category. If it needs correction, make the scope narrower or create a variant.

Keep an undo path. Save the project before a large change, work on a duplicate timeline when the edit is sensitive, or use a small test range first. The point is not to fear presets. It is to preserve a known-good state while you find out how the settings interact with this footage.

Then record the exception. If your team has to adjust one setting on every third clip, the preset may be too broad or may need a named alternate. If a preset only works when a specific font is installed, include that dependency in the title or handoff note. If a setting changes with project frame rate or output format, make that boundary explicit.

Review old presets periodically. A list grows quietly, then the wrong entry becomes easy to choose. Remove duplicates you no longer use, distinguish variants by purpose, and avoid keeping expired client-specific presets in a shared list where someone could apply them by mistake. Resolve's public announcement does not specify a cross-project migration or backup contract for the new preset store, so retain your underlying reusable assets and recipes where they matter.

How should I learn Inspector presets if a video tutorial doesn't match?

Start with Blackmagic's version-specific documentation, then compare its terminology with your own interface and test on a disposable clip. A tutorial is useful for seeing the motion of a workflow, but its version and selected object must match your screen closely enough to trust each step.

Blackmagic's Support Center currently lists manuals for 21 and 21.1. Start with the manual that matches your installed build. If it does not answer a precise UI question, check a recent video and note the creator's version number. In comments or forum posts, ask with the version, operating system, selected object, and the menu you opened. “I can't find the button” leaves out the details that separate a 21.0 issue from a selection or context issue. (Blackmagic Design Support Center)

The best way to learn DaVinci Resolve for this narrow feature is not to watch every general editing course. Open a short test project, practice saving one parameter, apply it to a contrasting clip, then compare with a group preset. That gives you direct evidence about the scope in your version. A course is more valuable for the editing concepts around the control, such as framing, typography, sound, and timeline structure.

If you want to learn DaVinci Resolve fast, use a real task as the lesson. Pick a repeated decision from your current edit, save the smallest useful preset, and test it against an exception. Then write down what the preset does and where it fails. That note is more memorable than a menu path alone because it connects the feature to an actual choice.

An app that helps you while using DaVinci Resolve is useful when a tutorial's cursor is not where your control appears or you cannot identify the selected Inspector context. 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. The on-screen explanation can help you locate a menu while you keep the technical decision about preset scope in your hands.

The point is not that one source replaces every other one. Use Blackmagic documentation for version facts, a video for seeing the workflow, community answers for unusual configurations, and practice clips to check what the control actually changes. If you are building foundational editing skills, the DaVinci Resolve 21 tutorial path points to broader learning material and control differences.

Blackmagic Design CEO Grant Petty described the general value of removing repetitive work this way: “With AI assistant support, our customers can now ask Claude or ChatGPT to handle repetitive tasks,” said Grant Petty, Blackmagic Design CEO. (Blackmagic Design, DaVinci Resolve 21.1 announcement). Inspector presets are a separate, direct editing feature, but the same practical aim applies: spend less time re-entering settled values and more time judging the result.

Is an AI tool to learn DaVinci Resolve useful for this task?

An AI tool can help explain terminology or locate a control, but it should not be treated as proof of how a specific Resolve 21.1 preset behaves. Verify the answer against Blackmagic's release information and the visible result in your own project.

For a precise prompt, include your version, page, selection, and desired outcome: “I'm in Resolve 21.1 on the Edit page with a title selected. I want to save its font and position as one reusable group. Which Inspector menu should I inspect, and how can I test what gets applied?” That is more useful than “How do presets work?” The more clearly you describe the screen, the less the answer has to guess.

Do not paste confidential footage, client names, or project details into any assistant unless your organization's policy permits it. For basic UI navigation, describe the control without exposing protected material. If the assistant gives you a menu path that does not exist, check the version. The feature did not exist in 21.0, and a model trained on older help pages may return a workaround rather than the 21.1 control.

A screen-aware helper has a different role from a text-only chat answer. It can orient you to the visible interface, while official release notes remain the better authority for whether the feature is in a particular version. Neither should decide whether the saved values are appropriate for the shot. That remains an editorial judgment.

Why do older guides say Inspector presets are missing?

Older guides describe earlier versions of Resolve, when native Inspector presets were not available in the same way. DaVinci Resolve 21.1 adds the feature, so an older answer can be accurate for its publication date and outdated for your current build.

Blackmagic's own feature-request forum includes a September 2024 request for clip Inspector presets. That post shows the feature was being requested before Resolve 21.1, but a request is not documentation of the later implementation. Use it as historical context, not as a current instruction. (Blackmagic Design forum request)

An older workaround can remain useful. Copying attributes helps when you need a selective one-time transfer. A Power Bin can hold a reusable clip or graphic. A Fusion macro can preserve a node construction. Project Settings presets handle project configuration. The new Inspector preset feature gives you another tool, but it does not erase the reasons those workflows exist.

When reading a tutorial, check its upload date and software version before interpreting a missing control as your mistake. A five-year-old explanation can still teach a durable editing idea, such as why a title should stay within a safe area. It may not describe the current way to save its values. Keep the idea, update the click path.

What should I remember before I close Resolve?

Use DaVinci Resolve 21.1 or later, choose an individual preset for a narrow repeatable setting, and use a group preset only when the whole combination should travel together. Test it on another clip before broad use, and choose a reusable object, Paste Attributes, a macro, or a PowerGrade when that better matches what you need to preserve.

Blackmagic introduced Inspector presets in Resolve 21.1 and says they can save and recall favorite parameter configurations across video, audio, transitions, and transforms. The release note is the reliable version boundary. The rest is a workflow decision: pick the reusable unit, name it clearly, and check it in a different context. (Blackmagic Design 21.1 announcement)

If the preset control is absent, check the version and selected timeline object first. If the result is too broad, narrow the saved setting or split it into variants. If it disappears across projects or machines, verify the storage scope with a controlled test and keep the underlying object or numeric recipe available. Those checks answer most of the practical questions without confusing Inspector presets with every other Resolve feature that happens to use the word “preset.”

Resolve presets should save repeatable decisions, not replace them. Set a value for a reason, apply it where that reason still holds, and inspect the shot. That is the safe way to save time without making your edit look like it came from a menu.