Support & Learning

When setting a new shortcut, a conflict prompt pops up (e.g., showing it's already occupied by another command). Will force-binding it cause the original function to fail?

The underlying layer of keyboard shortcuts follows the principle of single command exclusivity. If you forcibly bind an already occupied key, the system will forcefully strip the shortcut mapping from the original function.

[Operation] ① When entering a key combination, if an occupancy prompt is triggered, the pop-up will explicitly state "Shortcut Conflict: Already occupied by [Command XX]"; ② Clicking "Continue Binding" will forcefully replace the binding relationship, and the original command will instantly lose the shortcut and become an unbound blank state. If you need to keep the original function, click "Do Not Bind" and switch to another free key; ③ Find free keys: Click the main key or modifier key in the visual keyboard area to check all function combinations occupied by that key in the right "Key Occupancy Details", and prioritize combinations with a low or 0 occupancy count; ④ After adjustments, you must click "Save" in the bottom right corner to apply the changes.

[Verification] Trigger the new command and the original command separately in the main software interface. The new command will execute normally, and the original command can be triggered via the main menu or right-click menu without creating hotkey conflicts.

Was This Helpful?

Need More Help?

Explore additional support options if you can’t find
what you’re looking for.

Account Center

Sign in with Wondershare ID to get invoice, redeem
serial number, cancel subscription, etc.

Contact us

Can’t find the answers you’re looking for? We’re
here to help.