Whoever decided this shouldn’t be allowed to decide things, this is absurdly awful behaviour.

When you have settings that only function on certain objects but not others, it creates ambiguity, and creates an absolutely awful user experience.

This is NOT a feature, this is a bug

I’m having the same issue. This forced snapping makes illustration and icon creation nearly impossible. It does make some sense for frames, but it’s incredibly frustrating since the width and height of an object are still allowed to have decimal places. This means that some objects can be resized but then never aligned properly with other items.

I also agree with other commenters that whoever pushed for this change needs to be more mindful of the user experience. This issue forced me to open another app to edit the vectors, which is something I haven’t had to do in a very long time.

This is genuinely one of the biggest issues with Figma and a huge reason why I (and apparently many other users) can’t illustrate–among other things–in this program. Incredibly frustrating and adds so much unnecessary time having to work around it. There’s no reasoning that makes any sense for why selecting “turn OFF snap to pixel” would not, in fact, fully turn off snap to pixel. Absolutely a bug - not a feature nor expected behavior.

Hello! I have this problem. Any new update on the resolution?

This is one of the reasons I have to keep Illustrator open. I can’t create proper illustrations or or icons when it insists on snapping to a grid. Sorry but I don’t have the time to waste to modify the X or Y coordinates manually.

this needs to be fixed.

It just explodes my brain. And gives me a very annoying user experience.

This is hugely annoying. I’m now experiencing an issue in my icon document where I cannot continue to create new frames without displacing them manually using the X-Y positioning.

Even worse, it seems that my former ‘off the grid’ -grid is positioned rightly on the round pixels. Now when I create a frame, it snaps ‘off grid’. On the Y it appears to be rounded somewhere halfway the actual grid. - complicated to explain, but right now my frames automatically snap somewhere halfway the grid. I have to manually fix this by decimals.

What the heck.

Can your devs explain why they think that it’s intentional to snap to pixel grid when “snap to pixel grid” is disabled? In every other software I used, it meant that you are able to move it around at the subpixel level with your mouse or arrow keys.

To me it seems support agrees that this is a bug, so that’s the classic case of support and users vs devs. 😆 Upvoted.

How can this still be a thing dating back to October 2021? How are people using this for professional work if you can literally be painted into a corner, and stuck typing numbers to position something properly.

I’m encountering this issue and it’s a real problem. Please please fix this! 🙏

I would love to see this fixed, was quite surprised to see this is considered ‘intended’.

With vectors points, you can hold “control” on mac to move them fluidly to fractional positions. This should be the case with all objects. I can’t get my designs to align properly right now unless I manually type the positions, which is way too time consuming.

This is so dumb.

Not expecting it to change, but it’s so dumb.

At least change the setting’s name. Turning off “Snap To Grid” and having things still snap to a grid is the most confusing thing…

Please ‘fix’ this, whatever that means to your developers. This is a horrible UX 😦

There are valid use cases for not wanting frames to snap to pixel. In my case, I use frames to mask images to comp designs outside of UI/UX. I want to utilize the frame constraints and the frame nesting as it’s much easier to work with than Figma’s masking function. All we’re asking for is an additional toggle in the settings that allows users to turn of snapping to pixel for frames/instances etc.

bump. ten characters.

also bump. would love the option to RnR without snap . . .

Seriously: if the Figma team can respond to say, “It’s an expected behavior,” why can’t they respond when dozens of uses call them out on that obvious baloney? In this case, “Expected Behavior” means, "Ooops, we wrote the code that way, and yep, Figma is doing what the code is written to do, so instead of admitting that it’s a problem, let’s lie to the people who use this software to make a living and tell them, “it’s a feature.”

Have some respect for your company and your team here. You know it’s not a feature. We know it’s not a feature. And yeah, your team has been hard at work on your major UI update, but bugs come first. And this is a bug. Sure, the code may be functioning as written, but the bug is in the spec’d behavior, not in the code.

For crying out loud, stop trying to Trump your way out of this and fix the problem.

…and while you’re in there writing new, correct code, why not make snapping to grid a property of the object, not of the application itself? That way everyone gets the solution they need, and both solutions can be applied in the same project.

It’s absolutely insane that we’re still having these issues. Snap to pixel, round to pixel… FGS exporting out assets should work as you’d expect @ true size. So infuriating.

Same here, also annoyed, while trying to edit icons, please fix this. It is not a feature, it is a UX flaw.

Its 17th Aug 2024 and still this anno

Same issue after years, I can’t properly center small icons even with snapping turned off. It’s annoying trying to work with small assets when working with vectors it always changes the position when scaling to fit the grid.

Still an issue…

To align a component or grouped object without snapping, you must break component instances from the main component and ungroup, which breaks the design system. Boooo…

Same frustration here. Just trying to create some simple vectors to enhance an existing UI component and I cannot for the life of me get them to line up because Figma has arbitrarily decided it’s the top (not the bottom) of the frame that should snap to pixel grid.

I was resigned to turning off pixel grid, zooming into max zoom and “eyeballing it” like a chump, when I discovered even that won’t work because of some arbitrary decision around frames and pixel snapping.

I’m assuming there’s a reason for this at the software level - I have to believe this is not a “design decision” but a “software architecture limitation” and probably wuld require a whole bunch of re-engineering to address.

That doesn’t change the fact that the behaviour is plain WRONG from an end-user standpoint and should be addressed - so long as it doesn’t have an immense impact on software performance.