Articles / Fixesupdated for DaVinci Resolve 21.1 (November 2026)

DaVinci Resolve Photo Page Keyboard Not Working? Fix It

Marius Manolachi33 min read

Quick answer

In DaVinci Resolve 21.1, a Photo Page key can seem unresponsive because the relevant panel lacks focus, a shortcut has a specific condition, or the active keyboard mapping changed. Click the panel named in the shortcut’s instructions, check the command in Keyboard Customization, and restore the DaVinci Resolve mapping if needed. On Windows, Resolve’s Command shortcuts use Control.

Illustration of a keyboard troubleshooting decision path for the DaVinci Resolve Photo Page.

I’d start with the panel, not the keyboard. On the Photo Page, a key can do nothing because Resolve is listening to a different part of the interface, or because the command only works in a particular mode. As of November 2026, this guide is for DaVinci Resolve 21.1; use the command search in your own installation when its displayed shortcut differs from a published list.

Why is the DaVinci Resolve Photo Page keyboard not working?

A Photo Page shortcut can appear broken when the wrong panel has focus, the shortcut’s required mode is inactive, the key is mapped to another command, or the operating system is sending a different input than you expect. Test those causes separately before resetting preferences or changing every shortcut.

DaVinci Resolve’s Reference Manual describes shortcuts as commands whose behavior can depend on the active panel. The manual also explains that shortcuts can be assigned to the application generally or to a specific panel. That distinction matters on the Photo Page: clicking a thumbnail, the viewer, a tool area, or the Inspector changes what Resolve treats as the active part of the workspace.

A key that works on another Resolve page can still fail on the Photo Page because the active panel and command conditions can differ.

A useful first question is not “Is my keyboard broken?” but “What exact command should this key run here?” Write down the key, the result you expect, the selected photo, and the visible panel that should receive the command. A report like “S does nothing” is hard to diagnose. “S should tag the selected image as Good Take, but the Photo Album is selected and no tag appears” gives you something specific to test.

Use this quick sequence:

  1. Click once inside the Photo Page area where the command is supposed to apply.
  2. Confirm the relevant image or tool is selected.
  3. Check whether the command has a mode requirement, such as Capture panel being active.
  4. Search for the command in DaVinci Resolve > Keyboard Customization.
  5. Compare the listed key with the key you pressed.
  6. Test the same physical key in another application.

If the key works in another application but not in Resolve, focus, command availability, or Resolve’s mapping becomes more likely than a failed keyboard. If the key fails everywhere, check the operating system, input device, and keyboard settings before editing Resolve’s shortcut preset.

That’s a diagnostic sequence, not a claim that one cause explains every report. Blackmagic’s manual documents focus-sensitive mappings and the Photo Page shortcut list documents conditions for particular actions. The specific symptom still matters.

How do I tell whether Resolve or the keyboard is ignoring the key?

Test one ordinary letter outside DaVinci Resolve, then test one known Photo Page command under its documented conditions. If the letter works elsewhere but the Resolve command does not, look inside Resolve first; if it fails across apps, investigate the keyboard or operating-system input settings.

This test separates input problems from application behavior without changing your preferences.

  1. Open a plain text field in another app and press a letter key such as A.
  2. Confirm whether the expected character appears.
  3. Return to Resolve and click the Photo Page panel you want to test.
  4. Try a documented shortcut whose requirements you can meet.
  5. Record what happened, including whether a menu, rating, tag, or image changed.

A text field is useful for checking whether a letter reaches the computer at all. It does not prove that a Photo Page shortcut is assigned correctly. If A types outside Resolve but a shortcut key does nothing in Resolve, that only narrows the investigation.

Use the command’s visible result as evidence. If you press a number to assign a rating, look at the selected image’s rating indicator. If you press a tag key, check the clip’s displayed tag state. If you issue a reset command, inspect the image and the relevant effect controls. A brief pause or a subtle UI change can be easy to miss, so don’t rely on sound or a vague impression.

Avoid testing with a shortcut that could change valuable work. In particular, do not use a reset command on an image whose adjustments you need unless you have saved or duplicated your work and understand what the command clears. Begin with non-destructive checks such as focus, command search, and a rating on a test image.

What the result tells you

