Related Videos

• Active file limits

  Figma design and FigJam files are designed for sharing and collaboration. Whether you're giving a talk or presentation, running a class or tutorial, or brainstorming with your team.

  In this article, we'll explore some of the current limitations when collaborating with large groups in FigJam and Figma design files.

  • Figma design files: currently support up to 500 active participants. This includes up to 100 editors at any one time.
  • FigJam files: currently support up to 50 active participants at a time. This includes both viewers and editors.

  Editors and viewers

  Before we jump into these limitations, we want to clarify what we mean when we say editor and viewer.

  A viewer is someone who can only view or comment on a file or prototype. Viewers can explore files and pages, select layers and inspect properties, view prototypes, observe other collaborators, and add comments, emotes, or cursor chats.

  An editor is someone who can edit or modify files and their contents. They can do everything that viewers can do, as well as make changes to any layers or objects and their properties and position.

  You can join a file as an editor if:

  • Link sharing is set to can edit
  • You have can edit access to the team or project where the file lives
  • You were invited to the file with can edit permissions
  • You have an editor role on Figma design or FigJam (Professional and Organization only)

  Roles and permissions in teams →

  File limits

  There are three limits when working in files in multiplayer: total number of cursors, editors, and total participants. These limits mostly apply to Figma design files, but you'll see the maximum participants limits in FigJam too.

  When the file reaches any of those limits, Figma will adjust the multiplayer experience to improve performance and maintain collaboration.

  Note: We're actively working on increasing these limits! Please let us know if you reach these limits during your multiplayer sessions. If you can, include the context and impact this had on your work.

  Cursors

  • Applies to Figma design files

  To improve performance, Figma will only show up to 100 multiplayer cursors to other users in a file at any one time (you'll always be able to see your own cursor). Figma will prioritize the cursors of any editors over viewers.

  Figma will always show the cursors of anyone being observed by other participants. These cursors won’t contribute to the 100 cursor limit.

  If you join any time after this limit is reached, Figma will notify you that your cursor is hidden to other participants. You’ll still be able to see your own cursor in the file.

  

  Tip! If people observe you in a file, your cursor will be shown to everyone whether you're a viewer or editor.

  Editors

  • Applies to Figma design files

  Anyone that joins a file as an editor is included in the editor count. Once the editor limit is reached in a file, anyone who joins the file will be given view-only access.

  If you join after this limit is reached, Figma will show an alert to confirm you’ve been converted to view-only access. Click Done to dismiss the window.

  If you have edit access to the file, this limitation only applies to the current multiplayer session. You'll be able to edit again once existing editors leave the file.

  

  Viewers can still take the following actions:

  • Follow someone using observation mode
  • View prototypes in presentation view
  • Add or reply to comments on files or prototypes
  • Add emotes to the board in FigJam files
  • Use cursor chat in FigJam files

  Participants

  • Applies to both Figma design and FigJam files

  Once the file reaches the maximum number of participants, anyone that joins the file will only get access to a static version of the file. It won't be possible to view any multiplayer actions, including other participants' cursors or any changes being made to the file.

  If you join the file after this limit is reached, Figma will let you know that you have view-only access and any multiplayer cursors are hidden. Click Open view-only to open the view-only version of the file.

  When participants start leaving the file, you can try refreshing the page to get access to it.

  

• Scheduled maintenance

  Figma performs occasional updates that require a restart of our platform and any related services. During scheduled maintenance, you will not be able to load Files in Figma.com or the Figma Desktop App.

  Tip! Visit status.figma.com to view service status in real time and confirm when scheduled maintenance is complete.

  What to expect

  Scheduled maintenance can take anywhere from 30 to 60 minutes. During this time, you won't be able to access Files via Figma.com or the Figma Desktop App.

  Performing maintenance on Figma’s software and platform means our services have to be restarted. The exact reason can vary, but in general, scheduled maintenance is required to perform software upgrades on our end to make Figma more reliable in the future.

  • If you try visiting Figma.com, we'll show you an alert letting you know Figma is currently unavailable.
  • If you are in the File Browser, you can browse your teams and Files, but won't be able to open any Files.
  • If you have a file open in the Editor, we will display a red banner to alert you to the ongoing maintenance. We will remove this once maintenance is complete and Figma is back online.
  • If you refresh a Figma tab, you will no longer be able to access that file or resource and any unsaved changes will be lost.

  

  What to do

  Caution Figma will not automatically save changes you make to a file during scheduled maintenance.

  To let you know your changes have not been saved, Figma will show a white dot next to the File name.

  We recommend you avoid making changes to files until maintenance is complete, especially if you are using the Figma Desktop app. If you have a file open, it will be possible to continue making edits, but these changes won’t be saved.

  To allow Figma to automatically save your changes when service is restored, we recommend you:

  • Keep any file tabs open in the browser
  • Avoid closing your computer or letting it go to sleep
  • Avoid making changes to the file itself like moving its location or renaming it
  • Save a copy of the file locally in .fig format after making any changes

  Save changes to a file

  From the top-left menu, select File > Save a local copy to download the latest version of your file as a .fig. You can only open .fig files in Figma. Or, use the keyboard shortcut:

  macOS: Shift Command S
  Windows: Shift Control S

  Once maintenance is complete, Figma will remove the red banner and the white dot next to the file name. At this point, any work in the Editor will automatically sync.

  Caution: Any changes involving metadata, like renaming or moving a file, will not automatically save. We recommend making these changes once Figma is back online.

• Files not opening

  There are a number of factors that may cause issues with loading files. If you're unable to open or load files there are a few things we recommend.

  Note: Every browser has its own active memory limit. This can differ across devices but the general understanding is there's an active memory limit of 2GB across all tabs for a browser. 

  If you're working with large files and libraries in Figma you may run into these limits. To continue to use affected files, you will need to reduce your memory usage. Learn how to reduce memory usage →

  404 page

  If you open a file link and land on a 404 page, there are two common explanations:

  • You no longer have access to the file
  • The file has been deleted

  We recommend the following:

  • Confirm you're logged in on the correct account
  • Confirm you've accepted the invitation to view or edit the file under the correct account
  • Check your deleted files to see if you can locate the file there
  • Reach out to the file owner to see if they have removed your access

  Restart Figma

  Here are some quicks actions you can take to improve performance:

  • Close any Figma tabs not being used.
  • Browser: Force-quit and open Figma in a new browser window.
  • Desktop App: Force-quit the Figma Desktop app and restart it.

  Check the Console Log

  The Developer Console Log gives us access to a list of actions the browser has performed. If there are any error messages that appear during the process, they will show in red here.

  

  Open the Developer Tools using the Keyboard shortcut. This works in both the Figma Desktop App and Figma Web App.

  • Mac: Command Option I
  • Windows: Ctrl Shift I

  If there are any errors there, we'll need to see a copy of the Console Log. Learn more about exporting the Console log in our [Use Chrome Developer Tools](You can open the Developer Tools using the Keyboard shortcut. This works in both the Figma Desktop and Figma Web apps. Mac: Command Option I Windows: Ctrl Shift I You can also open by Console log by heading to Help in the menu bar and selecting Toggle Developer Tools:) article.

  Tip! Check out our Technical Troubleshooting Tips for other things to try to improve performance.

  Share files with Figma Support

  As part of the troubleshooting process, we may need to access the affected File.

  If you are comfortable with sharing the File temporarily, you can update your link sharing settings. This will allow members of the Figma support team to see what's happening.

  To help diagnose the issue, we may ask you the following:

  • Does this happen on both the Figma desktop app and Figma browser app?
  • Does the problem persist in an incognito or private browsing tab?
  • Do you have a reliable internet connection?
  • Are you experiencing this issue with a single file all files?

  To update link sharing:

  1. Open Figma in the File Browser.
  2. Right-click on the File and select Share from the options.
  3. Update the link sharing settings to Anyone with the link.
  4. Update the permissions to can view.
  5. Click Copy link to copy the File URL to your clipboard.

  

  Note: If you would prefer not to share your File publicly, you can temporarily invite a member of the Figma support team to the File. They will give you specific instructions for how to do this when you contact them.

• Image loading issues

  This article covers some of the most common image-related issues experienced in Figma and how to fix them.

  Image resolution

  There can sometimes be a delay in loading your images in the Editor, or within your Prototypes.

  This can happen in files with a large number of high-resolution assets. Or when you're loading a large file with many assets for the first time.

  To improve loading performance, Figma stores images at different resolutions. If you're seeing a low-resolution version of an Image, don't worry! The high-resolution versions of your image are still available and are loaded where appropriate.

  We recommend trying the following:

  • Close any open Figma files you aren't currently using
  • Close the affected file and reopen it in the Editor
  • In the browser: quit your browser and relaunch it
  • In the Desktop app: right-click on the File tab and select Reload tab
  • Check your internet speed and connection to make sure your device is online

  Image rotation

  EXIF data (Exchangeable Image File Format) provides information on an image's characteristics such as orientation, size, device used to create the image, date, and more.

  

  Before mid-2020, internet browsers didn't always check the orientation value in an image's EXIF data, including those taken on a mobile device. When this happened, Figma would automatically rotate images according to the EXIF data.

  Now that most internet browsers check an image's EXIF data, images that were previously manually rotated in Figma may need to be corrected once more to account for this change in your browser's behavior.

  Note: You only need to correct image rotation once if you encounter this issue. Going forward, your browser will set image orientation correctly using an image's EXIF data.

  You may also need to manually rotate an image if the thumbnail image appears incorrectly rotated while zooming, loading, or panning around a file.

  Scenario

  1. You imported an image to a file in Figma.
  2. Your internet browser ignored the image's EXIF data, so Figma automatically corrected the image's orientation for you.
  3. In mid-2020, you updated your browser to a version with new EXIF data handling.
  4. Your images are rotated twice—once by the browser, then again by Figma, resulting in a wrong orientation.
  5. Before October 2020, you manually rotated the image to the correct orientation.
  6. In October 2020, Figma released an update to account for the new behavior by newer versions of internet browsers. Your image appears incorrectly rotated again.
  7. Any images manually rotated by you between mid-2020 and October 2020 may need to be corrected once more. You'll only have to do this once. All other images that appear correctly do not need to be rotated.

  Learn how to rotate images →

  Prototype images

  An issue with images not loading in a prototype is usually caused if:

  • Your device is experiencing a poor internet connection or is offline. Confirm your device has a reliable internet connection.
  • You have browser extensions, such as ad blockers, preventing images from appearing in Presentation view. Try disabling browser extensions or learn how to add figma.com to the allow list by referencing the extension's documentation.

  

  Extensions known to block images in Presentation view as of August 2020:

  • Ghostery
  • Video Downloader PLUS
  • iDM Integration Extension
  • Honey
• Reduce memory usage in files

  Every browser has its own active memory limit. This can differ across devices but the general understanding is there's an active memory limit of 2GB across all tabs for a browser.

  As Figma serves both the web app and the desktop app via a browser, these limitations apply when using the Figma desktop app too.

  If you're working with large files and libraries in Figma you may run into these limits. To continue to use affected files, you will need to reduce your memory usage.

  In this article, we'll outline some of the ways you can adapt your files so they work within these limitations.

  Memory usage alerts

  Figma measures your memory usage as a percentage, which means you might see different values across platforms or devices.

  To keep you informed of your memory usage, and any potential issues that may arise, Figma displays banners and alerts at certain thresholds:

  

  • A

    60% usage

    When you reach 60% of the browser's memory limit Figma will show a yellow warning banner, you can't dismiss this banner.

    This file is almost out of browser memory. Remove content to lower memory use to 50% or less. This will ensure you can continue to work in this file safely.

    Figma will offer you suggestions for reducing your memory usage. Click Show memory-reduction tips to view suggestions for reducing memory.

    At this point, you may experience performance issues—like lagging in multiplayer—when interacting with the file.

  • B

    75% usage

    When you reach 75% of your memory limit, Figma will show a red alert banner, you can't dismiss this banner.

    Adding content is no longer safe as data may be lost. Remove content to reduce this file’s memory use or restore a previous version.

    You can still make changes to the file, but we recommend taking immediate action to protect your work. Failure to reduce memory usage now will increase the possibility of data loss.

    Follow the tips we've outlined below ↓ to reduce your memory usage.

  • C

    100% usage

    If your file reaches 100% of your memory limit, Figma will lock the file and inform you there's no available memory.

    This file has run out of browser memory.

    At this point, closing other Figma tabs and reloading the browser may allow you to open the file. If you're unable to open and load the file, you'll need to restore a previous version of the file that used less memory:

    1. Open the project where the file is located.
    2. Hold down the modifier keys and click on the file in the file browser
       • Mac: ⇧ Shift ⌃ Control ⌥ Option
       • Windows: Alt Shift
    3. Select Restore from version.
    4. Click Restore next to the appropriate version
  • D

    Scheduled maintenance

    If you receive a memory usage alert during scheduled maintenance, Figma will display two banners at the top of the screen. We recommend leaving the file open and trying again once maintenance is complete.

    Figma is undergoing scheduled maintenance for the next 30 minutes. Keep this tab open to ensure your changes are synced once maintenance is over. Learn more.

  • E

    Memory reduced

    Once your memory usage drops below 50%, you'll see a success message in the banner. You can now dismiss the banner.

    You successfully reduced memory and this file is now safe to use. You can close this banner.

  Reduce memory usage

  There are a number of factors that contribute to memory usage. It's not as straightforward as a specific number of layers, data, or resources in the file.

  Note: We're using the term memory very generally here, but the memory usage banners are only triggered by WASM memory (WebAssembly.Memory) usage. Figma uses this memory to render layers and objects on the canvas, as well as deliver the collaborative multiplayer experience.

  Hidden layers

  Hidden layers are a big contributor to memory usage. This is because Figma needs to store and render information about those layers even when they're not visible.

  If you're using hidden layers to switch between different states or variations of a component, we recommend creating variants instead.

  This reduces the number of layers in each instance, while still allowing you to switch between different variants in a component set.

  This is also something to bear in mind for complex components and instances with multiple levels of nesting.

  Note: You'll also need to take into account the size of your component sets. A few component sets with thousands of variants in them will still contribute to memory usage.

  Tip! To delete a layer, select it in the canvas or Layers panel in the left sidebar. Then press the delete or backspace key to remove it.

  Large component or variant libraries

  Caution: At the moment, it isn't possible to move components between files without breaking the connection between the main components and instances in other files.

  If you have a large library of components or variants and are near the memory limit, you may need to divide it into smaller libraries.

  Both the number of components and the number of variants can contribute to memory usage. So you may still run into memory limits if you have only a few component sets, but they have 10000's of variants or properties.

  We realize the limitations around moving components is particularly frustrating when addressing memory issues. This is something we're actively working on. We've outlined one approach for moving components below.

  Note: We recognize this is very involved, especially at scale. In the meantime, third-party plugins like the Master plugin → which requires its own paid subscription, will allow you to do this programmatically.

  1. Copy components from the original file and paste them in the new file. This will create instances of your original component in the new file.
  2. Select all instances and use the Detach instance shortcut to detach them from the original main component.
  3. Select the frames and click the next to the component icon in the toolbar. Choose Create multiple components.
  4. Click the next to the file name in the toolbar and select Publish styles and components from the options. Add a description and click Publish.
  5. Open a file which uses components from your original library. Enable the new library that you just published so its available in the instance menu.
  6. Select an instance in the file and in the menu select Edit > Select all with same instance action. This will select any other instances of that component in your current file.
  7. In the right sidebar, use the Instance menu to select the same instance from the new file. You can change the source file using the file menu next to the search field.
  8. Repeat this for each relevant instance in the file. You'll also need to repeat this process in any other files that used components you moved from the original library.

  Tip! There are lots of different ways you could divide up your library, the best approach is the one that meets the needs of your library's users.

  Learn more about creating and organizing libraries: 📘 Best practices: components, styles, and shared libraries →

  Large files with multiple images and pages

  If you have a large file with a significant number of pages, or lots of high resolution images, you may experience performance or memory issues.

  If this causes browser-level crashes, Figma won't display the memory usage banners. This is something to think about when working in files with a large number of high-resolution images.

  We recommend splitting up large files into smaller files by copying the contents of each page, and pasting it into a new file.

  Tip!The Downsize plugin allows you to compress large images on the canvas.

  Caution: At the moment, it isn't possible to move components between files without breaking the connection between main components and instances in other files.

  If you need to break up a library file into smaller files, follow the instructions above ↑

  1. Create a new file in your Figma account.
  2. In a separate tab, open the original file and view the page you want to move.
  3. Use the Select all shortcut to select everything on the page.
     • Mac: ⌘ Command A
     • Windows: Ctrl + A
  4. Use the Copy shortcut to copy the page's contents to your clipboard.
     • Mac: ⌘ Command C
     • Windows: Ctrl + C
  5. Return to the new file in a separate tab. Use the Paste shortcut to paste the contents of your clipboard:
     • Mac: ⌘ Command P
     • Windows: Ctrl + P

  Large assets

  Importing large amounts of text, images, or complex vectors with many points can also impact your memory usage. You may need to reduce the number or quality of assets you import, or reduce the size of the files you're importing:

  • Break large files into smaller files.
  • Compress high resolution images.
  • Import complex SVGs in smaller parts.

  Learn how to import files into Figma →

  Note: Image decoding uses JS memory, which isn't included in the memory percentage or banner alerts. Images can still contribute to WASM memory as they are rendered on the canvas.

• Technical Troubleshooting Tips

  Something gone wrong? We are here to help!

  As part of the troubleshooting process, we'll need to confirm a few things about your setup. To help you prepare, we've put together a list of all our troubleshooting methods.

  Quick fixes: Here are some actions you can take to improve performance:

  • Close any Figma tabs not being used.
  • Browser: Force-quit and open Figma in a new browser window.
  • Desktop App: Force-quit the Figma Desktop app and restart it.
  • Split up large Files into smaller Files.
  • Toggle Multiplayer cursors, Layout Grids, or Effects off.

  Seeing an out of memory error? Check out our Troubleshoot Memory Issues article for tips on how to reduce file size and improve performance.

  Basic Troubleshooting

  We recommend you check the following things:

  ✅  You have a reliable and stable internet connection

  Figma requires access to a reliable and stable internet connection. Figma does not currently support offline move.

  If your connection is unreliable, or you experience periods of limited bandwidth, your performance will be impacted. Some things you may experience are:

  • Files loading slowly
  • Seeing low-resolution versions of your images
  • Reduced performance when panning and zooming in the Canvas

  We're actively working on improving the Figma experience for low-bandwidth connections. Let us know by reaching out to the Support Team or Submit a bug report.

  ✅  You're running the latest version of your preferred browser

  Figma doesn't support developer or beta versions of browsers. We only support stable release versions of Chrome, Firefox and Safari.

  Learn more in our What Platforms, Devices and Browsers are Supported? article.

  ✅  You have WebGL enabled

  Figma is built using WebGL. You will need to have this enabled to use Figma. You can check if your browser has this installed and enabled, by visiting this website: https://webglreport.com/

  Learn more in our Configure your browser for Figma article.

  ✅  You are running a 64-bit version of Windows

  You must be running the Figma Desktop app in a 64-bit environment. Figma is not supported on machines running a 32-bit environment.

  Learn more in our What Platforms, Devices and Browsers are Supported? article.

  ✅  You have enough available memory

  There is currently an active memory limit of 2GB on Files. If you are working with large Files in Figma, then you may run into some issues with memory. When your File reaches the active memory limit we will display an error message on screen.

  Learn more about managing and improving memory in our Troubleshoot Memory Issues article.

  🚫  You aren't using Figma behind a Firewall or Proxy

  If you're using the Desktop App behind a Firewall, proxy or Virtual Private Network (VPN), you may see the error message: Connection Error (407).

  You have two options:

  • Use Figma in the browser. You can access the Figma web app from any of our supported browsers. Learn more in our What Platforms, Devices and Browsers are Supported? article.
  • Ask your IT department or systems administrator to unblock Port 443. This is the standard port for websites that are run over SSL (Secure Sockets Layer - https).

  Advanced Troubleshooting

  If you're still encountering problems, we may ask you to perform some diagnostic tests.

  We've put together step-by-step instructions that take you through these tests. Follow the links below for more information.

  • Use Chrome Developer Tools
  • Record a Chrome Performance profile
  • View your graphics card specifications

  Submit a bug report

  If you're still experiencing problems, let us know! Check out our Submit a bug report to Figma article for more information on getting help.

• Submit a bug report

  What: Submit a bug report to Figma. The more information you can provide us with, the faster we can troubleshoot the issue.

  Why: This lets us know that there's something unusual happening in your account. We can then troubleshoot this further to find you a solution or explanation.

  If you've come across something that looks like a bug, you can submit a bug report in Figma.

  • 1 Record the bug

    The best way for us to identify the issue is to see it happening. We recommend including a short video that shows both the error and the action(s) you took before encountering it. If you're unable to take a video, please include:

    • A detailed description of the behavior. For example: whenever I import a file from Sketch, I get an error that I have a failed import.
    • Step-by-step instructions on how we can reproduce the issue.
    • A screenshot of the error message, issue, or unexpected outcome.

  • 2 Confirm your setup

    The Figma support team may ask you some additional questions about your setup. This will help us to identify where the issue might be occurring. You can include these in your message to speed up the process:

    • Are you experiencing this in Figma in the browser and in the desktop app?
    • Does the problem persist after restarting your computer?
    • Does the problem persist across different internet connections? Or on different browsers?
    • Is anyone else on your Team experiencing this issue?

  • 3 Share your file

    If this issue is happening in a specific file, the Figma support team may need access to the file to troubleshoot further. You'll be given the option to attach a URL to your Figma file to your bug report.

  Submit a report

  1. Click the question mark icon from anywhere in the Figma app, you can find this in the bottom-right corner of the screen. Select Get help from the options:
  2. You'll need to type something in the field, we recommend bug, then press the Enter key to move to the next step.
  3. Click the Contact us button at the bottom of the window.
  4. Select Bug report from the options and click Next.
  5. Enter your name, email address for your Figma account, and a subject in the fields provided. If you're already logged in, this will be populated for you:
  6. Add some information about the bug you're seeing using the subject and description fields. Please make sure to add any Reproduction steps for the bug you encountered.
  7. Add the Figma File URL of an affected file (if applicable).
  8. Click on Attachments to select and upload screenshots or videos of what you're experiencing. You can add up to 5 files. Click the "X" next to a file to remove it from your report.
  9. Click Send to complete the process. The Figma support team will follow up with you via your email address.

  Note: If you're in the Editor and don't see the help icon, you may have disabled Figma's Help UI. Open the menu andsearch for Hide help UI. Click on the setting to toggle it on.

• Use Chrome Developer Tools

  What: Use the Developer Tools to view and capture any errors in the Console log, or problems connecting to the Network.

  Why: The Developer Console Log gives us access to a list of actions the browser has performed. This will highlight any error messages that appeared during the process. The Network tab details any connection issues.

  Open Developer Tools

  Open the Developer Tools using the Keyboard shortcut. This works in both the Figma Desktop and Figma Web apps.

  • Mac:  Command Option I
  • Windows:  Ctrl Shift I

  Or, head to Help in the menu bar and selecting Toggle Developer Tools:

  

  Export Console Log 

  1. From the Developer Tools window, select the Console tab:

  2. Any Console errors will be shown in red. Right-click in the console and choose Save as from the options.

     Note: We recommend saving a copy of the log. This allows us to view the errors in more detail and is preferable to taking a screenshot.
     
     You may see console errors relating to "api-iam.intercom.io". These do not impact performance or indicate an error with Figma. You can safely ignore these.

  3. Attach the File(s) to your conversation with Figma Support.

  Tip! Follow the links below for more information on how to use the Developer Console in your preferred browser:

  • Microsoft Edge
  • Mozilla Firefox
  • Google Chrome
  • Safari

  Export the Network Log

  The Network log will highlight any connection issues. This is useful if you're experiencing issues with loading times, image quality, or importing and exporting assets.

  1. From the Developer Tools window, select the Network tab: 
  2. Perform the action you're experiencing an issue with. This could be importing an image, interacting with an object, or performing a multi-player action.
  3. The Network tab will show details of any interactions between your Figma account and the network.
  4. Click the down arrow ⇩ in the toolbar to Export HAR file: 
  5. Attach the File(s) to your conversation with Figma Support.

  Need to submit a bug report? Check out our Submit a bug report to Figma article for more information.

• Record a Chrome Performance Profile

  When: If you are experiencing performance issues, like slowness and lagging, in the Figma Desktop app.

  What: Use the Chrome Developer tools to record yourself performing the affected actions.

  Why: Recording a Chrome Performance Profile will help us to identify how Figma is performing.

  Record a Performance Profile

  Note: You'll need to complete quit the Figma Desktop app, before you relaunch the app and record a performance profile.

  1. Launch the Figma Desktop app.

  2. Click Help in the menu bar and select Toggle Developer Tools:

     

  3. This will open a Developer Tools window above the Figma app. Select the Performance tab from the options:

     

  4. Click the Record button in the top left corner of the window:

     

  5. A progress dialog will indicate that a profile is being recorded:

     

  6. You can now go back to the Figma app and perform any of the specific actions you're having issues with.

  7. When you're finished, return to the Developer Tools window and click the Stop button to end the profile:

     

  8. The Console will now show you a detailed view of the profile. You can even scroll through the timeline at the top to view a screenshot of each action:

     

  9. Right-click in the console and select Save profile. This will download a copy of the Performance Profile to your computer.

     

  10. You can then attach the saved File to your Figma Support conversation.

  Tip! You can also use the keyboard shortcuts to start and stop the profiling process.

  Mac: Command E Windows:  Ctrl E

  Need to submit a bug report? Check out our Submit a bug report to Figma article for more information.