CopySync troubleshooting

Read the import preview before you apply; it names every row that will be skipped and why.

"No changes found in the file"

Every row's text matches the layer's current text, or the ids do not match. Check that you edited the text column (or chose the right Apply column), and that the file was exported from this page: ids are per file, so a CSV from a copy of the file will not match.

Ids not found

The layer was deleted, moved to another page, or detached in a way that changed its id. Re-extract and merge your edits into the new file.

"Importing more than 20 changed rows per run needs Pro"

The free tier applies up to 20 changed rows per import. Split the file, or activate Pro for unlimited imports.

Rows skipped for missing fonts

Figma cannot write into a layer whose font is not available. Install the font, or select those layers and swap the font in Figma, then import again. The preview shows exactly which layers are affected before anything happens.

Bold, links or mixed styles were lost

Without Pro, or when the new text shares no beginning or end with the old text, the whole string is replaced and the layer's base style applies. With Pro, partial edits keep the surrounding styles. For a complete rewrite of a mixed-style layer, re-apply the styling in Figma afterwards.

Accents or emoji came back broken

The CSV is UTF-8. Excel sometimes saves CSV in a legacy encoding; choose "CSV UTF-8" when saving, or use Google Sheets, or paste the rows directly into the plugin. Leading zeros and long numbers are safe because ids are read as text.

Component instance text did not change

Text inside an instance can be overridden, but if the instance's text property is bound to the main component the override may not stick. Edit the main component's text instead, or tick Exclude component instances at extract time so those rows never appear.