Test resultWhat it suggestsNext check
A letter fails in a text field and in ResolveThe operating system or input device may not be delivering the key as expectedTest another keyboard or connection; review OS input and accessibility settings
A letter works in a text field, but one Resolve command failsThe keyboard can send input; the command may lack focus, a required mode, or an active mappingCheck the command’s documented conditions and Keyboard Customization
The same command works after clicking a different panelPanel focus was likely part of the problemMake the correct panel active before using that shortcut
A menu command works, but its assigned key does notThe command exists; the key assignment, modifier, or input interpretation needs checkingSearch for the command and inspect its mapping
One shortcut works but a different Photo Page shortcut does notThe issue may be command-specific rather than a general keyboard failureDiagnose each command separately
The shortcut works in another project but not this oneCompare workspace state, selected panel, and any project-specific or saved interface configuration before resetting shortcutsReproduce the test in the same visible state

Treat this table as a decision aid, not a guarantee. A shortcut can have more than one condition. A different result after clicking a panel supports a focus diagnosis, but it doesn’t tell you why the original focus changed.

If basic letters also fail in other apps, Resolve is not the first place to fix the issue. Check whether the keyboard is connected, whether the input source has changed, and whether accessibility features are filtering or delaying key input. If only one modifier combination fails, inspect both the modifier key and the key layout before concluding the entire keyboard is unresponsive.

How do I check panel focus on the Photo Page?

Click the panel that the command is meant to affect, then retry the shortcut. DaVinci Resolve allows panel-specific mappings, so a key can invoke a different command, or no relevant command, when another panel is active.

Resolve’s Reference Manual says that a panel has focus when an item or control within it is clicked. The manual also describes a focus indicator option in User Preferences that can show a red line at the top of the active panel. If you’re unsure which region currently has focus, enable that indicator and look for the highlighted panel.

Use this sequence:

  1. Identify the object the shortcut should change, such as the selected photo or an Inspector control.
  2. Click the relevant panel, not an empty part of the interface.
  3. Confirm that the intended photo remains selected.
  4. Check the panel focus indicator if you have enabled it.
  5. Press the shortcut once.
  6. Look for a visible change in the correct object or control.

A common trap is clicking the viewer to inspect an image, then assuming the Inspector still has keyboard focus. The viewer and Inspector are different interface areas. If a command’s documentation says “The Inspector must be in focus,” click the Inspector before testing that command.

Another trap is assuming a page name describes one single focus target. The Photo Page contains distinct work areas. The keyboard is not necessarily acting on “the page” as a whole. A shortcut may apply to the selected item in a photo browser, depend on a capture view being active, or work only when a particular control panel has focus.

Focus also explains why a shortcut can seem intermittent. You may be clicking different panels as you compare images, adjusting a control, or selecting a thumbnail. That changes the active panel, even if the overall layout looks almost the same.

If you want to make focus easier to track, use Resolve’s focus indicator setting described in the Reference Manual. It does not repair a mapping, but it gives you a visible clue about where Resolve expects keyboard input. Once enabled, test the same shortcut twice: first with the original panel active, then after clicking the intended panel. Note whether the result changes.

When a shortcut’s effect depends on the selected panel, clicking the correct panel is part of the command.

Do not confuse a missing page-navigation button with a keyboard failure. Resolve lets users hide page buttons or hide the navigation bar; its manual says hidden pages can still be reached through the Workspace menu or shortcuts. If the Photo Page itself is missing from the bottom bar, check Workspace > Show Page and Workspace > Show Page Navigation before concluding that the keyboard stopped working.

The Photo Page is new in Resolve 21. Blackmagic’s announcement of DaVinci Resolve 21 describes it as a page for working with still photographs. The interface and available commands are not identical to the Edit or Color pages. A shortcut remembered from an editing tutorial may not be relevant to the selected Photo Page panel.

For a guided introduction to that workspace, see how to use the DaVinci Resolve 21 Photo Page. For this keyboard problem, though, begin with the active panel and the exact command rather than switching workflows.

Which DaVinci Resolve Photo Page shortcuts should I test?

The Resolve 21 New Features Guide lists Photo Page shortcuts for capture, ratings, tags, rotation, flipping, and resets. Several have explicit requirements, so confirm the mode or panel before deciding a key is broken.

The official Resolve 21 New Features Guide lists the following shortcuts. The guide presents modifier keys using macOS terminology; Blackmagic’s Reference Manual explains the Windows and Linux equivalents.

