Documentation Index

For the complete documentation index, see llms.txt. Markdown versions of docs pages are available through the page's alternate Markdown link.

Current page: Troubleshooting HyperCrop - Troubleshooting guide for HyperCrop covering export settings, image issues, and common errors.. Machine-readable page: /hypercrop/faq/troubleshooting.md.

Troubleshooting HyperCrop

Troubleshooting guide for HyperCrop covering export settings, image issues, and common errors.

You can't add duplicate custom crop sizes ​

If you try to add a custom size to your available crop sizes list that you've already added before, HyperCrop will pop-up a notification to let you know that you've already added that size before.

Images must have export settings to appear in HyperCrop ​

To make your images/layers from Figma show up in HyperCrop, please ensure that you've added at least one export setting to the layer by clicking the + icon in the right-hand side column of Figma, under the Export heading.

Blank file extensions using Figma desktop app on Windows ​

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.

Thin white line around image exports ​

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 (for example, 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.

Pixelated image exports ​

If you're exporting images 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 exporting your images with the HyperCrop plugin.

To help further with solving this issue, you can use the "Downsizer" feature in our TinyImage Figma plugin 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.

VPN may be required in China ​

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.

'An error occurred while loading the plugin environment' ​

This may happen in the Figma desktop app if the Use Developer VM debug setting in Figma is enabled by mistake; you can make sure it's turned off by right-clicking anywhere on your Figma canvas, hovering over Plugins, then hovering over Development, and making sure that the Use Developer VM is unchecked; after it is unchecked (and does not have a tick icon next to it), re-running the Figma plugin should work as expected.