Skip to main content
Question

Critical typing/input bug on Windows (affecting 30+ users, unusable for teaching) Hi,

  • May 2, 2026
  • 9 replies
  • 91 views

Witold Wójcik

Hi,

I want to report a critical issue with typing/input in Figma and FigJam on Windows.

Problem:

  • Typing becomes extremely laggy or completely unusable
  • Characters are skipped or input behaves unpredictably
  • Sometimes typing only works correctly when holding Ctrl
  • Scroll/zoom behavior also becomes inconsistent

Important observations:

  • The issue starts after a short time of working (initially typing works fine)
  • Affects both Figma desktop app and browsers (Chrome, Edge)
  • Occurs across multiple accounts and different machines

Scope:

  • This issue affects over 30 of my students
  • It is not limited to a single setup or device
  • Makes it impossible to conduct classes

Additional detail:

  • Users on iPads do NOT experience this issue at all
  • Other applications (e.g. OneNote) work perfectly fine on the same devices
  • Resetting Windows and reinstalling Figma did NOT fix the issue

This strongly suggests a bug related to keyboard/input handling on Windows (Chromium/Electron environment).

Has anyone else experienced this?

This is currently blocking real teaching work, so any confirmation or workaround would be greatly appreciated.

9 replies

Witold Wójcik

Below is a short video showing the issue.

At the beginning, typing works normally. After a short time, input becomes unstable — characters are skipped, delayed, or not registered at all.

You can also notice inconsistent behavior where typing sometimes only works correctly when holding the Ctrl key.

This happens consistently across multiple users and devices.


KlaudiaB
  • New Member
  • May 2, 2026

I’m having the exact same issue with Figma freezing — it’s really frustrating, especially during work. Hope this gets fixed soon!


Tom Reem
Figmate
  • Figmate
  • May 2, 2026

Hi ​@Witold Wójcik and ​@KlaudiaB, thanks for flagging this, and for sharing the video. That's really helpful for the investigation.

  • @Witold Wójcik — I checked in on your case and our Technical Quality team is actively looking into it. They'll follow up with you directly as soon as there's an update. Your ticket number is: 1876460. Please keep an eye on your inbox.
  • @KlaudiaB — I've opened a case on your behalf as well. Your case number is: 1881032. Please check your inbox for an email from me with next steps, and grant view access to support-share@figma.com on the file where this is happening so the team can take a closer look.

Thanks to both of you for your patience as we work through this.


Witold Wójcik

Hi ​@Witold Wójcik and ​@KlaudiaB, thanks for flagging this, and for sharing the video. That's really helpful for the investigation.

  • @Witold Wójcik — I checked in on your case and our Technical Quality team is actively looking into it. They'll follow up with you directly as soon as there's an update. Your ticket number is: 1876460. Please keep an eye on your inbox.
  • @KlaudiaB — I've opened a case on your behalf as well. Your case number is: 1881032. Please check your inbox for an email from me with next steps, and grant view access to support-share@figma.com on the file where this is happening so the team can take a closer look.

Thanks to both of you for your patience as we work through this.

Hi, thank you for your help and for escalating this issue.

I really appreciate your support. I’ve granted access to the file as requested and I’ll wait for further instructions.

Please let me know if you need anything else from my side.


antek
  • New Member
  • May 3, 2026

I have the same issue as people above and it slows down my work a lot.


Wojciech Wrzeszcz

I have the same problem, please fix it.


Tom Reem
Figmate
  • Figmate
  • May 4, 2026

Thanks for keeping us updated, everyone. I checked in with our Technical Quality team and have a few updates as they continue to investigate.

  • @Witold Wójcik — a team member reached out with next steps. Please check your inbox for their message on case: 1881032.

@antek and ​@Wojciech Wrzeszcz, thanks for adding your reports here as well. Can you confirm if you’re using FigJam on a Windows operating system, too? In addition, please let me know if this happens on the browser or Figma Desktop App version. To keep things moving forward, I've opened cases for each of you and sent an email with next steps on sharing file access securely. Please check the inbox tied to your Figma accounts:

  • @antek — case: 1883527
  • @Wojciech Wrzeszcz — case: 1883539

Again, appreciate you reporting this and for your patience as we investigate. We'll follow up as things progress.


Igor Ruta
  • New Member
  • May 5, 2026

I also have same problem, I would appreciate it if you fixed it.


Celyn_L
Figmate
  • Figmate
  • May 6, 2026

Hey ​@Igor Ruta, thanks for reaching out here. I work closely with Tom and I’m happy to help. 

As a general guideline, importing large amounts of text, images, or complex vectors with many points (Draw) can impact the performance of the file. You may need to reduce the number or quality of assets you import, or reduce the size of the files you're importing. A few things you can try:

  • Break large files into smaller ones
  • Compress high-resolution images before importing
  • Import complex SVGs in smaller sections

This article might also be helpful: Reduce memory usage in files

In the meantime, I’ve gone ahead and created a support ticket for you so the team can take a closer look if the issue persists - your ticket number is #1886929.

If you’re still seeing the issue after trying the steps above, it would really help if you could reply to the ticket with:

  • A full-window screen recording showing the steps leading up to the issue, if possible
  • A link to your file with view access granted to support-share@figma.com (this won’t count toward your billing)

Let us know how it goes!