📂

Import content from file

Frontitude lets you import product content from the code, localization tools, or other external sources, straight into your copy library. Using this feature, you can upload your UX content to Frontitude and store it in a single source of truth.

Supported file types

The import feature currently supports the following file formats:

CSV

Supported CSV filed for import should contain the following columns:

  • Unique key - The copy component's unique key
  • Value - Text's actual source-language text value
  • Value (<locale>) - A separate column for each configured target language, including the locale identifier (LCID). Only those languages defined in your workspace as target languages will be considered
  • Name (Optional) - A display name for the copy component
  • Status (Optional) - The component's workflow status. Supported values: New, Draft, Review, Final
  • Copy guidelines (Optional) - Notes or instructions for writers and translators (also accepted as Notes)
  • Tags (Optional) - A comma-separated list of tag labels associated with the text value
💡 Tip: The best way to import copy components from a CSV file is to first export your library to a CSV file, then use this file for the import process.
💡 Important: Only those languages defined in your workspace as target languages will be considered

Download a sample CSV file to learn about the supported format.

JSON - Flat

JSON - Nested

💡 In nested JSON structure, all non-leaf keys (keys that point to an object and not a string) will be converted into categories, to make the import better organized.

How to import content from file

Once you have a file that includes content, either generated by developers from the codebase or exported from Frontitude or other tools, you can import it to the library by following the next steps:

  1. Open you Copy Library.
  2. On the top of the screen, click on the Options menu (three dots), and choose Import from file.
  3. You can either click on browse or simply drag and drop a supported file into the droppable area.
  4. Once the file is processed, the number of valid entries detected will be displayed.
  5. Check the Override values of existing copy components checkbox to update existing components with the imported content. Keeping it off ensures that existing component will remain unchanged.
  6. (Optional) Check Assign tags to imported components to open the tag picker. Select existing tags or create new ones — all imported components will be tagged with your selection once you click Done.
  7. Click Import to start the import process. Once finished, you'll see the number of components created and updated. Notice that this process can take a while for large files.
  8. Click Done. If you assigned tags, the library view will automatically filter to show only the newly imported components, making it easy to review, edit, or roll back your import.
  9. The imported copy will be stored as "Uncategorized" and wait for you to be categorized.
  10. Follow this guide to learn how to build and maintain an organized copy library.

Assigning tags during import

Tags make it easy to group, filter, and manage imported components together. By assigning tags at import time, you can:

  • Review your import in one click — after clicking Done, the library automatically filters to show only the tagged components.
  • Organize content by batch — use a tag like "March import" or a sprint name to track exactly which components came from a specific file.
  • Roll back safely — filter by the import tag and bulk-delete if something went wrong.

💡 You can select existing workspace tags or type a new name to create a tag on the spot. New tags are immediately added to your workspace and available across all projects.

Import translations from a CSV file

To import or update translations from a CSV file, ensure the following:

  • Your CSV file has separate column for every language, named in the following format: Value (<Language Name> - <Locale>).
    • Example: Value (Portuguese - pt_BR), Value (French - fr_CA), Value (Polish- pl)
  • The languages included in the CSV file are configured as target languages in your Frontitude workspace.
  • The Override values of existing copy components flag is checked.

Import translations from a JSON file

Copy library import supports files in flat format only. If the file is exported from Frontitude, make sure that you have unchecked the Include metadata option.
  1. Open you Copy Library.
  2. On the top of the screen, next to Add components click on the Options menu (three dots), and choose Import from file.
  3. You can either click on browse or simply drag and drop and JSON file into the droppable area.
  4. Once the file upload has been completed, Frontitude will notify the number of valid entries that have been detected in the file.
  5. Click Import to start the import process. Once it's finished, you'll get the number of translations created. Notice that this process can take a while for large files.

💡 Translations are created only for existing copy components. If no component found for a key, the translation will be skipped.

Next steps

Once you're done importing your content as copy components, you can invite other members of your team, manage all your UX content in one place, sync the it with the design and code, and localize it with Frontitude.

Copied!
🍪