Photo Page actionPublished shortcutCondition or note
Image CaptureCCapture Panel or Capture Live View must be active
Assign star rating1 through 5Applies in the Photo Album and Media Pool
Remove star rating0Removes all stars
Tag Good TakeSPress S again to clear the tag
Tag Rejected TakeXPress X again to clear the tag
Rotate leftCommand-[On Windows and Linux, Command corresponds to Control
Rotate rightCommand-]On Windows and Linux, Command corresponds to Control
Flip horizontallyShift-[Check the current mapping if your keyboard layout changes these characters
Flip verticallyShift-]Check the current mapping if your keyboard layout changes these characters
Reset PhotoCommand-RInspector must be in focus
Remove All Photo EffectsShift-RInspector must be in focus
Remove and Reset AllCommand-Shift-RInspector must be in focus

The most useful troubleshooting tests are the ones with clear visible outcomes and low risk. A star rating or tag can be easier to verify than a reset. Start with a selected test photo and note its current state. Press a rating key once, check the rating, then use the documented clear action if you want to return the test image to its previous state.

The capture shortcut has a mode condition. Pressing C while neither the Capture Panel nor Capture Live View is active does not establish that the key itself is faulty. First switch to the required capture mode, then test the key.

The reset shortcuts deserve extra care. They are not generic “undo whatever went wrong” keys. The guide assigns distinct actions to Reset Photo, Remove All Photo Effects, and Remove and Reset All. Those names describe different scopes. If a reset key appears to do nothing, first check the Inspector-focus requirement; if it works but changes more than you intended, stop and use undo or restore a known good image state rather than repeating it.

This list is a reference for Resolve 21’s Photo Page guide, not a promise that every customized installation uses the same mapping. If you or someone else changed a preset, the Keyboard Customization window is the authority for what your installation currently assigns.

What if the key is right but the result looks unchanged?

A command can run without producing an obvious result. A photo may already have the chosen rating, a tag may already be cleared, or a transformation may be difficult to notice at the viewer’s current zoom. Check the value or state the command is meant to change, not just the overall picture.

For example, if you press a rating key on an image that already has that rating, the visible state may remain the same. That does not prove the key press failed. Select a test image with a different known state, apply one rating, and inspect the rating indicator. Likewise, when toggling or clearing a tag, check the tag’s displayed state after the key press.

For rotation or flipping, inspect the image orientation closely. A symmetrical subject can make a flip hard to recognize. Use an image with an obvious left-right feature, such as readable text, and compare before and after. This is a worked diagnostic example, not a claim that a particular test was performed.

For resets, compare a specific control value or effect state before and after. A subtle grade can make a reset hard to see at a glance. If you don’t know which values the reset affects, don’t use a valuable image as the experiment. Start with a duplicate or an image whose edits you can safely reproduce.

How do I check the shortcut assignment in Resolve 21.1?

Open DaVinci Resolve > Keyboard Customization, search for the command name, and inspect its current keystroke and mapping preset. Resolve’s manual describes this window as the place to choose a shortcut set, find available shortcuts, and create a custom mapping.

Use the command name, not only the key, as your search term. For example, search for Reset Photo rather than guessing which reset combination ought to work. Blackmagic’s manual says the Keyboard Customization window can search the command list, including All Commands, and display commands alongside assigned keystrokes.

Try this:

  1. Open DaVinci Resolve > Keyboard Customization.
  2. Select All Commands if you don’t know the command category.
  3. Search for the action’s name, such as Image Capture, Reset Photo, or Star Rating.
  4. Read the keystroke shown for the matching command.
  5. Check which keyboard preset is selected.
  6. If the command appears more than once, inspect the relevant panel-specific entry as well as the application-level entry.

The same key may be mapped to different actions at different levels. The manual gives the example of a shortcut being assigned to the application and to a particular panel. When the relevant panel is active, a panel-level assignment can take priority. So, don’t stop after finding a key somewhere in the command list. Confirm that you found the matching command for the active context.

If the command has no keystroke listed, the key you expect may never have been assigned to it in that mapping. You can assign a shortcut in the customization window, but do that only after checking the existing mapping and possible conflicts. A key that appears unused in one command group might have another assignment elsewhere.

Blackmagic’s keyboard customization overview confirms that Resolve supports custom shortcuts and saved presets. The Reference Manual is more useful for diagnosing this particular issue because it describes panel-level mappings, searching commands, and managing presets.

How do I know whether a custom preset is the cause?

Compare the selected preset with the mapping you intended to use, then check the specific Photo Page command. A custom preset isn’t automatically wrong; it may simply assign a different key or preserve an earlier choice.

A preset can be intentional. You might have selected a mapping designed to resemble another editing application, or created a custom set for a particular workstation. The problem is a mismatch between what you expect and what Resolve currently shows, not the existence of customization itself.

