Not able to move 10 pixels while measuring

Hi ​@Mathijs Hooykaas,

I understand that you’re experiencing an issue when measuring distances, which makes it difficult to move objects by 10 pixels.

I tested this on my Mac, both in the Desktop app and in Chrome, and here’s what I observed:

1. Select a frame.

2. Hold the Option key.

3. Moving the selected frame while holding Option duplicates the selected frame (A) and displays the distances between the original frame and the duplicated one (B).

It seems that behavior (A) follows the expected shortcut actions described in the Cursor tab, and behavior (B) follows the functions described in Measure distances between layers

I haven’t found any preference settings that allow you to modify the duplication shortcut or disable the distance measurement behavior so far, so please double-check the shortcuts panel and the guide.

If the issue persists, could you please try the following quick steps to see if there’s any difference?

• Close any unused Figma tabs.

  • Browser: Force-quit and reopen Figma in a new browser window.

  • Desktop app: Force-quit the Figma Desktop app and restart it.

Also, could you please confirm:

• Does this happen only in a supported browser, in the desktop app, or in both?

• Does it occur in a specific file or across all files?

If the issue continues, I recommend submitting a support request through this secure form:Submit a request

To help our team take a closer look, please include:

• A video recording of the issue showing the full Figma screen

• Detailed steps to reproduce the issue

For reference, you can check this guide: Submit a bug report

Thanks,

Check out this, if it can help, 

Use arrow keys for precise movement

• Shift + Arrow keys → Move object by 10px.

• Arrow keys → Move object by 1px.
  You can still press Alt (Option) afterward to quickly check distances — though not simultaneously while dragging.

Hi everyone,

I’m experiencing the same issue as Mathijs Hooykaas mentioned earlier. I used to be able to move objects by 10 pixels in any direction while holding Option (Alt) + Shift and dragging — this allowed me to both measure to nearby objects and nudge/move at the same time.

Now, when I press Option + Shift, the object no longer moves — it only shows measurements to objects that are further away. I can still move objects normally with arrow keys or dragging, but not while using the measure shortcut.

Did something change recently in Figma, or did I accidentally toggle a setting that prevents moving while measuring?

I’d really appreciate any help — I used this shortcut all the time for precise spacing!

Thanks in advance.

Exact same problem! Used to be able to measure + nudge, now shit + alt + arrow swaps the object being measured. Terrible change, whoever made it.

I just now discovered this same problem.

This has to be the worst snap change in a long time.

Why has this changed? We need to be able to see real time measurement updates as we are moving stuff around with the arrow keys; whether that is by 1px using arrow  + option keys or by moving in increments of our large nudge amount using the arrow + shift + option keys.

This should be changed by immediately or at least provide us with options on how we want to use the software.

This is going to slow me down. 
 

F —

Perhaps Shift + Tab would be a better idea if I want to TAB through how my object’s distance relates to others on the page. It matches the way the TAB key usually works. You are TABBING through measurements. 

But when I am moving stuff it is generally in relation to one specific target and I can use the Option key to OPTIONALLY view a tooltip of my progress as I go.

Make Shift + Tab for tabbing distance relationships across the page or frame and keep Shift + Option the way it has been since FOREVER!

Hi! I noticed the same issue today. I use Shift + Opt + Arrow all the time, but it suddenly stopped working. I don’t think I changed anything in my cloud settings. I checked another Figma profile I use for other projects, and everything works correctly there.

Since the issue appears on two different computers, it seems to be related to my account or cloud settings. Any ideas?

Hey All, thanks for reaching out and flagging this! 

Our engineering team identified the root cause of this issue and has rolled out a fix. 

Let us know if you run into any further issues.

SO glad this was fixed!