Skip to main content
Question

Sometimes annotations don't get saved but disappear

  • February 6, 2026
  • 8 replies
  • 63 views

e.frommhold

Hi, 
Sometimes annotations don’t get saved but simply disappear.
It often seems to happen in this order: writing annotation - selecting category - enter.
So when clicking enter while the focus is not in the text field of the annotation… 

I started to copy the written text before leaving the annotation, so I don’t have to rewrite everything again, which is very unpleasant- especially in meetings.
 

8 replies

Kyle_Johnson
  • New Participant
  • February 12, 2026

I noticed this issue too, and it causes quite a headache when trying to enter multiple annotations quickly. It does not happen all the time, and I have not been able to figure out the steps to reproduce the issue consistently.

When typing text into an annotation, the expected interaction from pressing [ENTER] would be to save the edits to the current annotation and return you to the annotation tool to be ready to create a new annotation. Instead, when pressing [ENTER] while typing text into an annotation, sometime it closes the annotation and does not save your typed text.


Kogulan
  • New Member
  • March 10, 2026

Pressing [ENTER] should save annotations but they currently disappear. 


djv
Figmate
  • Community Support
  • March 10, 2026

Hi ​@Kogulan, thanks for reaching out! 

I just tested adding a new Annotation in Figma as well as editing an existing Annotation in Figma, and they are both saving successfully when using enter to submit the change. 

What OS are you using? Is this happening in the browser of the desktop app? Is this happening in all files or one file in particular?

Please let me know, so we can continue troubleshooting what may be causing this issue.


Ryan_Parker1

Hello ​@djv ! I’m having the same problem as ​@Kogulan, with a slight difference.

 

The annotation does save when I’m typing in the field and press Enter, BUT if I’m typing in the field, then select a Category from the dropdown, and then press Enter (without clicking out of the “category selected” state) my annotation will disappear. And since this is usually the process my brain does (write annotation then categorize it) I’ve lost *so many* annotations because I forget to click out of the “category selected” state before pressing Enter.

Also, this only happens on brand new annotations. If I do this while editing an existing annotation, (select new category, press Enter) the annotation will stay but revert back to how it was before I started editing (also annoying, but not as bad).


djv
Figmate
  • Community Support
  • May 20, 2026

Hi ​@Ryan_Parker1, thanks for chiming in here! 

I combined the two similar, existing topics in the Community that you commented on to keep things organized and under one topic. Thanks for looping me in and for the additional context. 

I just tested the repro steps you provided and when typing then selecting a Category from the dropdown, the annotation won’t be saved by simply clicking enter, but it will save if I click onto the canvas or continue writing an annotation then clicking enter. Is this the same behavior you’re experiencing? And if so, is this consistent across both the desktop app and the browser? 

With your confirmation, I can flag this over to our team to investigate further. 

 


Ryan_Parker1

@djv This is on the desktop app. I just tried it on the browser, and it does NOT do the same thing. Typing an annotation, then selecting a category, then immediately pressing enter doesn’t cause anything to happen. Pressing Esc will save it, or clicking anywhere on the canvas will save it, but Enter does not.

 

I’d still expect Enter to save the annotation, but on the desktop app it removes the annotation completely and I can’t undo or anything to recover it.


jamuy87
  • New Participant
  • May 21, 2026

Sometimes annotations are not saved properly and disappear unexpectedly. Please look into this issue.


djv
Figmate
  • Community Support
  • May 21, 2026

Thanks for the additional context, ​@Ryan_Parker1

 

And thank you ​@jamuy87 for chiming in here. I’ve created a bug report and passed this onto the team to investigate further. We appreciate your patience and understanding while our team looks into this issue. I’ll be sure to follow up here if/when I receive any updates from the team.