If you share a workstation, ask whether another user changed the mapping before you reset it. If you imported a preset, locate the imported mapping and check its assignments. If you copied a setup from another computer, keep in mind that a shortcut file represents a mapping choice; it cannot make a command available in a context where Resolve does not support it.

The Reference Manual lists options to save a new preset, import a preset, export a preset, and delete a preset. That gives you a safer path than removing settings folders or resetting all application preferences. Export a mapping you want to preserve before replacing or deleting anything.

How do I reset DaVinci Resolve Photo Page keyboard shortcuts safely?

Choose the DaVinci Resolve mapping in the Keyboard Customization preset dropdown to return to the default Resolve shortcut set. Before replacing a custom mapping, export it from the Option menu so you can import it again if you need it.

The phrase “reset shortcuts” can mean two different things. You may want to switch from a custom set back to Resolve’s standard mapping, or you may want to erase a custom preset. Those are not the same operation. Prefer selecting the standard DaVinci Resolve mapping when your goal is to test the defaults; don’t delete a custom preset just to see whether one Photo Page command works.

A careful reset sequence:

  1. Open DaVinci Resolve > Keyboard Customization.
  2. If the current mapping contains custom work you want to keep, open the window’s Option menu and choose Export Preset.
  3. Save the exported shortcut file somewhere you can find later.
  4. Use the preset dropdown to select DaVinci Resolve.
  5. Search for the Photo Page command that was failing.
  6. Confirm its listed shortcut.
  7. Return to the Photo Page and test it with the required panel and mode active.

The export step is a backup, not a requirement for every user. It is useful if you created a custom mapping or inherited one that you may need later. The Reference Manual documents both exporting and importing keyboard shortcut files, as well as saving new presets.

After selecting the standard preset, test only the command that failed. Don’t change several mappings at once. If the command now works, the previous mapping or its context likely contributed to the problem. If it still fails, return to focus, mode, keyboard input, and operating-system checks instead of repeatedly switching presets.

As of Resolve 21.1, Blackmagic says saved custom keyboard changes automatically update the base shortcut settings when new Resolve versions add non-conflicting shortcuts. The manual says this feature preserves custom shortcuts while updating remaining non-conflicting ones. That reduces one reason to rebuild a preset after each update, but it does not prove that your current key assignment matches the default or that a panel has focus.

Do not delete Resolve preferences folders based on a single dead key. That is a much broader intervention than selecting the standard keyboard mapping. It can affect settings unrelated to the Photo Page and makes it harder to identify the actual cause.

Changing a shortcut preset is a controlled test; deleting preferences is a much broader reset.

What if I changed only one key?

Search for the exact command and inspect both its application-wide and panel-specific assignments. If the intended key was reassigned, make one deliberate change, check for conflicts, save the mapping, and test the same Photo Page state again.

A keyboard mapping can be customized at a broad or narrow level. If a key works in one panel but not another, check whether the command was assigned at the panel level. If the command is available only in a particular Photo Page context, make sure the matching mapping applies to that context.

Before editing a shortcut, write down the current assignment. Then change one thing, not several. If the result gets worse, you can restore the previous key without guessing which edit caused it.

Avoid taking a key just because it feels convenient. The manual’s command search can reveal whether a key combination is already used. A shortcut conflict can create a new symptom: the key may trigger an unexpected action, or an existing command may become harder to reach.

If you’re assigning keys that contain punctuation, test the exact physical key and modifier combination in your operating system. Keyboard layouts differ in where punctuation characters sit and which modifiers produce them. A command involving [ or ] can be especially confusing on a layout where those characters require an extra modifier or occupy a different physical key.

Why does the Photo Page shortcut work on Mac but not Windows?

DaVinci Resolve’s Reference Manual uses macOS Command and Option notation. Blackmagic says Command shortcuts correspond to Control on Windows and Linux, while Option corresponds to Alt, so translate the modifier before testing a published shortcut on Windows.

For example, the New Features Guide lists Command-R for Reset Photo. On Windows, try the corresponding Control-R mapping if your Keyboard Customization window confirms it. A Mac user pressing Command and a Windows user pressing Command are not pressing equivalent keys in Resolve’s documented shortcut notation.

The manual also says that macOS Control is not used by default for Resolve shortcuts, though it can be assigned through customization. So don’t assume a Mac instruction written as Command means Control on a Mac. Blackmagic’s convention is specifically about mapping Command to Control on Windows and Linux.

Manual notationmacOS keyWindows/Linux key
CommandCommandControl
OptionOptionAlt
ShiftShiftShift
Letter or numberSame named key, subject to layout and active mappingSame named key, subject to layout and active mapping

