Skip to main content

Additional keyboard modifiers or shortcuts to deep-select to select only components

  • November 20, 2024
  • 3 replies
  • 122 views

Tom_Auger2

Use case: Once an advanced UI has been built , users want a way to quickly select nested components in order to modify their properties and attributes. In this stage of design, designers are less interested in manipulating sub-elements of a component, and more interested in selecting the component itself to modify properties and variables.

Current challenges: the deep-select modifier (CMD/CTRL) is currently the most efficient way to access deeply nested items, however it is fairly indiscriminate and will often select the deepest nested element under the cursor. With complex components this often means a graphical element like a frame or a text element, requiring the user to step out of the hierarchy, often a number of steps, before arriving on the parent component, or they must use the mouse to then select the parent component from the Design properties panel.

Recommendation / Request:
Provide an optional modifier key to be used while deep-selecting to restrict selection to only components. It could still select the deepest nested component in cases where there is ambiguity. For example, (on the Mac):

  • CMD-click to select the deepest nested layer under the cursor (current functionality)
  • CMD-right-click to get a menu of all the nested layers under the cursor (currently functionality but please fix the layer select bug)
  • CMD-Opt-click to select the deepest nested component under the cursor
  • CMD-Opt-right-click to get a menu of only nested component layers under the cursor.

This would greatly improve the efficiency of working at later stages of mockup/design.

Optional shortcut: please provide a shortcut/hotkey for “Select Parent Instance” which can currently only be accessed via a hidden UI control in the Design properties palette when hovering over the parent instance.

3 replies

ty_le
  • New Member
  • August 4, 2025

+1! I was going to post about this and glad that others also share the same frustrations! I noticed this has been discussed years ago in various other threads that are now closed: 

I very often find myself clicking on the text of a nested component and then having to use \ or ⇧+⏎ multiple times to go “up” to the parent component.

On one of the old threads, someone suggested to lock child layers and add a 0.01% opacity fill on the top level layer of the component, but this is a hacky workaround. Please give us this feature!


Luca_Benazzi

This would definitely be a very useful feature and I am surprised Figma hasn't addressed it already. I don’t think an additional modifier key is necessary. When the user is in cmd + hover mode, it already highlights with a red dotted line the different hierarchical layers based on where the cursor is (even if it’s a bit dodgy in the current implementation). Problem is, it doesn’t allow to select them! It would save so much time if one could just double click to select the whole group/frame/component, based on the current hover position/highlighted layer. 

As of May 2026, right click when holding the Cmd key is probably the best way to make a selection at any level in the hierarchy. The implementation is a very good one (feedback on hover helps identify what the current layer is, and which sit above/below, then on mouseover the layer names and correspondent selection on the canvas get highlighted at the same time). It would really help to have a way to bypass that menu, and go straight to the desired level on hover. 

Note: double clicking twice is a way to select a whole component/frame/group at the highest level and it works reasonably well already, but things get tricky when that element is not in front, e.g. in the screenshot attached, the elements in red are part of a group, but because that group sits below some rectangular shape with no fill, selecting it on double click is utterly impossible. 

 


Luca_Benazzi

As I can’t edit the previous reply, I just want to add that the current functionality does indeed allow to select at a higher layer than the deepest, when in ‘cmd sometimes it doesn’t work as expected (e.g., it doesn’t allow me to select a frame/group if it’s positioned on top of other layers, in a situation similar to the one described above, in the screenshot).