Your secure links and images will automatically be removed after a 180 day period of inactivity (180 days after the link was last accessed and viewed) to ensure they are not accidentally laying around after they’ve served their purpose.
Your static design images are securely stored as images in Google Cloud, with the same encryption used by many of Google’s production services, including Gmail and Google’s own corporate data. Please note, this doesn’t apply to the “Figma Prototype” option, which is an embed hosted by Figma.
Due to it being a fairly sensitive feature, instead of adding a button/icon to click, we’ve made this feature activate only by entering the “Konami Code” on your keyboard while the plugin is running:
Up, Up, Down, Down, Left, Right, Left, Right, B, A
Typing that sequence of keys on your keyboard will trigger the Crypto plugin to create a brand new URL/password for your Figma file, so you could enter it in a duplicated Figma file to give it a different brand new URL/password than the original one.
There’s a known issue with the Figma desktop app (only on Windows), which also happens for normal file exports from Figma. When you go to save your file, you may see an “all files” label. If you ignore this and continue by clicking “Save”, it should still save the file with the correct extension and allow you to open it as expected after it has downloaded to your computer. If it still saves the file with a blank extension, you should be able to rename the file to manually append the correct extension to the file name.
If you’re uploading your images or exporting a PDF while the image assets in Figma are still progressively loading, they may be exported looking pixelated, as the image wasn’t fully loaded in the Figma file before it was exported. To resolve this, please ensure that all of the images have loaded 100% and are looking sharp inside the Figma file before uploading your images or exporting PDFs with the Crypto plugin. To help further with solving this issue, you can use the “Downsizer” feature to shrink down your image fills to match their layer size, which will shrink their file size and ensure they load much faster in your Figma file.
Occassionally some images will contain a faint, thin white line around the edges. Figma does this if a layer isn’t positioned on a rounded pixel value (eg. Y: 156.76 or X: 56.3) will automatically result in this sub-pixel line getting included in the export. To resolve the issue, please ensure that your layer positions are all rounded pixel values.
One reason this might be happening is if your ISP (internet service provider) is blocking the QUIC protocol. You can confirm this by opening up your developer console in the browser or in Figma and see the error message
ERR_QUIC_PROTOCOL_ERROR. There are a couple of workarounds for this issue:
- Switching to your mobile phone’s Wi-Fi hotspot/tether for your computer’s internet connection
- Disabling QUIC in your browser
If your PDF exports are going really slow, it’s likely due to having high-res/large image fills in some of the content, which causes Figma to take a much longer time generating PDFs. To help with this issue, you can use the “Downsizer” feature in TinyImage to shrink down your image fills to match their layer size, which will shrink their file size and ensure they load much faster in your Figma file. Once you’ve finished downsizing the image fills in your Figma page, re-running Crypto and exporting your PDF again via the plugin should be much faster.
Please note, if you’re in China, the accounts server may be blocked by “The Great Firewall of China”. If you’re seeing an activation error, despite using a valid key, you will likely need to use a VPN to resolve the issue.