This is a translation guide, not a substitute for checking your active preset. If the mapping has been customized, the command may use a different combination on either platform. Search for the command in Resolve to confirm the actual assignment.

A Mac keyboard connected to a Windows computer can add another source of confusion. The physical labels may not match the modifier names used in the manual, and the operating system may interpret the keyboard differently. Test the modifiers in another app, confirm which key Resolve receives, and check the assignment shown in Keyboard Customization.

Don’t infer a keyboard problem from the command symbols alone. Translate the modifier, then verify focus and mode. If a shortcut uses brackets, punctuation, or a non-US layout, test the character and inspect the selected input layout too.

Could my keyboard layout or input source be changing the shortcut?

Yes. A changed input source or keyboard layout can alter which character a physical key produces, especially for punctuation-based combinations. Confirm the active layout in Windows or macOS, then test the exact shortcut Resolve displays.

Microsoft documents that Windows can have multiple keyboard layouts and that Windows key + Spacebar cycles through installed layouts. If a key combination stopped working after switching languages or layouts, check the input indicator in the taskbar and select the layout that matches your physical keyboard.

On Windows, use Settings > Time & language > Language & region to inspect installed languages and layouts. Microsoft’s guidance notes that a keyboard layout can change independently of the Windows display language. That means the interface can remain in English while the active key layout changes.

On macOS, check the current input source in Keyboard settings. Apple’s documentation describes the Keyboard Viewer as a way to see the layout for the current input source, including how Option and Shift change the displayed characters. If the physical keyboard and selected input source do not match, the same physical key can produce a different character.

This matters most when the shortcut includes punctuation such as [ or ]. Don’t assume that the symbol printed in a manual corresponds to the key position you are pressing on every regional keyboard. Search for the command in Keyboard Customization and check what Resolve expects, then use your operating system’s keyboard viewer or layout indicator to confirm the character being sent.

A practical check:

  1. Note the active input language or source.
  2. Open a text field and press the physical key you intend to use.
  3. Confirm the character that appears.
  4. Compare it with the shortcut Resolve displays.
  5. Switch to the intended layout only if you recognize the change and want that layout.

If the shortcut uses letters or numbers, the layout may still affect the behavior of a modifier combination or the key’s location. If the command uses punctuation, layout mismatch becomes a more obvious possibility.

Apple notes that applications may have their own shortcuts and that a shortcut in one app may not apply in another. That is another reason to test inside Resolve and not assume a system-wide combination should work as a Resolve command.

Could an operating-system accessibility setting be affecting the keyboard?

It can. Windows and macOS offer accessibility features that change how key presses are accepted, delayed, or interpreted. Check these settings if keys are missed, repeated, or behave unusually across applications, not just on the Photo Page.

On Windows, Microsoft documents Filter Keys as a setting that can ignore brief or repeated keystrokes. Its accessibility shortcut list says holding the Right Shift key for eight seconds toggles Filter Keys. If you see unexpected filtering or a prompt after holding Shift, inspect Settings > Accessibility > Keyboard before changing Resolve’s mappings.

Windows also offers Sticky Keys, which changes how modifier keys are entered. If a combination like Control-Shift-R behaves differently from a single key, check whether Sticky Keys is enabled. Microsoft documents Shift pressed five times as a shortcut that can turn Sticky Keys on or off, depending on the system’s configuration.

On Mac, Apple lists Slow Keys and Sticky Keys among keyboard accessibility settings and documents an Accessibility Shortcuts panel that can be opened with Option-Command-F5, or by quickly pressing Touch ID three times on supported Mac or Magic Keyboard models. Check System Settings > Accessibility > Keyboard if a key seems delayed or modifier combinations behave differently than expected.

Don’t switch off an accessibility feature just because it exists. If you use it intentionally, keep it on and adapt your testing to its behavior. The point is to identify whether the feature explains the symptom. If the keyboard works normally in other apps and only a specific Photo Page command fails, accessibility settings are a less direct lead than panel focus or command mapping.

SymptomOS setting worth checkingWhy check it
Brief taps seem ignored across several appsWindows Filter Keys or Mac Slow KeysThese can change how short or delayed key presses are handled
Modifier combinations behave differentlySticky Keys or a stuck modifierModifier state affects shortcuts even when letter keys work
Punctuation shortcut sends the wrong characterActive input source or keyboard layoutThe physical key may not produce the character shown in Resolve
Keys fail only in ResolveResolve focus, mode, or mapping firstA system-wide setting is less likely if other apps receive the same keys normally

