Skip to main content
Solved

NEW problem with deleting guides

  • February 18, 2026
  • 4 replies
  • 69 views

coral

Strange behavior, I don't remember if it was already there or not, but it's causing me problems: in the browser version (latest Firefox 147.0.4 (aarch64) on mac osx 26.3), when I select a guide by clicking on it, I can no longer delete it by pressing the DELETE key. Instead, I first have to move it even just one pixel, and only then can I delete it.

Best answer by djv

Hey All, thanks for flagging this issue! 

I completely understand how this must be slowing down your workflow. I sent this topic over to the team, and they confirmed that this is a confirmed bug that they are investigating. While I can’t promise an exact timeline for a solution, rest-assured that this is on the team’s radar for improvement.

In the meantime, as a temporary solution, as mentioned by ​@coral, moving the guide or other similar actions to refocus the Guide should help allow it to be deleted. We appreciate your patience and understanding while the team works through this towards a solution. 

4 replies

Jess and Kira
  • New Member
  • February 18, 2026

I’m on a windows computer and am experiencing the same issue. Although moving the guide, as you said, doesn’t work for me 😕


Raviraj_Samant

Facing the same issue even on Macbook pro. I sometimes have to move it to delete or use the contextual menu

 


Armando_Lopez
  • New Member
  • February 25, 2026

Same issue using the Mac OS Figma app. One click select does not allow me to delete a guide. I have to click on it a second time to be able to delete by pressing the delete key.

The first click brings up additional specs of all guides in the frame. It’s a bit frustrating to make the user click twice even though the guide highlights on the first click. 

 


djv
Figmate
  • Community Support
  • Answer
  • March 9, 2026

Hey All, thanks for flagging this issue! 

I completely understand how this must be slowing down your workflow. I sent this topic over to the team, and they confirmed that this is a confirmed bug that they are investigating. While I can’t promise an exact timeline for a solution, rest-assured that this is on the team’s radar for improvement.

In the meantime, as a temporary solution, as mentioned by ​@coral, moving the guide or other similar actions to refocus the Guide should help allow it to be deleted. We appreciate your patience and understanding while the team works through this towards a solution.