Related Videos

• 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
• Troubleshoot Files not opening

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

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

  • Are you experiencing this on both the Figma Desktop app and Figma browser app?
  • Does the problem persist in Incognito or Private browsing?
  • Do you have a reliable internet connection?
  • Are you experiencing this issue with a single file, or with all files.

  Note: 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 usually display an error message. Depending on the size of the File you may not be able to even load it.

  Learn more about how to manage memory in our Troubleshoot Memory Issues article.

  File opens a 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:

  • Make sure you're logged in to Figma under the correct email address.
  • Make sure you have accepted the invitation to view or edit the File under the correct email address.
  • Check your Deleted Files to see if you can locate the File there. Learn more about viewing deleted files in our Delete a File article.
  • 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 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.

• Troubleshoot memory issues

  If you are working with large files in Figma, then you may run into some issues with memory.

  There is currently an active memory limit of 2GB on files. This is a technical limitation with browsers. Figma serves both the web app and desktop app via a browser.

  When your file reaches the active memory limit we will display an error message on screen.

  Restore a Previous Version

  In some rare circumstances, you may no longer be able to view, edit, or delete the file once your file size reaches this limit. If this happens, you will need to restore a previous version of the file before you can continue.

  Note: Any changes you have made to the file between the last version and the restored version will no longer be available.

  As the Error message indicated, you won't be able to access the normal version history view, as the file cannot be opened.

  Instead, you can recover your previous work via a hidden menu option in the file Browser.

  1. Navigate to the file Browser.
  2. Access the hidden Version History menu item using these shortcuts when clicking on the tile for the affected file: 
     • macOS: Option Shift and right-click
     • Windows: Alt + Shift and right-click
  3. Select Restore from version from the options:
  4. You will then be able to select which version you wish to restore. Click Restore to open the required version:
     
     
     

  If you are unable to view the last version of a file, then you may need to go back further. If you're having trouble accessing previous versions, please reach out to the Support Team. Click the " ?" in the bottom-right corner and select "Get Help". Or, send us an email on support@figma.com.

   

  Managing memory usage

  There are a number of factors that contribute to memory usage.

  Hidden Layers

  The most common reason for running out of memory in Figma is using multiple Instances of a Component within hidden layers. If a Component has a large number of hidden layers, a Figma file can potentially have millions of objects associated with it. This increases the risk of running out of memory.

  We recommend that you avoid using hidden layers to represent different states. Instead, create separate Components for each state and switch between them.

  

  Check out our Using Instances and Components article for more information. Or, watch the Figma Tutorial: Components Playlist (see below).

  Files with multiple pages or images

  If you have a large file with a significant number of pages, or lots of high resolution images included, your active memory will be affected.

  We recommend splitting up large files into smaller files. This can be done by copying and pasting the content of individual pages into a new Figma file.

  Importing Large Assets

  If you have imported a large text, image or vector based file into a Figma file, then this will also affect your memory usage. You may need to reduce the number of quality of assets you import. Alternatively, you may wish to:

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

  Check out our Importing files to Figma article for more information on importing files.