If a key is physically stuck, dirty, or failing, an operating-system setting won’t repair the hardware. Use another keyboard or the computer’s built-in keyboard as a comparison test when available. Change one variable at a time so you can tell whether the result comes from Resolve, the operating system, or the device.

Why does Command-R reset Photo work only sometimes?

The published Photo Page guide says the Inspector must be in focus for Reset Photo, Remove All Photo Effects, and Remove and Reset All. Click inside the Inspector first, confirm the selected image, and then test the intended reset command.

The three reset actions in the guide are distinct:

  • Reset Photo uses Command-R.
  • Remove All Photo Effects uses Shift-R.
  • Remove and Reset All uses Command-Shift-R.

The Inspector-focus requirement applies to that group in the guide. On Windows, translate Command to Control, then confirm your own assignment in Keyboard Customization. Don’t swap among the three commands as if they were interchangeable.

Before using any reset action, decide what you want to preserve. If you only want to remove effects, don’t assume a full reset is equivalent. If your goal is to restore every adjustment, read the command name and inspect its result on a safe test image first.

Use a non-destructive diagnostic:

  1. Select an image whose state you can safely change.
  2. Note the relevant adjustment or effect state.
  3. Click inside the Inspector.
  4. Confirm the command name and assigned shortcut.
  5. Trigger the command once.
  6. Inspect the same controls or effects for the expected change.

If the shortcut still seems unresponsive, use the command search to confirm the current mapping and verify that the Inspector is active. If you’re not sure what a reset will remove, use the menu command or leave the image unchanged until you have a copy. A reset that works but removes more than expected is not a keyboard problem.

This is one place where the visible result matters more than a keystroke. A command might reset one aspect of the photo while other changes remain. Check the control you expected to reset instead of judging only the overall image.

Why does C do nothing on the Photo Page?

The Resolve 21 New Features Guide lists C for Image Capture only when the Capture Panel or Capture Live View is active. Switch to the documented capture context, then test the key again.

This is a useful example of a shortcut condition. The key can be assigned correctly and still do nothing useful when its required panel or mode is inactive. A test outside that state cannot confirm whether the capture shortcut works.

Check the Capture Panel or Capture Live View, then press C once. Confirm a visible capture-related result before pressing it again. If the key still fails, search for Image Capture in Keyboard Customization and check the active assignment.

If the Capture Panel is unavailable or the camera is not ready, the command may not produce the result you expected. Don’t troubleshoot a missing capture outcome by remapping C immediately. First confirm that the capture interface is open and that the command is available in the current setup.

Also separate the camera or capture-device issue from the keyboard issue. If the keyboard reaches other commands but the capture action does not proceed, the failure may be in the capture state or device connection. Test a different documented shortcut, such as a star rating on a selected photo, to see whether the Photo Page responds to keys at all.

Why do star rating or tag shortcuts appear not to work?

The guide assigns number keys 1 through 5 to star ratings, 0 to remove all stars, and S or X to Good Take and Rejected Take tags. Select the intended image, press one key, then check the image’s displayed rating or tag state.

Ratings and tags are easy to misread if the wrong item is selected. Before pressing a number, confirm which photo is active. Afterward, inspect that photo rather than the image currently shown in another panel.

The guide says the rating shortcuts work in both the Photo Album and Media Pool. If you’re in one of those locations and the selected image still does not show the expected rating, inspect the assignment in Keyboard Customization and confirm the current mapping. If you’re in a different context, don’t assume the same command applies.

For tags, the published list says pressing S or X again clears that tag. That toggle-like behavior can make a shortcut look unreliable if you press it twice while checking whether it worked. Press it once, inspect the tag, then press again only if you intend to clear it.

Try an orderly test with a single image:

  1. Select one photo and note its current rating.
  2. Press one rating key from 1 through 5.
  3. Check the displayed rating.
  4. Press 0 only if you want to clear all stars on that test image.
  5. Press S once and inspect the Good Take tag.
  6. Press S again only if you want to clear it.
  7. Repeat for X if you need to test the Rejected Take tag.

These steps describe the documented behavior. They are not a measured result from hands-on testing. If the UI state does not change, the next useful checks are the selected item, panel focus, and active key assignment.

Why do bracket shortcuts rotate or flip the wrong way?

The Resolve 21 guide lists bracket-based shortcuts for rotation and flipping, but the character produced by a physical key can vary with keyboard layout. Check the exact combination shown in Keyboard Customization and verify the input source before remapping the command.

