Skip to main content
JosephxBrick
Active Member
October 21, 2021

Turning off "snap to pixel grid" should turn snapping off!

  • October 21, 2021
  • 68 replies
  • 51035 views

Hi!

Turning off “snap to pixel grid” in a Figma Design file no longer changes snapping behavior when dragging frames around.

Whether this feature is turned on or off, a dragged frame still snaps to each pixel, no matter how zoomed-in. Note that some other objects (e.g., vector objects) still respect this setting. It’s just an issue with frames, components, and component instances. Note that If I group the frame, I then can drag the group to any sub-pixel location.

I’ve restarted my machine, restarted Figma, checked for updates, reloaded tabs, tried it in other design files. Tried it in the client, in Chrome, and in Safari. Same problem.

Can anyone else replicate this?

68 replies

Jonathan_Schmitz
March 7, 2023

Thank you for confirming! Hope this can be changed to the expected behaviour in the future. Perhaps the options could be: “Snap to pixel grid”, “Only snap frames to pixel grid” and “Don’t snap to pixel grid”.

JosephxBrick
Active Member
March 7, 2023

This is recent behavior that started last October. Frames once recognized this setting. What is the rational for calling this a feature and not a bug? It’s not as if frames cannot be positioned at sub-pixel coordinates.

djv
Figmate
Community Support
March 7, 2023

Hey there,

We hear you, and while we do have a record of users who report that it stopped working last October, as of October 12th, 2022, the team confirmed that certain layer types (frames/instances/components/widgets) will always snap to pixel grid no matter what by design, going forward.

To be completely transparent, the team views this as the expected behavior. We’ll continue to pass along your feedback to the team for future consideration.

Stan5
New Participant
May 3, 2023

This is a problem, not a feature.
It’s a very important setting when working at pixel level (for instance when you need to export to other file formats).

I do not understand the poor decision. Why would users that explicitly turn off Snap still want stuff to snap?

Sounds like a “its a feature not a bug” moment from Figma.

djv
Figmate
Community Support
May 3, 2023

We hear you @Stan5 and completely agree with and understand your frustration. Our team here can only relay the information we receive from the community to our developers and vice-versa.

With more feedback and Votes from the community, we can make a better case for this issue and force the team to reconsider the current behavior.

May 9, 2023

Maybe this usecase will help convincing the developers:
I am trying to draw a complex pictogram and need to be in full control while drawing.
While snapping to a grid is great when you are making a layout, it really sucks if you try to make a curve or the placement of an anchorpoint exactly right and the application won’t let you do it. Extremely frustrating.
I think I’ll start over in Adobe Illustrator, because I have no control in Figma and need precision.

Guy_Lepage
May 22, 2023

Uff… This is a huge issue for creating illustrations and configuring logos, vector graphics, etc. Please fix this.

May 30, 2023

Hello! I’m yet another frustrated user 🙂
Despite of my love for Figma, I am forced to moving back to Adobe Illustrator because of the “feature” of not being able to turn off snapping.

JosephxBrick
Active Member
June 20, 2023

This still frustrates me to no end. “Snap to Pixel Grid Disabled” should mean exactly that, no matter what type of node is selected. Apparently there is a Figma product owner out there who insists on dying on this hill. Please, someone talk them out of it!

Or at least, explain the rational, because – I don’t know – maybe there is valid merit to this decision.

Otherwise, dvaliao’s forwarded statement saying “Certain layer types (frames/instances/components/widgets) will always snap to pixel grid no matter what, so this is an expected behavior,” smells terrible.

Karel_Cancara
June 28, 2023

This is so frustrating!