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.
Same, although I found a bit of a work around, its not great, but you just have to tyope the exact decimal in the x & y positions, not great at all if you’re drawing vectors etc, but can work for frames. Sometimes.
I deselected the “Snap to pixel grid” option, and still frames snap to the pixel grid. All the other types of layer don’t, only frames. Essentially, both coordinates and dimensions of frames are not allowed to be decimal (sub-pixel), except if you change the value manually in the sidebar, but as soon as you “touch” the dimensions on the canvas, it will pop back to the nearest pixel. I’m wondering if this is a bug or not.
To me this is a problem because it generate weird behaviors, for example here in the picture, I’m trying to anchor the “Frame 2” vertex to the rectangle’s vertex, you can see the red “snap indicator” is there but the frame is not allowed to stay in between the pixels, so I cannot place it where I need it. In this specific case I could move the rectangles over the frame, but in complex design that could be not feasible. That’s why it seems weird.
When “Span to pixel grid” is disabled, frames ignore this settings when moving them on the canvas. They still snap to the pixel grid, unless a decimal value is entered manually in the inspector sidebar. Rectangles, vectors etc all respect this setting.
This seems to have been a bug for a while: see here and here
We’ve confirmed with the team that certain layer types (frames/instances/components/widgets) will always snap to pixel grid no matter what, so this is an expected behavior.
We’ll update this topic into a feature request, so users can continue to share their feedback and vote for future changes.
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”.
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.
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.
