Skip to main content

The anchor shortcut on keyboard sometimes not working

  • February 6, 2026
  • 4 replies
  • 31 views

jimmy.yang

I was using pen tool to draw a curve, somehow when I pressed “alt” trying to edit the curve through anchor handle,  it didn’t work if the anchor handle I is the last one of the vector or line. It’s really a big problem and slowing down my work. Did I accidentally change the setting or it’s a bug ?

4 replies

Figgy Newton
  • New Member
  • February 11, 2026

Same here. As of last week, whenever I hold the option key while using the vector tool, it no longer grabs a single side of the handle. It’s driving me bonkers. I restarted and re-installed Figma. It has worked a couple of times as it use, but then stops. I haven’t changed anything manually. I use this ALL THE TIME for work.

Today, it has also started showing something like a bounding box, when I select more than one point at a time, and makes it difficult to then grab and move the points around (image attached).

 

I have checked my modifier keys in the OS, and verified that this also happens when using Figma on the web.

 

Figma Desktop App 126.1.2

Tahoe 26.2

 

 


djv
Figmate
  • Community Support
  • February 19, 2026

Hi All, thanks for flagging this issue and apologies for the delayed reply! 

Are you still having issues with the anchor shortcut? I completely understand how this could disrupt your workflow. If so, with a few more details, I can send this over to our team to investigate further. 

Since ​@jimmy.yang mentioned that it only sometimes does not work, may I ask if this is only occurring with existing anchor points? Or is it happening with both new and existing anchor points?


Figgy Newton
  • New Member
  • February 20, 2026

For me it resolved yesterday. I haven’t had the issue since. When it was occurring, it was on both new and old vectors, and seemed mostly random, but would occasionally work on the first point or two of a new vector. 


djv
Figmate
  • Community Support
  • February 20, 2026

Glad to hear that, ​@Figgy Newton

Please let me know if you have any further issues. I’ll still pass this additional context onto the team in the meantime, just in case the team does need it in the future.