# Troubleshooting TinyImage

# Layers must have export settings to be compressed

TinyImage works by detecting the export settings/formats you've set on any layers in your Figma page and allows you to export them as compressed images using the TinyImage plugin.

For more details about the fundementals of Figma export settings and how they work, please see the official Figma guide to exports in Figma (opens new window).

Please ensure you've added export settings (by clicking Export + in the right hand Figma column) to any layers you would like to compress, otherwise they won't show up when you open TinyImage, just like the standard Figma exports work.

# PNGs and PDFs take longer to compress

Compressing PNG and PDF exports can take a bit longer than JPG and SVG exports, especially if they're very detailed or have large dimensions. TinyImage will warn you if an image is too large to compress.

# GIF transparency

The GIF format doesn't support alpha transparency. This means that pixels either need to be completely transparent or not; any pixel with lower than 50% opacity will be transparent, while any pixel with opacity greater than 50% will be opaque.

# Images exported 1px bigger/smaller than their size in Figma

There's a strange bug in Figma related to using "sub-pixels" in your frames/image properties, which can cause your exported images to be "rounded" up or down to a different size. The solution to this is to ensure that the frame or parent frame (artboard) that you're exporting doesn't contain any sub-pixel values (eg. 1000.08) by removing them from the property (eg. 1000). This should export the image in the dimensions you expected.

For more details, there's a thread on the Figma forums (opens new window) discussing the issue.

# 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.

# Safari isn't supported

Due to browser compatibility issues, TinyImage isn't supported in Safari. Please run the plugin in another browser (like Chrome (opens new window)) or the Figma Desktop App (opens new window) instead.

# Thin white line around image exports

Occassionally some images will contain a faint, thin white line around the edges. Figma does this (opens new window) 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.

# Pixelated image exports

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

To help further with solving this issue, you can use the "Downsizer" feature (opens new window) 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.

# Tiled images not rendering in PDF exports

There's currently a bug where some "Tile" image fills won't be included in compressed PDFs; the work around is currently changing the fill in Figma to either "Fit" or "Fill".

# VPN may be required in China

Please note, if you're in China, the license server may be blocked by "The Great Firewall of China". If you're seeing a license error, despite using a valid key, you will likely need to use a VPN (opens new window) to resolve the issue.