You may encounter memory limitations if you are dealing with larger files or libraries in Motiff. This article will introduce how to adjust file memory so they work within these limitations.
Tip: The memory referred to in this article is a specific type of memory: WASM memory (WebAssembly Memory). Motiff uses WASM memory to render layers and elements on the canvas and provide a cloud-based collaborative experience.
Each browser has its own memory limit, with most browsers having a memory limit of 2GB per tab.
As Motiff is a design tool built on browser technology, these limitations apply when you are using desktop applications as well.
Motiff measures the current file's memory usage based on the percentage of available memory in the browser or device.
You can check the memory usage of a file by following these steps:
To remind you of the current file's usage and potential risks, Motiff will display banners and warning prompts at specific thresholds.
When the file's memory usage reaches 60%, Motiff will display a yellow warning banner at the top of the editor.
At this point, your operations in the file may encounter performance issues, such as lag in multiplayer scenarios.
When the file's memory usage reaches 75%, Motiff will display a red warning banner at the top of the editor, which cannot be closed.
At this time, you can still edit the file, but Motiff recommends that you take immediate action to protect your file. If you do not reduce memory usage now, there may be a risk of data loss.
When the file's memory usage reaches 100%, Motiff will lock the file and notify you that there is no available memory space.
Users with Can edit permission can try to reload the file, such as closing the tab. Sometimes reloading the file can free up enough memory for you to continue viewing the file.
Note: You may not see all warnings in order. When memory usage increases rapidly in a short time, you may not receive warnings.
Although hidden layers are not visible on the canvas, Motiff needs to store and render this layer information, which causes hidden layers to occupy some memory usage.
You can reduce memory usage by deleting hidden layers.
The number of component sets and variants affects memory usage. For example, if there are only a few component sets in a library, but there are hundreds of variants, you may encounter memory limitations.
You can split a library file that occupies a large amount of memory into multiple files.
Files that contain multiple pages and a large number of high-resolution images can also encounter performance or memory issues.
You can create a new file for related pages in the current file:
Note: Importing multiple texts, images, or vector networks will affect your file's memory usage.
During the import process, you may need to reduce the number of imported layers or lower the resolution of them.