The listed actions are Command-[ for rotate left, Command-] for rotate right, Shift-[ for horizontal flip, and Shift-] for vertical flip. On Windows or Linux, Command corresponds to Control in Blackmagic’s manual.

If your layout makes brackets difficult to enter, don’t assume that pressing the same physical key as a US keyboard will produce the same command. Check the keyboard layout indicator or Keyboard Viewer, then compare the produced character with Resolve’s displayed shortcut.

Use a test image with an obvious orientation. A portrait with visible text or a clear left-right feature is easier to inspect than a symmetrical object. If a key rotates the photo but the direction differs from what you expected, first confirm whether you pressed the left or right bracket as interpreted by your layout. If the command itself is assigned differently, Resolve’s Keyboard Customization window will show that.

Do not keep pressing a transformation shortcut while uncertain about its effect. Rotation and flipping can be cumulative. If you need a clean baseline, stop, inspect the image state, and use a known-safe copy rather than trying random modifier combinations.

What if the shortcut works in menus but not on the Photo Page?

A menu command working while its shortcut fails points toward focus, shortcut mapping, or modifier interpretation. Run the command once from the menu to confirm it is available, then inspect its keystroke and panel-specific assignment in Keyboard Customization.

Menu behavior can help isolate the problem, but it doesn’t prove the entire Photo Page is functioning as expected. A menu command may apply to the selected item even when the panel that receives a shortcut is different. Make sure the same image and relevant interface state are active for both tests.

Use this comparison:

  1. Select the photo you want to test.
  2. Run the command from the menu if one is available.
  3. Note exactly what changed.
  4. Search for the command in Keyboard Customization.
  5. Check the assigned key and any panel-level mapping.
  6. Click the intended panel and try the displayed shortcut.

If the menu action works and the keystroke does not, you have evidence that the command is available but the shortcut path differs. Check focus, the active preset, and the actual modifier. If the menu action also fails, the issue may be selection, mode, or command availability rather than the keyboard alone.

The Reference Manual describes shortcuts that are application-wide and shortcuts assigned to specific panels. It also says a panel-level action takes priority when that panel is in focus. This can explain why a menu command and keypress appear to disagree.

If the menu item itself is disabled, don’t try to solve that by assigning a new shortcut. First establish why the command is unavailable in the current context. A new key cannot make an unavailable action valid.

What if only one key, one modifier, or one keyboard fails?

Compare the same command using another keyboard or a different key assignment, then check the physical key and modifier separately. A failure limited to one device or one modifier is a different diagnostic pattern from every Photo Page shortcut failing.

If only one physical key fails across applications, test a different keyboard if available. On a laptop, compare the built-in keyboard with an external keyboard. On a desktop, reconnect the keyboard or try another port if that’s practical. These checks can help distinguish a device issue from a Resolve shortcut issue without changing the project.

If letter keys work but combinations fail, test the modifier keys by themselves in a safe context. A held or stuck Control, Command, Option, Alt, or Shift key can change what a normal letter means. The visible keyboard layout or system accessibility features may also affect how modifier combinations are processed.

If one keyboard works and another doesn’t, compare the keyboard labels, layout, and modifier arrangement. A compact keyboard may place function or modifier keys differently. On a Mac keyboard connected to Windows, the printed modifier labels may not match the names Resolve’s shortcut list uses.

If one key fails only in Resolve, inspect its assignment before deciding it is physically broken. Resolve allows custom mappings and panel-specific actions. If the key is assigned to another command, the key may be working perfectly while producing an unexpected result.

If all keyboard commands appear to fail only in one project, note that observation, but don’t infer that the project file caused it. Recheck the selected Photo Page panel and repeat the same test in the same mode. Then compare with another project only if you can do so without disrupting your work. A changed workspace state or selected item can alter the result without indicating a damaged project.

Should I update Resolve or reinstall it to fix Photo Page shortcuts?

Don’t reinstall Resolve as the first response to one unresponsive shortcut. First check focus, the command’s required mode, the current mapping, and operating-system input settings; consider an update or reinstall only when there is broader evidence of an application problem.

DaVinci Resolve 21 introduced the Photo Page, and the New Features Guide documents its shortcuts. This article’s version context is Resolve 21.1. If you’re on another major or point release, check that version’s manual and the command list in your installation rather than assuming every interface detail is identical.

The Reference Manual says Resolve 21.1 custom keyboard settings update non-conflicting shortcut assignments as new versions add them. That is a specific behavior for saved custom keyboard changes. It does not mean all shortcut behavior is identical across versions, nor does it make reinstalling a sensible first step.

