# Troubleshooting CopyDoc

# Microsoft Word line height exceeding the height of a text layer

If your text layer has a large line height (that exceeds the height of the text layer itself), your text will be pushed down in the Microsoft Word (.docx) export.

# Google Sheets converting "ID" column to numbers

When importing a CSV file into Google Sheets, please ensure you uncheck the Convert text to numbers, dates and formulas checkbox, otherwise your Figma IDs will be modified and messed up, which means they won't be able to be imported properly back into Figma.

# Any Figma layers with a missing font can't be replaced, updated or spell checked

If your Figma text layer contains a missing font (opens new window), the plugin won't be able to update it. Please ensure any text layers you would like to update in any way using the CopyDoc plugin have their missing fonts resolved.

# Error when trying to export Figma comments

If you're using a valid Figma API token in a Figma file that has comments, but you're seeing an error message saying that the token is invalid, you ISP is likely blocking the API request to fetch Figma comments; so you will likely need to use a VPN (opens new window) to resolve the issue.

# DOCX file exports aren't optimised for Google Docs

If you're exporting your Figma designs to .docx, please open them in Microsoft Word, as some features won't be supported in Google Docs.

# Opening CSV files with unicode characters in Microsoft Excel

Microsoft Excel requires you to use the built-in Import Wizard (opens new window) to import the CSV if your text contains unicode characters (for example, if your content is in Polish or Russian or has certain accented characters). Please note that other spreadsheet software like Apple Keynote and Google Sheets doesn't require you to do this, and you can open the CSV file normally in those apps.

To do this in Microsoft Excel, you can create a brand new Excel file, click on the Data tab in the Excel header, select the From Text button, browse for the exported .csv that CopyDoc exported, then select UTF-8 as the file origin; then confirm to import the file into Excel as expected.

To save the edited file, selecting the CSV UTF-8 (Comma-delimited) (*.csv) option should preserve the unicode characters (instead of swapping them out as question marks with a normal CSV file).

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

# Pixelated image exports

If you're exporting design references or exporting a PDF/DOCX 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 re-exporting with the CopyDoc 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.

# VPN may be required in China

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