Active Member

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

Forum|Forum|4 years ago
October 21, 2021
68 replies
51038 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?

Share an idea

Show previous replies

Carlos_Aguilar

Just learned about this when trying to align a logo that has a M and C and uses the C as base, when we need the M. So just keeping the request active to see if we get a solution 😉

Lorenzo2

Why did we get an app-wide update to UI sooner than a 3 years old fix?

deb2

New Member

Please fix this. Its entirely breaking my workflow for small reusable elements on prototype of a vector-based map. There’s no reason these elements need to be fixed to the pixel grid.

Liam_Salas

Figma please fix this. It’s extremely disruptive to workflow.

Tom_Auger2

Active Member

I don’t know whether I’ve already posted my +1 - I probably have, but this should have been fixed ages ago.

The image below shows a frame nested inside another frame. The outer frame’s dimensions were set by a Distribute operation, thus it’s not on the pixel grid. The inner frame was created after this process and so I need to snap to object/geometry, NOT the pixel grid. Pixel grid is OFF and yet the corner handles snap to the grid when they absolutely should not.

Snap to Pixel Grid should be universal with no exceptions. I can’t think of a single use case where this might be the desired behaviour.

Figma, please address this bug ASAP, and please make it retroactive in UI V2 (because UI V3...)