Before updating, decide whether you need to preserve the current project and custom mappings. Export a custom keyboard preset you want to keep, and follow Blackmagic’s current project backup guidance for the version you use. Do not treat an update as a shortcut reset; it can change more than the mapping and may not address a focus or input-layout problem.

Use a broader application repair only if other Resolve features also malfunction, the problem persists across projects and keyboard tests, and you have already checked the documented shortcut conditions. If Resolve shows an error or a specific version’s release notes identify a relevant issue, follow the vendor’s instructions for that issue. Without that evidence, reinstalling is guesswork.

What should I record before asking for help?

Write down the Resolve version, operating system, exact command, exact key combination, selected Photo Page panel, and the result of testing the key elsewhere. That short record makes it easier for someone else to tell a focus problem from a mapping or input problem.

Include facts you can observe:

  • The Resolve version shown by your installation.
  • Whether you use macOS, Windows, or Linux.
  • The keyboard layout or input source currently selected.
  • The command name from the menu or Keyboard Customization search.
  • The exact key combination shown for that command.
  • Which Photo Page panel was active when you pressed it.
  • Whether the command has a mode requirement.
  • Whether the key works in a text field or another application.
  • What visibly changed, if anything.

Avoid describing the symptom only as “keyboard broken.” Say whether all keys fail, only one command fails, or the shortcut works after clicking a different panel. If the issue is limited to brackets or a modifier combination, say that too. Specific symptoms save time because each points to a different check.

Do not share private project media or account information just to demonstrate a shortcut. A written description of the interface state is often enough to begin troubleshooting. If a screen image is necessary, remove personal or client information first.

When can on-screen guidance help with this problem?

On-screen guidance can help when you know the result you want but can’t locate a command, panel, or setting in your current Resolve layout. It cannot replace checking the shortcut list or guarantee that a key or mapping will be fixed.

If the command search, panel labels, or a tutorial’s interface is hard to follow, an assistant that can see your current screen may help you locate the control while you remain in Resolve. 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.

Use any guidance alongside the checks above. Confirm the command name and key in Resolve’s own Keyboard Customization window, and keep control of changes to your mapping. The troubleshooting answer remains the same whether you use an assistant or not: identify the command, satisfy its panel and mode conditions, then verify the active assignment.

For general key combinations and command names, the DaVinci Resolve keyboard shortcuts reference is a useful companion. If your keyboard problem is resolved and you want to transfer Photo Page adjustments between images, see how to copy effects to other photos in the Photo Page.

The practical next step is simple: click the panel named by the command’s condition, search for that command in Keyboard Customization, and test one key with a visible result. If that works, you’ve found the right branch. If it doesn’t, the command’s displayed mapping and your operating system’s input settings are the next checks.

Frequently asked questions

Why is my keyboard not working on the DaVinci Resolve Photo Page?
The most common things to check are whether Resolve has focus, whether the correct Photo Page panel is active, and whether the command is available in the current mode. Click the target panel, then search for the command in DaVinci Resolve > Keyboard Customization to see its assigned key.
How do I reset DaVinci Resolve Photo Page keyboard shortcuts?
Open DaVinci Resolve > Keyboard Customization and choose the DaVinci Resolve mapping in the preset dropdown. If you saved a custom mapping, export it first from the Keyboard Customization window’s Option menu so you can restore it later.
What are the DaVinci Resolve Photo Page keyboard shortcuts?
The Resolve 21 New Features Guide lists C for image capture when the Capture panel or Capture Live View is active; 1-5 for star ratings, with 0 to clear them; S and X for Good Take and Rejected Take; and rotate, flip, and reset commands. Some work only in the right panel or mode.
Do DaVinci Resolve Photo Page shortcuts differ on Windows?
Yes. Blackmagic’s manual documents shortcuts using macOS Command and Option keys. It says Command maps to Control on Windows and Linux, while Option maps to Alt. Check the displayed mapping in your own Keyboard Customization window if you changed presets.
Why does Command-R reset Photo work only sometimes?
The Photo Page shortcut guide says the Inspector must be in focus for Reset Photo, Remove All Photo Effects, and Remove and Reset All. Click inside the Inspector before trying the reset command, and check the assignment in Keyboard Customization if it still does nothing.

Sources

Put this guide to work with TryUncle.

Ask about the step you’re on. TryUncle sees your screen and points at the control you need, so you can keep learning in your own project.

Get TryUncle for Mac or Windows

Keep reading