Please note that we only specified a relative address for the image. Since we specified a base URL in the head section, the browser will look for the image at "https://www.w3schools.com/images/stickman.gif".

Text

` | | `content` | translatable if contained in `meta` tag | `` | # Workflow Overview > Learn how to create a workflow template and assign it to projects Workflow is a sequence of steps that content in your project should go through, like translation or proofreading. You can use unlimited workflow steps that can be connected either in parallel or subsequently. You can create a workflow template that works best for you and assign it to several projects. Editing a workflow after it’s assigned to a project won’t affect the original template. Otherwise, you can create a new workflow each time you create a project. ## [Creating a Workflow template](#creating-a-workflow-template) [Section titled “Creating a Workflow template”](#creating-a-workflow-template) To create a Workflow template, follow these steps: 1. Open your organization’s **Workspace > Workflow templates**. 2. At the lower-right corner, click **Create**.  3. Name your Workflow and add a description(optional). 4. Click **Create**. 5. Select workflow steps from the left panel and drag them to the working area. 6. Connect steps in the order in which the content should flow between them. Steps can be connected in parallel or subsequently. 7. (Optional) Add target languages to each step and assign contributors to them. This can be skipped when creating a template, as you might want to add different languages and assignees for different projects. 8. When you’re finished creating your workflow, click **Save**.  Your new template will be available on the Workflow templates page and in the workflow list when creating a project. ## [Workflow Steps](#workflow-steps) [Section titled “Workflow Steps”](#workflow-steps) Here’s a list of the workflow steps that you can use to create a workflow. ### [Source Text Review](#source-text-review) [Section titled “Source Text Review”](#source-text-review) The Source Text Review step is essential if your source texts need to be reviewed before translation. Use this step to ensure consistency in terminology, correct formatting, and accurate grammar. This helps avoid potential issues during translation by detecting and correcting issues early. By ensuring that your source text is clear and consistent, you reduce the risk of errors later in the process, saving time and effort. Read more about [Source Text Review](/enterprise/source-text-review/). ### [Custom Code](#custom-code) [Section titled “Custom Code”](#custom-code) The Custom Code step allows you to apply specific rules to your workflow using JavaScript. This is useful when you need to split strings into different workflow paths based on certain conditions. For example, you can set up custom routes for specific content types or apply unique processing rules that meet your project’s needs. This step adds flexibility and allows you to customize the workflow to handle complex localization tasks. Read more about [Custom Code](/enterprise/custom-code/). ### [Switch Source Language](#switch-source-language) [Section titled “Switch Source Language”](#switch-source-language) The Switch Source Language step allows you to change the source language of your project. This is particularly useful when translating between languages that aren’t commonly paired. By switching to a more widely used intermediary language, you can simplify the translation process and improve the overall quality of the translations. ### [TM Pre-translation](#tm-pre-translation) [Section titled “TM Pre-translation”](#tm-pre-translation) The TM Pre-translation step uses your existing Translation Memory (TM) to pre-translate content into target languages. You can pre-translate strings with a configurable TM match (from 40% to 100%) or a perfect match (101%), giving you control over the translation quality. There’s also an option to enable Auto-Substitution, if you want to get improved suggestions wherever possible. This step is particularly useful when you have a well-developed TM, as it reduces manual translation efforts and increases consistency. ### [MT Pre-translation](#mt-pre-translation) [Section titled “MT Pre-translation”](#mt-pre-translation) The MT Pre-translation step integrates Machine Translation (MT) engines into your workflow. You can connect MT engines like Google Translate and AutoML Translation, Microsoft Translate, and more. After configuring your preferred MT engines, you can select specific engines for the languages you want to pre-translate. This step is useful for quickly handling large volumes of content. By combining MT with human proofreading steps, you can maintain a balance between speed and translation quality. ### [AI Pre-translation](#ai-pre-translation) [Section titled “AI Pre-translation”](#ai-pre-translation) The AI Pre-translation step uses advanced AI models to pre-translate your content. Unlike other pre-translation methods, AI Pre-translation considers context at multiple levels, resulting in improved translation quality. You can integrate AI models from providers like OpenAI, Google Gemini, Microsoft Azure OpenAI, and more. Similar to MT Pre-translation, you can select specific AI prompts for the languages you want to pre-translate. This step reduces manual translation efforts and helps maintain consistency across your project. ### [Translation](#translation) [Section titled “Translation”](#translation) The Translation step involves human translators translating your content into target languages. You can invite in-house translators, freelancers, or agency professionals to your project and assign specific target languages to each. This ensures that translators only access the resources relevant to their assignments. ### [Translation by Vendor](#translation-by-vendor) [Section titled “Translation by Vendor”](#translation-by-vendor) The Translation by Vendor step allows you to outsource translation tasks to professional vendors. Choose a vendor, specify the target languages, and provide any necessary instructions in the comment section that will be sent along with the content. This step is ideal for accessing specialized expertise and scaling your translation efforts efficiently. ### [Translation by API Vendor](#translation-by-api-vendor) [Section titled “Translation by API Vendor”](#translation-by-api-vendor) The Translation by API Vendor step automates translation orders from translation agencies that provide their services via API integration. Add an API vendor to your organization, configure it in your workflow, and specify the target languages. This step allows you to place orders manually or set them to be processed automatically, simplifying and speeding up your translation process. Read more about [Translation by API Vendor](/enterprise/translation-by-api-vendor/). ### [Crowdsourcing](#crowdsourcing) [Section titled “Crowdsourcing”](#crowdsourcing) The Crowdsourcing step engages your community to translate your product into multiple languages on a volunteer basis. Set up Crowdsourcing in your project workflow to configure public settings, branding, and gamification features. You can customize the project name, logo, description, and URL, and offer single sign-on options for easy access. Enable gamification to reward volunteers and use status images to showcase translation progress. Build and manage your community by sharing the project link to attract contributors and encourage participation. Read more about [Crowdsourcing](/enterprise/crowdsourcing/). ### [Proofreading](#proofreading) [Section titled “Proofreading”](#proofreading) The Proofreading step involves reviewing and refining translations to ensure accuracy and quality. You can invite in-house proofreaders, freelancers, or agency professionals to your project and assign specific target languages to each. This ensures that proofreaders only access the content relevant to their assignments. ### [Proofreading by Vendor](#proofreading-by-vendor) [Section titled “Proofreading by Vendor”](#proofreading-by-vendor) The Proofreading by Vendor step allows you to outsource proofreading tasks to professional vendors. Choose a vendor, specify the target languages, and provide any necessary instructions in the comment section that will be sent along with the content. This step is ideal for ensuring high-quality translations and efficiently scaling your proofreading efforts. ### [App-based Workflow Step](#app-based-workflow-step) [Section titled “App-based Workflow Step”](#app-based-workflow-step) By installing apps from the [Crowdin Store](https://store.crowdin.com/), you can introduce custom steps into your workflow. Depending on the app, these steps might provide advanced QA checks, AI-driven proofreading, scheduling or delaying content processing, or other specialized functionalities. This gives you the flexibility to tailor workflows to your team’s exact needs. Read more about [App-based Workflow Step](/enterprise/app-based-workflow-step/). ## [Assigning Workflows to Projects](#assigning-workflows-to-projects) [Section titled “Assigning Workflows to Projects”](#assigning-workflows-to-projects) If you choose a project with a workflow during project creation, you’ll be asked to choose a workflow. To assign an existing workflow template, click on the preferred workflow, and then click **Create Project**. Read more about [Creating a Project with a Workflow](/enterprise/creating-project/#projects-with-a-workflow). # XML File Configuration > Configure XML files to import the content for translation The XML files, similar to CSV and XLSX files, require additional configuration after uploading to the project so the system could import the content of these files. To configure XML files, follow these steps: 1. Open your project and go to **Sources > Files**. 2. Click **Configure** next to the file to open the configuration window. 3. Select which content should be translated and click **Save & Import** to proceed.  [XML translation with Crowdin ](https://store.crowdin.com/xml) Limitations XML files are not supported in [string-based](/enterprise/creating-project/#string-based-project) projects. ## [Configuration Options](#configuration-options) [Section titled “Configuration Options”](#configuration-options) When configuring XML files, you’ll have the following options: **Basic Configuration** and **Advanced Configuration**. Additionally, you can use the **Content Segmentation**, which is available for both configuration options. ### [Basic Configuration](#basic-configuration) [Section titled “Basic Configuration”](#basic-configuration) Basic Configuration allows you to select all nodes and/or all attributes to be available for translation.  ### [Advanced Configuration](#advanced-configuration) [Section titled “Advanced Configuration”](#advanced-configuration) Advanced Configuration allows you to select the specific nodes and specific attributes to be available for translation.  The file structure is depicted with the help of icons: * – Node * – Attribute [XSL Transformer for XML ](https://store.crowdin.com/xslt-preview)Preview your XML file directly in Editor with the XSL Transformer for XML application. ### [Configure All XML Files at the Same Time](#configure-all-xml-files-at-the-same-time) [Section titled “Configure All XML Files at the Same Time”](#configure-all-xml-files-at-the-same-time) To configure all XML files at once, click **Configure All** at the top of the **Files** page. When using **Configure All**, ensure that all XML files contain the same structural elements. Otherwise, some nodes that require translation might be unavailable during configuration and won’t be imported into the project. In this case, it would be necessary to configure each XML file separately. In the configuration window, you’ll be able to switch between the selected files to preview and verify if the applied configuration is correct for all files. ## [Content Segmentation](#content-segmentation) [Section titled “Content Segmentation”](#content-segmentation) You can use **Content Segmentation** to split the source file’s content into shorter text pieces, mostly sentences and short paragraphs. This is helpful when translating content units consisting of several sentences because it will be easier to translate smaller pieces of text. Segmentation Rules eXchange (SRX) are used for automatic content segmentation. Read more about [Custom segmentation](/enterprise/custom-segmentation/). ## [See Also](#see-also) [Section titled “See Also”](#see-also) [Uploading Source Files ](/enterprise/uploading-files/)Learn how to upload source files to your project for translation. [File Management ](/enterprise/file-management/)Manage and configure source files in your project. # Expression Syntax Elements > Learn about the different elements of the expression syntax You can configure verbal expressions and custom placeholders using a shared set of expression syntax elements. These elements define how specific parts of a string should be matched, based on structure, character types, or formatting patterns. ## [Expression Elements](#expression-elements) [Section titled “Expression Elements”](#expression-elements) Use the elements below to configure verbal expressions and custom placeholders. | **Element** | **Aliases** | **Description** | **Usage examples** | | -------------- | ------------------------------ | --------------------------------------------------------------------------------------------------- | -------------------- | | `start` | `startofline`, `start of line` | mark expression with ^ | | | `end` | `end of`, `endofline` | mark the expression with $ | | | `then` | `find` | add a string to the expression | `then "abc"` | | `maybe` | | define a string that might appear once or not | `maybe "abc"` | | `word` | | match any word that contains characters from a-z, A-Z, 0-9, including the \_ (underscore) character | | | `anything` | | accept any string | | | `range` | | add a range to the expression | `range "a,z,0,9"` | | `something` | | accept any non-empty string | | | `anythingbut` | `anything but` | accept any string but the specified character | `anythingbut "abc"` | | `anyof` | `any`, `any of` | any of the listed characters | `anyof "abc"` | | `somethingbut` | `something but` | anything non-empty except for these characters | `somethingbut "abc"` | | `limit` | | add character limit | `limit "1,3"` | | `linebreak` | `line break, br` | match \r \n (might be used only with other elements) | | | `tab` | | match tabs \t (might be used only with other elements) | | | `multiple` | | adds the multiple modifier | | ## [Verbal Expressions](#verbal-expressions) [Section titled “Verbal Expressions”](#verbal-expressions) In the Editor, you can use verbal expressions in the [Advanced Filter](/online-editor/#advanced-filter) to search for strings that match specific patterns, similar to regular expressions. You can use it to filter strings based on patterns like punctuation, character types, length, and more. For example, to find all strings that start with an uppercase letter and end with a period, use the following expression: ```graphql start "true", range "A,Z", anything, range "a,z,A,Z,0,9", limit "1,50", then ".", end "true" ``` This expression means: * `start "true"` – the string begins at the start * `range "A,Z"` – starts with a capital letter * `anything` – followed by any characters * `range "a,z,A,Z,0,9"` – allows letters and numbers * `limit "1,50"` – string length between 1 and 50 characters * `then "."` – ends with a period * `end "true"` – end of the string [Verbal Tester ](https://store.crowdin.com/verbal-tester)Create, check and edit verbal expressions in Crowdin project with Verbal Tester application [Try Verbal Expressions GPT ](https://chat.openai.com/g/g-NdFRRXHwm-crowdin-verbal-expressions-maker)Helps with Verbal Expressions development in Crowdin. ### [Verbal Expression Examples](#verbal-expression-examples) [Section titled “Verbal Expression Examples”](#verbal-expression-examples) Below are several examples of verbal expressions along with the types of strings they help match in your project. These are useful when you want to filter strings with specific content or structure. ##### [Start with Uppercase and End with a Period](#start-with-uppercase-and-end-with-a-period) [Section titled “Start with Uppercase and End with a Period”](#start-with-uppercase-and-end-with-a-period) String example: ```plaintext A test string. ``` Expression: ```graphql start "true", range "A,Z", anything, range "a,z,A,Z,0,9", limit "1,50", then ".", end "true" ``` ##### [Strings Containing URLs](#strings-containing-urls) [Section titled “Strings Containing URLs”](#strings-containing-urls) String example: ```plaintext Visit http://example.com or https://www.example.com ``` Expression: ```graphql then "http", maybe "s", then "://", maybe "www.", anythingbut " " ``` ##### [Strings with `%s` and `%d` Placeholders](#strings-with-s-and-d-placeholders) [Section titled “Strings with %s and %d Placeholders”](#strings-with-s-and-d-placeholders) String example: ```plaintext Welcome, %s! You have %d new messages. ``` Expression: ```graphql then "%", anyof "s,d" ``` ##### [Strings with Variables in Double Curly Brackets](#strings-with-variables-in-double-curly-brackets) [Section titled “Strings with Variables in Double Curly Brackets”](#strings-with-variables-in-double-curly-brackets) String example: ```plaintext Hello, {{user.name}}! ``` Expression: ```graphql then "{{", range "a,z", multiple, then ".", range "a,z", multiple, then "}}" ``` ##### [Strings with Variables in Double Curly Brackets (Including Uppercase Letters and Digits)](#strings-with-variables-in-double-curly-brackets-including-uppercase-letters-and-digits) [Section titled “Strings with Variables in Double Curly Brackets (Including Uppercase Letters and Digits)”](#strings-with-variables-in-double-curly-brackets-including-uppercase-letters-and-digits) String example: ```plaintext Hello, {{User123.name42}}! ``` Expression: ```graphql then "{{", range "a,z,A,Z,0,9", multiple, then ".", range "a,z,A,Z,0,9", multiple, then "}}" ``` ##### [Strings That Contain Floating Point Numbers](#strings-that-contain-floating-point-numbers) [Section titled “Strings That Contain Floating Point Numbers”](#strings-that-contain-floating-point-numbers) String example: ```plaintext The result is 3.14159 ``` Expression: ```graphql start, range "0,9", multiple, then ".", range "0,9", multiple, end ``` ##### [Strings That Start with Title Case (Two Capitalized Words)](#strings-that-start-with-title-case-two-capitalized-words) [Section titled “Strings That Start with Title Case (Two Capitalized Words)”](#strings-that-start-with-title-case-two-capitalized-words) String example: ```plaintext Quick Access is available now. ``` Expression: ```graphql start, range "A,Z", range "a,z", multiple, then " ", range "A,Z", range "a,z", multiple ``` ##### [Strings with Trailing Whitespace](#strings-with-trailing-whitespace) [Section titled “Strings with Trailing Whitespace”](#strings-with-trailing-whitespace) String example: ```plaintext This is a sentence with trailing space ``` Expression: ```graphql start "true", range "A,Z", anything, range "a,z,A,Z,0,9", then " ", end "true" ``` ##### [Strings Starting with a Hash Symbol (e.g., Hashtags or Anchors)](#strings-starting-with-a-hash-symbol-eg-hashtags-or-anchors) [Section titled “Strings Starting with a Hash Symbol (e.g., Hashtags or Anchors)”](#strings-starting-with-a-hash-symbol-eg-hashtags-or-anchors) String example: ```plaintext #GettingStarted ``` Expression: ```graphql start "true", then "#", something, end "true" ``` ##### [Strings Containing HTML Tags](#strings-containing-html-tags) [Section titled “Strings Containing HTML Tags”](#strings-containing-html-tags) String example: ```plaintext Click here to continue. ``` Expression: ```graphql then "<", something, then ">" ``` ##### [Strings Containing an Email Address Format](#strings-containing-an-email-address-format) [Section titled “Strings Containing an Email Address Format”](#strings-containing-an-email-address-format) String example: ```plaintext Please contact us at support@example.com ``` Expression: ```graphql then "@", somethingbut " " ``` ##### [Strings with Double Spaces (Possible Spacing Issue)](#strings-with-double-spaces-possible-spacing-issue) [Section titled “Strings with Double Spaces (Possible Spacing Issue)”](#strings-with-double-spaces-possible-spacing-issue) String example: ```plaintext This string has extra space. ``` Expression: ```graphql then " " ``` ##### [Strings Ending with a Colon](#strings-ending-with-a-colon) [Section titled “Strings Ending with a Colon”](#strings-ending-with-a-colon) String example: ```plaintext Enter your name: ``` Expression: ```graphql then ":", end "true" ``` ##### [Strings with a Currency Symbol Followed by Digits](#strings-with-a-currency-symbol-followed-by-digits) [Section titled “Strings with a Currency Symbol Followed by Digits”](#strings-with-a-currency-symbol-followed-by-digits) String example: ```plaintext Total: $29.99 ``` Expression: ```graphql then "$", range "0,9", multiple ``` ##### [Strings in camelCase Format](#strings-in-camelcase-format) [Section titled “Strings in camelCase Format”](#strings-in-camelcase-format) String example: ```plaintext lowerUpper ``` Expression: ```graphql start, range "a,z", multiple, range "A,Z", range "a,z", multiple, end ``` # Figma Plugin > Start localizing at the design stage With the Crowdin for Figma plugin, you can use texts from Crowdin in your designs to save time for both designers and developers. These could include original or translated texts. If necessary, you can add new ones (e.g., dialog titles, button labels) and send them to translators in Crowdin. ## [Use Cases](#use-cases) [Section titled “Use Cases”](#use-cases) * Quickly generate multilingual creative assets. * Translate mockups and test them in different languages before the programming starts. * Stop using ‘Lorem Ipsum’, add real texts from Crowdin to your prototypes instead. Strings added from Crowdin become linked to the text fields in Figma. * Create and upload source strings from your designs to your Crowdin project. Created strings become linked to text fields in Figma. This way, developers could use uploaded strings, reducing time spent on development. * Preview translations and string keys in your designs. * Upload tagged screenshots to your Crowdin project. ## [Installation](#installation) [Section titled “Installation”](#installation) 1. Sign in to Figma. 2. Open one of your design files or click **New design file**. 3. In the file menu, click **Plugins > Manage plugins…**. Alternatively, right-click the canvas and click **Plugins > Manage plugins**. 4. Use the *Search all plugins* field to find **Crowdin for Figma** plugin. 5. Click on **Crowdin for Figma** plugin and select **Save**. 6. Hover over the **Crowdin for Figma** plugin and click **Run**. ## [Configuration](#configuration) [Section titled “Configuration”](#configuration) ### [Setting up Credentials](#setting-up-credentials) [Section titled “Setting up Credentials”](#setting-up-credentials) To specify your Crowdin credentials in Figma, follow these steps: 1. In the file menu, go to **Plugins > Saved plugins**. Alternatively, right-click the canvas and click **Plugins > Saved plugins**. 2. Click **Crowdin for Figma**. 3. Switch to **Settings**. 4. Provide your Personal Access Token. 5. Click **Connect**.  To generate a new token in Crowdin, follow these steps: 1. Go to **Account Settings > API**, *Personal Access Tokens* section, and click **New Token**. 2. Specify *Token Name*, select *Scopes*, and click **Create**. ### [Selecting a Project](#selecting-a-project) [Section titled “Selecting a Project”](#selecting-a-project) To select the Crowdin project you’d like to work with, follow these steps: 1. Click the drop-down menu in **Settings > Crowdin Project**, and select a project from the list.  2. Select a **content type** you’re going to work with in this project and click **Save**. The selected option affects which mode of the Crowdin for Figma plugin will be available to a user. 3. *(Optional)* In the **Crowdin Branch** section, select the specific branch your content will be uploaded to. If your project uses version branches, you can either select an existing one or create a new one directly from Figma; otherwise, you can skip this step. * **To select an existing branch**: Choose the desired branch from the drop-down list. * **To create a new branch**: Click next to the branch field. In the **New Version Branch** dialog, enter a name and click **Create**. The new branch will be created in your Crowdin project and automatically selected in the plugin.  [UI Localization ](#ui-localization) [Marketing Visuals Localization ](#marketing-visuals-localization) ## [UI Localization](#ui-localization) [Section titled “UI Localization”](#ui-localization) Use the *Strings* tab when localizing UI and working on dynamic pages with your development and marketing teams. In this tab, you can add source strings from Crowdin to your designs in Figma in a click. After the texts are used in the designs, you can automatically upload tagged screenshots for translators’ reference back to Crowdin. ### [Using Source Strings from Crowdin in Figma](#using-source-strings-from-crowdin-in-figma) [Section titled “Using Source Strings from Crowdin in Figma”](#using-source-strings-from-crowdin-in-figma) 1. Open the Crowdin plugin for Figma. 2. In the *Strings* tab, use the *Search* field to find the specific copy. You can search strings by source text, string identifier, or context.  3. Select the text layer to which you want to add text and click the link icon next to the needed string.  After using the source strings from Crowdin in your designs, they become linked with the text fields, and you can [preview translations](#previewing-strings) for these strings in Figma and [upload screenshots](#uploading-tagged-screenshots-to-crowdin) for them to your Crowdin project. You can link a single Crowdin string to one or multiple text fields in Figma. However, one text field can be linked only to a single Crowdin string. If you link a text field with an existing connection to a new Crowdin string, the previous connection will be terminated, and a new connection will be established. If you’d like to unlink a Crowdin string from all text fields it was previously linked to, right-click on the link icon next to the needed string. ### [Adding Source Strings from Figma to Crowdin](#adding-source-strings-from-figma-to-crowdin) [Section titled “Adding Source Strings from Figma to Crowdin”](#adding-source-strings-from-figma-to-crowdin) You can add strings that are already used in the designs. 1. Open the Crowdin plugin for Figma. 2. To add the strings used in the designs, select the whole frame, multiple frames, or the needed strings on the frames. 3. In the *Strings* tab, click . 4. In the appeared dialog, fill in the required fields. You can filter the displayed strings if needed: * Select the **Skip hidden elements** filter option if some frames contain hidden elements that should not be added to Crowdin. * Select the **Skip untranslated elements** filter option if some frames contain untranslated elements that should not be added to Crowdin.  5. *(Optional)* To update the string context and set the max.length of the translated text, click toward the needed string. 6. Once all the needed strings are selected and configured, click **Next**. 7. In the next dialog page, select the preferred options: * **Auto-link existing strings** – automatically compare text to existing strings in Crowdin. If there’s a match, the text element will be linked to the string in the Crowdin project. * **Create missing keys** – only new text elements are added to Crowdin. * *(Optional)* To add labels to the strings, alternately select them from the **Select Label** drop-down menu. * **Merge duplicates** – link identical text elements to a single new string in Crowdin. The default behavior is to identify duplicates by comparing their source text. This is useful in the following cases: * When adding multiple text fields with the same text (e.g., several buttons with the label `Submit`), the plugin adds only one string to your Crowdin project and links all duplicate text fields to it. * If your Crowdin project already contains a string with the same text you’re adding from designs, the plugin links to the existing string instead of creating a new one. * To change the duplicate detection method, enable the **Detect duplicates by key** sub-option, which appears when *Merge duplicates* is active. This will make the plugin identify duplicates by their string identifiers (keys) rather than their text content. * [**Send screenshots**](#uploading-tagged-screenshots-to-crowdin). 8. Select the file in Crowdin to which you want to add the strings. To add the same strings into multiple files in Crowdin, alternately select the needed files from the **Select File** drop-down menu. 9. Click **Submit**. 10. Once the strings are added to Crowdin, you’ll see a summary of the content sent. Added strings will be transferred to your Crowdin project and also displayed in the **Strings** tab’s list. You can edit, hide, or delete the strings from the same list anytime. The respective changes will also be applied to the strings in your Crowdin project. ### [Adding Source Strings with Plural Forms](#adding-source-strings-with-plural-forms) [Section titled “Adding Source Strings with Plural Forms”](#adding-source-strings-with-plural-forms) You can add strings with plural forms. 1. Open the Crowdin plugin for Figma. 2. To add the strings used in the designs, select the whole frame, multiple frames, or the needed strings on the frames. 3. In the *Strings* tab, click . 4. In the appeared dialog, fill in the required fields. You can filter the displayed strings if needed. 5. Click toward the needed string and click **Add plurals**. 6. In the appeared dialog, fill in the fields for each plural form and click **Save**. Depending on the source language of the connected Crowdin project, there could be a different number of plural forms you should specify. 7. Once all the needed strings are selected and configured, click **Next**. 8. Select the preferred options and the file in Crowdin you want to add the strings to, click **Submit**. Read more about [Plural Forms](/online-editor/#plural-forms). ### [Configuring ICU Source String Placeholders](#configuring-icu-source-string-placeholders) [Section titled “Configuring ICU Source String Placeholders”](#configuring-icu-source-string-placeholders) When using ICU strings in your design, you can set the placeholders’ values, and after adding such strings to designs, they will be displayed in a formatted view with the preconfigured values. Once you [use](#using-source-strings-from-crowdin-in-figma) the needed ICU string from Crowdin in your design, you can configure its placeholder values. 1. Open the Crowdin plugin for Figma. 2. In the *Strings* tab, use the *Search* field to find the specific copy. You can search strings by source text, string identifier, or context. 3. Click on the needed ICU string. 4. Click **Set placeholders**. 5. Type the needed values for ICU string placeholders. 6. Click **Submit** to save the entered placeholders. 7. Click **Submit** to update the source string text in designs. When [previewing translations](#previewing-strings) for ICU strings in Figma, they will also be displayed in a formatted view if the values were preconfigured beforehand. ### [Key Naming Pattern Settings](#key-naming-pattern-settings) [Section titled “Key Naming Pattern Settings”](#key-naming-pattern-settings) To simplify adding strings from Figma to the Crowdin project, you can set up the desired key naming pattern for the source string identifiers in the plugin settings. The Crowdin plugin for Figma will suggest the string identifiers for new strings based on the selected pattern. While adding new source strings, you can always edit the suggested identifier to the preferred look. To select the key naming pattern, follow these steps: 1. Open the Crowdin plugin for Figma. 2. Switch to **Settings**. 3. In the *Key naming pattern* section, select the preferred option from the drop-down menu. Besides the existing patterns, you can configure your own pattern. To use a custom pattern, select the **Custom key naming pattern** option from the drop-down list and specify your pattern in the **Custom Key Naming Pattern** field. ### [Uploading Tagged Screenshots to Crowdin](#uploading-tagged-screenshots-to-crowdin) [Section titled “Uploading Tagged Screenshots to Crowdin”](#uploading-tagged-screenshots-to-crowdin) When [adding source strings used in the designs](#adding-source-strings-from-figma-to-crowdin), make sure to keep **Send screenshots** selected. As a result, the Crowdin plugin for Figma will upload screenshots along with the source strings. Also, you can update screenshots with an **Update screenshots** option while editing a Crowdin string that is linked to the text fields in designs. Additionally, you can mass upload screenshots to Crowdin for strings linked with text fields in designs. 1. Open the Crowdin plugin for Figma. 2. Select one or more frames with the linked strings. 3. In the *Strings* tab, click to upload screenshots for selected frames. Read more about [Screenshots](/screenshots/). ### [Previewing Strings](#previewing-strings) [Section titled “Previewing Strings”](#previewing-strings) Preview translations from Crowdin for the strings used in the designs in Figma. You can preview translations in the new frames or the original ones. When previewing translations in the new frames, you can populate them with the actual translations or with string keys for further use by developers. To preview strings populated with translations, follow these steps: 1. Open the Crowdin plugin for Figma. 2. In the *Strings* > *Preview Strings* section, select *Preview in duplicated page* or *Preview in the current page*. 3. Select *Create with language*. 4. Select the target language you want to preview translations for (optionally, you can select the preferred plural forms). You can also choose *All languages*. 5. Choose the content you want to preview in Figma. Select *All Frames* or *Selected Frames*.  To preview strings populated with key names, follow these steps: 1. Open the Crowdin plugin for Figma. 2. In the *Strings* > *Preview Strings* section, select *Preview in duplicated page*. 3. Select *Create with key names*. 4. Choose the content you want to preview in Figma. Select *All Frames* or *Selected Frames*.  ### [Filtering Strings](#filtering-strings) [Section titled “Filtering Strings”](#filtering-strings) You can filter strings in the *Strings* tab by various criteria, such as file or status. Click to open the filter settings. To view only the strings linked to specific text fields, follow these steps: 1. Select the needed text fields. 2. In the *Strings* tab, click **Filter strings**. 3. Select **Show strings linked to selected text elements**. In the same way, you can filter strings linked to text fields for the whole frame or multiple frames. ## [Marketing Visuals Localization](#marketing-visuals-localization) [Section titled “Marketing Visuals Localization”](#marketing-visuals-localization) Use the *Pages* tab to localize static pages, like brochures and banners. In this tab, you can send texts with context for translators to Crowdin and upload translated copies back to Figma. Limitations The Pages tab and some other plugin settings may be unavailable when working with [string-based](/creating-project/#string-based-project) projects. ### [Sending Texts for Translation to Crowdin](#sending-texts-for-translation-to-crowdin) [Section titled “Sending Texts for Translation to Crowdin”](#sending-texts-for-translation-to-crowdin) You can send text for translation either from selected or all frames from a Figma file. Translators will work with those texts in the list view and use designs as an additional context for even higher translation quality. In Crowdin, a root folder *figma-plugin* will be created. It will contain a subfolder named after your Figma file with HTML files for each frame inside. If needed, you can disable content segmentation in the plugin **Settings** so the long texts will not be split into sentences. To send Figma designs for translation, follow these steps: 1. Open the necessary Figma file. 2. Go to **Plugins > Crowdin for Figma**. 3. In the *Pages* > *Figma to Crowdin* section, select the content you’d like to translate. Select *All Frames* or *Selected Frames*.  When the source files are uploaded to your Crowdin project, you can invite contributors to translate and proofread them. Read more about [translation strategies](/translation-strategies/). ### [Uploading Translations from Crowdin to Figma](#uploading-translations-from-crowdin-to-figma) [Section titled “Uploading Translations from Crowdin to Figma”](#uploading-translations-from-crowdin-to-figma) You can synchronize texts between Figma and Crowdin projects whenever you want to test the translated copy inside Figma or generate multilingual assets. To upload translated copies to Figma, follow these steps: 1. Open the necessary Figma file. 2. Go to **Plugins > Crowdin for Figma**. 3. In the *Pages* tab, *Crowdin to Figma* section, select the target language you want to upload translations for. You can also select *All languages*. 4. Select the content you want to preview in Figma. Select *All Frames* or *Selected Frames*.  After uploading translations to Figma, the modified file will contain a separate frame with translations for each target language. The newly uploaded translated versions won’t override the ones you uploaded previously. You can always delete the translated copies you no longer need. If you’d like the newly uploaded translated versions to override the previously uploaded ones, open the plugin **Settings** and select **Override existing translations**. ## [Pseudo-localization](#pseudo-localization) [Section titled “Pseudo-localization”](#pseudo-localization) Even before translations are completed, you can test whether your application is ready to be localized using pseudo-localization. This feature allows you to simulate how the application’s UI will look with different languages to check whether the source strings should be modified before the project localization starts. Depending on the content you want to test, you can use the *Strings* or *Pages* tab in the Crowdin for Figma plugin. * Strings tab 1. Open the necessary Figma file. 2. Go to **Plugins > Crowdin for Figma**. 3. In the *Strings* > *Preview Strings* section, select *Preview in duplicated page*. 4. Select *Pseudo-localization*. 5. On the next dialog page, you can choose from predefined presets and configure the settings according to your preferences. 6. Click **Submit**. * Pages tab 1. Open the necessary Figma file. 2. Go to **Plugins > Crowdin for Figma**. 3. In the *Pages* > *Pseudo-localization* section, select the content you’d like to test with pseudo-localization. Select *All Frames* or *Selected Frames*. 4. On the next dialog page, you can choose from predefined presets and configure the settings according to your preferences. 5. Click **Submit**. Read more about [Pseudo-localization](/developer/pseudolocalization/) and its settings. ## [Crowdin for Figma Plugin in Dev Mode](#crowdin-for-figma-plugin-in-dev-mode) [Section titled “Crowdin for Figma Plugin in Dev Mode”](#crowdin-for-figma-plugin-in-dev-mode) Figma’s Dev Mode allows designers and developers to collaborate, ensuring accuracy in implementation and a smooth transition from design to code. Read more about [Figma Dev Mode](https://help.figma.com/hc/en-us/articles/15023124644247-Guide-to-Dev-Mode). The integration of Crowdin for Figma plugin with Dev Mode extends the functionality of both platforms, enhancing the localization process within the design environment. While Dev Mode in Figma has its limitations – it’s read-only, certain limitations apply to the Crowdin for Figma plugin’s capabilities: **What You Can Do**: * Access the *Strings* tab to view and manage strings. * Explore string details, including file, key, context, and labels. * Quickly copy string keys for efficient workflow. Features not available in Dev Mode: adding new strings to Crowdin, linking strings, sending screenshots, previewing translations, editing, hiding, or deleting strings. ### [Using Crowdin for Figma Plugin in Dev Mode](#using-crowdin-for-figma-plugin-in-dev-mode) [Section titled “Using Crowdin for Figma Plugin in Dev Mode”](#using-crowdin-for-figma-plugin-in-dev-mode) Despite the limitations, the Crowdin for Figma plugin remains valuable in Dev Mode, offering developers a streamlined approach to text elements management. Here’s a typical use case: 1. Enter [Dev Mode](https://help.figma.com/hc/en-us/articles/15023124644247-Guide-to-Dev-Mode#01H8CR3K6VG21T3H9789QMV6CP). 2. In the right sidebar, switch to the *Plugins* tab. 3. Click on **Crowdin for Figma**. 4. In the *Strings* tab, click **Filter strings** and select **Show strings linked to selected text elements**. 5. Select the needed string on the frame and hover over the icon in the string list to view all needed information (i.e., key, context, file it’s stored in, labels) about this particular string. 6. *(Optional)* Click **Copy string key to clipboard** to further use it in code. ### [Compatibility with Figma for VS Code](#compatibility-with-figma-for-vs-code) [Section titled “Compatibility with Figma for VS Code”](#compatibility-with-figma-for-vs-code) Furthermore, the Crowdin for Figma plugin seamlessly integrates with Figma for VS Code, extending its functionality to developers using this environment. Read more about [Figma for VS Code](https://help.figma.com/hc/en-us/articles/15023121296151-Figma-for-VS-Code). ## [Troubleshooting](#troubleshooting) [Section titled “Troubleshooting”](#troubleshooting) ### [Screenshot Generation Issues in Large Figma Files](#screenshot-generation-issues-in-large-figma-files) [Section titled “Screenshot Generation Issues in Large Figma Files”](#screenshot-generation-issues-in-large-figma-files) When uploading strings with screenshots from large Figma files, users may experience slow performance or Figma freezing. This issue occurs when text elements are placed within a large top-level frame. When you add a string from Figma to Crowdin, the plugin: 1. Identifies the top-level frame containing the text element. 2. Converts this frame into an image using the Figma API. 3. Uploads the image to Crowdin as a screenshot. The plugin always searches for the highest-level frame in the hierarchy and stops when encountering a non-frame element (such as a section or group). If the top-level frame is too large, generating a screenshot can cause performance issues. For example: * `section` > `group` > **`frame`** > `text` → The plugin captures the screenshot from `frame`. * **`frame 1`** > `frame 2` > `frame 3` > `text` → The plugin captures the screenshot from `frame 1`. To prevent slowdowns, restructure your Figma file so that top-level frames contain only the relevant UI context. Instead of placing all UI elements in a single large frame, break them into smaller, logical sections. ### [Font Replacement When Linking Strings](#font-replacement-when-linking-strings) [Section titled “Font Replacement When Linking Strings”](#font-replacement-when-linking-strings) When working in Figma, fonts that are missing locally may cause unexpected changes after linking strings using the Crowdin for Figma plugin. This situation typically happens when: * The original design uses a font that is not installed in your local Figma environment. * Figma marks missing fonts with a special **A?** icon shown in the upper-left corner of the canvas and next to the font name in the **Typography** section of the right sidebar. * When you select a text element with a missing font, Figma displays a **Missing font** dialog offering to replace it. If you link a Crowdin string to such a text element, Figma will automatically substitute the missing font with a default available font (e.g., Roboto). This is expected behavior. The plugin attempts to preserve the original font, but when it’s not available in your local system, Figma replaces it to ensure the text remains visible and editable. This issue may not be immediately noticeable. Some users detect the font change only after uploading screenshots from Figma to Crowdin, which can cause confusion. To avoid this: * Check for missing font indicators (**A?**) before linking strings. * Make sure the fonts used in the original design are installed and available in your Figma. * If necessary, coordinate with the designer to confirm the correct font setup. # File Management > Manage and configure source files in your project You can manage all the project’s files via **Sources > Files**. Here you can manually upload files for localization using various [supported formats](/supported-formats/). When the files are uploaded, you’ll be able to take a glance at how many *Strings* your files include and how many *Revisions* (changes) were done to each of them. If you want to configure an automatic files’ synchronization with your project, use the **Integrations** tab. ## [Prioritizing Files](#prioritizing-files) [Section titled “Prioritizing Files”](#prioritizing-files) You can set a specific priority for each file by clicking an arrow icon next to the needed file. Then translators will be able to see files sorted according to their priority on the language page and in the Editor. Files might have the following priorities: * – low * – normal * – high  ## [File Settings](#file-settings) [Section titled “File Settings”](#file-settings) To access the configurations of specific files, right-click on the necessary file or click next to it and then select **Settings**. Alternatively, just double-click on the file.  ### [Title as it Appears to Translators](#title-as-it-appears-to-translators) [Section titled “Title as it Appears to Translators”](#title-as-it-appears-to-translators) Show descriptive file titles to translators. For example: use *About Us Dialog* instead of *abt\_us.xml*, or *In-app texts* instead of *Localizable.strings*. Caution The file title is only shown in the Crowdin UI and doesn’t rename the actual file. ### [File Export](#file-export) [Section titled “File Export”](#file-export) Define a file name or full path in the resulting archive, use the available placeholders to indicate the structure of exported content. For example, you want the source file `Overview.csv` with Ukrainian translation to be named `Overview.ukrainian.csv` before integrating it with the application. In this case, you’d need to set the *Resulting file after translations export* to the following: `Overview.%language%.csv`. By default, Crowdin adds [Crowdin language codes](/developer/language-codes/) during the file export. To use custom ones for specific languages in the whole project, set up [Language Mapping](/project-settings/languages/#adding-custom-language-codes).  ### [Parser Configuration](#parser-configuration) [Section titled “Parser Configuration”](#parser-configuration) Some file formats allow you to configure import and export behavior. In this case, file’s Settings dialog will also contain the **Parser configuration** tab.  Read more about [Parser configuration](/project-settings/parser-configuration/). ### [File Target Languages](#file-target-languages) [Section titled “File Target Languages”](#file-target-languages) By default, the source files are available for translation into all target languages of the project. Clear the checkboxes in the *File target languages* list next to the languages your file shouldn’t be translated into, and click **Save**.  ### [File Context](#file-context) [Section titled “File Context”](#file-context) Add additional information or instructions to help translators better understand how to translate a file. File context can be added as plain text or Markdown in **File Settings > Context** or directly in the Editor. The provided context will be visible to translators in the Editor in the [File Context](/online-editor/#file-context) tab. The icon appears next to files that have file context added, helping you quickly identify which files include helpful notes for translators.  Limitations File Context is only available for [file-based](/creating-project/#project-types) projects. ## [Pre-translating Files and Folders](#pre-translating-files-and-folders) [Section titled “Pre-translating Files and Folders”](#pre-translating-files-and-folders) To quickly run pre-translation for one or more files or folders, right-click on the necessary item or click next to it and select **Pre-translate**. Read more about [pre-translating selected files or folders](/pre-translation/#pre-translating-files-and-folders-via-context-menu). ## [Viewing Strings](#viewing-strings) [Section titled “Viewing Strings”](#viewing-strings) To view all strings from a specific file, right-click on the file and select **View strings**. This opens the **Strings** tab with a pre-applied filter that displays only the strings from the selected file. Read more about [String Management](/string-management/). ## [Renaming Files](#renaming-files) [Section titled “Renaming Files”](#renaming-files) To change the file’s name, right-click on the necessary file or click next to it and select **Rename**.  ## [Cost Estimate](#cost-estimate) [Section titled “Cost Estimate”](#cost-estimate) To estimate the cost of translation or proofreading for a specific file, right-click on the file and select **Cost Estimate**. Read more about [generating Cost Estimate report](/project-reports/#generating-cost-estimate). ## [Creating a Task](#creating-a-task) [Section titled “Creating a Task”](#creating-a-task) To create a task for a specific file, right-click on the file and select **Add task**. This allows you to assign translation or proofreading work for just that file to selected contributors or translation vendors. Read more about [Project Tasks](/tasks/). ## [Opening in Editor](#opening-in-editor) [Section titled “Opening in Editor”](#opening-in-editor) To open a file directly in the Editor, right-click on the file and select **Open in Editor**. This allows you to review translations and approvals, answer string comments, and more. ## [Checking Progress](#checking-progress) [Section titled “Checking Progress”](#checking-progress) You can check the translation and approval progress for a branch, folder, or file you need. Right-click on the needed branch, folder or file, and select the **Progress**. To see how many words are translated and approved for each language, hover over the progress bar. To open the selected file in the Editor, click on the needed language. To download translations for the chosen file, select the required languages, and click **Build & Download**. Optionally, you can select **Preserve folder hierarchy for export** to export translation files along with the folders they’re stored in Crowdin.  ## [Previewing Source Files](#previewing-source-files) [Section titled “Previewing Source Files”](#previewing-source-files) To preview the raw structure and content of a source file, right-click the file and select **Preview source**. This opens a read-only modal showing the file’s contents exactly as Crowdin received them. ## [Downloading Source Files](#downloading-source-files) [Section titled “Downloading Source Files”](#downloading-source-files) To download a source file stored in your Crowdin project, right-click on the file and select **Download source**. This can be useful for reviewing the original content outside Crowdin, sharing it with teammates, or making offline edits before reuploading. ## [Updating Source Files](#updating-source-files) [Section titled “Updating Source Files”](#updating-source-files) In case you have added some new strings to one of the source files, you’d want to update it to make newly added strings visible to translators. Click **Update** next to the needed file and select the new file on your machine.  If some of the source strings were modified, the system shows a dialog with a list of edited strings. You’ll be able to choose which existing translations you want to keep without changes (*Current Strings* column) and whether you want to keep or remove approvals. The translations for other changed strings will be removed.  After updating files, Crowdin may detect changes and display a blue dot next to the **Refresh** button in the upper-right corner of the **Files** tab. Click this button to refresh the file list and display the most up-to-date information. ## [Restoring Previous Versions](#restoring-previous-versions) [Section titled “Restoring Previous Versions”](#restoring-previous-versions) Each time you update the source file, a new revision is created. To restore your file to the previous revision, click the number on the needed file in the *Revision* column. In the appeared dialog, select the revision you want to restore your file to and click **Restore** next to it.  ## [Branches and Folders](#branches-and-folders) [Section titled “Branches and Folders”](#branches-and-folders) You can create folders and branches in **Sources > Files** with **New Folder** and **New Version Branch** buttons. Folders represent your content structure, while branches help to manage different versions of the content. Usually, branches in Crowdin are created automatically if you use GitHub, GitLab, or other VCS integration. Still, if you need to create branches manually, make sure to upload the master branch first, as all the others will be considered the feature branches. Duplicates might be managed in **Settings > Import > Source Strings** by choosing the corresponding option for *Duplicate Strings*.  Read more about [Version Management](/version-management/). ## [Changing Scheme for CSV and XLSX Files](#changing-scheme-for-csv-and-xlsx-files) [Section titled “Changing Scheme for CSV and XLSX Files”](#changing-scheme-for-csv-and-xlsx-files) File formats like CSV and XLSX might require changing the initially configured scheme. Usually, it might be needed when you add a new target language to your Crowdin project. Read more about [changing the scheme for CSV and XLSX files](/csv-xlsx-configuration/#changing-scheme-for-csv-and-xlsx-files). # For Managers > A guide to managing localization projects in Crowdin > Crowdin is a localization management platform that helps companies, teams, and individuals stay agile when translating products like mobile, desktop & web apps, websites, games, help documentation, and more. In this article, we’ll walk you through a typical localization workflow for managers in Crowdin. We’ll cover creating a project, uploading content, inviting project members, pre-translating your project, generating reports, and downloading translations. ## [Create a Project](#create-a-project) [Section titled “Create a Project”](#create-a-project) Create a project to be able to upload your content for localization. When creating a project, you can select the preferred *project visibility*, *project type*, and select the source and target languages.  Read more about [Creating a Project](/creating-project/). Once you’ve created a project, you can add content to be translated. Each project has its own source content, resources, target languages, integrations, members, etc. ## [Upload Content](#upload-content) [Section titled “Upload Content”](#upload-content) Once you’ve created the project, upload localizable files and resources, such as screenshots, translation memory, and glossary. ### [Upload Source Files for Localization](#upload-source-files-for-localization) [Section titled “Upload Source Files for Localization”](#upload-source-files-for-localization) You can upload localizable files in a way that works best for you: * Manually via the web interface (UI). * Integrate Crowdin with the tools you already use: * Repo *(GitHub, GitLab, etc.)* * Marketing tools *(Contentful, Webflow, WPML, Hubspot, Marketo, etc.)* * Help center *(Help Scout, Zendesk, Intercom, etc.)* * Development tools *(VS Code, Android Studio, Google Play, etc.)* * Email automation *(MailChimp, SendPulse, ActiveCampaign, Mandrill, Moosend, etc.)* * Design tools *(Figma, Sketch, Adobe XD)*. * Use API or console client.  Read more about [Uploading Source Files](/uploading-files/). To automatically sync files between your Crowdin project and the tools of your choice, add and set up the respective integration. Once you add the integration, you can proceed to the setup. [Crowdin Store ](https://store.crowdin.com/)Explore 700+ integrations to streamline your localization process. ### [Upload Existing Translations](#upload-existing-translations) [Section titled “Upload Existing Translations”](#upload-existing-translations) If you already have some translations done outside Crowdin, you can upload them to your Crowdin project to keep everything in one place and continue working on translations. Read more about [Uploading Existing Translations](/uploading-translations/). ### [Upload Localization Resources](#upload-localization-resources) [Section titled “Upload Localization Resources”](#upload-localization-resources) In most cases, you might have localization resources like [Translation Memory](/translation-memory/) and [Glossary](/glossary/). It is a good idea to upload them to your Crowdin project since these localization resources help your translators during the translation process and ensure high translation quality. ### [Upload Screenshots](#upload-screenshots) [Section titled “Upload Screenshots”](#upload-screenshots) Screenshots are another great way to provide additional context so translators can understand better how they should translate the source strings. To upload screenshots, open your project and go to the **Screenshots** tab. Tag the source strings on the screenshots. This way, screenshots with tagged strings will appear under each string in the Editor’s Context and Translations section.  Read more about [Screenshots](/screenshots/). [Context features in Crowdin ](https://crowdin.com/blog/2019/11/05/no-context-no-quality-give-translators-context-to-get-better-translations)No Context, No Quality. Give Translators Context to Get Better Translations. [Translate Your UI with Crowdin's Screen Translation Feature ](https://crowdin.com/translate-ui-with-crowdin)Crowdin's Screen Translation simplifies UI localization by allowing users to translate interface elements with a real-time preview of your app design. ## [Pre-translate Your Project](#pre-translate-your-project) [Section titled “Pre-translate Your Project”](#pre-translate-your-project) To save time, you can pre-translate your Crowdin project using [Translation Memory](/translation-memory/) (TM), [Machine Translation](/machine-translation/) (MT), or [AI](/crowdin-ai/). Pre-translating your content means some strings will already be translated before translators begin their work. You can apply pre-translation manually or set up automatic pre-translation, so each time new content is added, it’s translated automatically based on your settings.  Read more about [Pre-translation](/pre-translation/). ## [Invite People](#invite-people) [Section titled “Invite People”](#invite-people) Decide who will translate and manage your content. You can collaborate with professional translation agencies (i.e., vendors) integrated with Crowdin or invite your own team. If you decide to work with agencies, go to **Store > Vendors** to select a translation vendor that meets your requirements. Read more about [Ordering Professional Translations](/ordering-professional-translations/). If you decide to invite your own team, open your project and go to the **Members** tab to add people by Crowdin username, email, or invitation link. Based on what each person will do in the project, you can assign the following roles: Manager, Developer, Language Coordinator, Proofreader, and Translator.  Read more about [Inviting People](/inviting-people/). Once added to the project, team members can start working in the [Editor](/online-editor/) or access other project areas depending on their role. ## [Generate Reports](#generate-reports) [Section titled “Generate Reports”](#generate-reports) Crowdin provides project-level reports to help you track progress, evaluate translation accuracy, estimate and count costs, and measure contributor activity. To access them, open your project and go to the **Reports** tab. Available reports include: * Overview * Cost Estimate * Translation Cost * Pre-translation Accuracy * Translator Accuracy * Top Members * Archive  Read more about [Reports](/project-reports/). ## [Download Translations](#download-translations) [Section titled “Download Translations”](#download-translations) You can download translations manually using the web interface (UI) or set up automated delivery using integrations (e.g., GitHub or other connected tools), the Crowdin API, the console client (CLI), or Over-The-Air Content Delivery. Translations are downloaded according to the export settings configured in the project’s **Settings** tab. Read more about [Downloading Translations](/downloading-translations/). # For Translators > Learn how to contribute to localization projects as a translator > Crowdin is a localization management platform that helps companies translate their software. In this article, you will find information on how you can contribute to localization projects as a translator. In this article, you will learn about the typical workflow of a translator or volunteer translator on Crowdin. You will also learn how to find projects to contribute to, explore your workspace, and work in the editor. ## [Create an Account](#create-an-account) [Section titled “Create an Account”](#create-an-account) If you are not registered in Crowdin, you can [create an account](https://accounts.crowdin.com/register) using your email or sign up with the help of social media profiles (Google, Facebook, Twitter), GitHub, or GitLab profiles. Click the profile picture in the upper-right corner and select *Settings* to access your Account Settings where you can view and manage your personal information, profile security, notifications, define preferred languages, etc. [Account Settings ](/account-settings/) ## [Profile Page](#profile-page) [Section titled “Profile Page”](#profile-page) A profile page is a place where you start working on Crowdin projects. In the *Projects* tab, you can see all the projects you have joined. If you’ve requested to join a project that requires manager approval, it will appear in the *Pending* section until your request is reviewed.  ## [Exploring Projects](#exploring-projects) [Section titled “Exploring Projects”](#exploring-projects) Find a Crowdin project you would like to contribute to using the search field in the header or the direct URL provided by the project manager. However, not all projects can be found with the help of the search field. This is because they are private and only accessible via invitation links. Visit our [Showcases](https://crowdin.com/projects#showcases) page, where you can find some popular public projects grouped by category. Use the *Advanced Search* if you want to apply specific filter options (e.g., target languages, platform) to find a public project.  ## [Explore Your Workspace](#explore-your-workspace) [Section titled “Explore Your Workspace”](#explore-your-workspace) Once you find and open the needed project, you can access the following tabs: * **Dashboard** – the page with a list of project languages, the main project details, and the list of project managers. Click on the needed language to access files for translations. You can also use the **Translate All** button to access all project strings at once. Caution Some projects might have a moderated project joining. Click **Join** to submit an access request to a specific language and wait until a project manager confirms it. * **Tasks** – the page that contains the list of tasks assigned to you (if any). * **Reports** – the page where you can see the project status and view the project’s top members. Crowdsourcing projects don’t usually have financial rewards for translations. So you can use the [My Contribution](/contributor-reports/) report to see the overall amount of the strings you translated and proofread without setting the rates. * **Activity** – the page where all the [Project Activity](/project-activity/) is shown. For example, comments, newly joined users, translated, and proofread strings. * **Discussions** – the page with the project-related conversations. You can participate in already existing discussions or create a new topic if necessary.  ### [Requesting a New Language](#requesting-a-new-language) [Section titled “Requesting a New Language”](#requesting-a-new-language) If a language you’d like to translate is not currently listed in the project, you can request its addition. This feature is available in all public projects in Crowdin. To request a language, follow these steps: 1. Open the project and go to the **Dashboard** tab. 2. Click **Request new language** in the **Details** section. 3. In the appeared modal, select the preferred language. 4. *(Optional)* Add a message to the project managers to be included with your request. 5. Click **Send**. The project managers will review your request and determine whether the language can be added. If another user has already submitted a request for the same language, you will receive a notification about the existing request. This notification will also appear if you submit multiple requests for the same language while the first request is still under review by the managers. ### [Contacting a Project Manager](#contacting-a-project-manager) [Section titled “Contacting a Project Manager”](#contacting-a-project-manager) If you have questions about the project’s content, need clarification on a specific task, or would like to be promoted to a proofreader role, you can contact the project manager. You might also reach out if you need additional resources, have feedback on translations, want to discuss project timelines, etc. To contact the project manager, open the project and click **Contact** next to their name. You will be redirected to the **Create Conversation** page with the project manager pre-selected as the recipient. If needed, you can also add other users to the conversation. Click **Go**, and the conversation will be created, allowing you to begin communicating. You will be notified when the manager replies, and the discussion will continue in the same thread. ### [Intellectual Property Rights](#intellectual-property-rights) [Section titled “Intellectual Property Rights”](#intellectual-property-rights) Before contributing translations to a project, it’s important to understand the intellectual property terms. Projects may define how your translations will be used, shared, or licensed. If you’re contributing to open-source or community-driven projects, check if the project provides additional legal or licensing terms. When in doubt, contact the project manager for clarification. Read more about [Intellectual Property Rights](/intellectual-rights-for-translations/). ### [Reporting a Project](#reporting-a-project) [Section titled “Reporting a Project”](#reporting-a-project) If you come across a project in Crowdin that contains inappropriate or unsafe content, you can report it. Reports are reviewed to ensure the project complies with [Crowdin’s Terms and Conditions](/terms/). To report a project, follow these steps: 1. Open the project and go to the **Dashboard** tab. 2. In the **Details** section, click **Report**. 3. In the appeared modal, select the type of issue you’re reporting. 4. *(Optional)* Add additional details in the text field. 5. Click **Submit**. After submitting the report, you’ll see a confirmation message. The Crowdin team will review your report and take action if necessary. ## [Working in the Editor](#working-in-the-editor) [Section titled “Working in the Editor”](#working-in-the-editor) The Editor is where translators and proofreaders work on translations online. The String List section displays strings from the selected file or all project strings, with the active string highlighted. String context and details for the selected string appear in the String Details section. [Online Editor ](/online-editor/) ### [Translation](#translation) [Section titled “Translation”](#translation) Collaborate with other project members, discuss any issues or questions in the Comments section, vote for the best translation variants, and take advantage of the project [Glossary](/glossary/) and [Translation Memory](/translation-memory/). Use the machine translations as a basis for your own suggestions.  #### [String List](#string-list) [Section titled “String List”](#string-list) The **String List** is your primary workspace for managing translations. ##### [Layout and Status](#layout-and-status) [Section titled “Layout and Status”](#layout-and-status) * Source Text: On the left. * Translations: On the right. * Status icons indicate whether strings are untranslated, translated, or approved. Comments or issues are highlighted. ##### [Searching and Filtering](#searching-and-filtering) [Section titled “Searching and Filtering”](#searching-and-filtering) * Use the *Search in file* field to locate strings. * Apply Simple or Advanced Filters to sort and filter strings. ##### [QA Checks](#qa-checks) [Section titled “QA Checks”](#qa-checks) Pop-up messages may appear to alert you to potential issues, such as inconsistent punctuation, mismatched spaces, or missing variables. These checks help maintain translation quality. #### [AI Assistant](#ai-assistant) [Section titled “AI Assistant”](#ai-assistant) The AI Assistant in the Editor helps you work faster and more accurately by providing context-aware suggestions, rephrasing support, and other smart editing tools. You can use predefined actions like *Rephrase*, *Shorten*, *Translate All*, or [create your own prompt](/online-editor/#ai) to interact with the Assistant directly. To access the AI Assistant, click on the AI Assistant tab in the right sidebar of the Editor. #### [Context and Translations](#context-and-translations) [Section titled “Context and Translations”](#context-and-translations) This section contains the resources that might be useful: * Context, labels, screenshots, and additional information to guide the work. * Translations by other project members * Translation Memory (TM) suggestions * Machine Translation (MT) suggestions * Translations to other languages If you see that there is already a correct suggestion, vote for it by clicking the *plus* sign if you like the translation, or the *minus* sign if you don’t think the translation is correct. Translations that receive the most positive votes will have a higher rating and will appear at the top of all available translations for the string.  #### [Comments](#comments) [Section titled “Comments”](#comments) In the *Comments* section, you can discuss the meaning of the source string or other related questions with other project members. Use ”@” and a username to mention the specific person or [create an issue](/issues/#for-translators) related to the string. ### [Main Menu](#main-menu) [Section titled “Main Menu”](#main-menu) The Main menu in the upper-left corner allows you to switch between files for translation, change translation languages, contact a manager, and configure the Editor view.  ### [Keyboard Shortcuts](#keyboard-shortcuts) [Section titled “Keyboard Shortcuts”](#keyboard-shortcuts) Click in the upper-right corner to see the list of available keyboard shortcuts. They can make your work in the Editor more efficient and fast. Most shortcuts can be customized. Click on the needed key combination and modify it using your keyboard. ## [Offline Translation](#offline-translation) [Section titled “Offline Translation”](#offline-translation) As an alternative to translating online in the Editor, you can download project files for [offline translation](/offline-translation/) if the project manager has enabled public downloads. Use the XLIFF file format for offline translation, which is supported by most desktop localization tools. # GDPR Commitment > GDPR compliance at Crowdin localization software We’re committed to helping Crowdin customers and users understand and comply with the General Data Protection Regulation (GDPR). The GDPR is the most comprehensive EU data privacy law that went into effect on May 25, 2018. The GDPR strengthens the rights that individuals have regarding personal data relating to them and seeks to unify data protection laws across Europe, regardless of where that data is processed. This page provides an overview of the data-related roles and responsibilities that come into effect, once you choose Crowdin as your localization platform and will explain Crowdin’s efforts to live up to the values and requirements of the GDPR. ## [Crowdin as the data processor](#crowdin-as-the-data-processor) [Section titled “Crowdin as the data processor”](#crowdin-as-the-data-processor) The source files and translations that you store in Crowdin are your data and you are the data controller for any personal data that may appear thought these resources. In our [Terms of Service](/terms/) and [Privacy Policy](/privacy-policy/), this data is referred to as Client Data. Using the Crowdin platform to manage your localization files means that you have engaged Crowdin as a data processor to carry out certain processing activities on your behalf. According to Article 28 of the GDPR, the relationship between the controller and the processor needs to be made in writing (electronic form is acceptable under subsection (9) of the same Article). This is where our [Terms of Service](/terms/) and [Privacy Policy](/privacy-policy/) come in. These two documents also serve as your data processing contract, setting out the instructions that you are giving to Crowdin concerning the processing of your personal data and establishing the rights and responsibilities for both parties. Crowdin will only process your Client Data based on your instructions as the data controller. All customers have a contractual relationship with our EU entity, based in Estonia. #### [Data transfers](#data-transfers) [Section titled “Data transfers”](#data-transfers) One topic that often comes up with customers is data transfers outside of the EEA. The GDPR establishes strict requirements for moving data outside of its scope of protection. As our customers have a legal relationship with our EU entity. If Crowdin subsequently engages sub-processors outside the EEA, it is our job to ensure that we transfer the data lawfully. We will keep an up-to-date [list of sub-processors](/sub-processors/) to be fully transparent about these transfers. This list will also explain what data is involved and how we have ensured that the data is adequately protected even after it leaves the EEA. We do this by making sure that our third-party service providers have signed the EU Commission’s standard contractual clauses for data transfers with us. ## [Crowdin as the data controller](#crowdin-as-the-data-controller) [Section titled “Crowdin as the data controller”](#crowdin-as-the-data-controller) Additionally, Crowdin acts as the data controller for the personal data we collect about users of our web application and website. There are a few reasons we have to process personal data: 1. We process data that is necessary for us to perform our contract with you (GDPR Article 6(1)(b)); 2. We process data to meet our obligations under the law (GDPR Article 6(1)(c)) — this primarily involves financial data and information that we need to meet our accountability obligations under the GDPR. 3. We process your personal data for our legitimate interests in line with GDPR Article 6(1)(f). Our legitimate interests are the following: * Improving the functionality of the platform to help the users’ productivity. * Ensuring the safety and security of your data and Crowdin’s systems. * Responsible marketing of our product and its features. ## [What is Crowdin doing for the GDPR](#what-is-crowdin-doing-for-the-gdpr) [Section titled “What is Crowdin doing for the GDPR”](#what-is-crowdin-doing-for-the-gdpr) As an EU company, we are obligated to make sure each and every aspect of our business complies to EU laws in general and GDPR specifically. For all those reasons we have implemented technical and organizational measures in line with the GDPR to safeguard the personal data of our customers and users that are processed by Crowdin. ### [Internal processes, security and data transfers](#internal-processes-security-and-data-transfers) [Section titled “Internal processes, security and data transfers”](#internal-processes-security-and-data-transfers) We developed and maintain necessary procedures to ensure that data processes are mapped and auditable, which is a large part of the GDPR requirements. We also have added elements to our application development cycle to build features based on the Privacy by Design principles. Any access to the Client Data that we process on your behalf is strictly limited. Our internal procedures and logs make sure that we meet the GDPR accountability requirements in this regard. We have established a process for onboarding third-party service providers and adopting tools that makes sure that these third-parties meet the high expectations that Crowdin and its customers have when it comes to privacy and security. Readiness to comply with subject access requests The ownership of personal data by Data Subjects takes the central place of the GDPR. We have all the necessary means to respond to data subject requests regarding deletion, modification, or downloading of their data. This means that our Customer Support Specialists along with the Engineers that assist them in their work are well-prepared to help you in any matters involving your personal data, in addition to providing the awesome customer support experience. ### [Documentation](#documentation) [Section titled “Documentation”](#documentation) Our [Terms of Service](/terms/), [Privacy Policy](/privacy-policy/), [List of Subprocessors](/sub-processors/), [Cookie Statement](/cookies/), and [Security Page](https://crowdin.com/page/security) are constantly being revised to increase transparency and to make sure these documents meet the GDPR requirements. As these are the basis for our relationship with you, it is very important for us to explain our commitments and your rights in these documents comprehensively and openly. Additionally, we’re constantly mapping all our data processing activities to be able to comply with the GDPR accountability requirements. ### [Training](#training) [Section titled “Training”](#training) All of the above is supported by extensive training efforts within the company so that the GDPR compliant processes we’ve put in place are followed. Sessions on data privacy and security are an integral part of our onboarding process and each department receives training that is tailored to their work involving personal data. Crowdin is firmly convinced that meeting GDPR requirements is much more than just checking off boxes in a list. For us, the GDPR is truly a lifestyle of respect to individuals’ privacy and responsibility in handling personal data. Hopefully, this helps you to better navigate the EU’s data protection requirements. If you have any questions regarding the above, you’re welcome to reach out to us at and we’ll do our best to explain things further. # GitHub Integration > Synchronize files between your GitHub repository and Crowdin The GitHub integration allows you to synchronize files between your GitHub repo and Crowdin project. In file-based projects, there are two possible GitHub integration modes you can choose from: * **Source and translation files mode** – synchronize source and translation files between your GitHub repository and Crowdin project. * **Target file bundles mode** – generate and push translation files to your GitHub repository from the Crowdin project in the selected format. In this mode, integration pushes translation files and doesn’t sync sources from your repo. In cases when you perform a source text review in your Crowdin project and want to get updated source texts to your repo, you can add a source language as a target language, which will be pushed to your repo along with translations. In string-based projects, GitHub integration exclusively operates in the **Target file bundles mode**. Read more about [project types](/creating-project/#project-types). All translated and approved files (or target file bundles) are automatically merged into the `l10n` branch of the GitHub repository. ## [Connecting GitHub Account](#connecting-github-account) [Section titled “Connecting GitHub Account”](#connecting-github-account) 1. Open your project and go to the **Integrations** tab. 2. Click on **GitHub** in the Integrations list. 3. Click **Set Up Integration** and select **Source and translation files mode** or **Target file bundles mode** from the drop-down list to integrate via your GitHub account.  4. Then authorize the connection with Crowdin on the GitHub side:  In case the repository you need is private, and you have limited or no access to it, please ask the repository owner to provide you with an [Access Token](https://help.github.com/articles/creating-an-access-token-for-command-line-use/#creating-a-token). Afterward, click **Use personal access token** and insert the token into the *Token* field and click **Set Up Integration**. ### [Selecting Repository](#selecting-repository) [Section titled “Selecting Repository”](#selecting-repository) In the appeared dialog, select your repository and branches that should be translated. * File-based project  It’s recommended to switch Duplicate Strings to **Show within a version branch**, so identical strings will be hidden between branches. If your source files contain strings with apparent identifiers (keys), it’s better to use a *strict* version of this option. In other cases, feel free to use a *regular* one. * String-based project  [Duplicate Strings ](/project-settings/import/#duplicate-strings) [Version Management ](/version-management/) When working with GitHub integration in the **Target File Bundles Mode**, the integration will send the completed translations from your Crowdin project without pulling sources from your repo. So when selecting a repository and branches that should be translated, you specify where the integration should put the generated bundles with translations. Read more about [configuring target file bundles for VCS integration](/bundles/#bundles-in-vcs-integrations). When you work with private integrations (e.g., integrations with self-hosted VCS), you need to add dedicated Crowdin IP addresses to the allowlist to ensure that it operates properly while staying secure. Read more about [IP Addresses](/developer/ip-addresses/#integrations). ### [Service Branches](#service-branches) [Section titled “Service Branches”](#service-branches) When translations are finished and your languages are ready to go live, Crowdin sends the pull request with translations to your version control system. For every branch that is under localization, Crowdin creates an additional service branch with translations. We don’t commit directly to the master branch so that you can verify translations first. By default, `l10n_` is added to the created service branch name. If necessary, you can easily change it. ### [Synchronization Settings](#synchronization-settings) [Section titled “Synchronization Settings”](#synchronization-settings) Configure the synchronization settings according to your needs and preferences. Limitations The *Import existing translations* and *Push Sources* options are only available for file-based projects. #### [Import Existing Translations](#import-existing-translations) [Section titled “Import Existing Translations”](#import-existing-translations) To import existing translations from your repo, select one of the following options: * **One-time translation import after the branch is connected** * **Always import new translations from the repository** By default, the first option is selected to import translations only once. Alternatively, you can clear both options if you don’t want to import translations from your repo. Click **Upload translations options** to access the following additional options: * **Allow target translation to match source** * **Approve added translations** #### [Push Sources](#push-sources) [Section titled “Push Sources”](#push-sources) By default, sources are not pushed to the repo with translations. Although, if you perform a source text review in your Crowdin project and would like to push the changes made to your source files on Crowdin back to your repo, click **Edit**, select *Push Sources* in the integration settings, and click **Save**. #### [Sync Schedule](#sync-schedule) [Section titled “Sync Schedule”](#sync-schedule) The synchronization is processed every hour automatically. If necessary, you can change the update interval in the integration settings. To configure the synchronization schedule – click **Edit**, scroll down to the *Sync Schedule*, set the preferred interval, and click **Save**. There are cases when it’s necessary to disable translations from being pushed to the repo temporarily. In this situation, click **Edit**, clear *Sync Schedule* in the integration settings, and click **Save**. When ready to sync translations with the repo, select the *Sync Schedule*, and click **Save**. Not depending on the synchronization settings, the source files’ changes on the repo will still be synced with Crowdin continuously. ### [Branches to Sync Automatically](#branches-to-sync-automatically) [Section titled “Branches to Sync Automatically”](#branches-to-sync-automatically) When you set up the integration, you select existing repository branches to be added to the Crowdin project. To add future branches from GitHub to Crowdin automatically, create a pattern for the branch names in the integration settings. For example, you add a pattern \**feature* in the GitHub integration settings. In this case, the future branches that contain this word at the end of the title will be added to the project. To add a pattern for branch names, follow these steps: 1. Click **Edit** in the GitHub integration section. 2. In the appeared dialog, scroll down to the *Branches to Sync Automatically*. 3. In the *Branches to Sync Automatically* field, use wildcard selectors such as `*`, `?`, `[set]`, `\` and others to identify the necessary branches. 4. Click **Save**. ### [Default Configuration File Name](#default-configuration-file-name) [Section titled “Default Configuration File Name”](#default-configuration-file-name) `crowdin.yml` is the default file name that is used for automatically synchronized branches. To change the default settings, click **Edit**, specify the preferred name in the *Default configuration file name* field in the integration settings, and click **Save**. If you don’t specify your custom configuration file name for automatically synchronized branches, and the integration doesn’t find a configuration file with the default name `crowdin.yml` in the root of the branch, these branches will be marked in the integration settings with a red icon with an exclamation mark saying “Not Ready. Check the configuration”. ## [Selecting Content for Synchronization](#selecting-content-for-synchronization) [Section titled “Selecting Content for Synchronization”](#selecting-content-for-synchronization) To make integration work, you need to specify which source files should be translated and how Crowdin should structure translated files in your repository. To make integration work in the Target file bundles mode, you need to select the required bundles that you want to push to your repository. There are two ways you can specify content for synchronization: * Configuring online * Configuring manually by creating a configuration file ### [Configuring Online](#configuring-online) [Section titled “Configuring Online”](#configuring-online) This procedure is the same for all integrations with version control systems (VCS). Check [Configuring VCS Integrations Online](/configuring-vcs-integrations-online/) to get to know how to select content for synchronization online. ### [Creating Configuration File](#creating-configuration-file) [Section titled “Creating Configuration File”](#creating-configuration-file) The configuration file `crowdin.yml` should be stored in the GitHub repository along with each separate branch that you want to translate. It should have the same structure as required for CLI, but your project’s credentials should not be stored in the file’s header for security reasons. Read more about [creating a configuration file](/developer/configuration-file/). ## [Working with Multiple Repositories within One Project](#working-with-multiple-repositories-within-one-project) [Section titled “Working with Multiple Repositories within One Project”](#working-with-multiple-repositories-within-one-project) If you’re working with a multi-platform product that has versions for different operating systems, you may want to connect multiple repositories that contain source files for each operating system. In this case, localization resources (e.g., TMs, Glossaries) and translations could be used more efficiently, reducing the time needed for project localization. To add another repository, follow these steps: 1. Open your project and go to the **Integrations** tab. 2. Click on **GitHub** in the Integrations list. 3. Click **Add Repository**. 4. Configure the integration with the new repository according to your needs and preferences. ## [Checking the Status of Synchronization](#checking-the-status-of-synchronization) [Section titled “Checking the Status of Synchronization”](#checking-the-status-of-synchronization) Once the integration is set up, all related information is stored in **Integrations > GitHub**. After the integration is connected, the settings can be updated only by the project member who configured it. All project managers except the person who configured the integration will see the **Edit** button disabled with the following message when hovering over it: `Integration was configured by {Full Name} ({username})`. By default, synchronization is processed every hour automatically. If you need to launch the synchronization immediately – click **Sync Now**.  Alternatively, if you need to sync only one branch separately, click on the needed branch and select **Sync branch**. ## [Uploading Translations from Repo](#uploading-translations-from-repo) [Section titled “Uploading Translations from Repo”](#uploading-translations-from-repo) By default, the translations stored on the repo are uploaded to Crowdin during the first synchronization only. To upload translations to Crowdin manually, click on the drop-down toggle on the **Sync Now** button, and click **Sync Translations to Crowdin**. The integration will upload existing translations to your Crowdin project.  Limitations The *Sync Translations to Crowdin* option is available for file-based projects only. ## [Q\&A](#qa) [Section titled “Q\&A”](#qa) # GitLab Integration > Synchronize files between your GitLab repository and Crowdin The GitLab integration allows you to synchronize files between your GitLab repo and Crowdin project. In file-based projects, there are two possible GitLab integration modes you can choose from: * **Source and translation files mode** – synchronize source and translation files between your GitLab repository and Crowdin project. * **Target file bundles mode** – generate and push translation files to your GitLab repository from the Crowdin project in the selected format. In this mode, integration pushes translation files and doesn’t sync sources from your repo. In cases when you perform a source text review in your Crowdin project and want to get updated source texts to your repo, you can add a source language as a target language, which will be pushed to your repo along with translations. In string-based projects, GitLab integration exclusively operates in the **Target file bundles mode**. Read more about [project types](/creating-project/#project-types). All translated and approved files (or target file bundles) are automatically merged into the `l10n` branch of the GitLab repository. ## [Connecting GitLab Account](#connecting-gitlab-account) [Section titled “Connecting GitLab Account”](#connecting-gitlab-account) 1. Open your project and go to the **Integrations** tab. 2. Click on **GitLab** in the Integrations list. 3. Click **Set Up Integration** and select **Source and translation files mode** or **Target file bundles mode** from the drop-down list to integrate via your GitLab account.  4. Then authorize the connection with Crowdin on the GitLab side:  In case the repository you need is private, and you have limited or no access to it, please ask the repository owner to provide you with an access token. Afterward, click **Use personal access token** and insert the token into the *Token* field and click **Set Up Integration**. ### [Selecting Repository](#selecting-repository) [Section titled “Selecting Repository”](#selecting-repository) In the appeared dialog, select your repository and branches that should be translated. * File-based project  It’s recommended to switch Duplicate Strings to **Show within a version branch**, so identical strings will be hidden between branches. If your source files contain strings with apparent identifiers (keys), it’s better to use a *strict* version of this option. In other cases, feel free to use a *regular* one. * String-based project  [Duplicate Strings ](/project-settings/import/#duplicate-strings) [Version Management ](/version-management/) When working with GitLab integration in the **Target File Bundles Mode**, the integration will send the completed translations from your Crowdin project without pulling sources from your repo. So when selecting a repository and branches that should be translated, you specify where the integration should put the generated bundles with translations. Read more about [configuring target file bundles for VCS integration](/bundles/#bundles-in-vcs-integrations). When you work with private integrations (e.g., integrations with self-hosted VCS), you need to add dedicated Crowdin IP addresses to the allowlist to ensure that it operates properly while staying secure. Read more about [IP Addresses](/developer/ip-addresses/#integrations). ### [Service Branches](#service-branches) [Section titled “Service Branches”](#service-branches) When translations are finished and your languages are ready to go live, Crowdin sends the merge request with translations to your version control system. For every branch that is under localization, Crowdin creates an additional service branch with translations. We don’t commit directly to the master branch so that you can verify translations first. By default, `l10n_` is added to the created service branch name. If necessary, you can easily change it. ### [Synchronization Settings](#synchronization-settings) [Section titled “Synchronization Settings”](#synchronization-settings) Configure the synchronization settings according to your needs and preferences. Limitations The *Import existing translations* and *Push Sources* options are only available for file-based projects. #### [Import Existing Translations](#import-existing-translations) [Section titled “Import Existing Translations”](#import-existing-translations) To import existing translations from your repo, select one of the following options: * **One-time translation import after the branch is connected** * **Always import new translations from the repository** By default, the first option is selected to import translations only once. Alternatively, you can clear both options if you don’t want to import translations from your repo. Click **Upload translations options** to access the following additional options: * **Allow target translation to match source** * **Approve added translations** #### [Push Sources](#push-sources) [Section titled “Push Sources”](#push-sources) By default, sources are not pushed to the repo with translations. Although, if you perform a source text review in your Crowdin project and would like to push the changes made to your source files on Crowdin back to your repo, click **Edit**, select *Push Sources* in the integration settings, and click **Save**. #### [Sync Schedule](#sync-schedule) [Section titled “Sync Schedule”](#sync-schedule) The synchronization is processed every hour automatically. If necessary, you can change the update interval in the integration settings. To configure the synchronization schedule – click **Edit**, scroll down to the *Sync Schedule*, set the preferred interval, and click **Save**. There are cases when it’s necessary to disable translations from being pushed to the repo temporarily. In this situation, click **Edit**, clear *Sync Schedule* in the integration settings, and click **Save**. When ready to sync translations with the repo, select the *Sync Schedule*, and click **Save**. Not depending on the synchronization settings, the source files’ changes on the repo will still be synced with Crowdin continuously. ### [Branches to Sync Automatically](#branches-to-sync-automatically) [Section titled “Branches to Sync Automatically”](#branches-to-sync-automatically) When you set up the integration, you select existing repository branches to be added to the Crowdin project. To add future branches from GitLab to Crowdin automatically, create a pattern for the branch names in the integration settings. For example, you add a pattern \**feature* in the GitLab integration settings. In this case, the future branches that contain this word at the end of the title will be added to the project. To add a pattern for branch names, follow these steps: 1. Click **Edit** in the GitLab integration section. 2. In the appeared dialog, scroll down to the *Branches to Sync Automatically*. 3. In the *Branches to Sync Automatically* field, use wildcard selectors such as `*`, `?`, `[set]`, `\` and others to identify the necessary branches. 4. Click **Save**. ### [Default Configuration File Name](#default-configuration-file-name) [Section titled “Default Configuration File Name”](#default-configuration-file-name) `crowdin.yml` is the default file name that is used for automatically synchronized branches. To change the default settings, click **Edit**, specify the preferred name in the *Default configuration file name* field in the integration settings, and click **Save**. If you don’t specify your custom configuration file name for automatically synchronized branches, and the integration doesn’t find a configuration file with the default name `crowdin.yml` in the root of the branch, these branches will be marked in the integration settings with a red icon with an exclamation mark saying “Not Ready. Check the configuration”. ## [Selecting Content for Synchronization](#selecting-content-for-synchronization) [Section titled “Selecting Content for Synchronization”](#selecting-content-for-synchronization) To make integration work, you need to specify which source files should be translated and how Crowdin should structure translated files in your repository. To make integration work in the Target file bundles mode, you need to select the required bundles that you want to push to your repository. There are two ways you can specify content for synchronization: * Configuring online * Configuring manually by creating a configuration file ### [Configuring Online](#configuring-online) [Section titled “Configuring Online”](#configuring-online) This procedure is the same for all integrations with version control systems (VCS). Check [Configuring VCS Integrations Online](/configuring-vcs-integrations-online/) to get to know how to select content for synchronization online. ### [Creating Configuration File](#creating-configuration-file) [Section titled “Creating Configuration File”](#creating-configuration-file) The configuration file `crowdin.yml` should be stored in the GitLab repository along with each separate branch that you want to translate. It should have the same structure as required for CLI, but your project’s credentials should not be stored in the file’s header for security reasons. Read more about [creating a configuration file](/developer/configuration-file/). ## [Working with Multiple Repositories within One Project](#working-with-multiple-repositories-within-one-project) [Section titled “Working with Multiple Repositories within One Project”](#working-with-multiple-repositories-within-one-project) If you’re working with a multi-platform product that has versions for different operating systems, you may want to connect multiple repositories that contain source files for each operating system. In this case, localization resources (e.g., TMs, Glossaries) and translations could be used more efficiently, reducing the time needed for project localization. To add another repository, follow these steps: 1. Open your project and go to the **Integrations** tab. 2. Click on **GitLab** in the Integrations list. 3. Click **Add Repository**. 4. Configure the integration with the new repository according to your needs and preferences. ## [Checking the Status of Synchronization](#checking-the-status-of-synchronization) [Section titled “Checking the Status of Synchronization”](#checking-the-status-of-synchronization) Once the integration is set up, all related information is stored in **Integrations > GitLab**. After the integration is connected, the settings can be updated only by the project member who configured it. All project managers except the person who configured the integration will see the **Edit** button disabled with the following message when hovering over it: `Integration was configured by {Full Name} ({username})`. By default, synchronization is processed every hour automatically. If you need to launch the synchronization immediately – click **Sync Now**.  Alternatively, if you need to sync only one branch separately, click on the needed branch and select **Sync branch**. ## [Uploading Translations from Repo](#uploading-translations-from-repo) [Section titled “Uploading Translations from Repo”](#uploading-translations-from-repo) By default, the translations stored on the repo are uploaded to Crowdin during the first synchronization only. To upload translations to Crowdin manually, click on the drop-down toggle on the **Sync Now** button, and click **Sync Translations to Crowdin**. The integration will upload existing translations to your Crowdin project.  Limitations The *Sync Translations to Crowdin* option is available for file-based projects only. ## [Q\&A](#qa) [Section titled “Q\&A”](#qa) # Glossary > Learn how to create, manage, and share glossaries in Crowdin With a glossary, you can create, store, and manage all the project terminology in one place. The main aim of terminology is to explain some specific terms or the ones often used in the project to be translated properly and consistently. Each glossary term is displayed as an underlined word in the Editor. Hover over the underlined term to highlight it and see its translation, part of speech, and definition (if they are provided).  ## [Creating Glossary](#creating-glossary) [Section titled “Creating Glossary”](#creating-glossary) In addition to the project glossaries that are automatically created with each project, you can create separate glossaries and populate them with content by uploading your existing glossaries in TBX, XLSX, or CSV format. These glossaries can then be assigned to the relevant projects as needed. To create a glossary, follow these steps: 1. Open your profile home page and select **Glossaries** on the left sidebar. 2. Click **Create Glossary**.  3. In the appeared dialog, name your glossary and select a default language that will be displayed first in the table of glossary records. 4. *(Optional)* Assign the glossary to the needed projects. You can skip this step and assign a glossary later. 5. Click **Create**.  [Assigning Glossary ](/project-settings/glossaries/#assigning-glossary) [Changing Default Glossary ](/project-settings/glossaries/#changing-default-glossary) ## [Managing Glossary Concepts and Terms](#managing-glossary-concepts-and-terms) [Section titled “Managing Glossary Concepts and Terms”](#managing-glossary-concepts-and-terms) Depending on your project needs, you can use a simpler approach with one term per language or make your glossary more detailed and complete using the advanced functionality that glossary concepts can offer. ### [Creating Glossary Concepts and Terms](#creating-glossary-concepts-and-terms) [Section titled “Creating Glossary Concepts and Terms”](#creating-glossary-concepts-and-terms) Concept – the highest-level terminology element that contains concept-level data (e.g., concept definition, subject, etc.), including language-level (i.e., term language) and term-level data (e.g., term, the term’s part of speech, type, etc.). Simply put, a concept incorporates glossary terms and their variations with multiple translations and other relevant information. You can specify the following concept and term details when adding glossary concepts. Concept details: * Definition – concept definition. * Subject – a branch of knowledge the concept is related to. * Translatable – specifies whether the concept could be translated into other languages. * Note – short notes about a concept that might be helpful to translators. * URL – URL to the web page with relevant information about a concept. * Figure – URL to the relevant image. Term details: * Term – specific word or phrase that is being defined. * Language – specifies the language of the term. * Part of speech – e.g., noun, verb, adjective, etc. * Type – e.g., full form, acronym, abbreviation, etc. * Status – preferred, admitted, not recommended, obsolete, draft. * Gender – term gender. * Description – term description. * Note – short notes about a term that might be helpful to translators. * URL – URL to the web page with relevant information about a term. To add a new glossary concept, follow these steps: 1. Open your profile home page and select **Glossaries** on the left sidebar. Alternatively, open your project and go to **Settings > Glossaries**. 2. Click **View Records** on the needed glossary. 3. Click **Add concept**.  4. In the appeared dialog, select the language from the drop-down menu, and specify the term and all related details. Click to detect the part of speech automatically. 5. *(Optional)* Click **Add term** to add a term variation (e.g., acronym, short form, etc.) 6. Specify the concept details. 7. Click **Create**.  To add glossary concepts via the Editor, follow these steps: 1. In the Editor, select the needed word in the source string. 2. In the appeared menu, select **Create Term**. Alternatively, you can use the keyboard shortcut to add a concept (by default, `Ctrl` +`G` ).  3. Follow the steps described in the section above. To allow translators and proofreaders to manage terms in the Editor, follow these steps: 1. Open your project and go to **Settings > Privacy & collaboration**. 2. In the [**Glossary Access Settings**](/project-settings/privacy-collaboration/#glossary-access-settings) section, select the preferred access level for project members. You can choose to allow them to manage only draft terms. When a project member adds a draft term, project managers can filter terms by draft status, review them, and make necessary modifications or add glossary concept details. Alternatively, you can grant full access, allowing them to manage all glossary terms and concept details with the same level of control as the project owner and managers. ### [Viewing and Filtering Glossary Concepts and Terms](#viewing-and-filtering-glossary-concepts-and-terms) [Section titled “Viewing and Filtering Glossary Concepts and Terms”](#viewing-and-filtering-glossary-concepts-and-terms) Once you open a glossary, you can view and filter its glossary concepts and terms using either the Concepts or Terms pages. On the Concepts page, you can view glossary content grouped as concepts (one concept per row, each term displayed in a separate language column).  On the Terms page, you can view glossary content as individual terms (one term per row) with the following details: * Term – contains either source or target language text. * Language – specifies the language of the term. * Part of speech – specifies the part of speech of the term. * Type – specifies the type of the term. * Status – specifies the status of the term. * Gender – specifies the gender of the term. * Description (context) – specifies the description of the term. * Note – specifies the note of the term. * Concept subject – specifies the concept subject of the term. * Concept definition – specifies the concept definition of the term.  By default, all glossary concepts and terms are displayed in the Concepts and Terms pages. To filter the concepts or terms displayed, click and use the available filter options: * Languages (Specific to the Terms page): All languages, specific language. * Modified: All, Custom Range. * Part of speech: All, Adjective, Adposition, Adverb, Auxiliary, Coordinating conjunction, Determiner, Interjection, Noun, Numeral, Pronoun, Proper noun, Particle, Subordinating conjunction, Verb, Symbol, Other. * Type: All, Full form, Acronym, Abbreviation, Short form, Phrase, Variant. * Status: All, Preferred, Admitted, Not recommended, Obsolete, Draft. * Gender: All, Masculine, Feminine, Common, Neuter, Other. * Author: All, particular user. To search for a particular term, type your search phrase in the **Search** field. To refine the search results, you can use the following options: * Match case * Match whole phrase * Exact match To sort concepts or terms, click **Sort by** and select one of the available options: * Text * Last modified * Created ### [Editing Glossary Concepts and Terms](#editing-glossary-concepts-and-terms) [Section titled “Editing Glossary Concepts and Terms”](#editing-glossary-concepts-and-terms) You can edit existing glossary concepts of a particular glossary. To edit a glossary concept, follow these steps: 1. Open your profile home page and select **Glossaries** on the left sidebar. Alternatively, open your project and go to **Settings > Glossaries**. 2. Click **View Records** on the needed glossary. 3. Open a glossary concept with a double-click or click **Edit**. 4. In the appeared dialog, make the necessary edits to the concept or terms and click **Save**.  ### [Deleting Glossary Concepts](#deleting-glossary-concepts) [Section titled “Deleting Glossary Concepts”](#deleting-glossary-concepts) You can delete one, multiple, or all the glossary concepts at once. To delete all the concepts from the glossary, follow these steps: 1. Select the top checkbox above the concept list. 2. Confirm the selection of all concepts. 3. Click .  ## [Uploading and Downloading Glossary](#uploading-and-downloading-glossary) [Section titled “Uploading and Downloading Glossary”](#uploading-and-downloading-glossary) You can upload existing glossaries to Crowdin or download your glossary content for backup, editing, or other purposes outside Crowdin. Glossaries can be downloaded in full or with applied filters, which is useful when you want to export only a subset of glossary concepts that meet specific criteria (e.g., by subject, status, or language). To upload or download the glossary, follow these steps: 1. Open your profile home page and select **Glossaries** on the left sidebar. Alternatively, open your project and go to **Settings > Glossaries**. 2. Click **View Records** on the needed glossary. 3. Click and select one of the following options: * **Upload** – uploads new glossary content. * **Download** – downloads the full glossary. * **Download filtered** – downloads only glossary concepts that match the applied filters or search criteria.  The project owner and managers can upload and download the glossary in the following file formats: TBX (v2), TBX (v3), CSV, XLSX. Limitations The maximum file size is 100 MB. If your file exceeds this limit, it is recommended to split it into several smaller files, and upload them one at a time. If you upload a glossary in CSV or XLS/XLSX file formats, select the language for each column and the column value (term, description, or part of speech) in the configuration dialog.  When downloading a glossary from Crowdin, some browsers may add an XML extension to the downloaded file so that the file may be named *sample.tbx.xml*. To import such a file back to Crowdin, rename it to *sample.tbx*. ### [Automatic Column Identification for Glossary in CSV and XLSX File Formats](#automatic-column-identification-for-glossary-in-csv-and-xlsx-file-formats) [Section titled “Automatic Column Identification for Glossary in CSV and XLSX File Formats”](#automatic-column-identification-for-glossary-in-csv-and-xlsx-file-formats) Once you upload your glossary file in CSV or XLSX formats, the system automatically detects the file scheme based on the column names specified in the first row. The identification is performed in a case-insensitive manner. Columns that weren’t detected automatically will be left as **Not used**/**Not chosen** for manual configuration. Automatic column identification is especially helpful when you upload glossary spreadsheets that contain many languages and additional columns (e.g., Status, Type, Gender, etc.). To get the most out of the automatic column detection, we recommend that you name the columns in your CSV or XLSX glossary files using the patterns described below: * Term details – `{column-type} [{crowdin-language-code}]` (e.g., `Term [en]`, `Description [en]`, `Part of Speech [en]`, etc.). * Concept details – `Concept {concept-details-type}` (e.g., `Concept Definition`, `Concept Subject`, `Concept Note`, etc.). To redetect the glossary file scheme, click **Detect Configuration**. ## [Sharing Glossaries](#sharing-glossaries) [Section titled “Sharing Glossaries”](#sharing-glossaries) To share your glossaries between all of the projects you own, follow these steps: 1. Open your profile home page and select **Glossaries** on the left sidebar. 2. Select **Share Glossaries**.  ## [Translating Glossary Terms](#translating-glossary-terms) [Section titled “Translating Glossary Terms”](#translating-glossary-terms) [Translate Glossary App ](https://store.crowdin.com/glossary-translate-app)The app allows you to translate your glossary terms directly in Crowdin. # Google Play Integration > Connect Google Play with Crowdin to localize your app's data With Crowdin’s Google Play integration, you can speed up the process of your app’s data localization. Once the integration is enabled, all the texts from the store page are collected in one file and added to your project in Crowdin. When translations are completed, it takes a few clicks to add them to your app’s page in the store. ## [Connecting Google Play with Crowdin](#connecting-google-play-with-crowdin) [Section titled “Connecting Google Play with Crowdin”](#connecting-google-play-with-crowdin) To connect Google Play with your project in Crowdin, follow these steps: 1. Open your project and go to the **Integrations** tab. 2. Click on **Google Play** in the Integrations List. 3. Enter the package name and click **Set Up Integration**. You can edit the package name if you entered it incorrectly and delete the integration if needed. The integration will collect the source texts into a file which will be placed in **Sources > Files**. By default, the file name is set to `google_play.xml`. ## [Publishing Translations](#publishing-translations) [Section titled “Publishing Translations”](#publishing-translations) To publish translations, follow these steps: 1. Open your project and go to **Integrations > Google Play**. 2. Click **Preview & Publish Translations**.  3. Available translations will appear accordingly to the configured [Export options](/project-settings/export/). See whether all translations look good and clear the checkbox next to the languages you don’t want to publish. Click **Next** to proceed.  4. Upload a file with your [service account credentials](#creating-service-account-credentials) and click **Publish**.  5. You can track the publishing progress in the next dialog. Once the translations are uploaded, click **Close**.  Limitations Google Play limits the number of times you can publish translations for the same language in one day. ## [Creating Service Account Credentials](#creating-service-account-credentials) [Section titled “Creating Service Account Credentials”](#creating-service-account-credentials) To publish translations from Crowdin directly to your Google Play project, you need to configure access to your Google Play Console beforehand. To create and add your service account credentials, follow these steps: 1. Link Google Play Console with Google Cloud project: * Open the Google Play Console and go to **Setup >** [**API access**](https://play.google.com/console/u/0/developers/api-access). * Link an existing project or create a new one.  2. Generate service account credentials: * Go to [**Service accounts**](https://console.developers.google.com/iam-admin/serviceaccounts). If prompted, select one of the existing projects.  * Click **Create Service Account**.  * Specify the service account name and click **Create and Continue**.  * From the **Role** list, select **Service Accounts > Service Account User** and click **Done**.  * Open the Actions menu on the created service account and select **Manage keys**.  * In the **Keys** tab, click **Add key > Create new key**.  * Select **JSON** and click **Create**.  * A JSON file that contains your service account credentials will be downloaded to your machine. 3. Grant access to your service account: * In the Google Play Console, go to **Setup >** [**API access**](https://play.google.com/console/u/0/developers/api-access) and click **Grant access** on your service account.  * In the **Account permissions** tab, select the following permissions: * View app information and download bulk reports (read-only) * Publish Play Games Services projects * Release to production, exclude devices, and use Play App Signing * Manage store presence  * Click **Invite user**. After it, you can use the file with your service account credentials to publish your translations from Crowdin to Google Play. # HIPAA Disclaimer > Description of how protected health information may be processed THIS DISCLAIMER DESCRIBES HOW PROTECTED HEALTH INFORMATION MAY BE ACCESSED, DISCLOSED, TRANSFERRED AND USED WITHIN THE COMPANY Crowdin OÜ[1](#user-content-fn-1) (hereinafter – **“Company”** or **“We”**) acknowledges its duty and responsibility to protect the privacy and security of Individually Identifiable Health Information (hereinafter – the **“IIHI”**) generally, and Protected Health Information (hereinafter the - **“PHI”**) as defined in the Health Portability and Accountability Act (hereinafter – the **“HIPAA”**) as amended by the Health Information Technology for Economic and Clinical Health (“HITECH”) Act of 2009 (Title XIII of division A and Title IV of division B of the American Recovery and Reinvestment Act “ARRA”) and the HIPAA Omnibus Rule (Effective Date: March 26, 2013) and other federal and state laws protecting the confidentiality of personal information, and under principles of general and professional ethnics. Company, acting as a Business Associate under HIPAA, also acknowledges its duty and responsibility to support and facilitate the time and unimpeded flow of health information for lawful and appropriate purposes. **Collection and Use of PHI:** We collect and use PHI only as necessary to provide our services to Covered Entities or as required by law. We will not use or disclose PHI for any other purpose without the explicit written consent of the Covered Entity. **Security of PHI:** We have implemented appropriate administrative, physical, and technical safeguards to protect the confidentiality, integrity, and availability of PHI, as required by HIPAA. We regularly review and update our security measures to ensure that they are effective and compliant with applicable laws and regulations. We have drafted our inner HIPAA Compliance Policy, which is mandatory for our employees and contractors, who works under HIPAA-related projects. **Breach Notification:** In the event of a breach of unsecured PHI, we will provide notification to the affected Covered Entity as required by HIPAA. **Business Associate Agreements:** We enter into written Business Associate Agreements with all Covered Entities that we provide services to upon their request, in order to ensure compliance with HIPAA and other applicable laws and regulations. Covered Entities that are subject to HIPAA and want to utilize Crowdin in connection with Protected Health Information (PHI) must sign Crowdin’s Business Associate Agreement. **Access to PHI:** Covered Entities and individuals have the right to access and receive a copy of their PHI that we maintain. Requests for access should be made in writing to our Privacy Officer, whose contact information is provided below. **Contact Information:** If you have any questions or concerns about our HIPAA Policy or the handling of PHI, please contact our Privacy Officer at: **Complaints:** In case you are not satisfied with the manner in which the Company as well as the Covered Enity handles your PHI, you may submit a complaint at: *** ## [Footnotes](#footnote-label) [Section titled “Footnotes”](#footnote-label) 1. Crowdin OÜ hereunder also refers to Crowdin LLC as the main subcontractor, which is subject to a similar list of obligations and responsibilities in terms of HIPAA compliance. [↩](#user-content-fnref-1) # ICU Message Syntax > Use ICU Message format to handle language-specific nuances Crowdin supports ICU Message syntax, which is used to help express the subtleties of language-specific spelling, grammar, and formatting in translations. Strings formatted in the ICU Message syntax can have different types of replacements called **arguments**. Each argument is enclosed in curly brackets and refers to a value in the input data. Arguments of the following types are supported in Crowdin: number, date, time, select, and plural. ### [ICU Message Syntax in the Editor](#icu-message-syntax-in-the-editor) [Section titled “ICU Message Syntax in the Editor”](#icu-message-syntax-in-the-editor) ICU syntax arguments are always highlighted in the [Editor](/online-editor/), so you know which part of the string shouldn’t be translated. Change the position of arguments in translation to follow the natural word order in the target language. There’s also a preview mode, that allows you to see how the translation will be displayed in the UI to make sure that all the translatable elements are translated.  [The Ultimate Guide to ICU Message Format ](https://crowdin.com/blog/2022/04/13/icu-guide)This article will cover the ICU i18n and ICU message format basics, and how Crowdin handles it. ## [Plural](#plural) [Section titled “Plural”](#plural) Plural type is used to handle plural category variations, as each language has its own set of plural categories (for example, English has “one” and “other”, while Ukrainian has “one”, “few”, “many”, and “other”). ```json You {itemCount, plural, =0 {have no projects} one {have # project} other {have # projects} }. ``` The following short tags are used to determine the plural categories: * zero * one (singular) * two (dual) * few (paucal) * many (also used for fractions if they have a separate class) * other (required—general plural form—also used if the language only has a single form) In the Editor, you don’t have to manually add or delete plural categories to the translations you are making. Just click **Copy Source**, and the source string will be copied to the translation field with the number of plural categories right for the current target language. Read more about [Language Plural Rules](https://www.unicode.org/cldr/charts/latest/supplemental/language_plural_rules.html). ## [Select Ordinal](#select-ordinal) [Section titled “Select Ordinal”](#select-ordinal) The purpose of the select ordinal type is to choose output based on the ordinal pluralization rules (1st, 2nd, 3rd, etc.) of the current target language. It is very similar to the plural type, except the value is mapped to an ordinal plural category. ```json Congrats! It's your {year, selectordinal, one {#st} two {#nd} few {#rd} other {#th} } subscription anniversary! ``` ## [Select](#select) [Section titled “Select”](#select) Select type is mostly used to represent the right gender-based inflections in the message. ```json {gender, select, male {He uses} female {She uses} other {They use} } Crowdin. ``` ## [Number](#number) [Section titled “Number”](#number) The purpose of the number type is to display different number values such as percentage, currency, and decimal numbers independently of the locale conventions for those. This enables adjustment of the message output to the number formats used in different locales. [ICU Number Skeletons](https://unicode-org.github.io/icu/userguide/format_parse/numbers/skeletons.html) are also supported. ```json The app price is {price, number, ::currency/USD} with {discount, number, percent} discount. ``` ## [Date, Time](#date-time) [Section titled “Date, Time”](#date-time) Date and time types show date and time values according to the formats preferred in the specified locales. These types can also have a style – extra information on how the value will be formatted. The following four styles can be used: short, medium, long, and full. ```json Your meeting is scheduled for {dateValue, date, long} at {timeValue, time, short} AM. ``` ## [Syntax Errors](#syntax-errors) [Section titled “Syntax Errors”](#syntax-errors) Syntax error detection significantly reduces confusion when translating strings with ICU Message syntax, as the platform automatically detects potential translation errors. If a syntax error is found, you’ll see a notice with a suggestion of what needs to be fixed.  # Integrations > Seamlessly integrate localization into any phase of your product Seamlessly integrate localization into any phase of your development cycle. Crowdin offers a wide range of integrations with the tools you already use. Automate your localization workflow and save time on manual tasks. [Crowdin Store ](https://store.crowdin.com/)Explore 700+ integrations to streamline your localization process. ## [VCS Integrations](#vcs-integrations) [Section titled “VCS Integrations”](#vcs-integrations) The key challenge engineers face is the lack of automation. Source content needs to be constantly extracted from the codebase and handed over to the translation team. Completed translations should then be integrated back into the codebase. Without an automated approach, this workflow becomes a repetitive and time-consuming exchange of files. With the automation provided by VCS Integrations, source strings are pulled automatically, ensuring they are always up-to-date for your translators. Completed translations are then pushed back to your repository as a request. [GitHub ](/github-integration/) [GitLab ](/gitlab-integration/) [Bitbucket ](/bitbucket-integration/) [Azure Repos ](/azure-repos-integration/) ## [Design](#design) [Section titled “Design”](#design) Quickly generate language-specific assets. Send content for translation with context for translators, while you’re working on the mock-ups or polishing prototypes. [Figma ](/figma-plugin/) [Sketch ](/sketch-plugin/) [Adobe XD ](/adobe-xd-plugin/) [More ](https://store.crowdin.com/categories/design) ## [Starred Apps](#starred-apps) [Section titled “Starred Apps”](#starred-apps) You can star an app by clicking the icon next to its name, either from the app list or within the app itself, allowing you to mark apps for quick access. This feature is available for integrations and tools (excluding service-related items like Webhooks, Service Logs, etc.) and is accessible to project members with the Developer role or higher. Once you star an app, it gets pinned to the top of the relevant tabs, such as **Integrations** or **Tools**. The app list is automatically sorted by starred items once you add your first favorite. Starred apps also appear as horizontal shortcut tabs at the end of the main project navigation. Clicking a shortcut opens the tab that contains the app (e.g., **Integrations**) and automatically opens the app within that tab. The tab that contains the app is highlighted as active, while the shortcut remains unhighlighted. Starring works on an individual account basis, meaning each project member will see their own starred apps in the **Integrations**, **Tools**, and project navigation, independent of other members’ selections. ## [Co-managing Crowdin Apps](#co-managing-crowdin-apps) [Section titled “Co-managing Crowdin Apps”](#co-managing-crowdin-apps) Multiple managers and developers can collaboratively manage the same Crowdin App within a project, simplifying teamwork and ensuring shared control over integrations. When an app is first configured in a project, the initial manager who logs in becomes its primary manager, with exclusive rights to log out from the app. All invited managers and developers share common app settings—meaning changes made by one manager are immediately visible to others. This approach facilitates efficient team collaboration, avoids duplication of efforts, and ensures consistent configuration across your localization workflow. ### [Inviting Another User to Manage an App](#inviting-another-user-to-manage-an-app) [Section titled “Inviting Another User to Manage an App”](#inviting-another-user-to-manage-an-app) To invite additional managers or developers to co-manage an app, follow these steps: 1. Open the app in your Crowdin project. 2. Click **Share** within the app interface. 3. Select existing project members from the user list or enter the invitee’s email to invite them as a new project manager. You can invite users with the following roles: * Owner * Managers * Developers 4. Click **Save** to send the invitation. Once invited, users will gain full access to manage and configure the app (except logging out). ### [Requesting Access to Manage an App](#requesting-access-to-manage-an-app) [Section titled “Requesting Access to Manage an App”](#requesting-access-to-manage-an-app) If you open an app that has already been configured by another manager, you’ll see a message indicating that you don’t have access. The message also displays the name of the manager currently managing the app. To request access, follow these steps: 1. Click the primary manager’s name in the message. 2. You’ll be redirected to a private conversation with the manager in Crowdin. 3. Send a message requesting access to co-manage the app. 4. The primary manager can open the app, click **Share**, and invite you from the user list. As soon as you are invited, you’ll immediately gain access to manage and configure the app (except logging out). ### [Permissions and App Management Roles](#permissions-and-app-management-roles) [Section titled “Permissions and App Management Roles”](#permissions-and-app-management-roles) All managers co-managing an app have identical permissions within it, except only the primary manager—the first to configure the app—can log out from the app. Managers can also invite Developers, who will gain similar permissions but cannot further invite other users to manage the app. Owner roles can also be invited with full permissions. ## [See Also](#see-also) [Section titled “See Also”](#see-also) [Content Delivery ](/content-delivery/) [Jira ](/jira-integration/) [Google Play ](/google-play-integration/) [Slack ](/account-notifications/#slack-integration) # Intellectual Property Rights for Translations > Learn about intellectual property rights for translations on Crowdin By this article, we would like to emphasize that Crowdin does not participate in the process of transferring any intellectual property rights between the parties (from and among project participants, translators and project owners). The responsibility for retaining/acquiring intellectual property rights rests solely with the project owner or responsible manager. Depending on whether the project is designated as a private or public, the process of the intellectual property rights transfer/license might differ. Some of the examples are listed below which you may find useful. THIS IS NOT A LEGAL ADVICE. It is strongly recommended that an appropriate legal advice shall be obtained from a legal counsel from the applicable jurisdiction. ## [Public Projects with Open Join Policy](#public-projects-with-open-join-policy) [Section titled “Public Projects with Open Join Policy”](#public-projects-with-open-join-policy) In the public project which the translators can join without a confirmation from the project owner or manager, the project owner or manager may want to post a sufficient notice with respect to the intellectual property rights emphasizing which party is the owner of the intellectual property rights and whether the intellectual property rights, including rights to translations, are transferred/licensed to the project owner or manager and terms of such transfer/license. ## [Public Projects with Moderated Join Policy](#public-projects-with-moderated-join-policy) [Section titled “Public Projects with Moderated Join Policy”](#public-projects-with-moderated-join-policy) In the public project that has a moderated join policy, the translators can join the project only after confirmation of the project owner or manager. For these projects, when a request from the translator to join the project is received, the project owner or manager may make the approval of the request conditional upon execution of the agreement with respect to the ownership of the intellectual property rights. The work flow may take the following steps: The translator requests a confirmation to join the project. The project owner or responsible manager shares the appropriate intellectual property agreement with the translator. Upon execution of the agreement by the translator, the project manager grants access to the project. ## [Private Projects](#private-projects) [Section titled “Private Projects”](#private-projects) In the private project, the project owner or responsible manager may want to ensure that the appropriate agreements with respect to the ownership of the intellectual property rights are executed before the translator is invited to participate in the project. # Introduction > Get started with Crowdin localization software and its core features > These guides will help you get started with Crowdin. Here you will find all the information you need about Crowdin and how to use it. ## [What is Crowdin?](#what-is-crowdin) [Section titled “What is Crowdin?”](#what-is-crowdin) Crowdin software is a localization management solution for agile teams. We empower companies of any shape and size to grow by reaching people who speak different languages. More than a million users from all over the world registered to deliver their websites, mobile apps, games, docs, and other content in the language of their customers. Crowdin aims to provide the latest technology solutions that make translation and localization as easy as possible. ## [What is Agile Localization?](#what-is-agile-localization) [Section titled “What is Agile Localization?”](#what-is-agile-localization) Agile localization is an approach that helps you deal with frequently updated content that you want to make available to your customers worldwide. Once you’ve decided to localize your product, it’s important to keep it that way and ensure the new content is also multilingual. This typically includes new features, product updates, documentation, websites, and other user-facing content. While you’re creating new content, translators can work on translations, so you can get work done faster by working in parallel. The latest content can be available to translators nearly instantly and updated automatically. This way, they can start translating immediately in their own translation environment. At the same time, you can quickly receive finished translations via integrations and other automation tools. This approach makes it easy to track which content has been updated, requires translation, or is ready for production. So when the new feature is ready for release, translations won’t slow you down, as they are done in parallel. ## [Features](#features) [Section titled “Features”](#features) Discover Crowdin’s core features required to help you make your products multilingual. ### [Team Cooperation](#team-cooperation) [Section titled “Team Cooperation”](#team-cooperation) Invite users Invite people to your projects and define their access level: manager, translator, proofreader. Additionally, you can configure access for translators and proofreaders to specific target languages. Basic reports View the activity within your projects (translations, approves, file updates, and more), and a list of top members. Advanced reports Calculate the approximate translation costs to plan your budget. Calculate the exact translation costs to pay your translators and proofreaders after localization is complete. Tasks Create tasks to get the needed work done in time. Choose files to assign translators and proofreaders to, and set due dates. Receive notifications about all the changes and updates in tasks. Split files between several users. Messages Send private or group messages directly within Crowdin. Translation vendor store Order professional translations from translation agency vendors available in Crowdin Store. ### [Integrations](#integrations) [Section titled “Integrations”](#integrations) VCS Sync translatable content from your GitHub/GitLab/Bitbucket/Azure Repos repository with a localization project. Receive translations as pull/merge requests. Design Localize your Figma/Sketch/Adobe XD content before design and programming start, translate assets, or do localization in parallel. Webhooks Collect information about your Crowdin project’s key events like completed translations, proofreading, and more. Mobile SDK Deliver new translations from Crowdin to your mobile application in no time with over-the-air content delivery. Get better translations with real-time translation preview, screenshot uploading, and tagging. CLI Easily integrate Crowdin with your CI server, GIT, SVN, Mercurial, and more. Connect cross-platform Crowdin CLI directly to your code repository. API Seamlessly add new content for translation to your Crowdin project, check translation status, merge new content, and more. Branches Get feature branches translated independently from the main branch. Google Play Collect content from your app’s store page to do translations and publish them in just a few clicks. Android Studio/VS Code Send your source files to your project in Crowdin and pull translated content back. Jira Software Keep track of issues reported by users working on the project translation. Each new issue in Crowdin will become a sub-task in Jira. Slack Receive notifications about completed translations, new files, mentions, and other important events in your projects. Custom file formats Request custom file format support. And more [Browse 700+ integrations and plugins](https://store.crowdin.com) ### [Translator’s Efficiency](#translators-efficiency) [Section titled “Translator’s Efficiency”](#translators-efficiency) Translation Memory (TM) TM is a database that stores the content strings translated before. Reuse translations for the same or similar content you add. Use project-based TM (available only to the assigned project) or global TM (stores translations contributed by all of the open projects). QA checks QA checks help you easily and quickly detect and avoid common mistakes. For example, they check translations for missed commas, extra spaces, typos, etc. Screenshots Screenshots are a great way to improve the quality of translations. They appear under each separate string in the Editor so translators see the exact location of a string in the UI. In-Context Visual Editor Translate texts directly within an overlay of your web application with Crowdin In-Context. Preview translations just as they would appear on your web app. Glossary Create or upload a list of terms used in your project, their definitions, and approved translations to other languages. Keep translations consistent and provide help to translators. Machine Translations Connect MT engines to get quick translations. Currently, Crowdin supports the following MT engines: Google Translate, Microsoft Translator, DeepL Translator, and Amazon Translate. Crowdsourcing Engage your community to help translate your project. Translators will be able to suggest multiple translations and vote for the best ones. Pre-translation Automatically translate source files using Machine Translation engines or translations stored in the Translation Memory. Custom Variables Specify variables that should not be translated. Custom variables will be highlighted in the source strings to translators. ### [Translation Editor](#translation-editor) [Section titled “Translation Editor”](#translation-editor) Online Editor Workspace for translators and proofreaders available online on any device, with no need to install any software. Offline translation Enable translators to download source files and make translations offline on their machines. Hidden text Hide texts that shouldn’t be translated. They are visible only to the project owner and managers. Customizable keyboard shortcuts Create shortcuts for saving translations, switching between strings, and more. Support for right-to-left languages Translate right-to-left languages as they will be displayed properly in the translation field and exported correctly. Search and replace Find specific words and phrases used in your translations and replace them in the strings you choose or all at once. Control over the length of the target segment Specify the length of translation required for specific strings. Preview for over 40 file formats Preview both the source and translated segments. Comments and issues Easily leave comments for each specific string. Translators can discuss the best translation variants, ask context-related questions, or raise issues regarding source strings or translations. Glossary highlight Glossary terms will be highlighted directly in the source string, so translators will easily notice them. Filtering options Sort strings by date added, length, file order, and others. Filter strings without translations, with comments, approved ones, added after a specific date, or use any other available filter to view only the strings you need. ### [Security & Management](#security--management) [Section titled “Security & Management”](#security--management) The security of your data is our top priority. Crowdin provides a variety of security features to help you keep your data safe. Custom domain name Easily share your project on your own URL. Invoice billing Request an invoice for your annual payments. Security log All Crowdin user accounts come with a user activity log, where you can review the performed actions. Required two-factor authentication Require users to enable two-factor authentication for their accounts. It applies to project and organization members. ### [Support](#support) [Section titled “Support”](#support) Crowdin provides a variety of support options to help you get the most out of your localization efforts. [Community Forum ](https://community.crowdin.com/)Join the Crowdin Community Forum to discuss or browse the existing topics. [Email and chat support ](https://crowdin.com/contacts)Need help finding the answers in our Knowledge Base? Get in touch with us! [Crowdin Resources ](https://crowdin.com/localization-best-practices)Get industry insights, practical tips, and draw inspiration. We prepared webinars, e-books, and other content for you. [Feature Request ](https://crowdin.com/feature-request)Have an idea for a new feature or improvement? Share it with us! [Additional Support Services ](/additional-support-services/)Need help with translations, project setup, or other services? Check out our additional support services. # Inviting People > Learn how to invite people to your translation project You can invite people to your project via the **Members** tab. The available roles include Manager, Developer, Language Coordinator, Proofreader, and Translator. For the Translator, Proofreader, and Language Coordinator roles, you can optionally limit access to specific target languages. If no languages are selected, the invitee will have access to all target languages in the project. [Roles ](/roles/)Learn more about the roles and permissions in Crowdin. There are two main methods of involving people in the project: * Email or username invitation * Sharing invitation links Limitations The daily limit for inviting users is 1,000 per account for the Proofreader and Translator roles, and 50 per account for the Manager role. ## [Email or Username Invitation](#email-or-username-invitation) [Section titled “Email or Username Invitation”](#email-or-username-invitation) To invite people via email or Crowdin username, follow these steps: 1. Open your project and go to the **Members** tab. 2. Click **Invite**.  3. In the **Invite People** dialog, click the role title to open the **Select role** dialog. 4. In the **Select role** dialog, select the desired role. For the Translator, Proofreader, or Language Coordinator roles, you can select specific target languages or leave the field empty to allow access to all. 5. Click **Save** to confirm your selection.  6. In the **Invite People** dialog, enter the emails or Crowdin usernames of the people you want to invite. 7. *(Optional)* Customize the message your invitees will receive. 8. Click **Invite**. ## [Sharing Invitation Link](#sharing-invitation-link) [Section titled “Sharing Invitation Link”](#sharing-invitation-link) To invite people via invitation link, follow these steps: 1. Open your project and go to the **Members** tab. 2. Click **Invite**. 3. Configure the preferred role and language access as described in the [Email or Username Invitation](#email-or-username-invitation) section. 4. In the **Invite People** dialog, click **Get Link**. 5. *(Optional)* Click the arrow next to **Get Link** to configure additional settings: * **Link Expiration** – choose how long the invitation link will remain active (One hour, One day, One week, One month, or One year). * **Short URL** – enable this option to generate a more compact invitation link. 6. Share the copied link with the person you want to invite.  ## [Managing Invitation Links](#managing-invitation-links) [Section titled “Managing Invitation Links”](#managing-invitation-links) To view and manage previously generated invitation links, click **Manage Links** in the **Invite People** dialog. In the **Manage links** dialog, you can: * View each link’s creation and expiration date * See the role assigned to the link (e.g., Translator, Language Coordinator) * Copy the link using the copy icon * Revoke any link by clicking **Revoke link** Once revoked, a link immediately becomes inactive and can no longer be used to join the project.  ## [See Also](#see-also) [Section titled “See Also”](#see-also) [Project Members ](/project-members/)Manage project members and their roles in your project. [Manager Permissions ](/manager-permissions/)Learn about the manager role and how to assign managers to resources. # Issues > Report and manage translation issues in the Editor Issues help ensure translation quality by giving translators, managers, and developers a structured way to report and resolve problems with strings in the Editor. Translators use them to flag unclear source strings, incorrect translations, or missing context. Managers use them to ensure that feedback is addressed quickly and that translations stay accurate. Crowdin provides issue tracking directly within the Editor, making it easy to report and resolve issues without interrupting the translation process. ## [For Translators](#for-translators) [Section titled “For Translators”](#for-translators) When working on translations in the Editor, you may occasionally come across unclear source strings, formatting questions, or existing translations that seem incorrect. In these cases, don’t guess-report the issue so it can be clarified or corrected. This section explains how to report issues effectively and shares best practices for contributing to high-quality translations. ### [Reporting Issues](#reporting-issues) [Section titled “Reporting Issues”](#reporting-issues) When you’re unsure how to translate a string or spot a mistake, it’s important to report the issue instead of guessing. To report an issue, follow these steps: 1. Open the **Comments** section. 2. Select the **Issue** checkbox. 3. Choose the issue type. 4. Add a comment explaining the problem.  Available issue types include: * **General question** – Ask anything related to the string or its translations. * **Current translation is wrong** – The existing translation is incorrect. * **Lack of contextual information** – You need clarification to understand what the string means. * **Mistake in the source string** – There’s a typo or error in the original text. Once submitted, the issue becomes visible to project managers and is marked in the Editor with a icon. ### [Editing or Resolving Your Own Issues](#editing-or-resolving-your-own-issues) [Section titled “Editing or Resolving Your Own Issues”](#editing-or-resolving-your-own-issues) If you’ve reported an issue, you can edit, resolve, or delete it at any time. To manage your issues, follow these steps: 1. Hover over your comment in the **Comments** section. 2. Select **Edit**, **Resolve**, or **Delete**.  ### [Best Practices](#best-practices) [Section titled “Best Practices”](#best-practices) Clear, specific issues help project managers and developers respond quickly and improve translation quality across the project. If you’re ever unsure, even if there’s context or a screenshot, report the issue. It’s always better to ask than assume. * **Report uncertainty** – Don’t guess. If the meaning of a string isn’t clear, create an issue. * **Describe the problem clearly** – Give enough detail for managers to understand the context and provide a useful response. * **Choose the correct issue type** – This helps route your message to the right person and speeds up resolution. * **Avoid duplicates** – If a similar issue already exists, add a comment to continue the discussion instead of creating a new one. ## [For Managers](#for-managers) [Section titled “For Managers”](#for-managers) A clear process for handling reported issues helps ensure that translators receive timely support and that translation quality stays high. This section explains how to view and manage reported issues, outlines best practices for maintaining a responsive workflow, and offers suggestions for tools and integrations that can help scale the process. ### [Managing Issues](#managing-issues) [Section titled “Managing Issues”](#managing-issues) Project managers and proofreaders can view, filter, respond to, and resolve issues reported by translators. Whether you’re working directly in the Editor or managing large-scale feedback across projects, Crowdin provides flexible tools to help you stay organized and respond efficiently. #### [Viewing and Filtering Issues](#viewing-and-filtering-issues) [Section titled “Viewing and Filtering Issues”](#viewing-and-filtering-issues) To see all strings with unresolved issues in the Editor, follow these steps: 1. Click to open the string filter. 2. Select **With Unresolved Issues**. 3. Select **All Languages** or **Current Language** to narrow results.  Strings with unresolved issues are marked with the icon. Filtering helps you prioritize which strings need attention first. To fine-tune the list of strings even further, you can use the [Advanced Filter](/online-editor/#advanced-filter). For example, to show only issues of a specific type or those reported by a certain project member. Read more about [Filtering Strings](/online-editor/#filtering-strings). #### [Responding and Resolving](#responding-and-resolving) [Section titled “Responding and Resolving”](#responding-and-resolving) You can respond to translator questions or feedback directly in the **Comments** section of the string. 1. Open the string with the reported issue. 2. Open the **Comments** section. 3. Click **Reply** on the reported issue, add your response, and press `Ctrl` +`Enter` or `⌘` +`Enter` or click **Send**. 4. Click **Resolve** once the issue has been addressed.  If needed, you can delete an issue. Hover over it to reveal the available options. ### [Best Practices](#best-practices-1) [Section titled “Best Practices”](#best-practices-1) Clear communication and consistent handling of issues help maintain translation quality and team trust. Here’s how to build an effective issue management workflow: * **Encourage a culture of asking questions** – Make it clear to translators that reporting issues is welcome and expected. It shows they care about accuracy-not that they’re slowing things down. * **Assign responsibility for responses** – Define who should handle different types of issues (e.g., source text problems, lack of context, UI-specific questions). This prevents confusion and speeds up replies. * **Aim for quick first responses** – Even a short “Looking into this” message lets translators know their feedback isn’t being ignored. * **Review issue trends regularly** – Frequent reports of the same type (e.g., unclear UI strings) can help you identify larger problems in your content or workflow. * **Close the loop** – Whenever possible, follow up in Crowdin when an issue is resolved. It builds trust and shows that feedback matters. ### [Recommended Tools and Workflows](#recommended-tools-and-workflows) [Section titled “Recommended Tools and Workflows”](#recommended-tools-and-workflows) To handle issues more efficiently especially in large or complex projects you can extend Crowdin’s functionality using integrations and automation: * Use the [Jira Integration](/jira-integration/) to automatically create and track reported issues in your development workflow. * Set up the [Slack Integration](/account-notifications/#slack-integration) to receive real-time notifications when translators report issues, so your team can respond promptly. * Use [Webhooks](/webhooks/) to trigger custom workflows when issues are created, updated, deleted, or restored in Crowdin. * Build custom issue-handling automations using the [Crowdin API](/developer/api/), such as forwarding issues to internal tools or triggering email alerts. * Browse the [Crowdin Store](https://store.crowdin.com/) to find ready-to-use apps and integrations that support issue tracking and response workflows. [Issues Manager ](https://store.crowdin.com/issues-manager)Track, filter, and resolve issues across multiple projects from a single dashboard. # Jira Integration > Keep track of source string and translation issues reported in Crowdin Integration with Atlassian Jira allows you to keep track of source string and translation issues reported by users working on the project translation in Crowdin. With current integration, the following issue types reported in Crowdin are supported for the Jira dashboard: * General issues * Lack of context issues * Translation issues * Source string issues Each synchronized issue type will have the parent task in Jira named after it. Each issue reported in Crowdin will create a sub-task in the corresponding parent task in Jira. Caution The integration disables email notifications for project issues in Crowdin that are synchronized with Jira. Once all reported issues have been resolved and their respective sub-tasks closed in Jira, you can also close their parent Jira task representing one of the Crowdin issue types. As translators report new issues in the Crowdin project, the Jira integration will create new parent Jira task with its corresponding sub-tasks for each issue in the Crowdin project.  ## [Connecting Jira with Crowdin](#connecting-jira-with-crowdin) [Section titled “Connecting Jira with Crowdin”](#connecting-jira-with-crowdin) To connect Jira with your project in Crowdin, follow these steps: 1. Open your project and go to the **Integrations** tab. 2. Click on **Jira Software** in the Integrations list. 3. Enter the Base URL of your Jira project and click **Set Up Integration**.  You’ll then access the **Providing Access to Your Jira Project** dialog. 4. Configure an **Application Link** in Jira: 1. Log in to Jira as a user with **Jira Administrator** permissions. 2. Go to **Jira settings > Products > Application links**. 3. Click **Create link**.  4. Select **Direct application link**, enter your Crowdin URL, and click **Next**.  Due to Jira functionality, it sometimes does not receive the response from the entered URL. If you see the message below, check the provided URL to be correct and click **Continue**.  5. Fill in all the required fields in dialog windows and click **Continue** to finish configuring the link: * Application name: Crowdin Integration * Application type: Generic Application * Select **Create incoming link** and click **Continue**  * Consumer Key: Crowdin * Consumer Name: Crowdin * Public Key: copy it from the **Providing Access to Your Jira Project** dialog in Crowdin  Click **Continue** to finalize the Application Link setup. 5. Go back to Crowdin and click **Next** in the **Providing Access to Your Jira Project** dialog.  6. Allow read and write access to project data in Jira. Crowdin will use this access to help the integration run correctly.  7. Choose the Jira project key, select types, and configure settings of Crowdin issues that you’d like to be synchronized with your Jira project. Jira issue settings available are: * Type * Subtask Type * Priority * Assignee * Labels (Optional) * Status – used to select the Jira status value that will trigger the closure of a related string issue in the Crowdin project. 8. Click **Save**.  ## [Synchronizing Issues](#synchronizing-issues) [Section titled “Synchronizing Issues”](#synchronizing-issues) Once you set up the integration, you can synchronize already existing issues in Crowdin (if any). A short message would tell you how many issues aren’t synchronized yet. To synchronize them, click **Sync Issues**.  ## [Managing Jira Integration Settings](#managing-jira-integration-settings) [Section titled “Managing Jira Integration Settings”](#managing-jira-integration-settings) To change the integration settings, click **Settings** and apply the necessary changes. Updated settings will apply only to the newly synchronized issues. All the issues synchronized before will remain without any changes. ## [Deleting Integration](#deleting-integration) [Section titled “Deleting Integration”](#deleting-integration) To delete the integration, click **Delete Integration**. # Machine Translation > Learn how to configure machine translation engines in Crowdin Machine translation engines integrated with Crowdin provide translation suggestions from services like Google Translate and AutoML Translation, Microsoft Translate, and others. MT suggestions are displayed in the Editor’s TM and MT Suggestions section in the order of the engines’ configuration dates. To prioritize a specific engine’s suggestions, configure that engine first. Also, you can perform [Pre-Translation](/pre-translation/) using MT engines.  [Add More Machine Translation Engines ](https://store.crowdin.com/tags/machine-translation)Install more machine translation engines from the Crowdin Store. By default, machine translations are enabled for each project, but it is required to configure the translation engines before the project members can use them. If you want to disable this option for specific projects, clear **Show machine translation suggestions** in [Project Settings](/project-settings/machine-translation/). To configure the machine translation engines, follow these steps: 1. Open your profile home page and select **Machine Translation** on the left sidebar. 2. Click toward the MT engine you want to configure and select **Edit**. Alternatively, just double-click on the needed MT engine. 3. Select **Enabled**. 4. Enter the credentials for the selected translation engine. 5. *(Optional)* In the **Advanced settings** section, you can configure the following options: * Select the languages for which the MT engine should provide translations. Alternatively, leave empty to enable all languages. * Select the projects in which you want to use the MT engine. Alternatively, leave empty to enable it for all projects. 6. Click **Update**. Caution Machine translation engines must be configured using the project owner’s account. ### [Microsoft Translator](#microsoft-translator) [Section titled “Microsoft Translator”](#microsoft-translator) Go to [Windows Azure](https://portal.azure.com/#blade/HubsExtension/BrowseAll) to access your Microsoft Translator API subscription key. Translator Text API offers a free tier with 2,000,000 translated characters. [How to sign up for the Microsoft Translator Text API ](https://docs.microsoft.com/en-us/azure/cognitive-services/translator/translator-text-how-to-signup) ### [DeepL Translator](#deepl-translator) [Section titled “DeepL Translator”](#deepl-translator) DeepL API is accessible only with the DeepL API Free and Pro subscription plans ([For developers](https://www.deepl.com/pro.html#developer) tab). Navigate to the [DeepL Pro Account page](https://www.deepl.com/pro-account.html) to get a unique Authentication Key. Please note that the DeepL API plan is the only plan that provides this feature. If you’re subscribed to a different subscription plan, you can switch to the DeepL API plan in your [personal account settings](https://www.deepl.com/pro-account.html). DeepL also provides a [simulator](https://www.deepl.com/docs-api/simulator) that allows you to check your Authentication Key in action. ### [ModernMT](#modernmt) [Section titled “ModernMT”](#modernmt) ModernMT Real time translation API is accessible with the Real time or Human-in-the-loop subscription plans. Navigate to the [ModernMT Dashboard](https://www.modernmt.com/dashboard/) to get your License key. If you’re subscribed to a different subscription plan, you can switch to the Real time or Human-in-the-loop plan via the [Manage Plan](https://www.modernmt.com/dashboard/manage-plan) page. ### [Amazon Translate](#amazon-translate) [Section titled “Amazon Translate”](#amazon-translate) The free version of Amazon Translate is available for 12 months. Afterward, you will need to pay for the number of characters translated. Crowdin uses Standard Text Translation type provided by Amazon Translate. Read more about [available Amazon Translate pricing options](https://aws.amazon.com/translate/pricing/). Read more about [obtaining your access key](https://docs.aws.amazon.com/general/latest/gr/aws-sec-cred-types.html#access-keys-and-secret-access-keys) needed for Amazon Translate integration. To use your [Custom Terminology](https://docs.aws.amazon.com/translate/latest/dg/how-custom-terminology.html), follow these steps: 1. Specify your AWS Region (e.g., us-east-2). 2. Select your Custom Terminology from the respective drop-down menu. ### [Google Translate](#google-translate) [Section titled “Google Translate”](#google-translate) To use Google Translate, you shall have a Google Cloud account with an active billing profile. Cloud Translation is priced monthly based on usage. [Learn more](https://cloud.google.com/translate/pricing). To obtain the API key necessary for integration, follow these steps: 1. Go to [Google Cloud Console](https://console.cloud.google.com/). Log in to the existing Google Cloud account or set up a new one. 2. Select an existing project or add a project using the **New Project**. 3. Go to [API & Services > Library](https://console.cloud.google.com/apis/library) and search for *Cloud Translation API*. 4. Click **Enable**. 5. Go to [API & Services > Credentials](https://console.cloud.google.com/apis/credentials/) and click **Create credentials > API key**. 6. Copy the API key and click **Close**. ### [Google Cloud AutoML Translation](#google-cloud-automl-translation) [Section titled “Google Cloud AutoML Translation”](#google-cloud-automl-translation) To use AutoML Translation, you shall have a Google Cloud account with an active billing profile. Google AutoML Translation is priced monthly based on how many characters you send for translation. [Learn more](https://cloud.google.com/translate/automl/pricing#translation_costs). To create a service account key and obtain the necessary credentials for integration, follow these steps: 1. Go to [Google Cloud Console](https://console.cloud.google.com/). Log in to the existing Google Cloud account or set up a new one. 2. Select an existing project or add a project using the **New Project**. 3. Go to [API & Services > Library](https://console.cloud.google.com/apis/library) and search for *Cloud AutoML API*. 4. Click **Enable**. 5. The next step is to create a service account private key pair. The service account is used by Crowdin. Applications use service accounts to make authorized API calls. To set up authentication and create your private key, follow these steps: 1. Go to [API & Services > Credentials](https://console.cloud.google.com/apis/credentials/). 2. Click **Create credentials > Service account**. 3. In the *Service account name* field, enter a name that describes what this service account will do. 4. Click **Create and continue**. 5. From the *Role list*, select *Project* > *Cloud Translation API Editor* and click **Continue**. 6. Click **Done**. 7. In the [API & Services > Credentials](https://console.cloud.google.com/apis/credentials/), click on the created service account. 8. Switch to the **Keys** tab. 9. Click **Add key > Create new key**. 10. Select **JSON** and click **Create**. A JSON file that contains your key will be downloaded to your computer. #### [Google Cloud AutoML Custom Glossary Configuration](#google-cloud-automl-custom-glossary-configuration) [Section titled “Google Cloud AutoML Custom Glossary Configuration”](#google-cloud-automl-custom-glossary-configuration) Google Cloud AutoML custom glossary allows you to translate your domain-specific terminology consistently. To configure your Google Cloud AutoML custom glossary, follow these steps: 1. Open **Resources** and select **Machine Translation**. 2. In the Google AutoML Translation section, upload your JSON credentials. 3. Specify your Resource Location (e.g., us-central1). 4. Select your Glossary from the respective drop-down menu. 5. (Optional) Specify your Custom Model. If needed, configure language mapping between Custom Model and Crowdin languages.  ## [MT Engine IDs](#mt-engine-ids) [Section titled “MT Engine IDs”](#mt-engine-ids) Once you specify your MT engine credentials, the system automatically assigns a unique MT engine ID. Later on, you can use these IDs in API requests for pre-translation via machine engines. You can find the MT engine ID on the **Machine Translation** tab of your profile after opening the engine details. Alternatively, you can also [get your MT engine IDs via API](/developer/api/v2/#tag/Machine-Translation-Engines/operation/api.mts.getMany). ## [Clearing MT Engine Cache](#clearing-mt-engine-cache) [Section titled “Clearing MT Engine Cache”](#clearing-mt-engine-cache) When MT engines are updated with new features or models, cached translations in Crowdin may no longer reflect the latest translation capabilities. To display updated translations in the Editor’s **TM and MT Suggestions** section, clear the MT engine cache. This can be especially useful if you’ve already viewed certain strings in the Editor, as Crowdin stores cached MT suggestions for those strings. To clear the cache for your configured MT engine, follow these steps: 1. Open your profile home page and select **Machine Translation** on the left sidebar. 2. Click on the needed MT engine in the list. 3. Click **Clear cache**. ## [See Also](#see-also) [Section titled “See Also”](#see-also) [Pre-Translation ](/pre-translation/)Speed up the translation process and ease the work of translators. [Project Settings ](/project-settings/machine-translation/)Configure machine translation settings for your project. # Manager Permissions > Learn about the manager role and how to assign managers to resources In Crowdin, you can assign managers to projects or localization resources (e.g., TMs, Glossaries). [Roles ](/roles/)Learn more about the roles and permissions in Crowdin. ## [Adding Managers to a Project](#adding-managers-to-a-project) [Section titled “Adding Managers to a Project”](#adding-managers-to-a-project) There are two possible ways to add a manager to your Crowdin project. You can invite managers via the project’s **Members** tab or add them via your profile’s **Managers** section. Read more about [Inviting People](/inviting-people/). To add a new manager to your projects via the **Managers** section, follow these steps: 1. Open your profile home page and select **Managers** on the left sidebar. 2. Click **Add Manager**.  3. In the appeared dialog, specify the manager’s email or username.  4. (Optional) Enter a message your invitee will receive. 5. In the **Projects** tab, select the projects you’d like to assign to that manager. 6. Click **Add**. ## [Adding Managers to TMs and Glossaries](#adding-managers-to-tms-and-glossaries) [Section titled “Adding Managers to TMs and Glossaries”](#adding-managers-to-tms-and-glossaries) To assign a new manager to TMs and Glossaries, follow these steps: 1. Open your profile home page and select **Managers** on the left sidebar. 2. Click **Add Manager**.  3. In the appeared dialog, specify the manager’s email or username.  4. (Optional) Enter a message your invitee will receive. 5. In the **TM** and **Glossaries** tabs, select the localization resources you’d like to assign to that manager. 6. Click **Add**. ## [Editing Manager Permissions](#editing-manager-permissions) [Section titled “Editing Manager Permissions”](#editing-manager-permissions) If you’d like to edit manager permissions, follow these steps: 1. Open your profile home page and select **Managers** on the left sidebar.  2. Double-click on the needed manager in the list. 3. In the appeared dialog, modify the manager’s permissions according to your preferences.  4. Click **Save**. If you want to completely remove a manager and revoke their access to the projects, TMs, or Glossaries, select the needed manager in your profile’s **Managers** section and click **Remove**. # Messages > Communicate with translation project members Use **Conversations** to communicate with other project members. Create one-to-one or group conversations, each with a subject to help you easily navigate between chats.  ## [Creating a New Conversation](#creating-a-new-conversation) [Section titled “Creating a New Conversation”](#creating-a-new-conversation) To create a new conversation, follow these steps: 1. Open **Conversations**. 2. Click **Create Conversation**. 3. Filter users by: * project, role, language * recent contacts – users you already have conversations with 4. Select the users you want to message. 5. Click **Go**.  ## [Managing Conversations](#managing-conversations) [Section titled “Managing Conversations”](#managing-conversations) To manage a conversation, click and choose one of the following options: * *Change Subject* – displayed to all participants to help organize conversations. * *Mute Conversation* – stop receiving notifications about new messages. * *Add Users* – participants from common projects. A new conversation will be created with the new user set.  Limitations Deleting conversations is currently not supported. This functionality is planned for future updates. ## [Messages](#messages) [Section titled “Messages”](#messages) To manage a message, hover over it, click and select the needed option. The following actions are available: * *Share* – forward the message: * in the same conversation * to another conversation * to a user you’ve previously messaged * *Mark Unread* – mark the message as unread to return to it later. * *Edit* – available for your own messages. * *Delete* – available for your own messages. * *Report Spam* – available for messages from others.  ## [Unread Messages](#unread-messages) [Section titled “Unread Messages”](#unread-messages) Unread messages are indicated by a counter displayed: * next to each conversation’s subject, showing the number of unread messages in that conversation * at the top of the page next to the *Messages* icon, showing the total number of unread messages across all conversations # Migrating to Crowdin > Migrate your localization projects to Crowdin Crowdin provides team cooperation features (e.g., inviting project members, defining permission levels, tasks, messages, etc.), workflow automation, integrations and plugins, and many more features you would need for efficient project localization. To start your migration, you can use the following step-by-step migration instructions. ## [In Your Previous Translation Tool](#in-your-previous-translation-tool) [Section titled “In Your Previous Translation Tool”](#in-your-previous-translation-tool) To start your migration, you can use the following step-by-step migration instructions. 1. **Download source files**.\ In most cases, you’ll have them on your machine/server, so this step is optional. 2. **Download translations**.\ Download all the latest translations you have at the moment of transition. 3. **Download TM and Glossary**.\ Download the translation memory and glossary so your translators can reuse them in your Crowdin projects. ## [In Crowdin](#in-crowdin) [Section titled “In Crowdin”](#in-crowdin) #### [Sign up and create your localization project](#sign-up-and-create-your-localization-project) [Section titled “Sign up and create your localization project”](#sign-up-and-create-your-localization-project) Sign up or log in if you already have your Crowdin account and [create a project](/creating-project/) to which you’ll migrate your data. #### [Upload source files](#upload-source-files) [Section titled “Upload source files”](#upload-source-files) There are a couple of ways you can upload your source files to the Crowdin project. Use one of the following options: * via UI. * via direct integration with external services (e.g., GitHub, GitLab, etc.) Explore available integrations on the [Crowdin Store](https://store.crowdin.com/). * via Console Client (CLI). * via API. Read more about [Uploading Source Files](/uploading-files/). #### [Upload Existing Translations](#upload-existing-translations) [Section titled “Upload Existing Translations”](#upload-existing-translations) Upload your existing translations to ensure that your previous work won’t be lost and that you continue from where you performed the transition. If you plan to use integrations with GitHub, GitLab, or other services, your existing translations could be uploaded in an automated way. Read more about [Uploading Existing Translations](/uploading-translations/). #### [Upload TM and Glossary](#upload-tm-and-glossary) [Section titled “Upload TM and Glossary”](#upload-tm-and-glossary) If you have [Translation Memory](/translation-memory/) (TM) and [Glossary](/glossary/) from your previous translation tool, feel free to upload them to your Crowdin project. These localization resources might greatly help your translators during the translation process and ensure high-quality translations. ## [Assistance from our team](#assistance-from-our-team) [Section titled “Assistance from our team”](#assistance-from-our-team) If you require any assistance during the migration process, our team is ready to help you with any step. For any guidance, feel free to [contact us](https://crowdin.com/contacts). ## [See Also](#see-also) [Section titled “See Also”](#see-also) [For Managers ](/for-managers/)Read our quick guide for a seamless localization setup. [Migrating to Crowdin Enterprise ](/enterprise/migrating-to-crowdin-enterprise/#from-crowdin)Learn how to migrate your projects from Crowdin to Crowdin Enterprise. # Offline Translation > Downloading and uploading files for offline translation Offline translation allows you to work on project files outside Crowdin using your preferred desktop CAT tools. Once translations are completed, you can upload them back to the project. This option is available only if downloads are enabled in the [Project Settings](/project-settings/privacy-collaboration/#privacy) by the project manager. ## [Downloading Files](#downloading-files) [Section titled “Downloading Files”](#downloading-files) You can download each file separately (in original or XLIFF format), download filtered strings (in XLIFF format), or download all files for a specific language (in original or XLIFF format). It could be done via the Editor or the language page. [XLIFF File Format Details ](https://store.crowdin.com/xliff) ### [Downloading a Single File via Editor](#downloading-a-single-file-via-editor) [Section titled “Downloading a Single File via Editor”](#downloading-a-single-file-via-editor) To download a single file to translate offline, follow these steps: 1. Open the necessary file in the Editor. 2. Click the Main menu in the upper-left corner. 3. In the *File* menu, select **Download** or **Export in XLIFF**.  ### [Downloading a Single File via Language Page](#downloading-a-single-file-via-language-page) [Section titled “Downloading a Single File via Language Page”](#downloading-a-single-file-via-language-page) 1. Open your project and select a language. 2. Click next to the file you want to download. 3. Select **Download** or **Export in XLIFF**.  ### [Downloading All Files for a Specific Language](#downloading-all-files-for-a-specific-language) [Section titled “Downloading All Files for a Specific Language”](#downloading-all-files-for-a-specific-language) To download all the project files for a specific language, follow these steps: 1. Open your project and select a language. 2. Click . 3. Select **Download translations** or **Export in XLIFF**.  Using the **Download translations** option, you’ll get a ZIP archive with all the project files containing translations in the original format. This is useful if you want to test the localized version of your product. The **Export in XLIFF** option provides a single file containing all source strings and completed translations. This method is more convenient for offline translation in CAT tools, as it doesn’t require opening and exporting files individually. Most desktop localization tools support the XLIFF format. ### [Downloading Filtered Strings in XLIFF](#downloading-filtered-strings-in-xliff) [Section titled “Downloading Filtered Strings in XLIFF”](#downloading-filtered-strings-in-xliff) You can also export strings based on specific criteria. For example, you may want to export only untranslated strings, strings translated by a certain user, or strings with comments. To download filtered strings, follow these steps: 1. Open the necessary file in the Editor. 2. Apply filters based on your desired criteria. 3. Click the Main menu in the upper-left corner. 4. In the *File* menu, select **Export Filtered in XLIFF**.  If you are in the [Multilingual (Grid)](/online-editor/#multilingual-mode-grid) mode of the Editor, click the drop-down arrow next to a target language’s column and select **Export Filtered in XLIFF**.  Read more about [Online Editor](/online-editor/). ## [Uploading Translations](#uploading-translations) [Section titled “Uploading Translations”](#uploading-translations) After completing translations offline, you can upload them back to the project in the original or XLIFF format. Upload can be done via the Editor or the language page. ### [Uploading Translations via Editor](#uploading-translations-via-editor) [Section titled “Uploading Translations via Editor”](#uploading-translations-via-editor) To upload a file with translations, follow these steps: 1. Open the needed file in the Editor. 2. Click the Main menu in the upper-left corner. 3. In the *File* menu, select **Upload Translations**.  4. Adjust the [Advanced Import Settings](#advanced-import-settings) as needed. 5. Click **Select File** and choose the file with translations from your device. If you are in the [Multilingual (Grid)](/online-editor/#multilingual-mode-grid) mode of the Editor, click the drop-down arrow next to a target language’s column and select **Upload Translations**.  Read more about [Online Editor](/online-editor/). ### [Uploading Translations via Language Page](#uploading-translations-via-language-page) [Section titled “Uploading Translations via Language Page”](#uploading-translations-via-language-page) 1. Open your project and select a language. 2. Click next to the file you want to upload translations to. 3. Select **Upload Translations**.  4. Adjust the [Advanced Import Settings](#advanced-import-settings) as needed. 5. Click **Select File** and choose the file with translations from your device. ### [Uploading XLIFF Translations](#uploading-xliff-translations) [Section titled “Uploading XLIFF Translations”](#uploading-xliff-translations) Once you’ve finished translating an XLIFF file exported from the project, you can upload the completed translations back to Crowdin using the following steps: 1. Open your project and select a language. 2. Click . 3. Select **Upload XLIFF Translations**.  4. Adjust the [Advanced Import Settings](#advanced-import-settings) as needed. 5. Click **Select File** and choose the XLIFF file with translations from your device. ### [Advanced Import Settings](#advanced-import-settings) [Section titled “Advanced Import Settings”](#advanced-import-settings) When uploading translations, you can adjust the following import options to control how the system handles the new content: * **Allow target translation to match source** – Enable this if the translation is intentionally the same as the source (e.g., for product names or code terms). * **Approve added translations** – Automatically approve the uploaded translations if you’re confident in their accuracy. * **Translate hidden strings** – Include strings that are hidden from the Editor but still require translation (e.g., for system use or placeholders). # Editor Overview > Increase your productivity with the Crowdin Editor The Editor is the main place in Crowdin where project members can work on translations. It allows users to suggest, vote on, review, and approve translations online. Using the Main menu in the upper-left corner, you can switch between files for translation, change translation languages, contact a manager, change the view, and access help materials. ## [Core Features](#core-features) [Section titled “Core Features”](#core-features) The Editor provides all the necessary tools for translators and proofreaders, including: * List of strings available for translation, which may vary in different [Editor modes](#editor-modes). * Context, labels, and additional information to guide the work. * String search and filtering options for efficient translation management. * [AI Assistant](/crowdin-ai/#using-ai-in-the-editor), [Translation Memory (TM)](/translation-memory/) suggestions, and [Machine Translation (MT)](/machine-translation/) suggestions. * [Glossary](/glossary/) terms to ensure consistency. * Comments section for collaboration and reporting issues.  ### [String List](#string-list) [Section titled “String List”](#string-list) This section displays the list of strings, with the active one highlighted. Strings are text elements that are either individual words, phrases, or sentences. Some strings might have replacement tokens (e.g., 0, 1, %1, etc.) or elements of the [ICU message syntax](/icu-message-syntax/). Such items themselves should not be translated but are used by the website code to dynamically insert some information into strings. To work with such strings, you should copy the source string and translate only the real words. Strings can have the following statuses: * \- untranslated * \- partially translated (if some of the plural forms are not translated) * \- translated * \- partially approved (if some plural forms are not approved) * \- approved * \- hidden (visible only for project managers and proofreaders) There also might be the following icons besides strings: * \- the string has comments from contributors * \- the string has an unresolved issue * \- the string has labels #### [Suggesting Translations](#suggesting-translations) [Section titled “Suggesting Translations”](#suggesting-translations) To suggest a translation, select a string from the list and enter your suggestion in the field next to the original text. When you’re done, click **Save**. Your suggestion will be added to the string’s translation suggestions list, and you’ll automatically move on to the next string.  #### [Proofreading](#proofreading) [Section titled “Proofreading”](#proofreading) Review the translations to make sure they are ready for export, and click *Approve* icon next to the suggestion to approve each translation separately. To approve all or a couple of the strings at once, check the boxes on the left and then click **Approve**.   #### [WYSIWYG File Preview](#wysiwyg-file-preview) [Section titled “WYSIWYG File Preview”](#wysiwyg-file-preview) When translating the content of an HTML, XML, TXT, DOCX, XLSX, HAML, Web XML, Markdown, MDX, DITA, Wiki, ADOC, Coffee, FTL, JS, TS, and FTLH file formats, you can toggle a bottom panel (for Side-by-side and Multilingual modes) to see a file preview (i.e., WYSIWYG). For Comfortable mode, the file preview is displayed by default when working with the formats mentioned above. The string status is indicated by the following colors: * Red - untranslated * Blue - translated * Light-green - approved * Gray - not for translation An active string is highlighted in yellow.  The following options are available to manage the above view: * \- *Load basic list view*. Use it to switch to a standard mode and see a list of strings (Comfortable mode only). * \- *Highlight untranslated, translated, and approved strings*. Use it to toggle the color highlighting of strings on and off. * \- *Show translation preview*. Use it to toggle the translation preview mode on and off. * \- *Scale Toggle*. Use it to toggle between a zoomed-in and zoomed-out view (Comfortable mode only). #### [String Search](#string-search) [Section titled “String Search”](#string-search) To find specific strings in the Editor, type your query into the search field at the top of the string list. Use the keyboard shortcut (by default, `Ctrl` +`F` or `⌘` +`F` ) to instantly focus on the search field. Depending on the content you open in the Editor, the search will apply to the currently open file, folder, or all strings in the project. To refine your search results, click the **Search filter** icon next to the search field. This will open a drop-down menu with the following filters and options:  ##### [Search in](#search-in) [Section titled “Search in”](#search-in) Define the scope of your search by selecting one of the following criteria: * *Everything* – search through source texts, translations, context, and identifiers. * *Strings* – search through source texts only. * *Translations* – search through translations only. * *Context* – search through string context only. * *Identifier (Key)* – search through string identifiers only. ##### [Options](#options) [Section titled “Options”](#options) Refine your search further with these options: * *Match case* – finds only strings written in the same case. For example, a search for `Work` will find `Work`, `Works`, and `Working`, but not `work`. * *Match whole phrase* – finds strings that contain the search phrase in the exact order. For example, a search for `Machine Translation` will find `Machine Translation` or `machine translation`, but not `Translation Machine`. * *Exact match* – finds only strings that are identical to the search phrase. For example, a search for `Work` will find `Work` or `work`, but not `Works` or `Working`. You can combine *Match case* with either *Match whole phrase* or *Exact match*. Note that *Match whole phrase* and *Exact match* are mutually exclusive. The search phrase is limited to 128 characters. If you use a search phrase longer than 128 characters, it will be automatically truncated to the maximum allowed length. You can also find a specific string by its internal numeric identifier (a number automatically assigned by Crowdin). To do so, type the numeric ID (e.g., `34354`) into the search field without quotation marks to get an exact match. To search for the occurrences of the number in the text or context, enclose it in quotation marks (e.g., `"34354"`). #### [Filtering Strings](#filtering-strings) [Section titled “Filtering Strings”](#filtering-strings) To filter the strings displayed in the left sidebar, click and select the preferred filter option. Available filter options: * *Show All* – Show all strings from the open file/folder in their original order. * *All, Untranslated First* – Show all strings from the opened file/folder. Untranslated strings are displayed at the top of the list, followed by translated strings, and then approved ones are displayed at the bottom of the list. * *Untranslated* – Show only strings without any translations. * *Need to Be Voted* – Show already translated strings. * *Not Approved* – Show strings that are already translated but not yet approved by a proofreader. * *Approved* – Show only strings with approved translations. * *QA issues* – Show strings with no QA issues or with unresolved QA issues in the current language. * *Machine Translation* – Show strings that are translated by TM or MT suggestions without changes. Often these strings require additional review. * *With Comments* – Show strings that have comments. * *With Unresolved Issues* – Show strings with unresolved issues in the current language or all languages. * *Hidden* – Show strings that are hidden from translators. Strings can be hidden by project managers or automatically hidden by Crowdin when they are marked as duplicates. * *Advanced Filter* – A filter that allows you to configure custom filtering and sorting parameters. * *AI/CroQL Filter* – An AI-powered filter that allows you to create custom queries using the [Crowdin Query Language (CroQL)](/developer/croql/) for enhanced string filtering. Permissions Some of the filter options may be available only to project members with manager permissions (or higher).  ##### [Verbal Expressions](#verbal-expressions) [Section titled “Verbal Expressions”](#verbal-expressions) Verbal expressions allow you to search for strings that match specific patterns, such as formatting, punctuation, or variable placement. This feature is available in the [Advanced Filter](#advanced-filter). Caution When you enable verbal expressions, you can’t use the regular string search at the same time. [Expression Syntax Elements ](/expression-syntax-elements/)Learn how to build and use verbal expressions with practical examples. ### [Plural Forms](#plural-forms) [Section titled “Plural Forms”](#plural-forms) Some strings may have plural forms. Depending on the language, the number of plural forms may vary. For example, Chinese has one plural form, English has two plural forms, and other languages may have up to six plural forms. Crowdin works with plural forms according to the CLDR Language Plural Rules. Read more about [CLDR Language Plural Rules](https://www.unicode.org/cldr/charts/latest/supplemental/language_plural_rules.html). If a string has multiple plural forms, all variants of the string are displayed in the section where you type in translations. Enter translations in the appropriate sections that display the plural forms of the target language.  ### [QA Checks](#qa-checks) [Section titled “QA Checks”](#qa-checks) You might also get automatic Quality Assurance (QA) check pop-up messages to avoid some translation inaccuracy. For example, you can see notifications about inconsistency in punctuation, space mismatch, missing variables, and more.  ### [String Menu](#string-menu) [Section titled “String Menu”](#string-menu) Clicking in the upper-right allows you to: * **Remove Approval** – Remove the approval for a translation, reverting its status to unapproved. (Available for proofreaders or higher.) * **Remove Translation** – Clear translations for the selected strings along with the associated TM records. Duplicate translations from master strings remain unaffected. * **Hide/Make Visible** – Toggle the visibility of a string for translators. Hidden strings are accessible only to project managers or higher. * **Pre-translate** – Initiate [pre-translation](#pre-translation-in-the-editor) directly in the Editor using Translation Memory (TM), Machine Translation (MT), or AI. * **Copy String URL** – Access a specific string using its unique link or share it with colleagues. * **Copy Source Skeleton** – Copy untranslatable elements to the translation section. Useful when translating strings with ICU message syntax or HTML tags. * **Clear Selected Input** – Clear the translation field for the selected string. * **Translation History** – View all the modifications made to the string. * **View String In Context** – Display the string along with other strings surrounding it in the source file, helping you understand its context better. * **Labels** – Add or manage labels assigned to the string, helping to categorize or identify it for specific purposes. * **Max. Length** – View and edit the maximum character length allowed for the string translation. Clicking this option opens a modal with the following settings: * **Proportional to source texts** – Set the maximum length as a percentage of the source text length. Use the slider or manually enter a percentage (e.g., 100%, 150%, 200%) to define the limit. * **Fixed max. length** – Specify an absolute character limit for the string translation. * **Unlimited** – Allow translations of any length without restrictions. * **Delete String** – Permanently remove the string from the project. (Available to project members with manager permissions or higher.) Permissions Some of the string menu options may be available only to project members with manager permissions (or higher). In the translation window, you will also see the *Maximum length of translation* limit if it’s exceeded.  Additional action buttons available when translating a string: * \- *Copy Source*. Use it to keep the initial string structure while translating messages with replacement tokens or elements of ICU message syntax. * \- *Clear*. Use it when you need to clear the translation field quickly. Alternatively, use the *Clear Selected Input* option from the string menu. * \- *Text selection mode*. Use it when you want to copy a part of the translation from Translation Memory (TM) or Machine Translations (MT) (Comfortable mode only). ### [Context and Translations](#context-and-translations) [Section titled “Context and Translations”](#context-and-translations) This section contains the resources that might be useful: * Context, labels, screenshots, and additional information to guide the work. * Translations by other project members * Translation Memory (TM) suggestions * Machine Translation (MT) suggestions * Translations to other languages Click on one of the suggestions, and it will automatically appear in the translation field. Refer to it as a basis for your own suggestions. TM suggestions may include additional details such as the TM name, match percentage, creation date, and, if available, the name of the contributor who originally submitted the translation (displayed as full name and username, e.g., *by Michael Ross (m.ross)*). This information helps provide more context about the source and relevance of each suggestion. To quickly copy the TM or MT suggestion to the translation field and save it, click **Use and Save** on the desired suggestion. *Other Languages* section allows you to check the string translations into other target languages. This can be a useful tip for multilingual people and while translating dialects of a language.  #### [Voting](#voting) [Section titled “Voting”](#voting) If you see that there is already a correct suggestion, vote for it by clicking the *plus* sign if you like the translation, or the *minus* sign if you don’t think the translation is correct. Translations that receive the most positive votes will have a higher rating and will appear at the top of all available translations for the string.  #### [Requesting Context](#requesting-context) [Section titled “Requesting Context”](#requesting-context) Within the **Context & Translations** section, you can find the context for each string, which may include technical details, a description of where the string appears in the product, or a screenshot showing its location in the user interface. If a string lacks context and its meaning is unclear, click **Request** to notify a project manager that additional explanation is needed.  ### [Comments](#comments) [Section titled “Comments”](#comments) Using the *Comments* section, you can discuss the meaning of the source string or other related questions. It is recommended to use a source language of the project so other translators can understand it. Use ”@” and a username to direct your message to the specific person. To help you track new comments, a bubble indicator with the number of unread comments is displayed next to the *Comments* section icon in the right panel. This bubble appears when there are unread comments for the selected string and disappears once you open the section to read them. You can also use this section to report problems with source strings or translations, ask questions, or request additional context.  [Issues ](/issues/)Learn how to report and manage translation issues in the Editor. ### [Search TM](#search-tm) [Section titled “Search TM”](#search-tm) Using the *Search TM* section, you can check for all the available translations from [Translation Memory](/translation-memory/), which is the vault of translations uploaded to the system by project managers. The Search TM section provides the following options: * Source – Search for matches in a source language. * Target – Search for matches in target languages. * Guess translation – Highlight probable translation of a search phrase. * Numeric equivalence – Match digits from a search phrase with any other digits. Additionally, to maximize your search results, you can use the following wildcards with your search phrase: Type an asterisk **(\*)** to find words where the end or beginning may be different. Example: any\* finds *any*, *anyway*, *anything* Example: \*way finds *way*, *anyway*, *highway* Type a plus sign **(+)** to find words where the end or beginning must be different. Example: any+ finds *anyway*, *anything*, *anywhere*, except *any* Example: +way finds *anyway*, *highway*, *someway*, except *way* Type a minus sign **(-)** to exclude words from your search. Example: Save -as Use quotation marks to find the exact combination of words. Example: “Save as” Each TM suggestion in the search results also includes details such as the TM name, creation date, and, if available, the name of the contributor who originally submitted the translation.  ### [Editing TM Suggestions in the Editor](#editing-tm-suggestions-in-the-editor) [Section titled “Editing TM Suggestions in the Editor”](#editing-tm-suggestions-in-the-editor) When working in the Editor, you can view the TM suggestions displayed in the TM and MT Suggestions section and in the right sidebar found through the Search TM section. There may be situations where TM suggestions contain inaccuracies or need to be updated. Project members with manager permissions (or higher) can edit or delete TM records directly in the Editor, both in the TM and MT Suggestions section and in the Search TM section, rather than having to go to the Translation Memories page in the Resources or Project Settings. This ensures that TM suggestions are updated safely and quickly, improving the overall quality of the TM. To edit the TM suggestion, follow these steps: 1. Click in the TM and MT Suggestions section or **Edit** in the Search TM section.  2. In the appeared dialog, make the necessary edits (i.e., modify or delete) to the TM suggestions for each language present in the TM segment. 3. To revert accidental deletions or unwanted changes, click **Undo** next to the TM suggestions or click **Cancel** to revert all modifications before saving. 4. Once the desired edits are completed, click **Save** to confirm and apply these changes to the TM segment. To completely delete a TM segment from the TM, delete all TM records across all languages and click **Save**. ### [Terms](#terms) [Section titled “Terms”](#terms) Underlined words or phrases in strings indicate project-specific terminology, which should be translated according to the provided term description. You can view detailed explanations by hovering over the underlined text or visiting the Terms section. The Terms section allows you to browse the project glossary (if available) and search for specific terms. If a term is not found in the glossary, Wikipedia explanations will be displayed as a reference. Some terms may already have translations, which help maintain consistency across the project. To reuse a translated term, simply click on the underlined text, and its translation will automatically appear in the translation field.  ### [File Context](#file-context) [Section titled “File Context”](#file-context) The *File Context* section allows you to provide translators with additional details to help them understand how to translate a specific file. File context can be added as plain text or Markdown, either directly in the Editor or through the [File Settings](/file-management/#file-context) by the project members with manager permissions (or higher). For other project members, file context is read-only. To add file context in the Editor, follow these steps: 1. Click **Add File Context** in the File Context section. 2. Add the context or instructions for your translators. You can use either plain text or Markdown. 3. *(Optional)* Click **Preview** to see how the text will appear after saving. 4. Click **Save**. To edit file context, click the existing text in the File Context section, make your changes, and click **Save**.  ## [Editor Modes](#editor-modes) [Section titled “Editor Modes”](#editor-modes) The Editor offers several viewing modes to accommodate different translation workflows. The available modes include **Side-by-Side**, **Comfortable**, **Multilingual**, and **Multilingual (Grid)**, each providing a unique layout for presenting and managing translations. The **Side-by-Side** mode is enabled by default, but you can easily switch as needed. You can switch between Editor modes using the following methods: * **Via Main menu** – click on the **Main menu** in the upper-left corner, select **View**, and choose the preferred mode. * **Via Editor View icon** – click the **Editor View** icon in the upper-right corner and choose the preferred mode. ### [Side-by-Side Mode](#side-by-side-mode) [Section titled “Side-by-Side Mode”](#side-by-side-mode) Side-by-Side mode, detailed in the [Core Features](#core-features) section, is ideal for managing multiple translations at once. Translators can work on several strings simultaneously or swiftly review and vote on existing translations. Managers and proofreaders can efficiently approve the best options all within the same view. ### [Comfortable Mode](#comfortable-mode) [Section titled “Comfortable Mode”](#comfortable-mode) Comfortable mode allows translators and proofreaders to focus on one string at a time, ensuring accuracy without distractions. It emphasizes the active string, making it easier to review context and related resources. This mode is ideal for handling complex translations or performing detailed proofreading, where precision and thoroughness are essential. The main working area with the source string at the top and the translation section below. To add a translation, you need to select a string from the left section, and it will appear in the middle-top *Source String* field.  ### [Multilingual Mode](#multilingual-mode) [Section titled “Multilingual Mode”](#multilingual-mode) The multilingual mode provides similar features as the side-by-side mode and allows multilingual translators and proofreaders to work with multiple languages at the same time. You can select up to ten languages to work with simultaneously. The right panel shows the string’s translations of the language you’re entering a translation for or the one that was selected last.  Once you switch to the multilingual mode, select the languages you’d like to work with, and click **Apply**. To add new languages or remove some of the earlier selected ones, click on the Main menu in the upper-left corner, choose **Language**, alternatively click on the **Languages** in the upper-left corner, then do the necessary modifications to the language list and click **Apply**. ### [Multilingual Mode (Grid)](#multilingual-mode-grid) [Section titled “Multilingual Mode (Grid)”](#multilingual-mode-grid) In addition to the multilingual mode, there is a separate Multilingual (Grid) mode. It provides a spreadsheet-like layout where each language is shown in a separate column, allowing you to work with multiple languages in a compact tabular format. To adjust the order and visibility of columns displayed in this mode, and to pin specific columns, click **Sort Columns** in the upper-right corner and select the preferred ones. You can also reset the layout to the default column set by selecting **Reset To Default** at the bottom of the list. Additionally, to pin or hide individual columns, click the drop-down arrow next to a column title and choose the needed option. You can also switch between **Default View** and **Compact View** using the button in the upper-right corner. The compact option displays more rows by reducing vertical spacing.  #### [For Proofreaders](#for-proofreaders) [Section titled “For Proofreaders”](#for-proofreaders) The proofreading process works mainly the same way as in side-by-side mode, except when approving or removing approvals for all or a couple of strings at once, the system performs the action for all languages selected for the multilingual mode. #### [Using Filter in Multilingual Mode](#using-filter-in-multilingual-mode) [Section titled “Using Filter in Multilingual Mode”](#using-filter-in-multilingual-mode) When using filter options in multilingual mode, the system will show strings that meet the selected criteria for at least one of the selected languages. This behavior applies to the following filter options: * Untranslated * Not Approved * Approved * QA issues * Machine Translations * Advanced Filter > Translations updated * Advanced Filter > Translations > Partially translated (plurals) * Advanced Filter > Translations > Same as source string * Advanced Filter > Votes ## [Translating RTL Languages](#translating-rtl-languages) [Section titled “Translating RTL Languages”](#translating-rtl-languages) When translating between LTR and RTL languages, some elements in the translation field in the Editor might not be displayed the same way as they will be once exported. To be sure that RTL translations will be displayed correctly in the exported file, we recommend making translations the following way: 1. Click under the source text (or `Alt` +`C` key combination). 2. Translate the source texts into the target language. 3. Leave variables, tags, etc., unchanged in the translation, even if they look wrong. They will be in the right positions in the exported file.  ## [Command Palette](#command-palette) [Section titled “Command Palette”](#command-palette) The Command Palette in the Editor is your hub for accessing various commands efficiently. It serves as a central location for all available commands, ensuring a seamless and intuitive experience. To open the Command Palette, click in the upper-right corner.  ## [Managing Unsaved Translations](#managing-unsaved-translations) [Section titled “Managing Unsaved Translations”](#managing-unsaved-translations) When you enter translations but haven’t saved them, a green indicator appears next to the **Unsaved Translations** icon. Hovering over or clicking displays a tooltip with the number of unsaved translations. This feature offers the following options: * Check the number of unsaved translations. * Save all unsaved translations with a single click. * View and manage all strings with unsaved translations. To view unsaved translations, click in the upper-right corner and select **View Strings**. Alternatively, click and select **Unsaved translations**. Once filtered, you can continue editing unsaved translations. If they are ready to be saved, click **Save All** to apply the changes. ## [Editor Settings](#editor-settings) [Section titled “Editor Settings”](#editor-settings) To open the Editor settings, click in the upper-right corner. The Editor settings are grouped into tabs that contain various options for configuring the Editor according to your preferences. ### [General](#general) [Section titled “General”](#general) * *Translation Memory Suggestions* – you can specify the minimum similarity match (in percentages) for translation memory suggestions shown under the translation field. * *QA issues* – if enabled, the pop-up messages with warnings will appear each time you try to save a translation with some inaccuracy (punctuation/tags/spaces mismatch, missing variables, etc.)  * *Auto-complete* – if enabled, the pop-up with translation prediction and automatic translation completion will appear while you type the translation. * *Auto-approve* – if enabled, the translations added by proofreaders or members with higher permissions are automatically approved. * *Automatically move to next string* – if enabled, you’ll be automatically moved to the next string after saving a new translation or approving an existing one. ### [AI](#ai) [Section titled “AI”](#ai) The AI tab allows to configure custom prompts and shortcuts for AI Assistant. This tab will appear in the Editor settings once the project owner configures AI provider and sets up the **AI in editor** prompt. Read more about [Using AI in the Editor](/crowdin-ai/#using-ai-in-the-editor). ### [Appearance](#appearance) [Section titled “Appearance”](#appearance) * *Default Editor View* – set the default view mode that will be used each time you open the Editor. * *Compact strings view* – if enabled, only the beginnings of the long strings will be shown in the string list. * *Translation Preview* – if enabled, a translation preview will be displayed for translated strings in the string list. * *HTML Tags Displaying* – you can choose **Show** or **Hide** option that applies to all HTML tags. If you choose **Auto**, tags will be hidden in HTML, Haml, XML, Web XML, Markdown, and DOCX files but shown in other file formats. When tags are hidden, you can expect the following: ```plaintext Sample ``` will be replaced with ```plaintext <0>Sample ``` * *Non-printable characters displaying* – if enabled, non-printable characters (e.g., space, tab character, line break, etc.) will be displayed in source texts and translations. * *Translation field highlighting* – if enabled, words with potential QA issues will be underlined in the translation field. * *Real-Time Spellcheck* – instantly view spelling issues as you type a translation. displayed next to the translation means that no spelling issues were found. Otherwise, you’ll see a red label with the number of spelling issues detected. Click it for more details. * *UI Language* – select your preferred language for the Crowdin UI. The chosen language will be applied to the Editor and other parts of Crowdin. Caution Currently, the *Real-Time Spellcheck* feature is available for specific languages only. ### [Themes](#themes) [Section titled “Themes”](#themes) Set the **Light** or **Dark** theme, or select **Auto** to allow the Editor to set the theme based on your device system settings. In addition to the default themes, you can also install custom themes from the Crowdin Store or create your own custom theme. [Explore Existing Themes ](https://store.crowdin.com/collections/themes)Browse the collection of available themes in the Crowdin Store. [Create Custom Themes ](/developer/editor-themes/)Learn how to create your own custom themes. ## [Helpful Tips](#helpful-tips) [Section titled “Helpful Tips”](#helpful-tips) ### [Keyboard Shortcuts](#keyboard-shortcuts) [Section titled “Keyboard Shortcuts”](#keyboard-shortcuts) Use keyboard shortcuts to take actions in the editor quickly. Check the list of keyboard shortcuts by clicking the *keyboard* icon in the upper-right corner. Most of the hotkeys can be customized to your personal preferences. Click on the necessary key combination, and modify it with the help of your keyboard. ### [Quick Access to Menu Sections](#quick-access-to-menu-sections) [Section titled “Quick Access to Menu Sections”](#quick-access-to-menu-sections) Easy access to most-used menu items in one click: * *Project* – click on the current project name (*Umbrella* in the below screenshot) * *Language* – click on the current language (*French* in the below screenshot) * *Files* – click on the current file name (*strings.xml* in the below screenshot)  ### [Translation Progress Indicators](#translation-progress-indicators) [Section titled “Translation Progress Indicators”](#translation-progress-indicators) Use translation and approval indicators to monitor the progress of the currently opened file or folder. These indicators display the proportion of content that is translated and approved, allowing you to quickly assess the current status. There are two types of indicators available in the Editor: * **Circular Progress Indicators** – Located in the upper-right corner of the toolbar, these show the percentage of translated and approved content for the file or folder you’re working on. * **Detailed Progress Breakdown** – Accessible via the **Main menu > File**, this provides information on the total word count, number of translated, pre-translated, and approved words, along with percentage completion for each.  ### [Context Menu Options for Selected Words](#context-menu-options-for-selected-words) [Section titled “Context Menu Options for Selected Words”](#context-menu-options-for-selected-words) When you select a word or phrase in the source string or translation, the icon will appear. Clicking the icon opens a context menu with several useful options: * **Search TM** – Look for Translation Memory (TM) suggestions for the selected word or phrase. * **Search in Terminology and Wikipedia** – Find an explanation of the selected word or phrase in the project terminology or Wikipedia. * **Create Term** – Add the selected word or phrase to the project glossary as a new term. * **Transform** (only available for selected words in the translation) – Access a submenu with options to convert the selected text to lowercase or uppercase. * **Copy** – Copy the selected word or phrase to clipboard. * **Copy & Paste** – Copy the selected word or phrase and immediately paste it into the translation field. Permissions The *Create Term* option availability depends on the [Glossary Access Settings](/project-settings/privacy-collaboration/#glossary-access-settings) configured by the project managers.  ### [Switching to Another File](#switching-to-another-file) [Section titled “Switching to Another File”](#switching-to-another-file) To translate strings from the other files, follow these steps: 1. Click on the Main menu or click on the current file name in the upper-left corner. 2. Choose **File > Open**. 3. Select the necessary file and click **Open**. Alternatively, just double-click on the necessary file. To see all strings of the project, click on the Main menu in the upper-left corner, and go to **File** > **All Strings**. Alternatively, click on the current file name in the upper-left corner > **All Strings**. To quickly find and reopen one of the files you recently worked on, click on the Main menu in the upper-left corner, go to **File** and select the needed file from the **Recent files** section. ### [Source and Translated File Preview](#source-and-translated-file-preview) [Section titled “Source and Translated File Preview”](#source-and-translated-file-preview) In addition to the [WYSIWYG file preview](#wysiwyg-file-preview), which shows files as they would appear when rendered, there are **Source File Preview** and **Translated File Preview** modes that allow users to view the raw content of both source and translated files directly within the Editor. These previews provide insight into the file’s structure, layout, and formatting, helping users ensure accurate translations within the correct context. This is particularly helpful for identifying discrepancies or formatting issues without leaving the Editor. While the **Translated File Preview** is available to all users, the **Source File Preview** is restricted to members with Developer permissions or higher. To open a file in either of these previews, click on the Main menu in the upper-left corner, go to **File**, and select the needed file preview mode. ### [Replace in Suggested Translations](#replace-in-suggested-translations) [Section titled “Replace in Suggested Translations”](#replace-in-suggested-translations) You can easily find and replace suggested translations using the *Replace in Translations* feature. To replace previously added translations with the new ones, follow these steps: 1. In the project *Dashboard* tab, select the necessary language. 2. Click **Translate All** or choose a file for translation. 3. Click on the Main menu in the upper-left corner. 4. Go to **File** > **Replace in Translations**. 5. Enter the word, phrase, or sentence you want to substitute and the text to replace it with. Similarly to [string search](#string-search), you can use the *Match case* and *Exact match* options to refine the search results. 6. From the drop-down menu, specify the scope of your search, selecting between *File*, *All files*, or *Filtered strings* options. 7. Click **Find** to preview the strings that will be replaced.  8. *(Optional)* Click the *Settings* drop-down menu on the right and select what information to display in the search results other than translations. You can choose between *Key*, *Context*, and *Source*. 9. Select the translations you want to replace and click **Replace Selected** to finish. While translators can perform replacements only in their own translations, project members with proofreader permissions (or higher) can modify all suggested translations. Authorship of translations is preserved. ### [Replace in Sources](#replace-in-sources) [Section titled “Replace in Sources”](#replace-in-sources) Project members with developer permissions (or higher) can find and replace source texts using the *Replace in Sources* feature. To replace source texts, follow these steps: 1. In the project *Dashboard* tab, select the necessary language. 2. Click **Translate All** or choose a file for translation. 3. Click on the Main menu in the upper-left corner. 4. Go to **File** > **Replace in Sources**. 5. Enter the word, phrase, or sentence you want to substitute and the text to replace it with. Similarly to [string search](#string-search), you can use the *Match case* and *Exact match* options to refine the search results. 6. From the drop-down menu, specify the scope of your search, selecting between *File*, *All files*, or *Filtered strings* options. 7. Click **Find** to preview the strings that will be replaced.  8. *(Optional)* Click the *Settings* drop-down menu on the right and select what information to display in the search results other than strings. You can choose between *Key* and *Context*. 9. In the lower-left corner, click the drop-down menu and select the preferred behavior for the translations of the source strings to be replaced. You can choose between *Keep Translations*, *Remove Approvals*, or *Delete Translations*. 10. Select the source strings you want to replace and click **Replace Selected** to finish. ### [Pre-translation in the Editor](#pre-translation-in-the-editor) [Section titled “Pre-translation in the Editor”](#pre-translation-in-the-editor) The **Pre-translation** feature in the Editor allows you to apply translations to multiple strings directly within the Editor using Translation Memory (TM), Machine Translation (MT), or AI. This feature is available to project members with language coordinator permissions or higher. To apply Pre-translation in the Editor, follow these steps: 1. You can apply pre-translation in the Editor in two ways: * **Main menu** – click on the Main menu in the upper-left corner, go to **File** and select the preferred pre-translation method. * **String menu** (available in **Side-by-Side** and **Multilingual** modes) – click in the upper-right and select the preferred pre-translation method. 2. Configure the following pre-translation parameters: * **Scope** – select which strings to apply pre-translation to: * **Selected strings** (Specific to **Side-by-Side** and **Multilingual** modes) – applies only to strings manually selected in the Editor. * **Filtered strings** – applies to all strings matching the current filter. * **File** – applies to the currently opened file. * **All files** – applies to all strings across all files in the project, regardless of the file currently open in the Editor. * **Apply to untranslated strings only** – when selected, pre-translation will only be applied to strings that don’t have any translations. * **Allow duplicate translations** – adds translations even if they duplicate existing ones. Useful when comparing AI prompts or MT engines in the [Pre-translation Accuracy](/project-reports/#pre-translation-accuracy) report, as it ensures that all translations are registered as new and included in accuracy calculations. * **Minimum match ratio** (Specific to pre-translation via TM) - select either **100%** or **Perfect match (101%)** as the minimum similarity required for TM matches. Read more about [TM Match Types](/translation-memory/#tm-match-calculation). * **Skip approved translations** (Specific to pre-translation via TM and MT) – prevents overwriting strings that already have approved translations. * **Approve added translations** (Specific to pre-translation via TM) – allows you to auto-approve translations added through pre-translation. Options include: * **All** – approve all added translations. * **With perfect match** – approve only those with a 101% match. * **With perfect match (approved previously)** – approve perfect matches only if they were already approved before. * **All (skip auto-substituted translations)** – approve everything except translations improved by auto-substitution. * **Translation engine** (Specific to pre-translation via MT) – select the machine translation engine to use. * **AI prompt** (Specific to pre-translation via AI) – select the prompt that will guide the AI model’s behavior during pre-translation. 3. Click **Pre-Translation**. In Side-by-side and Comfortable modes, pre-translation is applied to the single language currently selected in the Editor. In Multilingual mode, translations are applied across all selected languages, as this mode allows working with multiple languages simultaneously. Read more about [Multilingual mode](#multilingual-mode). Use the **Queue** option in the String menu to track and manage all triggered pre-translation instances. Read more about [Pre-translation Queue](/pre-translation/#pre-translation-queue). ### [Advanced Filter](#advanced-filter) [Section titled “Advanced Filter”](#advanced-filter) You can create a custom filter of strings by clicking the *Filter strings* icon and choosing *Advanced Filter*. Use this filter to define multiple parameters at once, such as: * strings added or updated within a specific period * translations updated * [labels](/project-settings/labels/) * duplicates, comments, approvals, and more This helps locate the needed strings faster, especially in large projects. #### [Filtering by Labels](#filtering-by-labels) [Section titled “Filtering by Labels”](#filtering-by-labels) In the **Include by labels** and **Exclude by labels** fields, you can select one or more labels to refine your search. Additionally, choose how selected labels should be evaluated using the **Include match rule** and **Exclude match rule** settings: * **All selected labels** – returns only strings that match **all** selected labels (AND logic). * **Any selected label** – returns strings that match **at least one** of the selected labels (OR logic). This allows you to narrow or expand the filtered results depending on your needs. Here are a couple of examples of how this logic works in practice: * Include by labels example – to find strings tagged with both `ui` and `button`, select those labels and choose **All selected labels** as the match rule. * Exclude by labels example – to exclude all strings tagged either `marketing` or `deprecated`, select those labels and choose **Any selected label** as the match rule.  ### [AI/CroQL Filter](#aicroql-filter) [Section titled “AI/CroQL Filter”](#aicroql-filter) The AI/CroQL Filter allows you to filter strings similarly to the Advanced Filter but offers greater flexibility through the Crowdin Query Language (CroQL). #### [Generate CroQL with AI](#generate-croql-with-ai) [Section titled “Generate CroQL with AI”](#generate-croql-with-ai) In the **Generate CroQL with AI** field, you can write queries in plain text, which will then be transformed into a CroQL expression using AI. To get the best results possible, make sure your queries are clearly structured. For example, you can enter: *Return strings where there are translations by the user “username” into Ukrainian*. Once you specify your query, press `Enter` , and the AI will generate and populate the **CroQL expression** field with the corresponding CroQL expression. Alternatively, you can directly input a pre-prepared CroQL expression in the **CroQL expression** field. Click **Filter** to apply the specified filter to the strings in the Editor or click **Reset Filter** to clear the current filter settings. Read more about [Crowdin Query Language (CroQL)](/developer/croql/). ### [Pinning Sections](#pinning-sections) [Section titled “Pinning Sections”](#pinning-sections) In Side-by-Side or Multilingual modes, you can pin specific sections to keep them visible while navigating through other parts of the interface. This helps you access the pinned content quickly without losing sight of essential information. ### [Customizing Right Panel Section Order](#customizing-right-panel-section-order) [Section titled “Customizing Right Panel Section Order”](#customizing-right-panel-section-order) To personalize your workspace in the Editor, you can reorder the sections in the right panel (e.g., AI Assistant, Context and Translations, Comments, etc.) by dragging their icons. Click and hold the icon of the section you’d like to move, then drag it to a new position. The updated order will remain applied as you continue working in the Editor. ## [Tasks in the Editor](#tasks-in-the-editor) [Section titled “Tasks in the Editor”](#tasks-in-the-editor) Once a translator or proofreader has a task assigned, all the task details are accessible from the editor: The name of the task is displayed at the top of the toolbar.  Filters and searches apply to a particular task only. Task details can be accessed by clicking the menu in the upper-left corner. The task menu consists of the following components and features: * name, due date, language, type of the task, and assignee * options to download and upload translations for the particular task * possibility to quit the particular task editor and show all project strings * [Replace in Translations](#replace-in-suggested-translations) option * [Replace in Sources](#replace-in-sources) option  # Ordering Professional Translations > Order professional translations from vendors directly in Crowdin Crowdin provides localization services as a [Crowdin Language Services](/crowdin-language-services/) vendor and cooperates with several other professional translation agencies that offer such services to Crowdin customers.  Some of them, like BLEND and Gengo are integrated with Crowdin via API, so the translation ordering becomes fully automated. When you purchase translations from them, Crowdin forwards your untranslated data directly to the agency. After the translations are completed, they’re uploaded back to your Crowdin project, where you can download them to your machine. By selecting any other vendor from the list, you’ll contact a real person who can be assigned to a project as a proofreader or project manager. They will manage the process for you: involve the translators, maintain the quality, monitor the progress, and meet the deadlines. Professional translation is a paid service where the approximate cost for your project is calculated or negotiated during the purchasing process. ## [Automated Translations Ordering](#automated-translations-ordering) [Section titled “Automated Translations Ordering”](#automated-translations-ordering) You can order the translation from BLEND and Gengo in a few clicks. See the detailed instructions below. ### [Connecting BLEND and Gengo with Crowdin](#connecting-blend-and-gengo-with-crowdin) [Section titled “Connecting BLEND and Gengo with Crowdin”](#connecting-blend-and-gengo-with-crowdin) Before you can order translations from BLEND and Gengo, you need to have a Customer account on their platforms and sufficient balance. Register at [BLEND](https://app.getblend.com/auth/register) and [Gengo](https://gengo.com/auth/form/signup/) if you don’t already have an account. To establish the connection between your customer account and your Crowdin account, follow these steps: 1. Log in to Crowdin. 2. Open your profile home page and select **Vendors** on the left sidebar. 3. Select **BLEND** or **Gengo**. 4. Click **Connect Account**.  5. Enter *Public Key* and *Secret Key* from the BLEND [API keys](https://app.getblend.com/profile/#apikeys) tab or the Gengo [API settings](https://gengo.com/account/api_settings/). Click **Submit Keys**. ### [Creating Translation Tasks](#creating-translation-tasks) [Section titled “Creating Translation Tasks”](#creating-translation-tasks) To order translations from BLEND or Gengo, create a task in your Crowdin project. Follow these step-by-step instructions for task creation: 1. Click **Create Task** using the project’s **Tasks** tab or straight from the vendor page via **Vendors** being logged in as a project owner. Ensure to select the project from the drop-down list when creating a task via **Vendors**.  2. Set the [task parameters](#task-parameters). 3. Click **Create Task** to complete the translation order. ### [Translation Process](#translation-process) [Section titled “Translation Process”](#translation-process) When the task is created, it’s automatically sent to the selected vendor. As soon as translation starts, the related task in Crowdin will automatically change the status to *In Progress*. And when the translations are finished, the task will gain the *Done* status in Crowdin. Read more about [BLEND Integration](/blend-integration/). ## [Ordering Translations With a Dedicated Manager](#ordering-translations-with-a-dedicated-manager) [Section titled “Ordering Translations With a Dedicated Manager”](#ordering-translations-with-a-dedicated-manager) The dedicated project manager will manage the translation process for you (involve translators, meet the deadlines, and maintain quality). To start working with a vendor, follow these steps: 1. Log into your Crowdin account. 2. Open your profile home page and select **Vendors** on the left sidebar. 3. Click **View all vendors** to open the full list. 4. Select the preferred vendor. 5. Click **View**.  6. Select a project you’d like to translate. 7. Click **Create Task**. Alternatively, click **Create Task** using the [Tasks](/tasks/) tab in your project. 8. Set the [task parameters](#task-parameters). 9. Click **Create Task**. [Crowdin Language Services ](/crowdin-language-services/)Crowdin Language Services is an integrated solution that allows you to order professional translations and proofreading services for your Crowdin project in a few clicks ## [Task Parameters](#task-parameters) [Section titled “Task Parameters”](#task-parameters) | Parameter | Description | | -------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------ | | Title *(required)* | Specify the name of the task that will be visible to translators. | | Description | Add more details about the task that might be useful for translators. | | Type *(required)* | Select the task type. For ordering from vendors, choose *Translate by vendor*. | | Translation Vendor *(required)* | Select a vendor you’d like to work with. | | Create a pending proofreading task | Creates a [proofreading task](/tasks/#sequential-tasks) for each language that starts after the translation task is completed. | | Expertise | Define the desired quality level of translation (Specific to Gengo and BLEND). | | Tone | Define the preferred tone of translations (Specific to Gengo). | | Purpose | Define where the translations are intended to be used (Specific to Gengo). | | Comment | Provide instructions for translators (max. 500 characters) (Specific to Gengo). | | Include edit service | Send translations for additional review (Specific to Gengo and BLEND). | | Use preferred translators | Give priority to your preferred translators (Specific to Gengo). | | Skip strings already included in other tasks | Skip strings that are already assigned to other tasks. | | Strings *(required)* | Select whether to include all untranslated strings or only those modified within a specific period. | | Filter by labels | Include only strings with the specified labels. | | Exclude by labels | Exclude strings with the specified labels. | | Due Date | Set a deadline for the task. | | Files/Branches *(required)* | Depending on your [project type](/creating-project/#project-types), select files or branches to include in the task. | | Languages *(required)* | Select target languages. A separate task will be created for each selected language. | Read more about [Tasks](/tasks/). # Payments and Invoices > Learn how payments work in Crowdin and how to download invoices How you will be charged for Crowdin services depends on the subscription type you choose. There are two options available: Monthly and Annual. ### [Monthly Plans](#monthly-plans) [Section titled “Monthly Plans”](#monthly-plans) Monthly subscriptions use a recurring payment model. Once you subscribe to a monthly plan, your account limits are set according to the selected plan, and you’ll be instantly charged for the first billing cycle (one month). You will then be automatically charged again at the beginning of each following billing cycle. If you upgrade or downgrade in the middle of the monthly billing cycle, your account limits update instantly. Starting with the next billing cycle, you’ll be automatically charged the rate of the new plan. ### [Annual Plans](#annual-plans) [Section titled “Annual Plans”](#annual-plans) Annual subscriptions are paid upfront for the entire year. This payment is applied to your Crowdin account as a balance. Each month, Crowdin deducts the corresponding amount from this balance. #### [Changing Your Annual Subscription Plan](#changing-your-annual-subscription-plan) [Section titled “Changing Your Annual Subscription Plan”](#changing-your-annual-subscription-plan) As your project needs change, you can upgrade or downgrade at any time. When you change your plan, the remaining balance from your previous subscription is prorated and applied to the new subscription cost at the start of the next billing cycle. For example: * If you purchased an annual Team plan and later downgrade to Pro, your balance will last longer than one year. * Conversely, if you upgrade from Pro to Team, your balance may be depleted sooner. #### [Renewal of Annual Subscriptions](#renewal-of-annual-subscriptions) [Section titled “Renewal of Annual Subscriptions”](#renewal-of-annual-subscriptions) The renewal process depends on your chosen payment method: * **Subscriptions purchased via FastSpring (card payments)** automatically renew each year. Crowdin sends email reminders two months and one month before your renewal date. FastSpring also sends a notification one day before your card is automatically charged for the renewal. * **Subscriptions purchased via other payment methods (e.g., invoice)** do **not** renew automatically. Crowdin sends email reminders two months and one month before your subscription ends, prompting you to manually purchase a new subscription to continue using Crowdin. ## [Downloading Invoices](#downloading-invoices) [Section titled “Downloading Invoices”](#downloading-invoices) Invoices represent completed transactions and can be downloaded directly from Crowdin. To download invoices in Crowdin, follow these steps: 1. Go to **Account Settings > Billing**. 2. Choose the needed invoice from the list and click **Download**.  Also, you can download invoices via FastSpring, our payment processing partner. 1. Go to the [FastSpring Account Management page](https://crowdin.onfastspring.com/account). 2. To log in, specify the same email that was used to purchase your Crowdin subscription. 3. Click **Continue**. If you have active Crowdin app subscriptions, they’ll appear in the downloaded invoice next to your primary Crowdin subscription.  ## [See Also](#see-also) [Section titled “See Also”](#see-also) [Pricing page ](https://crowdin.com/pricing)Plans, Pricing, and Free Trial. [Changing Subscription Plan ](/changing-subscription-plan/)Upgrade or downgrade your subscription plan. [App Subscriptions ](/app-subscriptions/)Learn how to subscribe to paid apps in Crowdin Store. [Billing Settings ](/billing-settings/)Update your billing information and payment method. # Pre-Translation > Speed up the translation process and ease the work of translators Pre-translation helps speed up the translation process and ease the work of translators. It also allows you to save funds as part of translations can be automated. You can use and combine the following types of pre-translation: * **AI Pre-Translate** - uses AI Models to pre-translate the content. * **Machine Translation (MT) Pre-translate** – takes translations from supported machine translation engines (MTE) and applies them to the project content. You need to configure at least one of the translation engines to enable this feature. * **Translation Memory (TM) Pre-translate** – takes translations from the TM vault uploaded to the system and applies them to project content. [Crowdin AI ](/crowdin-ai/)Read more about Crowdin AI and how to use it. [Machine Translation ](/machine-translation/)Read more about Machine Translation and how to use it. [Translation Memory ](/translation-memory/)Read more about Translation Memory and how to use it. ## [Manual Pre-translation](#manual-pre-translation) [Section titled “Manual Pre-translation”](#manual-pre-translation) To apply Pre-translation manually, follow these steps: 1. Open your project and go to the **Dashboard** tab. 2. Click **Pre-translation** and select the preferred method (via Translation Memory, via Machine Translation, or AI).  3. Configure the following pre-translation parameters: * **Target languages** – select the languages to pre-translate into. * **Files for pre-translation** – select the files or folders you want to pre-translate. * **Apply to untranslated strings only** – when selected, pre-translation will only be applied to strings that don’t have any translations. * **Allow duplicate translations** – adds translations even if they duplicate existing ones. Useful when comparing AI prompts or MT engines in the [Pre-translation Accuracy](/project-reports/#pre-translation-accuracy) report, as it ensures that all translations are registered as new and included in accuracy calculations. * **Filter by labels / Exclude labels** – include or exclude specific strings based on their assigned labels. Read more about [Labels](/string-management/#labels). * **Minimum match ratio** (Specific to pre-translation via TM) – select either **100%** or **Perfect match (101%)** as the minimum similarity required for TM matches. Read more about [TM Match Types](/translation-memory/#tm-match-calculation). * **Skip approved translations** (Specific to pre-translation via TM and MT) – prevents overwriting strings that already have approved translations. * **Approve added translations** (Specific to pre-translation via TM) – allows you to auto-approve translations added through pre-translation. Options include: * **All** – approve all added translations. * **With perfect match** – approve only those with a 101% match. * **With perfect match (approved previously)** – approve perfect matches only if they were already approved before. * **All (skip auto-substituted translations)** – approve everything except translations improved by auto-substitution. * **MT engine** (Specific to pre-translation via MT) – select the machine translation engine to use for pre-translation. * **AI prompt** (Specific to pre-translation via AI) – select or create the prompt that will guide the AI model’s behavior during pre-translation. 4. Click **Pre-translation**. ### [Pre-translating Files and Folders via Context Menu](#pre-translating-files-and-folders-via-context-menu) [Section titled “Pre-translating Files and Folders via Context Menu”](#pre-translating-files-and-folders-via-context-menu) In addition to running the pre-translation from the project’s **Dashboard**, you can quickly pre-translate selected files or folders directly from the language page or **Sources > Files** using the context menu. #### [From the Language Page](#from-the-language-page) [Section titled “From the Language Page”](#from-the-language-page) To pre-translate a single file or folder from the language page, follow these steps: 1. Open your project and select the target language. 2. Click on the needed file or folder and select **Pre-translate**. 3. Select the preferred pre-translation method: **via TM**, **via MT**, or **via AI**. 4. In the Pre-translate dialog, the language and file/folder will already be selected for pre-translation. Configure the rest of the pre-translation parameters as described in the [Manual Pre-translation](#manual-pre-translation) section. 5. Click **Pre-translation**. #### [From Sources > Files](#from-sources--files) [Section titled “From Sources > Files”](#from-sources--files) To pre-translate one or multiple files or folders from the **Sources > Files** section, follow these steps: 1. Open your project and go to **Sources > Files**. 2. Click (or right-click) on the needed file or folder, or select multiple items using `Ctrl` , `⌘` , or `Shift` and then click (or right-click). 3. Select **Pre-translate**, then select the preferred pre-translation method: **via TM**, **via MT**, or **via AI**. 4. In the Pre-translate dialog, the files or folders you selected in **Sources > Files** will already be selected for pre-translation. Configure the rest of the pre-translation parameters as described in the [Manual Pre-translation](#manual-pre-translation) section. 5. Click **Pre-translation**. ### [Pre-translation Queue](#pre-translation-queue) [Section titled “Pre-translation Queue”](#pre-translation-queue) The Pre-translation queue allows you to trigger multiple manual pre-translations via TM, MT, or AI, each with different settings. After initiating a pre-translation, each instance enters a queue with a status of **Pending**. Upon triggering a manual pre-translation, you will receive a notification indicating that the pre-translation has been added to the queue. To review all pre-translations currently in the queue, navigate to **Tools > Pre-translation queue** in your project. Alternatively, click **Pre-translation** in the project’s **Dashboard** and select **Queue** to be redirected directly to the **Tools > Pre-translation queue**. Each entry in the Pre-translation queue table includes the following details: * **Created at:** Displays the date and time when the pre-translation was initiated * **Type:** TM, MT (MT engine name), AI (AI prompt name) * **Status:** Pending, In progress, Completed, Canceled You can cancel any pre-translation that is still in the queue if needed. Additionally, for completed pre-translations, you can view a report detailing the target languages, number of translations added and skipped, file list, and more. ## [Automatic Pre-translation](#automatic-pre-translation) [Section titled “Automatic Pre-translation”](#automatic-pre-translation) You can automate the Pre-translation in the project **Settings > Pre-translate**. In this case, each time you upload new content to your project, the system will automatically trigger the Pre-translation and apply translations to untranslated content. Read more about [Automatic Pre-translation](/project-settings/pre-translate/). ## [Handling QA Issues During Pre-translation via AI](#handling-qa-issues-during-pre-translation-via-ai) [Section titled “Handling QA Issues During Pre-translation via AI”](#handling-qa-issues-during-pre-translation-via-ai) If the AI provider returns translations with QA issues during pre-translation, Crowdin will collect the strings to which these faulty translations were applied and automatically reinitiate the pre-translation. The affected strings will be sent back to the AI provider along with details of the detected QA issues to ensure that the translations are corrected and meet quality standards. ## [Translation Memory Priority During Pre-translation via TM](#translation-memory-priority-during-pre-translation-via-tm) [Section titled “Translation Memory Priority During Pre-translation via TM”](#translation-memory-priority-during-pre-translation-via-tm) When using pre-translation via TM and the **Share TMs** option is enabled, Crowdin applies translations from translation memories based on a specific priority order. This priority ensures that translations come from the most relevant source, optimizing translation consistency and quality. The order of priority is as follows: 1. **Default TM**: Matches are first searched for in the project’s default TM. 2. **Assigned TMs**: If no match is found in the default TM, the system continues searching through any TMs assigned specifically to the project. 3. **Shared TMs**: If no match is found in the default or assigned TMs, translations are retrieved from shared TMs available to the project. This sequence allows Crowdin to apply translations from the most relevant TM source first, ensuring that high-quality matches are prioritized when multiple TMs are available. # Privacy Policy > Crowdin Privacy Policy Last revised on June 27, 2025 ### [In This Article](#in-this-article) [Section titled “In This Article”](#in-this-article) * [1. DEFINITIONS](#1-definitions) * [2. THE INFORMATION WE COLLECT ON THE SERVICE](#2-the-information-we-collect-on-the-service) * [3. HOW WE USE THE INFORMATION WE COLLECT](#3-how-we-use-the-information-we-collect) * [4. TO WHOM WE DISCLOSE INFORMATION](#4-to-whom-we-disclose-information) * [5. YOUR CHOICES](#5-your-choices) * [6. THIRD-PARTY SERVICES](#6-third-party-services) * [7. INTEREST BASED ADVERTISING](#7-interest-based-advertising) * [8. THIRD PARTY COOKIES](#8-third-party-cookies) * [9. MINORS AND CHILDREN’S PRIVACY](#9-minors-and-childrens-privacy) * [10. DATA SECURITY](#10-data-security) * [11. DATA RETENTION](#11-data-retention) * [12. SETTINGS](#12-settings) * [13. DATA TRANSFER](#13-data-transfer) * [14. DATA CONTROLLER AND DATA PROCESSOR](#14-data-controller-and-data-processor) * [15. CHANGES AND UPDATES TO THIS POLICY](#15-changes-and-updates-to-this-policy) * [16. USE OF GOOGLE WORKSPACE APIs](#16-use-of-google-workspace-apis) * [17. HOW TO CONTACT US](#17-how-to-contact-us) *** Welcome, and thank you for your interest in Crowdin (“Crowdin”, “we”, or “us”), our web site at [https://crowdin.com](https://crowdin.com/) (the “Site”), and all related web sites, downloadable software, mobile applications (including tablet applications), and other services provided by us and on which a link to this Privacy Policy is displayed, and all other communications with individuals though from written or oral means, such as email or phone (collectively, together with the Site, our “Service”). This Privacy Policy (“Policy”) describes the information that we gather on or through the Service, how we use and disclose such information, and the steps we take to protect such information. By visiting the Site, or by purchasing or using the Service, you accept the privacy practices described in this Policy. This Policy is incorporated into, and is subject to, the Crowdin Terms of Service. Capitalized terms used but not defined in this Policy have the meaning given to them in the Crowdin Terms of Service. ## [1. DEFINITIONS](#1-definitions) [Section titled “1. DEFINITIONS”](#1-definitions) | | | | --------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Client | a customer of Crowdin. | | Client Data | -personal data, reports, addresses, and other files, folders or documents in electronic form that a User of the Service stores within the Service. | | Personal Data | any information relating to an identified or identifiable natural person. | | Public Area | the area of the Site that can be accessed both by Users and Visitors, without needing to log in. | | Restricted Area | the area of the Site that can be accessed only by Users, and where access requires logging in. | | User | an employee, agent, or representative of a Client, who primarily uses the restricted areas of the Site for the purpose of accessing the Service in such capacity. | | Visitor | an individual other than a User, who uses the public area, but has no access to the restricted areas of the Site or Service. | ## [2. THE INFORMATION WE COLLECT ON THE SERVICE](#2-the-information-we-collect-on-the-service) [Section titled “2. THE INFORMATION WE COLLECT ON THE SERVICE”](#2-the-information-we-collect-on-the-service) We collect different types of information from or through the Service. The legal bases for Crowdin’s processing of personal data are primarily that the processing is necessary for providing the Service in accordance with Crowdin’s Terms of Service and that the processing is carried out in Crowdin’s legitimate interests, which are further explained in the section “How We Use the Information We Collect” of this Policy. We may also process data upon your consent, asking for it as appropriate. ### [2.1 User-provided Information](#21-user-provided-information) [Section titled “2.1 User-provided Information”](#21-user-provided-information) When you use the Service, as a User or as a Visitor, you may provide, and we may collect Personal Data. Examples of Personal Data include name, email address, mailing address, and credit card or other billing information. Personal Data also includes other information, such as geographic area or preferences, when any such information is linked to information that identifies a specific individual. You may provide us with Personal Data in various ways on the Service. For example, when you register for an Account, use the Service, post Client Data, interact with other users of the Service through communication or messaging capabilities, or send us customer service -related requests. ### [2.2 Information Collected by Clients](#22-information-collected-by-clients) [Section titled “2.2 Information Collected by Clients”](#22-information-collected-by-clients) A Client or User may store or upload into the Service Client Data. Crowdin has no direct relationship with the individuals whose Personal Data it hosts as part of Client Data. Each Client is responsible for providing notice to its customers and third persons concerning the purpose for which Client collects their Personal Data and how this Personal Data is processed in or through the Service as part of Client Data. ### [2.3 “Automatically Collected” Information](#23-automatically-collected-information) [Section titled “2.3 “Automatically Collected” Information”](#23-automatically-collected-information) When a User or Visitor uses the Service, we may automatically record certain information from the User’s or Visitor’s device by using various types of technology, including cookies, “clear gifs” or “web beacons.” This “automatically collected” information may include IP address or other device address or ID, web browser and/or device type, the web pages or sites visited just before or just after using the Service, the pages or other content the User or Visitor views or interacts with on the Service, and the dates and times of the visit, access, or use of the Service. We also may use these technologies to collect information regarding a Visitor or User’s interaction with email messages, such as whether the Visitor or User opens, clicks on, or forwards a message. This information is gathered from all Users and Visitors. Our use of cookies and other tracking technologies is discussed more below, and in more detail in our Cookie Statement [here](/cookies/). ### [2.4 Integrated Services](#24-integrated-services) [Section titled “2.4 Integrated Services”](#24-integrated-services) You may be given the option to access or register for the Service through the use of your user name and passwords for certain services provided by third parties (each, an “Integrated Service”), such as through the use of your Google account, or otherwise have the option to authorize an Integrated Service to provide Personal Data or other information to us. By authorizing us to connect with an Integrated Service, you authorize us to access and store your name, email address(es), timezones, gender, current city, profile picture URL, and other information that the Integrated Service makes available to us, and to use and disclose it in accordance with this Policy. You should check your privacy settings on each Integrated Service to understand what information that Integrated Service makes available to us, and make changes as appropriate. Please review each Integrated Service’s terms of use and privacy policies carefully before using their services and connecting to our Service. ### [2.5 Information from Other Sources](#25-information-from-other-sources) [Section titled “2.5 Information from Other Sources”](#25-information-from-other-sources) We may obtain information, including Personal Data, from third parties and sources other than the Service, such as our partners, advertisers and Integrated Services. If we combine or associate information from other sources with Personal Data that we collect through the Service, we will treat the combined information as Personal Data in accordance with this Policy. ## [3. HOW WE USE THE INFORMATION WE COLLECT](#3-how-we-use-the-information-we-collect) [Section titled “3. HOW WE USE THE INFORMATION WE COLLECT”](#3-how-we-use-the-information-we-collect) We use the information that we collect in a variety of ways in providing the Service and operating our business, including the following: ### [3.1 Operations](#31-operations) [Section titled “3.1 Operations”](#31-operations) We use the information – other than Client Data - to operate, maintain, enhance and provide all features of the Service, to provide the services and information that you request, to respond to comments and questions and to provide support to users of the Service. We process Client Data solely in accordance with the directions provided by the applicable Client or User. ### [3.2 Improvements](#32-improvements) [Section titled “3.2 Improvements”](#32-improvements) We use the information to understand and analyze the usage trends and preferences of our Visitors and Users, to improve the Service, and to develop new products, services, feature, and functionality. Should this purpose require Crowdin to process Client Data, then the data will only be used in anonymized or aggregated form. ### [3.3 Communications](#33-communications) [Section titled “3.3 Communications”](#33-communications) We may use a Visitor’s or User’s email address or other information – other than Client Data – to contact that Visitor or User (i) for administrative purposes such as customer service, to address intellectual property infringement, right of privacy violations or defamation issues related to the Client Data or Personal Data posted on the Service or (ii) with updates on promotions and events, relating to products and services offered by us and by third parties we work with. You have the ability to opt-out of receiving any promotional communications as described below under “Your Choices.” ### [3.4 Cookies and Tracking Technologies](#34-cookies-and-tracking-technologies) [Section titled “3.4 Cookies and Tracking Technologies”](#34-cookies-and-tracking-technologies) We use automatically collected information and other information collected on the Service through cookies and similar technologies to: (i) personalize our Service, such as remembering a User’s or Visitor’s information so that the User or Visitor will not have to re-enter it during a visit or on subsequent visits; (ii) provide customized advertisements, content, and information; (iii) monitor and analyze the effectiveness of Service and third-party marketing activities; (iv) monitor aggregate site usage metrics such as total number of visitors and pages viewed; and (v) track your entries, submissions, and status in any promotions or other activities on the Service. You can obtain more information about cookies by visiting [http://www.allaboutcookies.org](http://www.allaboutcookies.org/). For further information about the types of cookies and tracking technologies we use, why, and how you can control them, please see our Cookie Statement [here](/cookies/). ### [3.5 Analytics](#35-analytics) [Section titled “3.5 Analytics”](#35-analytics) We use Google Analytics to measure and evaluate access to and traffic on the Public Area of the Site, and create user navigation reports for our Site administrators. Google operates independently from us and has its own privacy policy, which we strongly suggest you review. Google may use the information collected through Google Analytics to evaluate Users’ and Visitors’ activity on our Site. For more information, see [Google Analytics Privacy and Data Sharing](https://support.google.com/analytics/answer/6004245). We take measures to protect the technical information collected by our use of Google Analytics. The data collected will only be used on a need to know basis to resolve technical issues, administer the Site and identify visitor preferences; but in this case, the data will be in non-identifiable form. We do not use any of this information to identify Visitors or Users. ## [4. TO WHOM WE DISCLOSE INFORMATION](#4-to-whom-we-disclose-information) [Section titled “4. TO WHOM WE DISCLOSE INFORMATION”](#4-to-whom-we-disclose-information) Except as described in this Policy, we will not intentionally disclose the Personal Data or Client Data that we collect or store on the Service to third parties without the consent of the applicable Visitor, User or Client. We may disclose information to third parties if you consent to us doing so, as well as in the following circumstances: ### [4.1 Unrestricted Information](#41-unrestricted-information) [Section titled “4.1 Unrestricted Information”](#41-unrestricted-information) Any information that you voluntarily choose to include in a Public Area of the Service, such as a public profile page, will be available to any Visitor or User who has access to that content. We may display information related to your account such as your name, username, languages you prefer, the translation projects made publicly available which you are participating in and activities you performed in such project. Please consider carefully what information you disclose in your profile page and your desired level of anonymity, that you can regulate from profile settings. You can review and revise your profile information at any time. ### [4.2 Service Providers](#42-service-providers) [Section titled “4.2 Service Providers”](#42-service-providers) We work with third party service providers who provide website, application development, hosting, maintenance, and other services for us. These third parties may have access to, or process Personal Data or Client Data as part of providing those services for us. We limit the information provided to these service providers to that which is reasonably necessary for them to perform their functions, and our contracts with them require them to maintain the confidentiality of such information. ### [4.3 Non Personally Identifiable Information](#43-non-personally-identifiable-information) [Section titled “4.3 Non Personally Identifiable Information”](#43-non-personally-identifiable-information) We may make certain automatically-collected, aggregated, or otherwise non-personally-identifiable information available to third parties for various purposes, including (i) compliance with various reporting obligations; (ii) for business or marketing purposes; or (iii) to assist such parties in understanding our Clients’, Users’ and Visitors’ interests, habits, and usage patterns for certain programs, content, services, and/or functionality available through the Service. ### [4.4 Law Enforcement, Legal Process and Compliance](#44-law-enforcement-legal-process-and-compliance) [Section titled “4.4 Law Enforcement, Legal Process and Compliance”](#44-law-enforcement-legal-process-and-compliance) We may disclose Personal Data or other information if required to do so by law or in the good-faith belief that such action is necessary to comply with applicable laws, in response to a facially valid court order, judicial or other government subpoena or warrant, or to otherwise cooperate with law enforcement or other governmental agencies. We also reserve the right to disclose Personal Data or other information that we believe, in good faith, is appropriate or necessary to (i) take precautions against liability, (ii) protect ourselves or others from fraudulent, abusive, or unlawful uses or activity, (iii) investigate and defend ourselves against any third-party claims or allegations, (iv) protect the security or integrity of the Service and any facilities or equipment used to make the Service available, or (v) protect our property or other legal rights, enforce our contracts, or protect the rights, property, or safety of others. ### [4.5 Change of Ownership](#45-change-of-ownership) [Section titled “4.5 Change of Ownership”](#45-change-of-ownership) Information about Users and Visitors, including Personal Data, may be disclosed and otherwise transferred to an acquirer, successor or assignee as part of any merger, acquisition, debt financing, sale of assets, or similar transaction, as well as in the event of an insolvency, bankruptcy, or receivership in which information is transferred to one or more third parties as one of our business assets and only if the recipient of the User or Visitor Data commits to a Privacy Policy that has terms substantially consistent with this Privacy Policy. Client Data may be physically or electronically transferred to an acquirer, or successor or assignee as part of any merger, acquisition, debt financing, sale of assets, or similar transaction, as well as in the event of an insolvency, bankruptcy, or receivership in which information is transferred to one or more third parties as one of our business assets, for the sole purpose of continuing the operation of the Service, and only if the recipient of the Client Data commits to a Privacy Policy that has terms substantially consistent with this Privacy Policy. ## [5. YOUR CHOICES](#5-your-choices) [Section titled “5. YOUR CHOICES”](#5-your-choices) ### [5.1 Access, Correction, Deletion](#51-access-correction-deletion) [Section titled “5.1 Access, Correction, Deletion”](#51-access-correction-deletion) We respect your privacy rights and provide you with reasonable access to the Personal Data that you may have provided through your use of the Services. If you wish to access or amend any other Personal Data we hold about you, or to request that we delete or transfer any information about you that we have obtained from an Integrated Service, you may contact us as set forth in the “How to Contact Us” section. At your request, we will have any reference to you deleted or blocked in our database. You may update, correct, or delete your Account information and preferences at any time by accessing your Account settings page on the Service. Please note that while any changes you make will be reflected in active user databases instantly or within a reasonable period of time, we may retain all information you submit for backups, archiving, prevention of fraud and abuse, analytics, satisfaction of legal obligations, or where we otherwise reasonably believe that we have a legitimate reason to do so. You may decline to share certain Personal Data with us, in which case we may not be able to provide to you some of the features and functionality of the Service. At any time, you may object to the processing of your Personal Data, on legitimate grounds, except if otherwise permitted by applicable law. If you believe your right to privacy granted by applicable data protection laws has been infringed upon, please contact us at . You also have a right to lodge a complaint with data protection authorities. This provision does not apply to Personal Data that is part of Client Data. In this case, the management of the Client Data is subject to the Client’s own Privacy Policy, and any request for access, correction or deletion should be made to the Client responsible for the uploading and storage of such data into the Service. ### [5.2 Navigation Information](#52-navigation-information) [Section titled “5.2 Navigation Information”](#52-navigation-information) You may opt out from the collection of navigation information about your visit to the Site by Google Analytics by using the [Google Analytics Opt-out feature](https://tools.google.com/dlpage/gaoptout). ### [5.3 Opting out from Commercial Communications](#53-opting-out-from-commercial-communications) [Section titled “5.3 Opting out from Commercial Communications”](#53-opting-out-from-commercial-communications) If you receive commercial emails from us, you may unsubscribe at any time by following the instructions contained within the email or by sending an email to the address provided in the “How to Contact Us” section. Users are able to view and modify settings relating to the nature and frequency of promotional communications that they receive from us by accessing the “Settings” tab on the account. Please be aware that if you opt-out of receiving commercial email from us or otherwise modify the nature or frequency of promotional communications you receive from us, it may take up to ten (10) business days for us to process your request. Additionally, even after you opt-out from receiving commercial messages from us, you will continue to receive administrative messages from us regarding the Service. Crowdin has no direct relationship with the Client’s customers or third party whose Personal Data it may process on behalf of a Client. An individual who seeks access, or who seeks to correct, amend, delete inaccurate data or withdraw consent for further contact should direct his or her query to the Client or User they deal with directly. If the Client requests Crowdin to remove the data, we will respond to its request within thirty (30) days. We will delete, amend or block access to any Personal Data that we are storing only if we receive a written request to do so from the Client who is responsible for such Personal Data, unless we have a legal right to retain such Personal Data. We reserve the right to retain a copy of such data for archiving purposes, or to defend our rights in litigation. Any such request regarding Client Data should be addressed as indicated in the “How to Contact Us” section, and include sufficient information for Crowdin to identify the Client or its customer or third party and the information to delete or amend. ## [6. THIRD-PARTY SERVICES](#6-third-party-services) [Section titled “6. THIRD-PARTY SERVICES”](#6-third-party-services) The Service may contain features or links to web sites and services provided by third parties. Any information you provide on third-party sites or services is provided directly to the operators of such services and is subject to those operators’ policies, if any, governing privacy and security, even if accessed through the Service. We are not responsible for the content or privacy and security practices and policies of third-party sites or services to which links or access are provided through the Service. We encourage you to learn about third parties’ privacy and security policies before providing them with information. ## [7. INTEREST BASED ADVERTISING](#7-interest-based-advertising) [Section titled “7. INTEREST BASED ADVERTISING”](#7-interest-based-advertising) Interest based advertising is the collection of data from different sources and across different platforms in order to predict an individual’s preferences or interest and to deliver to that individual, or his/her computer, smart phone or tablet, advertising based on his/her assumed preference or interest inferred from the collection of data pertaining to that individual or others who may have a similar profile or similar interests. We work with a variety of third parties to attempt to understand the profiles of the individuals who are most likely to be interested in the Crowdin products or services so that we can send them promotional emails, or serve our advertisements to them on the websites and mobile apps of other entities. These third parties include: (i) advertising networks, which collect information about a person’s interests when that person views or interacts with one of their advertisements; (ii) attribution partners, which measure the effectiveness of certain advertisements; and (iii) business partners, which collect information when a person views or interacts with one of their advertisements. In collaboration with these third parties, we collect information about our customers, prospects and other individuals over time and across different platforms when they use these platforms or interact with them. Individuals may submit information directly on our Sites or on platforms run by third parties, or by interacting with us, our advertisements, or emails they receive from us or from third parties. We may use special tools that are commonly used for this purpose, such as cookies, pixels, and similar technologies. We may have access to databases of information collected by our business partners. The information we or third party collect enables us to learn what purchases the person made, what ads or content the person sees, on which ads or links the person clicks, and other actions that the person takes on our Sites, or in response to our emails, or when visiting or using third parties’ platforms. We, or the third parties with which we work, use the information collected as described above to understand the various activities and behaviors of our customers, Site visitors and others. We, or these third parties, do this for many reasons, including: to recognize new or past visitors to our Sites; to present more personalized content; to provide more useful and relevant ads - for example, if we know what ads you are shown we can try not to show you the same ones repeatedly; to identify visitors across devices, sales channels, third party websites and Sites, or to display or send personalized or targeted ads and other custom content that is more focused on a person’s perceived interest in products or services similar to those that we offer. Our interest-based ads may be served to you in emails or on third-party platforms. We may serve these ads about our products or services or send commercial communications directly ourselves or through these third parties. Crowdin does not provide any personal information to the third party sites that display interest-based ads promoting Crowdin. ## [8. THIRD PARTY COOKIES](#8-third-party-cookies) [Section titled “8. THIRD PARTY COOKIES”](#8-third-party-cookies) We allow third parties with which we have a separate agreement to use cookies and other technologies to collect information about your use of the Site. These third parties include (i) business partners, which collect information when you view or interact with one of their advertisements on the Site; and (ii) advertising networks, which collect information about your interests when you view or interact with one of their advertisements. The information gathered by these third parties is used to make predictions about your interests or preferences so that they can display advertisements or promotional material on this Site and on other sites across the Internet tailored to your apparent interests. The business partners and advertising networks that serve interest-based advertisements on the Services have limited access to a small amount of information about your profile and your device, which is necessary to serve you advertisements that are tailored to your apparent interests. It is possible that they may reuse this small amount of information on other sites or services. We do not share with these third parties any information that would readily identify you (such as email address); however, these third parties may have access to information about your device (such as IP or MAC address). We do not have access to, or control over, the technologies that these third parties may use to collect information about your interests, and the information practices of these third parties are not covered by this Privacy Notice. Other than as discussed in this document, we have no control over these third parties. ### [8.1 The Following Types of Cookies Are Used in the Site](#81-the-following-types-of-cookies-are-used-in-the-site) [Section titled “8.1 The Following Types of Cookies Are Used in the Site”](#81-the-following-types-of-cookies-are-used-in-the-site) * strictly necessary/essential cookies - These cookies are essential in order to enable you to move around the website and use its features, such as accessing secure areas of the website. Without these cookies services you have asked for cannot be provided. These cookies don’t collect information that identifies a visitor. * functionality cookies - These cookies allow the website to remember choices you make (such as your user name, language or the region you are in) and provide enhanced, more personal features. For instance, a website may be able to provide you with local weather reports or traffic news by storing in a cookie the region in which you are currently located. These cookies can also be used to remember changes you have made to text size, fonts and other parts of web pages that you can customise. They may also be used to provide services you have asked for such as watching a video or commenting on a blog. The information these cookies collect may be anonymised and they cannot track your browsing activity on other websites. * behaviourally targeted advertising cookies - These cookies are used to deliver adverts more relevant to you and your interests. They are also used to limit the number of times you see an advertisement as well as help measure the effectiveness of the advertising campaigns. They are usually placed by advertising networks with the website operator’s permission. They remember that you have visited a website and this information is shared with other organisations such as advertisers. Quite often targeting or advertising cookies will be linked to site functionality provided by the other organisation. For more information about these and a full list of the cookies we use, what they do, and how to disable the non-necessary ones, please refer to our full [Cookie Statement](/cookies/). ### [9. MINORS AND CHILDREN’S PRIVACY](#9-minors-and-childrens-privacy) [Section titled “9. MINORS AND CHILDREN’S PRIVACY”](#9-minors-and-childrens-privacy) Protecting the privacy of young children is especially important. Our Service is not directed to children under the age of 18, and we do not knowingly collect Personal Data from children under the age of 18 without obtaining parental consent. If you are under 18 years of age, then please do not use or access the Service at any time or in any manner. If we learn that Personal Data has been collected on the Service from persons under 18 years of age and without verifiable parental consent, then we will take the appropriate steps to delete this information. If you are a parent or guardian and discover that your child under 18 years of age has obtained an Account on the Service, then you may alert us at and request that we delete that child’s Personal Data from our systems. The Service is not intended to be used by minors, and is not intended to be used to post content to share publicly or with friends. To the extent that a minor has posted such content on the Service, the minor has the right to have this content deleted or removed using the deletion or removal options detailed in this Privacy Policy. If you have any question regarding this topic, please contact us as indicated in the “How to Contact Us” section. Please be aware that, although we offer this deletion capability, the removal of content may not ensure complete or comprehensive removal of that content or information. ## [10. DATA SECURITY](#10-data-security) [Section titled “10. DATA SECURITY”](#10-data-security) We follow generally accepted industry standards to protect the information submitted to us, both during transmission and once we receive it. We maintain appropriate administrative, technical and physical safeguards to protect Personal Data against accidental or unlawful destruction, accidental loss, unauthorized alteration, unauthorized disclosure or access, misuse, and any other unlawful form of processing of the Personal Data in our possession. This includes, for example, firewalls, password protection and other access and authentication controls. We use SSL technology to encrypt data during transmission through public internet, and we also employ application-layer security features to further anonymize Personal Data. However, no method of transmission over the Internet, or method of electronic storage, is 100% secure. We cannot ensure or warrant the security of any information you transmit to us or store on the Service, and you do so at your own risk. We also cannot guarantee that such information may not be accessed, disclosed, altered, or destroyed by breach of any of our physical, technical, or managerial safeguards. If you believe your Personal Data has been compromised, please contact us as set forth in the “How to Contact Us” section. If we learn of a security systems breach, we will inform you and the authorities of the occurrence of the breach in accordance with applicable law. ## [11. DATA RETENTION](#11-data-retention) [Section titled “11. DATA RETENTION”](#11-data-retention) We only retain the Client Data collected from a User for as long as the User’s account is active or otherwise for a limited period of time as long as we need it to fulfill the purposes for which we have initially collected it, unless otherwise required by law. We will retain and use information as necessary to comply with our legal obligations, resolve disputes, and enforce our agreements as follows: * the Client Data of closed accounts are deleted within 3 months of the date of closure * backups are kept for 3 months * billing information is retained for a period of 7 years as of their provision to Crowdin in accordance with the Estonian accounting and taxation laws * information on legal transactions between Client and Crowdin is retained for a period of 10 years as of their provision to Crowdin in accordance with the general limitation period set for civil claims in the Estonian General Part of the Civil Code Act ## [12. SETTINGS](#12-settings) [Section titled “12. SETTINGS”](#12-settings) Although we may allow you to adjust your privacy settings to limit access to certain Personal Data, please be aware that no security measures are perfect or impenetrable. We are not responsible for circumvention of any privacy settings or security measures on the Service. Additionally, we cannot control the actions of other users with whom you may choose to share your information. Further, even after information posted on the Service is removed, caching and archiving services may have saved that information, and other users or third parties may have copied or stored the information available on the Service. We cannot and do not guarantee that information you post on or transmit to the Service will not be viewed by unauthorized persons. ## [13. DATA TRANSFER](#13-data-transfer) [Section titled “13. DATA TRANSFER”](#13-data-transfer) To provide our services, we use data centers located in the United States and Ireland. The geographical region for storing your data may depend on the service options. If you are a resident of the European Economic Area (EEA), the United Kingdom, or Switzerland, please note that we transfer your Personal Data outside of these regions to the United States and other countries for storage and processing. We ensure such transfers are lawful and that your data is adequately protected. The primary safeguards we rely on for international data transfers are: * Adequacy Regulations: We may transfer Personal Data to countries that have been deemed to provide an adequate level of data protection by the relevant authorities, such as the European Commission, the UK Secretary of State, or the Swiss Federal Council. * Data Privacy Frameworks: For transfers to service providers in the United States, we rely on their certification under the EU-U.S. Data Privacy Framework, the UK Extension to the EU-U.S. Data Privacy Framework, and the Swiss-U.S. Data Privacy Framework, as applicable to the data transfer. * Standard Contractual Clauses and Agreements: For transfers to countries without an adequacy decision or to service providers not certified under the Data Privacy Framework, we rely on Standard Contractual Clauses (SCCs) issued by the European Commission, which are supplemented by the UK’s International Data Transfer Addendum (UK Addendum) when required for UK data transfers. These clauses contractually oblige the data importer to process and protect your data with a level of security equivalent to that required by the GDPR and other applicable laws. You can find more information about the countries we transfer data to in our [Terms of Service](/terms/) and [Subprocessors List](/sub-processors/). ## [14. DATA CONTROLLER AND DATA PROCESSOR](#14-data-controller-and-data-processor) [Section titled “14. DATA CONTROLLER AND DATA PROCESSOR”](#14-data-controller-and-data-processor) Crowdin does not own, control or direct the use of any of the Client Data stored or processed by a Client or User via the Service. Only the Client or Users are entitled to access, retrieve and direct the use of such Client Data. Crowdin is largely unaware of what Client Data is actually being stored or made available by a Client or User to the Service and does not directly access such Client Data except as authorized by the Client, or as necessary to provide Services to the Client and its Users. Because Crowdin does not collect or determine the use of any Personal Data contained in the Client Data and because it does not determine the purposes for which such Personal Data is collected, the means of collecting such Personal Data, or the uses of such Personal Data, Crowdin is not acting in the capacity of data controller in terms of the European Union’s General Data Protection Regulation (Regulation (EU) 2016/679, hereinafter “GDPR”) and does not have the associated responsibilities under the GDPR. Crowdin should be considered only as a processor on behalf of its Clients and Users as to any Client Data containing Personal Data that is subject to the requirements of the GDPR. Except as provided in this Privacy Policy, Crowdin does not independently cause Client Data containing Personal Data stored in connection with the Services to be transferred or otherwise made available to third parties, except to third party subcontractors who may process such data on behalf of Crowdin in connection with Crowdin’s provision of Services to Clients. Such actions are performed or authorized only by the applicable Client or User. The Client or the User is the data controller under the Regulation for any Client Data containing Personal Data, meaning that such party controls the manner such Personal Data is collected and used as well as the determination of the purposes and means of the processing of such Personal Data. Crowdin is not responsible for the content of the Personal Data contained in the Client Data or other information stored on its servers (or its subcontractors’ servers) at the discretion of the Client or User nor is Crowdin responsible for the manner in which the Client or User collects, handles disclosure, distributes or otherwise processes such information. If you need a signed Data Processing Addendum in addition to the Terms of Service and Privacy Policy, you can find the document signed on behalf of Crowdin [here](https://downloads.crowdin.com/docs/DPA-singed.pdf). ## [15. CHANGES AND UPDATES TO THIS POLICY](#15-changes-and-updates-to-this-policy) [Section titled “15. CHANGES AND UPDATES TO THIS POLICY”](#15-changes-and-updates-to-this-policy) Please revisit this page periodically to stay aware of any changes to this Policy, which we may update from time to time. If we modify the Policy, we will make it available through the Service, and indicate the date of the latest revision, and will comply with applicable law. Your continued use of the Service after the revised Policy has become effective indicates that you have read, understood and agreed to the current version of the Policy. ## [16. USE OF GOOGLE WORKSPACE APIs](#16-use-of-google-workspace-apis) [Section titled “16. USE OF GOOGLE WORKSPACE APIs”](#16-use-of-google-workspace-apis) Crowdin confirms that the Google Workspace APIs accessed through our services (including the Crowdin platform and any applications developed by Crowdin and available for installation at store.crowdin.com) are used solely to provide the requested functionality. We do not share Google user data with any third parties except our sub-processors, who are contractually bound to process such data on our behalf and in accordance with applicable data protection laws. We do not use this data to develop, improve, or train generalized artificial intelligence (AI) or machine learning (ML) models. ## [17. HOW TO CONTACT US](#17-how-to-contact-us) [Section titled “17. HOW TO CONTACT US”](#17-how-to-contact-us) Please contact us with any questions or comments about this Policy, your Personal Data, our use and disclosure practices, your consent choices, or if you have any concerns or complaints about this Policy or your Personal Data, by email at . *** Your Crowdin Team. # Project Activity > Track all the events that happen in the project The Activity tab lets you track all main events that happen in the project. For good readability, activity records are grouped by days, users, and activity types. ## [Filter Activity Records](#filter-activity-records) [Section titled “Filter Activity Records”](#filter-activity-records) By default, the project Activity tab displays activity records for all activity types, all project languages, all users, and all time (newest activities first). You can filter activity records by the following activity types: * **All activity** – Show all activity records. * **Build Project** – Show records about project builds. * **Project Settings Updates** – Show records about project settings changes (e.g., updated target languages, updated export settings, etc.) * **Source Strings Updates** – Show records about source files uploads, updates, and removals, updates to source texts and context, etc. * **Translation Activity** – Show records about added and removed translations, votes, and approvals. * **Comments and Issues** – Show records about added comments, created and resolved issues. You can also filter activity records by a specific language or all languages, a specific user or all users, and the desired time period (e.g., Today, Yesterday, Last 7 days, Last 30 days, All time, and Custom Range).  ## [Undo Activity Records](#undo-activity-records) [Section titled “Undo Activity Records”](#undo-activity-records) If some unwanted actions (e.g., wrong translations upload, mistaken source file deletion, etc.) happen in the project, the project owner and managers can cancel them in the Activity tab by clicking UNDO next to the respective activity record. Proofreaders and translators can only cancel their own actions. Since activity records are grouped by types, you can either undo a whole group of activities or click **Details** and undo only some of them.  ## [View Updated File Diffs](#view-updated-file-diffs) [Section titled “View Updated File Diffs”](#view-updated-file-diffs) For updated project files, besides the number of added, deleted, and updated strings, you can view the actual strings added, deleted, or updated during the source file update and word quantity contained in the strings. To view the detailed diff for the file update, click **Diff** next to the needed activity record. For grouped project file update records, click **Details** to see all updated files in the group and then click **Diff** next to the needed file.  # Project Members > Manage project members and their roles in your project Roles define what project members can do based on their responsibilities and assigned languages. Project owners and managers can invite new members, assign roles, and manage their permissions. Language Coordinators can also manage members within their assigned languages, including inviting Translators and Proofreaders or reviewing join requests if the project uses [moderated joining](/project-settings/privacy-collaboration/#privacy). ## [Changing Role](#changing-role) [Section titled “Changing Role”](#changing-role) To change the role of a project member, follow these steps: 1. Open your project and go to the **Members** tab. 2. Click **Details** toward a needed member in the list. 3. In the appeared dialog, switch to the **Permissions** tab. 4. Select a new role. 5. Click **Save**.  [Roles ](/roles/)Learn more about the roles and permissions in Crowdin. ## [Languages Permissions](#languages-permissions) [Section titled “Languages Permissions”](#languages-permissions) For Translator, Proofreader, and Language Coordinator roles, if no specific language permissions are set during the invitation, access will be granted to all target languages by default. To configure language-specific access for these roles, follow these steps: 1. Open your project and go to the **Members** tab. 2. Click **Details** toward a needed member in the list. 3. In the appeared dialog, switch to the **Permissions** tab. 4. Select the needed languages a member should have access to. You can simultaneously set both the **Translator** and **Proofreader** roles to the same member with specific language permissions (e.g., Translator with access to Ukrainian and Proofreader with access to French). 5. Click **Save**.  ## [Q\&A](#qa) [Section titled “Q\&A”](#qa) ## [See Also](#see-also) [Section titled “See Also”](#see-also) [Inviting People ](/inviting-people/)Learn how to invite people to your translation project. [Manager Permissions ](/manager-permissions/)Learn about the manager role and how to assign managers to resources. # Project Reports > View your project status and various localization reports To view your project status, assess the effectiveness of pre-translation methods, estimate and count the translation cost, keep track of the most active members, and view historical data of previously generated reports, open your project and go to the **Reports** tab.  ## [Project Overview](#project-overview) [Section titled “Project Overview”](#project-overview) Use this section to get a comprehensive summary of your project’s health, monitor key activities, and track progress over selected time periods. In the upper-right corner, you can select a report unit (*words*, *strings*, *characters*, or *characters with spaces*) that will apply to all reports in this section. The comparisons shown in percentage are counted by comparing the chosen period of time to the same previous period of time (e.g., if you select a month, the current month is compared to the previous one). To download reports for further analysis or record-keeping, click **Export** and select the preferred format (CSV, XLSX, or JSON). In the reports that feature interactive graphs, you can hover over data points for more detailed information, such as daily or monthly totals for each category. The top of the page displays the primary statistics for your project’s volume: * *Translatable*: The total amount of text available for translation. * *Hidden*: The total amount of text in hidden strings. * *Total*: The total amount of text in the project (*Translatable* + *Hidden*). * *Translation to*: The number of target languages in the project. Below the main statistics, the **Overview** section contains the following reports: ### [Activity Summary](#activity-summary) [Section titled “Activity Summary”](#activity-summary) This report tracks the overall translation and proofreading activity in the project. You can filter the data by **Date Range** and **Language**. The report is split into two main parts: **Translation** and **Proofreading**. Each part displays the total work completed during the selected period with a percentage comparison to the previous period. You can expand the **Breakdown by Language** section in each part to view a table of the same metrics broken down by target language. #### [Translation](#translation) [Section titled “Translation”](#translation) This section shows the volume of translated text, broken down by the following key metrics: * *Total (end of period)* * *Human Translation* * *Translation Memory* * *Machine Translation* * *AI* The **Translation** graph below the metrics displays multiple lines simultaneously for each translation type. By hovering over the data points, you can view daily or monthly totals for each category. #### [Proofreading](#proofreading) [Section titled “Proofreading”](#proofreading) This section shows the volume of approved text and voting activity. The main metric displayed is *Approved* words. The **Proofreading** graph visualizes the approval and voting activity over time, showing two distinct lines: *Approved Words* and *Votes*. By hovering over the data points, you can view the daily or monthly totals for both approved texts and votes cast. ### [Translation Savings Summary](#translation-savings-summary) [Section titled “Translation Savings Summary”](#translation-savings-summary) Use this report to review the savings achieved by using Translation Memory (TM), Machine Translation (MT), and AI-assisted translation. You can filter the data by **Date Range** and **Language**. The report displays the total savings as well as a breakdown by each method. By clicking the settings icon, you can switch between viewing the data as **Relative savings (%)** or **Savings in currency**. This graph shows the savings achieved through Translation Memory (TM), Machine Translation (MT), and AI-assisted translation. Savings are calculated for each string if it represents either an initial translation via the Editor or an approved pre-translation, possibly with edits. Savings are only counted once per string. The graph may be updated for previous days as strings become approved. The bar chart breaks down the savings by each translation method. Hovering over the bars provides detailed information on savings per method on a daily or monthly basis. For a more granular view, you can also expand the **Breakdown by Language** section to see a table of savings for each specific language. ### [Source Content Updates](#source-content-updates) [Section titled “Source Content Updates”](#source-content-updates) This report tracks changes made to the source content over a selected time frame. You can filter the data by **Date Range**. The report displays the **Total (end of period)** volume of text, along with specific metrics for content that has been **Added**, **Deleted**, or **Modified**. The bar graph helps you visualize when the most significant content updates occurred. By hovering over the bars, you can see the specific changes that occurred each day or month. ### [QA Check Issues](#qa-check-issues) [Section titled “QA Check Issues”](#qa-check-issues) This report provides insights into the automated Quality Assurance (QA) checks, highlighting potential inconsistencies in translations. You can filter the data by **Date Range** and **Language**. Key metrics include: * *New (Period)*: The number of new QA issues found within the selected period. * *Total (end of period)*: The total number of unresolved QA issues at the end of the selected period. * *Per 1000 words*: The density of QA issues relative to the word count. This metric includes approved content and is only shown if the total word count is greater than 1000. * *Content with Issues*: The volume of text that contains QA issues, including approved content. * *Content with Issues Rate*: The percentage of text that has QA issues, including approved content. Below the metrics, the report also features several additional components: * **Breakdown by Language**: An expandable section that shows a table of the key metrics broken down by each target language. * **Issues Trend**: A line graph that monitors the total number of QA issues over time. You can hover over data points to see the total number of issues for a specific day. * **Issues by languages**: A heatmap-style table that visualizes the distribution of QA issue types (e.g., *Spelling mistakes*, *Consistent terminology*) across all target languages. You can hover over a cell to see the precise number of issues for that specific language and type. ### [Reported Issues](#reported-issues) [Section titled “Reported Issues”](#reported-issues) This report tracks issues manually created by project members to report problems or ask questions. You can filter the data by **Date Range** and **Issue Type**. The main metrics show the *Total*, *Created*, and *Resolved* issues, each with a comparison to the previous period. This report consists of the following components: * **Issues by Type**: A table showing the total, created, and resolved counts for each issue category (e.g., *General question*, *Current translation is wrong*). * **Incorrect Translations by Language**: A table focusing on the *Current translation is wrong* issue type, breaking down the numbers by language. * **Cumulative Created vs Resolved Issues**: A line graph that visualizes the cumulative number of created versus resolved issues. * **Average Resolution Time by Issue Type**: A bar chart showing the average time in days it takes to resolve each type of issue. * **Top Reporters & Resolvers**: A leaderboard of members who have reported and resolved the most issues, with sortable columns for *Name*, *Issues Reported*, and *Issues Resolved*. ### [Project Members](#project-members) [Section titled “Project Members”](#project-members) This report helps you monitor the activity and changes among your project members, which can help managers assess the level of engagement. You can filter the data by **Date Range**. The report displays key metrics about your member base for the selected period, including: * *Total (end of period)*: The total number of members in the project. * *Active*: The number of members who were active during the period. * *New*: The number of newly joined members. * *Pending (end of period)*: The number of users with pending join requests (including both incoming and outgoing invitations). * *Blocked (end of period)*: The number of blocked members. A graph below the metrics displays the trend of the total member count over time. ## [Cost Estimate](#cost-estimate) [Section titled “Cost Estimate”](#cost-estimate) Use this report to plan your budget and count the approximate cost of translations. Set the translation and approval rates to see the cost for untranslated and not approved strings in the project. You can generate a Cost Estimate report based on the following filter parameters: * Task: Not selected, All tasks, or a specific task. * Strings Added: Today, Last 7 days, Last 30 days, This month, All time, or Custom range. * Files: All or specific files. * Labels (Specific to [projects with labels](/project-settings/labels/)): Not selected, Strings with selected labels, or Strigns without selected labels. * Language: All languages or a specific target language. ### [Generating a Report](#generating-cost-estimate) [Section titled “Generating a Report”](#generating-cost-estimate) To generate the Cost Estimate report, follow these steps: 1. Select the preferred currency and the report unit (words, strings, characters without spaces, or characters with spaces). 2. Set your [rates](#rates-cost-estimate) for translations and approvals. 3. Use the available filter parameters to specify the report data you’re interested in. 4. Click **Generate**.  #### [Cost Estimate Queue](#queue-cost-estimate) [Section titled “Cost Estimate Queue”](#queue-cost-estimate) After you click **Generate**, the Cost Estimate report is added to a queue and processed in the background. This ensures that multiple reports generated by different users or with different filters don’t override one another. Each report is generated separately and appears in the **Reports > Archive** section once completed. When a report is added to the queue, a notification appears confirming that the report generation has been queued, with quick access to view the queue or close the message. While the report is being generated, a pop-up in the lower-right corner of the screen shows the queue status. The status updates automatically as the report progresses: * **Pending** – the report is waiting in the queue and has not started processing yet. * **In progress** – the report generation has started. A progress bar shows the current percentage. * **Completed** – the report has been generated successfully and can be accessed via the [Archive](#archive). * **Failed** – an error occurred during report generation. Each report runs independently, so you can safely generate multiple Cost Estimate reports with different filters without affecting those that might have been started earlier and are still in progress. ### [Rates](#rates-cost-estimate) [Section titled “Rates”](#rates-cost-estimate) You can set the prices for Base rates (full translation, proofread) and configure Net Rate Schemes (percentage of the full translation rate paid for translation using TM suggestions). #### [Base Rates](#base-rates-cost-estimate) [Section titled “Base Rates”](#base-rates-cost-estimate) In the Base Rates section, you can set rates for the following types of work: * **Full translation** – for each translation made by a person. * **Proofread** – for each approved translation. #### [Net Rate Schemes](#net-rate-schemes-cost-estimate) [Section titled “Net Rate Schemes”](#net-rate-schemes-cost-estimate) In the Net Rate Schemes section, in addition to the base rates, you can set the percentage of the full translation rate to be paid for translations made using TM suggestions of various TM Match types. By default, you can configure the percentage of the full translation rate for the following TM Match types: * **101 (perfect)** – for translations made using Perfect match TM suggestions (source strings are identical to TM suggestion by text and context). * **100** – for translations made using 100% match TM suggestions (source strings are identical to TM suggestion only by text). You can also add your own TM match types, specifying the preferred percentage of text similarity and the percentage of the full translation rate to be paid for such a translation. To add your own TM match types, follow these steps: 1. Click in the Net Rate Schemes section. 2. Click on the appeared button. 3. Specify the TM match range and the percentage of the full translation rate. 4. Click to save the settings.  #### [Adding Custom Rates](#custom-rates-cost-estimate) [Section titled “Adding Custom Rates”](#custom-rates-cost-estimate) In addition to base rates that are applied to all languages by default, you can add custom rates for specific languages. To add custom rates, click **Add custom rates**. To select the language or languages for custom rates, click **Edit Languages** and select the ones you need. You can create as many custom rates as you need.  #### [Rate Templates](#rate-templates) [Section titled “Rate Templates”](#rate-templates) If you plan to work with multiple rate configurations, save them as templates by clicking **Save as > New rates template**, then specify the template name and click **Save**. When saving a new template you can choose the template visibility using the following options: * **Share with all project members** – makes the template visible to all translators within the project. Regardless of the number of translators or their different rates, they all will have access to the template. It can include both general rates and custom rates for specific languages and translators, along with a net rate scheme. This transparency promotes clarity in pricing, allowing translators to review rates, generate reports on their translations, and calculate cost estimates. The key benefit is that translators understand the net rate scheme and can apply their base rate, even if it’s not included in the template. * **Share with managers within the owner’s projects** – makes the template global, visible only to managers across all projects of an owner. This option streamlines rate consistency across various projects. If neither of the options is selected, the template remains visible only to managers within the current project, limiting access to a select group of project members. These options provide flexibility in controlling who can view and use the rate template to accommodate different organizational preferences. Saved templates allows you to quickly switch between different configurations for report generation. Click **Templates** to view and manage your saved rate templates. ### [Include Pre-translated Strings](#include-pre-translated-strings) [Section titled “Include Pre-translated Strings”](#include-pre-translated-strings) Select **Include pre-translated strings** if you want to include pre-translated strings in a Cost Estimate report. By default, this option is selected. For example, you have an untranslated string `Validate your username` in your project. You generate a Cost Estimate report with the **Include pre-translated strings** option selected. This string will be included in the Cost Estimate. Then you pre-translate this string via TM or MT engine and once again generate a Cost Estimate report with the **Include pre-translated strings** option selected. This time, the pre-translated string `Validate your username` won’t be included in the Cost Estimate report. On the other hand, with the **Include pre-translated strings** option cleared, the string `Validate your username` will be included in the Cost Estimate report both times, when untranslated and when pre-translated via TM or MT engine. ### [Calculate Internal Fuzzy Matches](#calculate-internal-fuzzy-matches) [Section titled “Calculate Internal Fuzzy Matches”](#calculate-internal-fuzzy-matches) Internal Fuzzy Matches are partial (fuzzy) TM matches found among untranslated strings in your project that can potentially be added to the Translation Memory. For example, if the first string in a file is `Validate your username` and the last one is `Validate your username again`, there is an internal fuzzy match. To include fuzzy (99% and less) internal matches, as well as perfect (101%) and 100% matches, in your Cost Estimate report and get a more comprehensive prediction of how many strings can be added to the TM if translated in sequence, select **Calculate Internal Fuzzy Matches**. Note that these calculations are approximate because the actual translation order may differ. If you clear **Calculate Internal Fuzzy Matches**, the Cost Estimate report will only show perfect (101%) and 100% internal matches (repetitions), and will not include any fuzzy matches. ### [Result Analysis](#result-analysis-cost-estimate) [Section titled “Result Analysis”](#result-analysis-cost-estimate) When the Cost Estimate report is generated, it displays the following details: ##### [Cost Summary](#cost-summary) [Section titled “Cost Summary”](#cost-summary) * **Total** - General cost estimate for all languages (including translation, proofreading, and any TM savings). * **Subtotals** - Cost estimate for each target language: * **Translation** – Cost for strings requiring new or updated translations (no high–percentage match leverage). * **Proofreading** – Cost for reviewing translations. * **TM Savings** – Savings from existing translations (in TM or within the project). * **Weighted Words / Strings / Characters / Characters with Spaces** – Final word count for cost calculations after applying TM/internal match discounts. ##### [Categories](#categories) [Section titled “Categories”](#categories) Each row in the main table represents a match category or status: * **Total** – Summarizes all strings, words, and characters, as well as the weighted units after match discounts and percentage of the total. * **TM Match (total)** – Untranslated strings matching entries in Translation Memory, often split into: * **101% (perfect)** – Exact text and context match. * **100%** – Exact text match, but context differs. * **Repetitions (total)** or **Internal Match (total)** – Untranslated strings matching other strings within the project. Displaying depends on whether **Calculate Internal Fuzzy Matches** is enabled. Subcategories (e.g., 101%, 100%, and fuzzy) depend on your Net Rate Schemes. If an untranslated string has both a 101% TM match and a 100% internal match, it counts toward TM match. * **No Match** – Strings with no TM or internal matches, requiring translation from scratch. * **Not Approved** – Translated strings that still awaiting approval. * **Not Translated** – Completely untranslated strings requiring full translation. ##### [Columns](#columns) [Section titled “Columns”](#columns) * **Strings / Words / Characters / Characters with Spaces** – Basic volume metrics. * **Weighted Words / Strings / Characters / Characters with Spaces** – Shows the adjusted metric after factoring in repetitions and fuzzy matches, reflecting the actual translation effort. * **%** – Share of weighted units in each category. ##### [Folder/File Breakdown](#folderfile-breakdown) [Section titled “Folder/File Breakdown”](#folderfile-breakdown) After the main table, each language subtotal also includes a table showing data for each folder or file, indicating how many strings are **Not Approved**, **Not Translated**, match the **TM**, match **Internal**, or have **No Match**. This helps identify where to focus your translation efforts and budget. ##### [Export](#export) [Section titled “Export”](#export) To download the Cost Estimate report, click **Export** and select the preferred format (CSV, XLSX, or JSON) for further analysis or record-keeping.  ## [Translation Cost](#translation-cost) [Section titled “Translation Cost”](#translation-cost) Use this report to calculate the actual translation cost based on the completed job. You can generate a Translation Cost report based on the following filter parameters: * Task: Not selected, All Tasks, or specific task. * Date Range: Today, Yesterday, Last 7 days, Last 30 days, This month, Last month, All time, or Custom range. * Files: All files (including deleted files and strings) or Selected files (including deleted strings). * Branches (Specific to [string-based projects](/creating-project/#string-based-project)): All branches or Selected branches. * Labels (Specific to projects with [labels](/project-settings/labels/)): Not selected, Strings with selected labels, or Strigns without selected labels. * Language: All or specific target language. * Member: All or specific users. * Group by: Member or language. ### [Generating a Report](#generating-translation-cost) [Section titled “Generating a Report”](#generating-translation-cost) To generate the Translation Cost report, follow these steps: 1. Select the preferred currency and the report unit (words, strings, characters without spaces, or characters with spaces). 2. Set your [rates](#rates-translation-cost) for translations and approvals. 3. Use the available filter parameters to specify the report data you’re interested in. 4. Click **Generate**.  ### [Rates](#rates-translation-cost) [Section titled “Rates”](#rates-translation-cost) You can set the prices for Base rates (full translation, proofread) and configure Net Rate Schemes (percentage of the full translation rate paid for translation using TM suggestions, MT suggestions, and existing translations). #### [Base Rates](#base-rates-translation-cost) [Section titled “Base Rates”](#base-rates-translation-cost) In the Base Rates section, you can set rates for the following types of work: * **Full translation** – for each translation made by a person. * **Proofread** – for each approved translation. #### [Net Rate Schemes](#net-rate-schemes-translation-cost) [Section titled “Net Rate Schemes”](#net-rate-schemes-translation-cost) In the Net Rate Schemes section, in addition to the base rates, you can set the percentage of the full translation rate to be paid for translations made using TM suggestions, MT suggestions, and other translations of various Match types. By default, you can configure the percentage of the full translation rate for the following match type categories: **TM Match types:** * **101 (perfect)** – for translations made using Perfect match TM suggestions (source strings are identical to TM suggestion by text and context). * **100** – for translations made using 100% match TM suggestions (source strings are identical to TM suggestion only by text). **MT Match types:** * **100** – for translations made using 100% match MT suggestions (new suggested translations are identical to MT suggestion). **AI Match types:** * **100** – for translations made using 100% match AI suggestions (new suggested translations are identical to AI suggestion). **Other translations types:** * **100** – for translations made using existing translations (new suggested translations are identical to the existing translations). If a string has a combination of TM and MT suggestions and existing translations, the new translation is counted at the lowest Net Rate Scheme value. For example, if a string has a 101% (perfect) TM match suggestion (10% of the full translation rate) and a 100% MT match suggestion (5% of the full translation rate), the new translation added to this string will be counted at a 5% of the full translation rate. You can also add your own TM, MT, and Other translations match types, specifying the preferred percentage of text similarity and the percentage of the full translation rate to be paid for such a translation. To add your own match types, follow these steps: 1. Click in the Net Rate Schemes section. 2. Click on the appeared button. 3. Specify the match range and the percentage of the full translation rate. 4. Click to save the settings.  #### [Adding Custom Rates](#custom-rates-translation-cost) [Section titled “Adding Custom Rates”](#custom-rates-translation-cost) In addition to base rates that are applied to all languages and users by default, you can add custom rates for specific languages and users. To add custom rates, click **Add custom rates**. To select the languages and users for custom rates, click **Edit Languages** and **Edit Users** and select the ones you need. You can create as many custom rates as you need.  ### [Using Additional Translation Cost Options](#using-additional-translation-cost-options) [Section titled “Using Additional Translation Cost Options”](#using-additional-translation-cost-options) * **Exclude Approvals for Edited Translations:** select this option to exclude approvals when the same user has translated the string. This helps ensure that your cost reporting is more accurate by avoiding the duplication of approval costs. * **Pre-Translated Strings Categorization Adjustment:** select this option to have repetitive translations of pre-translated strings categorized under TM or MT match rates, rather than the default Other suggestion match rates. This is useful because post-editing translations from MT engines usually requires more effort than post-editing translations from human translators, leading to a more precise and fair measure of costs related to your translators. ### [Result Analysis](#result-analysis-translation-cost) [Section titled “Result Analysis”](#result-analysis-translation-cost) When the Translation Cost report is generated, it displays the following details: ##### [Cost Summary](#cost-summary-1) [Section titled “Cost Summary”](#cost-summary-1) * **Total** - General translation cost (including TM, MT, and AI savings, weighted words, and pre-translated words). * **User and Language Totals** - Below the general translation cost, the report shows totals for each user or language, depending on the selected **Group by** filter: * **Group by Member** - Shows each translator or proofreader general translation cost (including TM, MT, and AI savings, weighted words, and pre-translated words), along with language subtotals within. * **Group by Language** - Shows each target language general translation cost (including TM, MT, and AI savings, weighted words, and pre-translated words), along with translator or proofreader subtotals within. * **Subtotals** - Subtotal translation cost for each target language or user: * **Savings** - The amount saved with leveraged matches from TM, MT, or AI. * **Weighted Words / Strings / Characters / Characters with Spaces** – Shows the adjusted metric after applying repetitions and fuzzy matches, reflecting the actual translation effort. * **Pre-translated Words / Strings / Characters / Characters with Spaces** - Shows how many units were pre-translated. Within each user (or language) section, you’ll see a further breakdown of work types and match types in the tables: ##### [Translation & Post-Editing](#translation--post-editing) [Section titled “Translation & Post-Editing”](#translation--post-editing) Each row in the Translation & Post-Editing section represents a match category or total: * **No Match** – No leverage from TM, MT, or AI (full rate). * **TM Match** – Uses Translation Memory (with possible subcategories like **101% (perfect)** or **100%**). * **MT Match** – Uses Machine Translation (e.g., **100%**). * **AI Match** – Uses AI-based suggestions (e.g., **100%**). * **Other translations Match** – Leverage from existing translations added by other users. * **Total** – Summarizes all translated units under that user/language. ##### [Columns](#columns-1) [Section titled “Columns”](#columns-1) * **Strings / Words / Characters / Characters with Spaces** – Number of units handled at each match type. * **Rate per unit** – The price assigned per match type (based on your configured [Net Rate Schemes](#net-rate-schemes-translation-cost) and base rates). * **Price** – Total cost for the units × rate in that match category. ##### [Proofreading](#proofreading-1) [Section titled “Proofreading”](#proofreading-1) * **Words / Strings / Characters / Characters with Spaces** – Number of units that were proofread and approved. * **Rate per unit** – Proofreading rate. * **Price** – Total cost for proofread units (units × rate). ##### [Export](#export-1) [Section titled “Export”](#export-1) To download the Translation Cost report, click **Export** and select the preferred format (CSV, XLSX, or JSON) for further analysis or record-keeping.  ## [Pre-translation Accuracy](#pre-translation-accuracy) [Section titled “Pre-translation Accuracy”](#pre-translation-accuracy) Use this report to evaluate the translation quality of pre-translation methods (via AI, MT, and TM) used in your project by analyzing the post-editing effort required for pre-translated strings before approval. It compares the initial pre-translated strings with the final approved translations after post-editing, categorizing data based on the edit distance and pre-translation method. This report allows you optimize your translation workflows and improve overall content quality by identifying the best-performing pre-translation methods. The edit distance metric is calculated at the character level, while the report mode selection (Strings, Words, Chars) only affects how results are displayed: * Strings – The entire string is placed in a category if its total edit distance falls within the range. * Words – All words in the string are placed in the category. * Chars – All characters in the string are placed in the category. ### [Report Scope](#report-scope) [Section titled “Report Scope”](#report-scope) * Includes only approved strings with at least one pre-translation. * If multiple pre-translations exist for a string, each is included with its edit distance. * Only the top translation is used for comparison if multiple approvals exist. ### [Use Case and Best Practices](#use-case-and-best-practices) [Section titled “Use Case and Best Practices”](#use-case-and-best-practices) **Typical Use Case:** 1. Launch Pre-translation – use different methods (via AI, MT, and TM) for a portion of your content. Alternatively, you can use one method (e.g., AI) and compare various prompts with different settings. 2. Invite a Proofreader – have the pre-translated content reviewed and approved by a proofreader. 3. Generate Report – use the Pre-translation Accuracy report to evaluate which pre-translation method performed best by requiring the least amount of post-editing. 4. Optimize Workflow – use the most effective pre-translation method for all your content. **Best Practices:** * **Regular Reviews** – regularly generate and review the report to stay informed about the performance of your pre-translation methods. * **Adjust Methods** – use the insights from the report to adjust your pre-translation methods. For example, if AI pre-translations require minimal edits, consider increasing their use. ### [Generating a Report](#generating-pre-translation-accuracy) [Section titled “Generating a Report”](#generating-pre-translation-accuracy) You can generate a Pre-translation Accuracy report based on the following filters: * **Task** – Not selected, All Tasks, or a specific task. * **Language** – All, or specific language. * **Strings added (Date range of when the strings were approved)** – Today, Yesterday, Last 7 days, Last 30 days, This month, Last month, All time, or Custom range. Additionally, using the report’s **Settings**, you can adjust how post-editing information is displayed on the graphs: * **Total** – aggregates all post-editing data without breaking it into subcategories. * **Split into Categories by Edit Distance %** – offers a detailed view by categorizing units based on the extent of editing required. To generate the Pre-translation Accuracy report, follow these steps: 1. Select the preferred report unit (words, strings, characters with or without spaces). 2. Select the preferred way to group the histogram data (Day or Month). * When grouped by Day, the stacked histogram will have more bars, giving a more granular, day-by-day view. * When grouped by Month, the data is displayed in fewer, broader monthly segments. 3. *(Optional)* Select the task if you want to generate a report based on work done within all or specific tasks. Alternatively, leave it as **Not selected** to generate a report based on a wider content scope. 4. Select the preferred language. 5. Select the time range. 6. Click **Settings** and select one of the available options to configure how you want the post-editing information to be displayed. 7. Click **Generate**. ### [Result Analysis](#result-analysis-pre-translation-accuracy) [Section titled “Result Analysis”](#result-analysis-pre-translation-accuracy) When the report is generated, you will see the information grouped into pre-translation methods (via AI, MT, and TM): * Pre-translation via AI: * Total approved words, pre-translated by AI * Separate graphs for each prompt * Pre-translation via MT: * Total approved words, pre-translated by MT * Separate graphs for each MT engine * Pre-translation via TM: * Total approved words, pre-translated by TM In each section, the data is displayed as histograms and pie charts: * **Stacked Histogram** – visualizes the distribution of units approved with or without edits. It categorizes units based on the extent of post-editing, such as: * Approved with no post-edit * Post-edited with varying degrees of edit distance * **Quality Score Pie Chart** – provides an overall view of pre-translation quality based on post-editing effort, showing how many pre-translated words were good enough at the moment of approval. Includes the following metrics: * **Total** – total number of words included in the report. * **Edit rate** – percentage of translations that were edited before approval. * **Average edit distance** – average percentage of changes applied to translations. The quality score is calculated as a weighted average based on the edit distance. Translations approved without edits contribute fully (100 %) to the score. Partially edited translations contribute proportionally to the amount of unchanged content. For example, if a 10-word translation was edited by 10 %, 9 words (90 %) are counted as high quality. If a translation was approved without edits, all words (100 %) are counted. To download the Pre-translation Accuracy report, click **Export** and select the preferred export format (CSV, XLSX, or JSON).  ## [Translator Accuracy](#translator-accuracy) [Section titled “Translator Accuracy”](#translator-accuracy) Use this report to evaluate the translation quality of individual translators in your project by analyzing the post-editing efforts required before their translations are approved. It compares each translator’s initial translation with the final approved version, categorizing the data based on edit distance. This allows you to identify top-performing translators and those who may need additional guidance or training. ### [Report Scope](#report-scope-1) [Section titled “Report Scope”](#report-scope-1) * Includes only approved strings with at least one translation submitted by a human translator. * If multiple translations exist for a string, each is included with its edit distance. * Only the top translation is used for comparison if multiple approvals exist. ### [Use Case and Best Practices](#use-case-and-best-practices-1) [Section titled “Use Case and Best Practices”](#use-case-and-best-practices-1) **Typical Use Case:** 1. Collect Translations – have your translators work on the project’s content. 2. Proofread and Approve – invite your proofreaders to review and approve the translated strings. 3. Generate Report – use the Translator Accuracy report to evaluate each translator’s work, based on how much post-editing was required. 4. Optimize Translation Team – identify top-performing translators (those with minimal post-edits) and provide targeted feedback or training where needed. **Best Practices:** * **Regular Reviews** – generate and review this report periodically to keep track of translator performance and spot trends in post-editing needs. * **Targeted Feedback** – use the insights to guide training or feedback sessions, focusing on specific areas where translators may need improvement. ### [Generating a Report](#generating-translator-accuracy) [Section titled “Generating a Report”](#generating-translator-accuracy) You can generate a Translator Accuracy report based on the following filters: * **Users** – All, or selected users. * **Language** – All, or specific language. * **Strings approved** – Today, Yesterday, Last 7 days, Last 30 days, This month, Last month, All time, or Custom range. Additionally, using the report’s **Settings**, you can adjust how post-editing information is displayed: * **Total** – aggregates all post-editing data without breaking it into subcategories. * **Split into Categories by Edit Distance %** – provides a more granular view by grouping translations based on the extent of editing required. To generate the Translator Accuracy report, follow these steps: 1. Select the preferred report unit (words, strings, characters with or without spaces). 2. *(Optional)* Select one or more users if you want to generate the report for specific translators only. Otherwise, choose **All** to include everyone. 3. Select the preferred language or choose **All** if you want to include every target language. 4. Select the time range. 5. Click **Settings** and select one of the available options to configure how you want the post-editing information to be displayed. 6. Click **Generate**. ### [Result Analysis](#result-analysis-translator-accuracy) [Section titled “Result Analysis”](#result-analysis-translator-accuracy) When the report is generated, you will see the information grouped by language, and each translator is listed with their individual statistics: In each section, the data is displayed as pie charts: * **Pie Chart** – displays the proportion of units approved with or without edits. It categorizes units based on the extent of post-editing, such as: * No post-edit – displays that no further proofreader edits were made to the translator’s initial translation. * Post-edited with varying degrees of edit distance – displays one or more slices if you chose **Split into Categories by Edit Distance %**, each slice representing different ranges of edits applied to the translator’s work. If you selected **Total**, you’ll see just two slices: **No post-edit** and **Post-edited**. To download the Translator Accuracy report, click **Export** and select the preferred export format (CSV, XLSX, or JSON).  ## [Contribution Raw Data Report](#contribution-raw-data-report) [Section titled “Contribution Raw Data Report”](#contribution-raw-data-report) In addition to the Translation Cost report, which is based on the Contribution Raw Data and grouped by languages, you can retrieve this detailed contribution raw data using the [Generate Report](/developer/api/v2/#operation/api.projects.reports.post) (Contribution Raw Data schema) or via the [Raw Report Data](https://store.crowdin.com/raw-report) app available on the Crowdin Store. This allows you to generate your own custom report according to your specific requirements. The Contribution Raw Data report provides various columns depending on the selected mode (translations, approvals, or votes). Each column offers specific insights, for example `source string text hash`, which is useful for identifying changes in source strings despite having the same `stringId`. It’s important to note that multiple records can exist for the same `stringId` if the source hash or plural form varies. For repeated translations by the same user on the same source string, into the same target language, the same plural form, and if the source text has not changed, only the `translationId`, `targetUnits`, and `updatedAt` columns will update in the report statistics. Deleted translations are also included in the count. Understanding these columns can help you better interpret the raw data and optimize your localization process. View the available report columns and their mode applicability (i.e., translations, approvals, and votes) in the following table: | Name | Available in Report Mode | Description | | ---------------------- | ------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `userId` | Translations, Approvals, Votes | **Type:** `integer`Numeric identifier of a user who added a translation. | | `languageId` | Translations, Approvals, Votes | **Type:** `string`Target language identifier ([Crowdin language code](/developer/language-codes/) (e.g., uk)). | | `stringId` | Translations, Approvals, Votes | **Type:** `integer`Numeric string identifier in Crowdin project. | | `translationId` | Translations, Approvals, Votes | **Type:** `integer`Numeric identifier of the translation in Crowdin project. | | `fileId` | Translations, Approvals, Votes | **Type:** `integer`Numeric file identifier in Crowdin project where the source string is stored. | | `filePath` | Translations, Approvals, Votes | **Type:** `string`Path to the file that contains the source string (e.g., /main/docs/index.md). | | `pluralForm` | Translations, Approvals, Votes | **Type:** `string`Translation plural form (each plural form is displayed as a separate record in the report). | | `sourceStringTextHash` | Translations, Approvals, Votes | **Type:** `string`Hash of the source string. | | `mtEngine` | Translations, Approvals, Votes | **Type:** `string`MT engine name from which a translation was provided. | | `mtId` | Translations, Approvals, Votes | **Type:** `integer`Numeric MT engine identifier. | | `tmName` | Translations, Approvals, Votes | **Type:** `string`Translation memory name from which a translation was provided. | | `tmId` | Translations, Approvals, Votes | **Type:** `integer`Numeric translation memory identifier. | | `preTranslated` | Translations, Approvals, Votes | **Type:** `string`Specifies if a translation was applied via pre-translation. | | `tmMatch` | Translations | **Type:** `integer`The highest match value of the translation with other TM suggestions, if any. | | `mtMatch` | Translations | **Type:** `integer`The highest match value of the translation with other MT suggestions, if any. | | `suggestionMatch` | Translations | **Type:** `integer`The highest match value of the translation with suggestions from other translators, if any. | | `sourceUnits` | Translations, Approvals, Votes | **Type:** `integer`Specifies the number of words in the source text (available only if `strings` unit type is not selected). | | `targetUnits` | Translations, Approvals, Votes | **Type:** `integer`Specifies the number of words in the translation (available only if `strings` unit type is not selected). | | `createdAt` | Translations, Approvals, Votes | **Type:** `datetime`Specifies the date when the string was initially translated. | | `updatedAt` | Translations, Approvals, Votes | **Type:** `datetime`Specifies the date when the last translation was added. | | `mark` | Votes | **Type:** `string`A vote mark that indicates how the translation rating has changed (e.g., if a translation has been voted up or down, or if the vote has been canceled). | ## [Top Members](#top-members) [Section titled “Top Members”](#top-members) The Top Members report allows you to see who contributed the most to your project’s translation. Default parameters: * *Text unit*: words * *Time period*: Last 30 days * *Sorted by*: translated text units. A member who translated the most is placed at the top of the list. * *Languages*: all languages * *Contributors*: all The **YOU** label appears next to your own username in the report table, making it easier to identify your personal contribution. Re-sort the members by clicking on the needed parameter. For example, if you want to analyze members by their proofreading activity, click on the *Approved* parameter to redo sorting. ### [Generating a Custom List of Top Members](#generating-a-custom-list-of-top-members) [Section titled “Generating a Custom List of Top Members”](#generating-a-custom-list-of-top-members) To generate a custom list of top members, follow these steps: 1. Select the preferred report unit (words, strings, characters with or without spaces). 2. Select the time period for which you want to see the activity of contributors. 3. To make a list of contributors for a specific language, select the language you need from the drop-down menu above the list. Alternatively, select **All languages**. 4. Click **Generate**. To find a specific member, use the search field. To open the member’s profile page, double-click on the name. The Top Members list includes the following columns: * *Rank* – contributor’s position in the list based on the currently selected sorting criteria (e.g., *Translated*, *Approved*, etc.). * *Name* – contributor’s first name, last name and username. * *Languages* – project languages. * *Translated* – the number of translated source content units. * *Target Words* – the number of translated content units in a target language.\ This parameter is not available for the *Strings* content unit because the number of source and translated strings is always the same. * *Approved* – the number of approved content units. * *Voted* – the number of votes a contributor made. * *”+” votes received* – the number of upvotes a contributor received for translations. * *”-” votes received* – the number of downvotes a contributor received for translations. * *Winning* – the number of approvals a contributor received for translations. * *Joined* – the date a member joined a project. To customize the visibility of columns in the report, click at the upper-right side of the table and select the preferred ones. To download the Top Members report, click **Export** and select the preferred export format (CSV, XLSX, or JSON).  ## [Archive](#archive) [Section titled “Archive”](#archive) The Archive section allows you to access the records of previously generated Cost estimate and Translation cost reports, providing a convenient way to review historical data. This section also eliminates the need to wait for a report generation to complete. You can initiate a report generation and return to it later at your convenience. Within the Archive, you can review the report summary and, if necessary, download it in various supported file formats. Each project has its own independent archive section with previously generated reports available only to project members with manager permissions (or higher). Reports generated by translators based on their contributions are not added to the archives. ### [Viewing Previously Generated Reports](#viewing-previously-generated-reports) [Section titled “Viewing Previously Generated Reports”](#viewing-previously-generated-reports) To view the summary of the previously generated reports (i.e., archive records), follow these steps: 1. Open your project and go to **Reports > Archive**. 2. Click on the name of the needed archive record. 3. Once you open the archive report record, you can view all the needed data.  ### [Exporting Previously Generated Reports](#exporting-previously-generated-reports) [Section titled “Exporting Previously Generated Reports”](#exporting-previously-generated-reports) To export the previously generated reports, follow these steps: 1. Open your project and go to **Reports > Archive**. 2. Click on the needed report in the list. 3. Click on the preferred file format to export. ### [Deleting Previously Generated Reports](#deleting-previously-generated-reports) [Section titled “Deleting Previously Generated Reports”](#deleting-previously-generated-reports) To delete the previously generated reports, follow these steps: 1. Open your project and go to **Reports > Archive**. 2. Click on the needed report in the list. 3. Click **Delete**. ## [See Also](#see-also) [Section titled “See Also”](#see-also) [Contributor Reports ](/contributor-reports/)Estimate and count the price of your contribution to the project. # Project Settings > Configure project settings according to your needs You can configure project settings according to your needs in the **Settings** tab. In the **General** section, you can change the project name, add a public description, customize the appearance of your project, and share the localization progress by embedding badges. ## [Name](#name) [Section titled “Name”](#name) In the **Name** section, you can change the project name and add a public description.  ## [Project Language Page View Beta](#project-language-page-view) [Section titled “Project Language Page View ”Beta](#project-language-page-view) This section allows you to choose how translators interact with the content on your project’s language page. * **Show files only** – this option is useful if your project focuses on file-based translation without the need for visual context. It’s an easy setup for projects where the text is self-explanatory or where screenshots aren’t necessary. * **Show files and tagged screenshots** – displaying both files and tagged screenshots allows translators to reference visual context alongside the text. This option is useful for projects where the meaning of the text can be influenced by its visual environment, improving translation accuracy. * **Show screenshots only** – select this option if every string in your project is associated with a screenshot. By providing visual context for all text, you can significantly improve the quality of translations. This method is considered best practice, especially for projects with complex interfaces or where visual elements are crucial for understanding. However, it requires effort to maintain the accuracy and relevance of the screenshots. ## [Branding](#branding) [Section titled “Branding”](#branding) In the **Branding** section, you can customize the appearance of your project by setting up a custom domain and project logo. ### [Custom Domain](#custom-domain) [Section titled “Custom Domain”](#custom-domain) The custom domain feature allows you to host your Crowdin project on your own domain that supports the HTTPS protocol. To set up a custom domain, follow these steps: 1. Create a necessary domain in the domain name registrar. 2. Create a CNAME DNS record for this domain name pointing to `cname.crowdin.com` in your hosting service. 3. Open your Crowdin project and go to **Settings > General > Branding**. 4. Enter the created domain name into the **Custom Domain** field and click **Update**. For security reasons, new users will be redirected to Crowdin to login and stay at the default address, but when a logged-in users enter your domain, they will be able to access the project from your own domain. ### [Project Logo](#project-logo) [Section titled “Project Logo”](#project-logo) The project logo allows you to customize the appearance of your project’s main page.  ## [Badges](#badges) [Section titled “Badges”](#badges) With badges, you can share the localization progress of your Crowdin project by embedding them into your website or README. To embed badges, follow these steps: 1. Open your Crowdin project and go to **Settings > General > Badges**. 2. Enable **Display badges**. 3. Copy the badge code using Markdown, HTML, or Image URL. 4. Paste the badge code on your website or README.  [Badges & Status Images ](https://store.crowdin.com/bds)Badges & Status Images application allows to generate badges, charts, and additional graphics for each language in your Crowdin Project. ## [Delete Project](#delete-project) [Section titled “Delete Project”](#delete-project) This option is accessible exclusively to the project owner. You can delete your Crowdin project with all the translations and related localization resources if necessary. Danger Deleting the project will permanently delete all the resources associated with the project, including uploaded files, translations, approvals, etc. Deleted projects cannot be restored! # AI Settings > Configure and manage AI prompts in your project settings In your project’s **Settings > AI** section, you can configure and manage AI prompts and select prompts to be used in the Editor for features like AI Assistant, AI Suggestions, and AI-powered QA Check. By default, the prompts to be used in the Editor are applied from the AI settings of the project owner’s account. If default AI settings in the project owner’s account are not configured to apply automatically to all projects, it’s necessary to select the appropriate AI prompts in the project’s settings to activate the AI Assistant, AI Suggestions, and AI-powered QA Check features. Otherwise, these features will remain inactive. The AI prompts configured in the project settings will also be added to the list of AI prompts of the project owner’s Crowdin account. AI Prompt Types: * Pre-Translate * AI in Editor * QA Check * Custom type [Configuring AI Prompts ](/crowdin-ai/#configuring-ai-prompts) Before the AI Prompts can be configured in the project settings, it’s also necessary for the project owner to [configure the AI Providers](/crowdin-ai/#configuring-ai-providers).  ## [Selecting AI Prompts](#selecting-ai-prompts) [Section titled “Selecting AI Prompts”](#selecting-ai-prompts) To select the AI prompts to be used in the Editor, follow these steps: 1. Open your project and go to **Settings > AI**. 2. Click on the **Settings** tab. 3. Select the AI prompts from the drop-down menus for AI Assistant in editor, AI Suggestion in editor, and QA Check. Read more about [Crowdin AI](/crowdin-ai/). # Project Tab Settings > Configure the visibility and order of project tabs In the **Customize Tabs** section, you can manage the display of your project tabs, including their sorting order and visibility. This applies to both default project tabs and those from [Starred Apps and Starred Tools](/integrations/#starred-apps). This section only modifies how tabs appear in the project interface and does not disable or block the tabs themselves. The configured order and visibility of project tabs are displayed to all project members.  ## [Reordering Project Tabs](#reordering-project-tabs) [Section titled “Reordering Project Tabs”](#reordering-project-tabs) To reorder the project tabs, follow these steps: 1. Open your project and go to **Settings > Customize Tabs**. 2. Hover over next to the tab you want to move, then click and drag it to the preferred position in the list. ## [Toggling Tab Visibility](#toggling-tab-visibility) [Section titled “Toggling Tab Visibility”](#toggling-tab-visibility) To hide or show project tabs, follow these steps: 1. Open your project and go to **Settings > Customize Tabs**. 2. Clear the checkbox next to a tab’s name to hide it, or select it to make it visible. ## [Resetting Tab Settings](#resetting-tab-settings) [Section titled “Resetting Tab Settings”](#resetting-tab-settings) To reset the project tab order and visibility to their default settings, open your project and go to **Settings > Customize Tabs**, scroll down to the bottom of the list and click **Reset to defaults**. # Export Settings > Configure the translations export behavior In the **Export** section of the Project Settings, you can configure the translations export behavior. There are several options available to customize the export settings according to your needs including advanced options for each specific language. ## [Translations Export Settings](#translations-export-settings) [Section titled “Translations Export Settings”](#translations-export-settings) By default, when exporting translations, Crowdin fills untranslated strings with source text to avoid exporting empty files. You can change this behavior by using the options below. ### [Save context information in the files](#save-context-information-in-the-files) [Section titled “Save context information in the files”](#save-context-information-in-the-files) The context and max.length added in Crowdin will be visible in the downloaded files. This option only applies to CSV, Android XML, iOS strings, and RESX formats. Limitations This option only partially applies to iOS strings and RESX formats (i.e., only the context added in Crowdin will be visible in the downloaded files). ### [Skip untranslated strings](#skip-untranslated-strings) [Section titled “Skip untranslated strings”](#skip-untranslated-strings) Only translated strings will be included in the exported translation files. This option works in three different ways, depending on the file format. This option is not applied to text-formatted documents since missing texts can make downloaded files unreadable. Others are exported with empty values. And for the third file category, untranslated strings are entirely removed from the exported translation files. | Option not applied | Untranslated strings exported with empty values | Untranslated strings removed | | ---------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | DOCX, IDML, DITA, ADOC, MD, MediaWiki, TXT, HAML, HTML, assets, FM MD, FM HTML, Contentful JSON, SVG | JSON (with nested structure), PHP, XLSX, CSV, FJS, RC, XAML, XML, Web XML, TypeScript, JS, TOML, QT TS, i18next JSON, gettext PO, FLSNP, Coffee | Android XML, macOS/iOS Strings, Stringsdict, Chrome JSON, JSON (without nested structure), YAML, XLIFF, XLIFF 2.0, ARB, DTD, RRC, GO JSON, Flex, Joomla INI, Maxthon, Java Properties, Play Properties, Java Properties XML, RES JSON, RESW, RESX, SBV, STR, STF, VTT, WXL, VDF, FBT JSON | ### [Skip untranslated files](#skip-untranslated-files) [Section titled “Skip untranslated files”](#skip-untranslated-files) Only 100% translated files will be included in the exported translation archive. ### [Export only approved translations](#export-only-approved-translations) [Section titled “Export only approved translations”](#export-only-approved-translations) Only texts that are both translated and approved will be included in the exported translation files. ### [Automatically fill in regional dialects](#automatically-fill-in-regional-dialects) [Section titled “Automatically fill in regional dialects”](#automatically-fill-in-regional-dialects) Useful when the project is translated into the language dialects (e.g., Spanish, Argentina). On export, translations from Spanish will be automatically copied to untranslated strings in Spanish, Argentina. # File Processor Settings > Customize processing for supported file formats File processors allow you to customize processing for supported file formats. It can be useful if you want to edit the file content before it’s imported by Crowdin. The File Processors are implemented as Crowdin Apps. You can create your own File Processor or use the existing ones.  [Explore File Processors in Store ](https://store.crowdin.com/tags/file-processors) [Create a File Processor ](/developer/crowdin-apps-modules-file-processing/) ## [Managing File Processors](#managing-file-processors) [Section titled “Managing File Processors”](#managing-file-processors) To manage File Processors, go to the **File Processors** section of your project settings. ### [Configuring the Processing Order](#configuring-the-processing-order) [Section titled “Configuring the Processing Order”](#configuring-the-processing-order) The processing order of File Processors determines how modules of the same type are executed in your project. The order value sets the priority, starting with 0 (highest priority) and increasing incrementally. The sequence you set can significantly impact the outcome. For example, if you are translating a CSV file and have installed two apps with `file-post-export` modules: * The first module escapes HTML tags in strings, transforming `` into `\<\/h1\>`. * The second module checks if all closing tags are present and adds them if they are missing. The processing order of these modules will lead to different results: * If the HTML tag escaping module runs first, followed by the tag verification module, the output might be: * `

Hello World!` => `\Hello World!` => `\Hello World!

` * If the order is reversed, with the tag verification module running first, the output will be: * `

Hello World!` => `

Hello World!

` => `\Hello World!\<\/h1\>` Caution When multiple file-processing modules of the same type (e.g., `file-post-export`) share identical order value, unexpected behavior may occur. In such cases, the system selects which module to execute first based on the installation date of file-processing apps, potentially disrupting the intended processing sequence. Therefore, it is recommended to adjust the identical order values to ensure that files are processed in the desired sequence. ### [Editing File Processor settings](#editing-file-processor-settings) [Section titled “Editing File Processor settings”](#editing-file-processor-settings) To Edit the File Processor settings, follow these steps: 1. Open your project and go to the **Settings > File Processors** tab. 2. Click toward the needed processor and select **Edit**. 3. Make the necessary changes and click **Submit**. The processor settings may vary depending on the processor you are using. # Glossary Settings > Configure and manage glossaries for your project With a glossary, you can create, store, and manage all the project terminology in one place. The main aim of terminology is to explain some specific terms or the ones often used in the project to be translated properly and consistently. Read more about [Glossary](/glossary/). ## [Assigning Glossary](#assigning-glossary) [Section titled “Assigning Glossary”](#assigning-glossary) To assign a glossary to your project, in the **Glossaries** section, select the needed glossaries from the list.  ## [Changing Default Glossary](#changing-default-glossary) [Section titled “Changing Default Glossary”](#changing-default-glossary) To change your project’s default glossary, in the **Glossaries** section, click the icon next to the needed glossary in the list. # Import Settings > Configure how placeholders, duplicates, and word counts are handled In the **Import** section of the Project Settings, you can configure how Crowdin should handle placeholders, duplicate strings, and word counts in your project. ## [Source Strings](#source-strings) [Section titled “Source Strings”](#source-strings) Improve the translation consistency and streamline your workflow by unifying placeholders and handling duplicate strings. ### [Unify Placeholders](#unify-placeholders) [Section titled “Unify Placeholders”](#unify-placeholders) Enable the transformation of the placeholders to the unified format to improve the work with TM suggestions. On export, the placeholders in translations are transformed back to the original format. If your project contains iOS strings, iOS XLIFF, and Android XML files, you can enable the **Unify placeholders** option, and the system will transform placeholders into a unified look. For example, Crowdin will make the Android string `Hello, %s!`, and the iOS string `Hello, %@!` look in the Editor this way: `Hello, [%s]!`. This option is beneficial when you work with TM since TM suggestions from iOS strings, iOS XLIFF, and Android XML will be completely interchangeable. Crowdin will transform the translation placeholders back to the original format on export. This option only applies to iOS strings, iOS XLIFF, and Android XML formats. ### [Duplicate Strings](#duplicate-strings) [Section titled “Duplicate Strings”](#duplicate-strings) You can save time by translating all duplicates with the same translation and hiding these instances from translators. This can affect accuracy. Crowdin’s localization process is based on translating source strings to the defined target languages. Source strings are uploaded to the system in localization files. Each unique source string first uploaded or added (for CSV and other formats supporting [string editing](/string-management/#string-editing)) in Crowdin is considered a master string. All other strings that are identical to the master string but were uploaded or created later are considered duplicate strings. #### [Duplicate Strings Management](#duplicate-strings-management) [Section titled “Duplicate Strings Management”](#duplicate-strings-management) If your project contains duplicated strings, you can choose how the system should treat them using the following options: * **Show** – translators will translate each instance (string) separately. Duplicate strings won’t be hidden. * **Show, but auto-translate them** – duplicate strings will be automatically translated but remain visible to translators. Once the master string is translated, its translation is automatically shared with all duplicates. Translators can review and re-translate each duplicate with their own translation as needed. If a unique translation is provided for a specific duplicate, it will override the shared translation for that string alone, allowing for precise context-specific translations without affecting the other duplicates. If a translator removes a duplicate’s unique translation, it will be automatically translated with a translation from a master string. * **Show within a version branch (regular detection)** – duplicates will be hidden only between [version branches](/version-management/). * **Show within a version branch (strict detection)** – duplicates will be hidden only between version branches. * **Hide (regular detection)** – all duplicates will share the same translation. * **Hide (strict detection)** – all duplicates will share the same translation. Regular duplicate detection – when comparing strings, Crowdin considers only source texts. Strict duplicate detection – when comparing strings, Crowdin considers both string identifiers (keys) and source texts. #### [Show all duplicates](#show-all-duplicates) [Section titled “Show all duplicates”](#show-all-duplicates) When this option is selected, all duplicate strings will be visible to translators. Each duplicate will require a separate translation. 💡 **Use case**: works perfectly for projects where the same words might have various meanings depending on the context. #### [Show, but auto-translate duplicates](#show-but-auto-translate-duplicates) [Section titled “Show, but auto-translate duplicates”](#show-but-auto-translate-duplicates) When this option is selected, all duplicate strings are shown and automatically translated. Once the master string is translated, its translation is automatically shared among all duplicates. This allows translators to review and re-translate duplicate strings if necessary. 💡 **Use case**: works excellently if you want to save time but still require automatic translations to be reviewed. To better illustrate how the **Show, but auto-translate them** option works, consider the following five-string JSON file: two strings are unique, and three strings have identical source text. ```json { "hello": "Hello", "welcome": "Welcome!", "save1": "Save", "save2": "Save", "save3": "Save" } ``` Upon importing this file, the system marks the first of these identical strings (`"save1": "Save"`) as the master string with the “Master” marking, while the subsequent two identical strings (`"save2": "Save"` and `"save3": "Save"`) are labeled as duplicates of this master string with the “Duplicate” marking. Once you set the Duplicate strings option to **Show, but auto-translate them**, the system keeps all five strings visible to translators and for the master string and its two duplicates, automatic translation propagation is enabled. This means that translations are automatically shared from the master string to its duplicates. Let’s consider the following scenarios: * *Master string is translated first* – the system immediately propagates the translation of the master string to its duplicates. As a result, all three identical strings (the master string and its two duplicates) are displayed with translations. However, translators can review and re-translate each duplicate with their own translation as needed. If a unique translation is provided for a specific duplicate, it will override the shared translation for that string alone, allowing for precise context-specific translations without affecting the other duplicates. If a translator removes a duplicate’s unique translation, it will be automatically translated with a translation from a master string. * *One of the duplicates is translated first* – the system does not propagate the translation of the duplicate to the master string or the other duplicate. Consequently, one duplicate string is displayed with a translation, while the master string and the other duplicate remain untranslated. #### [Show within a version branch. Duplicates will be hidden only between version branches](#show-within-a-version-branch-duplicates-will-be-hidden-only-between-version-branches) [Section titled “Show within a version branch. Duplicates will be hidden only between version branches”](#show-within-a-version-branch-duplicates-will-be-hidden-only-between-version-branches) When this option is selected, only the master strings that were originally uploaded to the system will be available for translation. All duplicate strings will automatically get the translations of the original strings and will be hidden in all version branches. This option is available in two versions: regular duplicate detection, strict duplicate detection. If your source files contain strings with apparent identifiers (keys), it’s better to use a *strict* version of this option. In other cases, feel free to use a *regular* one. Here are a few things to keep in mind: * The system always checks the path to the string throughout the branches. For example, even if the strings are the same in different version branches (`branch1` and `branch2`), but their paths are different (branch1 - `/localization/android.xml` and branch2 - `/localization/apps/android.xml`), they won’t be recognized as duplicates. * This option works only for the strings located in the files that have the same format. For example, if there is the same string in `android.xml` and `ios.strings` files, it won’t be recognized as a duplicate. 💡 **Use case**: works perfectly for continuous projects with various version branches. Allows translators to work with unique strings in separate branches. #### [Hide all duplicates](#hide-all-duplicates) [Section titled “Hide all duplicates”](#hide-all-duplicates) When this option is selected, the system spots the duplicate strings in all files. Only the master strings that were originally uploaded are visible and should be translated. The hidden duplicate strings will automatically share the translations from the corresponding master strings. This option is available in two versions: regular duplicate detection, strict duplicate detection. If your source files contain strings with apparent identifiers (keys), it’s better to use a *strict* version of this option. In other cases, feel free to use a *regular* one. 💡 **Use case**: works great for projects with narrow scopes where all duplicates share the same context. ## [Word count](#word-count) [Section titled “Word count”](#word-count) You can set the preferred way Crowdin should count words in your project. Specifically, it applies to whether HTML tags should be counted as regular words or not. By default, Crowdin considers HTML tags as regular words for most of the supported formats, excluding the following ones: HTML, Front Matter HTML, HAML, MD, Front Matter MD, XML, WEBXML, IDML, XLIFF, XLIFF 2.0, ADOC, DOCX, DITA. * **Auto (default)** – HTML tags will be counted as regular words or skipped depending on the source file format. * **Count tags** – all HTML tags will be counted as regular words. * **Skip tags** – all HTML tags won’t be counted. More information about Crowdin [Word Counter](/word-counter/). # Label Settings > Use labels in your project to easily organize your resources Use labels in your project to easily organize resources (e.g., screenshots, strings, etc.) by specific topics. Once you add labels, you can filter items by those labels. If you already use labels for your source strings, you can use the same labels for screenshots. ## [Managing Project Labels](#managing-project-labels) [Section titled “Managing Project Labels”](#managing-project-labels) To create, edit, or remove project labels, follow these steps: 1. Open your project **Settings** tab. 2. Select the **Labels** section. 3. In the appeared screen, add new labels and edit or remove existing ones.  To edit or remove a label, click on the label you want to edit or remove and select the appropriate action. Use the **Search** field above the label list to quickly find specific labels. Caution Labels are case insensitive (e.g., `Label` and `label` are treated as identical). ## [See Also](#see-also) [Section titled “See Also”](#see-also) [Adding Labels to Strings ](/string-management/#labels) [Adding Labels to Screenshots ](/screenshots/#labels) # Language Settings > Manage your project source and target languages In the Languages section, you can manage your project source and target languages and configure language mapping to use custom language codes. ## [Source Language](#source-language) [Section titled “Source Language”](#source-language) The source language is the language you’re translating from. If you want to change the source language for your project, select a new language from the drop-down list and click **Update**. Here are a few points you should be aware of when changing the project’s source language: * Please note that there might be a plural form mismatch for imported strings depending on the new source language. For example, some plural forms might not be displayed in the Editor, or some plural form translations might be used in other ones on translation export. We recommend updating the source files if the new source language has different plural forms than the initial one. * If you had an opened browser tab with the Editor during the source language update, you might need to refresh it for changes to take effect and continue translating from the new source language. ## [Target Languages](#target-languages) [Section titled “Target Languages”](#target-languages) The **Target Languages** section allows you to add or remove target languages in your project, copy the target languages list from one project to another, and add custom languages. You can update your target languages anytime. To add or remove target languages in your project, follow these steps: 1. Open your project and go to **Settings > Languages**. 2. In the **Target Languages** section, you can make the following changes: * Select the languages you want to add to the project in the left panel. * Click on the languages you want to remove from the project in the right panel. 3. Click **Save**.  ### [Copying Target Languages](#copying-target-languages) [Section titled “Copying Target Languages”](#copying-target-languages) If you translate multiple projects into the same target languages, you can copy the target languages list from one project to another in a few clicks: 1. Open your project and go to **Settings > Languages**. 2. In the **Target Languages** section, click **Pre-fill** and select **Copy From Project…**. 3. Select the project you’d like to copy target languages from and click **Choose**.  4. Click **Save**. ### [Adding Custom Languages](#adding-custom-languages) [Section titled “Adding Custom Languages”](#adding-custom-languages) If you’d like to translate your project into rare or less common target languages that are not officially supported at the moment, you can still add them as custom languages. To add a custom language, follow these steps: 1. Open your project and go to **Settings > Languages**. 2. In the **Target Languages** section, click **Custom Languages**.  3. Click **Add**. 4. Specify a language name. 5. If your custom language is a dialect of any of the supported languages, select it from **The dialect of** drop-down menu. 6. Fill in language code fields. 7. Set the preferred text direction and plural forms options. 8. Click **Save**.  ### [Adding Custom Language Codes](#adding-custom-language-codes) [Section titled “Adding Custom Language Codes”](#adding-custom-language-codes) To add language mapping, follow these steps: 1. Open your project and go to **Settings > Languages**. 2. Scroll down to the **Add custom language codes** section. 3. Click **Language Mapping**. 4. Choose the necessary language and placeholder. 5. Add custom code. 6. You can map as many languages as you need. Click **Add Mapping** to add another custom code. 7. Click **Save**.  ## [See Also](#see-also) [Section titled “See Also”](#see-also) [Supported Languages ](/developer/language-codes/)Explore the list of languages supported by Crowdin. # Machine Translation Settings > Configure machine translation settings for your project In the **Machine Translation** section, you can manage the following settings: * **Show machine translation suggestions** – enable MT suggestions from machine translation engines such as Microsoft Translator, Google Translate, and others to be displayed in the Editor. ## [See Also](#see-also) [Section titled “See Also”](#see-also) [MT Engines ](https://store.crowdin.com/categories/machine-translation)Explore the list of supported machine translation engines and learn how to configure them. [Machine Translation ](/machine-translation/)Learn how to configure machine translation engines. [Pre-Translation ](/pre-translation/)Speed up the translation process and ease the work of translators. # Parser Configuration Settings > Configure import and export behavior for supported file formats The Parser configuration feature lets you change the default import and export behavior predefined for file formats supported by Crowdin. Parser configuration in a specific project is applied only to files stored in this project. You can set the parser configuration for all files of a certain format or single files. Once you save the parser configuration for some file format, you can upload source files to your project, and Crowdin will apply your settings accordingly. You can configure import and export behavior for the following formats: Java Properties, Generic XML, DITA, AsciiDoc, Plain text, MadCap Flare, HTML, Office documents, Adobe FrameMaker, Adobe InDesign, Markdown, and MediaWiki.  Caution Some parser settings may be unavailable in [string-based](/creating-project/#string-based-project) projects. ## [Parser Configuration Parameters](#parser-configuration-parameters) [Section titled “Parser Configuration Parameters”](#parser-configuration-parameters) Some parameters are common to all formats, while others are format-specific. In the table below, you can see the available parser parameters and formats they could be configured for. | Parameter | Description | Format | | --------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | | Content segmentation | On import, the source file’s content will be split into shorter text segments using predefined segmentation rules (SRX 2.0). | Generic XML, DITA, AsciiDoc, MadCap Flare, HTML, Office documents, Adobe FrameMaker, Adobe InDesign, Markdown | | Custom segmentation rules | Defines your own segmentation rules.Read more about [Custom Segmentation](/custom-segmentation/). | Generic XML, DITA, AsciiDoc, Plain text, MadCap Flare, HTML, Office documents, Adobe FrameMaker, Adobe InDesign, Markdown, MediaWiki | | Excluded elements | Defines a list of CSS style selectors for elements that should not be available for translation (e.g., code, pre > code, .code-block). Applicable only to block elements. Inline elements are ignored. | HTML, HTML with Front Matter | | Excluded front matter elements | Defines a list of front matter elements that should not be available for translation (e.g., keywords, “internal.description”, tags). The path elements should be delimited by a period. The keys containing a period must be enclosed in quotation marks. | HTML with Front Matter, MDX | | Exclude code blocks | Defines whether to import code blocks. Applicable only to code blocks. Inline elements with code are ignored. | MDX | | Translate content | Texts stored inside the tags will be available for translation. | Generic XML | | Translate attributes | Tag attributes will be available for translation. | Generic XML | | Translatable elements | Defines the specific nodes and attributes to be available for translation. | Generic XML | | Escape single quote | Defines the behavior regarding a single quote escaping in exported translations. Available options:- Do not escape single quote - Escape single quote by backslash (`It's okay`⇒`It\'s okay`) - Escape single quote by another single quote (`It's okay`⇒`It''s okay`) - Escape single quote by another single quote only in strings containing variables `{0}` (`{0} it's okay`⇒`{0} it''s okay`) | Java Properties | | Escape special characters | Any special characters (i.e., `=`, `:`, `!`, `#`) will be escaped by a backslash `\` in exported translations. | Java Properties | | Clean tags aggressively | Additional formatting tags related to text spacing will be removed on import. Useful when translating Office documents converted from other formats (e.g., PDF, etc.), and the conversion introduced lots of unnecessary formatting tags. | Office documents | | Translate hyperlink URLs | Hyperlink URLs will be available for translation. | Office documents | | Translate hidden text | The hidden text will be available for translation. | Office documents | | Translate hidden rows and columns | The hidden rows and columns will be available for translation. | Office documents | | Import hidden slides | The hidden slides will be available for translation. | Office documents | | Import notes | The slide notes will be available for translation. | Office documents | ## [Parser Configuration for All Project Files of a Specific Format](#parser-configuration-for-all-project-files-of-a-specific-format) [Section titled “Parser Configuration for All Project Files of a Specific Format”](#parser-configuration-for-all-project-files-of-a-specific-format) To set the preferred parser configuration for all files of a specific format, follow these steps: 1. Open your project and go to **Settings > Parser configuration**. 2. Choose the needed file format and click Edit. 3. Set the preferred settings. 4. Click **Save**. To add a new file format, click **Add Apps** and install the required format. ## [Parser Configuration for a Single File](#parser-configuration-for-a-single-file) [Section titled “Parser Configuration for a Single File”](#parser-configuration-for-a-single-file) In some cases, you might need to set the parser configuration not for all files of some file format but just for a single file. To set the parser configuration for a single file, follow these steps: 1. Open your project and go to **Sources > Files**. 2. Double-click on the needed file. 3. In the appeared dialog, switch to the **Parser configuration** tab. 4. Set the preferred settings. 5. Click **Save**. Once you save the file parser configuration, Crowdin will reimport this file and apply your settings. Read more about [file management](/file-management/) in Crowdin. # Pre-Translate Settings > Configure the automatic pre-translation of new content in project In the **Pre-translate** section of the Project Settings, you can configure the automatic pre-translation of new content uploaded to the project. You can choose to use translation memory, machine translation engines, or AI-powered translations to pre-translate the content.  When the **Pre-translate New Content Automatically** is enabled, Pre-translate will be triggered when new content is uploaded, when target languages are changed, and when file settings are changed. ## [TM Pre-translate](#tm-pre-translate) [Section titled “TM Pre-translate”](#tm-pre-translate) You can enable and configure the automatic pre-translation via TM. When enabled, the system will automatically apply translations from your TM in the following cases: when there is newly uploaded content, when target languages change, or after file settings are modified. * **Match Ratio** – select TM Match type of TM suggestions that should be applied during automatic pre-translation: * 100% Match * Perfect Match * **Approve Added Translations** – select whether to approve new translations. Further configure it with the following options: * With perfect match – approves only Perfect match translations. * With perfect match (approved previously) – approve Perfect match translations that were previously approved. * All (skip auto-substituted suggestions) – approve all except auto-substituted translations. * All – approve all new translations added during the pre-translation. Read more about [Translation Memory](/translation-memory/). ## [MT Pre-translate](#mt-pre-translate) [Section titled “MT Pre-translate”](#mt-pre-translate) Enable and configure the automatic pre-translation via MT. When enabled, the system will automatically apply translations provided by the selected MT engine in the following cases: when there is newly uploaded content, when target languages change, or after file settings are modified. You can configure the automatic pre-translation via MT by selecting the preferred MT engine and specifying all or selected project languages. Read more about [Machine Translation](/machine-translation/). ## [AI Pre-translate](#ai-pre-translate) [Section titled “AI Pre-translate”](#ai-pre-translate) Enable and configure automatic pre-translation via AI. When enabled, the system will automatically apply translations provided by the selected AI engine in the following cases: when new content is uploaded, when target languages change, or after file settings are modified. You can choose your preferred AI prompt and specify all or selected project languages. You can configure several different prompts for different languages. Click the plus button to configure a new prompt for AI Pre-translation. Read more about [Crowdin AI](/crowdin-ai/). # Privacy & Collaboration Settings > Configure the visibility of your project and its contents In the *Privacy & Collaboration* section of the *Project Settings* you can manage the visibility of your project and its contents. You can also configure the notifications sent to project participants. ## [Project visibility](#project-visibility) [Section titled “Project visibility”](#project-visibility) Set the preferred visibility for your project with the following options: * **Public project** – public projects can be found via search engines and Crowdin search. Crowdin users can join public projects without approval if the **Moderated project joining** option is disabled. * **Private project** – private projects can’t be found via search engines and Crowdin search. Only the invited users can join the project. ## [Privacy](#privacy) [Section titled “Privacy”](#privacy) Configure your project privacy settings with the following options: * **Two-factor authentication** – specify which project members are required to enable two-factor authentication in their **Account Settings > Account** tab to access the private project. This role-based option provides the following configurations: * **Turned off** – two-factor authentication is not required (default). * **All project members** – requires all project members to enable two-factor authentication, disabling other member category options. * **Managers** – requires only members with the Manager role to enable two-factor authentication. * **Developers** – requires only members with the Developer role to enable two-factor authentication. You can select the **Managers** and **Developers** options individually or together. After selecting your preferred categories, click **Update** to save changes. * **Moderated project joining** – require users to send requests to join the translation team of the preferred language. After the review, a project manager or proofreader can approve or decline the request. After joining the project, multilingual translators can submit new requests to join translation teams in other target languages. * **Task-based access control** – allow project members to work with tasks they are assigned to, even if they do not have full access to the language in the project. * **Allow offline translation** – allow translators to download source files to their machines for offline translation and upload translations back into the project. The project owner and managers can always download sources and upload translations, not depending on the option status. * **Allow proofreaders to access hidden strings** – allow proofreaders to work with hidden strings. The project owner and managers can always work with hidden strings, not depending on the option status. ## [Glossary Access Settings](#glossary-access-settings) [Section titled “Glossary Access Settings”](#glossary-access-settings) Control the level of access that project members have over glossary terms. The project owner and managers always have full control over glossary terms, regardless of these settings. Configure the preferred glossary access level with the following options: * **Read only** – allow members to view existing glossary terms without the possibility to modify them. This option provides access for reference only. * **Manage drafts** – allow members to view, add, edit, and delete draft glossary terms, and view approved terms. This option allows members to contribute to drafts without altering approved terms. * **Full access** – allow members to view, add, edit, and delete glossary terms, as well as edit concept details. This option provides members with full control over glossary terms and their details. ## [Notifications](#notifications) [Section titled “Notifications”](#notifications) Project notifications are disabled by default. Enable the necessary notifications for an agile translation process. Such approach helps to avoid creating additional tasks for every contributor. * **Notify translators about new strings** – translators will receive an email notification about newly added content for translation each time after the update. The **Receive emails** option should be activated in the translator’s profile. * **Notify project managers and developers about new strings** – project managers will receive an email notification about newly added content for translation each time after the update. * **Notify project managers and developers about language translation/proofreading completion** – project managers will receive the notification when some target language (all source files) is fully translated or fully proofread. # QA Check Settings > Configure QA checks to ensure the quality of translations The main aim of quality assurance (QA) checks is to help you efficiently handle different language-specific aspects in translations and ensure they are formatted the same way as the source strings and will fit the UI just as well. Some typical QA check issues include missed commas, extra spaces, or typos. With QA checks, a proofreader will see all those kinds of issues that should be fixed, as they will be highlighted in the Side-by-Side mode in the Editor. QA checks help to detect some common mistakes easily and quickly. It’s recommended to review and resolve all QA check issues before building your project and downloading translations.  In the **QA Checks** section, you can manage the types of QA issues to be highlighted in the Editor during the translation process. ## [Configure QA Checks](#configure-qa-checks) [Section titled “Configure QA Checks”](#configure-qa-checks) By default, QA checks are enabled. To select the needed QA checks in your project, follow these steps: 1. Open your project and go to **Settings > QA Checks**. 2. Ensure that **Enable QA Checks** is selected.  3. Select the QA check types according to your preferences. 4. For each selected QA check type, choose whether it should be possible to save translations with QA issues by selecting one of two options: **Error** and **Warning**. * **Warning** – translators are notified about QA issues with suggestions for fixes, but they can still save the translation using the **Save anyway** button. * **Error** – translators are notified about QA issues with suggestions for fixes, and they cannot save the translation until all issues are resolved. 5. Scroll down to the bottom of the QA Checks list and click **Save**.  Once enabled, QA checks will work in the background and scan the translations for potential QA issues. ## [QA Check Parameters](#qa-check-parameters) [Section titled “QA Check Parameters”](#qa-check-parameters) **Empty translation** – strings that lack translation. **Length issues** – translated strings that are longer than the limit of characters you set. **Tags mismatch** – strings containing HTML tags might lack some opening or closing tags in translations. **Spaces mismatch** – multiple spaces in a row, missing spaces. **Variables mismatch** – placeholders that lack some parts of code or have the odd ones. **Punctuation mismatch** – punctuation mistakes or differences in the punctuation marks. **Character case mismatch** – lower or upper case used differently in source and translated strings. **Special characters mismatch** – new paragraphs, currency signs, and other special characters used differently in source and translated strings. **“Incorrect translation” issues** – created issues with the “current translation is wrong” tag. **Spelling mistakes** – words that aren’t present in the dictionaries Crowdin supports. Limitations Currently available for specific languages only. **ICU syntax** – the correct usage of ICU message syntax in translations. **Consistent terminology** – checks whether the source words are translated accordingly to the respective glossary terms. Limitations Currently available for English, German, Spanish, French, Italian, Dutch, Norwegian, Norwegian Bokmal, Polish, Russian, Swedish, Ukrainian, Japanese, Korean, Chinese Simplified, and Turkish. **Duplicate translation** – translations that duplicate already existing translations. **FTL syntax** – the correct usage of the FTL syntax in translations. **Android syntax** – the correct usage of the Android syntax in translations. **Numbers mismatch** – checks for inconsistencies or missing numbers between the source and translations. **AI-powered check** – uses AI to detect translation issues, improving accuracy and ensuring translations meet project-specific quality standards. Requires configuring an AI prompt with defined evaluation criteria. Read more about [Configuring AI-powered check](/crowdin-ai/#setting-up-ai-qa-check). ## [QA Status Options](#qa-status-options) [Section titled “QA Status Options”](#qa-status-options) OFF – when it’s not enabled. IN PROGRESS – while it’s working. NO ISSUES – when it found no mistakes. ISSUES FOUND – when it found some mistakes. ## [More Information On Found Issues](#more-information-on-found-issues) [Section titled “More Information On Found Issues”](#more-information-on-found-issues) If the QA check status is *Issues Found*, you can click on it, then click **View Issues** to get detailed information on the found issues.  In the unfolded language details section, you will see the number of issues found. To see them in detail, click **Suggestions with QA issues**.  After it, you will be redirected to the [Side-by-Side mode](/online-editor/#side-by-side-mode) of the Editor to check the list of strings with QA issues. You can approve the existing translations if they are supposed to be the way they are or make changes and then approve the translations. ## [Spell Checker Ignore List](#spell-checker-ignore-list) [Section titled “Spell Checker Ignore List”](#spell-checker-ignore-list) If your project contains some uncommon words that are not recognized by the Spell checker, you can add them to the Ignore list to exclude them from being checked.  To review the words added to the Ignore list for the Spell checker, follow these steps: 1. Open your project and go to **Settings > QA Checks**. 2. Click *Spellcheck Ignore list* at the bottom of the page. In the opened window you can see the list of words added to the ignore list. You can filter or remove them from the list if necessary. # Translation Memory Settings > Configure and assign Translation Memories for your project The project TM is automatically created for each project. By default, every approved or last added translation is saved to the project TM. This behavior can be customized to save only approved translations. * **Enable Auto-Substitution** – the feature substitutes the non-translatable elements (such as tags, HTML entities, placeholders, numbers, and more) in TM translation suggestions with the ones used in the source text. The feature improves the TM suggestions applied during pre-translation and those shown as translation suggestions in the Editor. Improved suggestions are included in the Translation Costs report, and improvable ones are included in the Costs Estimation report. * **TM Suggestions for Dialects** – the feature allows you to display and use TM suggestions from the primary language for dialects if no dialect-specific suggestions are available. * **Use global Translation Memory** – translators will have access to the Global Translation Memory, where all translations from the projects with this feature enabled are stored. * **Save only approved suggestion to Translation Memory** – when selected, translations are saved to the project default TM only after they are approved. This option is especially useful for public or crowdsourced projects where you want to ensure only reviewed translations are stored in the TM. * **TM Match Context Type** – the feature allows you to choose what should be considered as string context when suggesting Perfect (101%) match Translation Memory (TM) suggestions. You can choose between the following options: * Key and Context – when selected, the system considers both the key and context of strings for suggesting Perfect match TM suggestions. This mode is particularly useful for key-value file formats. * Auto – when selected, the system automatically applies the most suitable context consideration mode based on your file format. * Previous and next segment – when selected, the system considers the segments immediately preceding and following the current segment for context. Most applicable to HTML-based and other formats without a defined key-value structure. Read more about [TM Auto-Substitution](/translation-memory/#tm-auto-substitution). ## [Penalties](#penalties) [Section titled “Penalties”](#penalties) In the **Penalties** section, you can configure penalties that decrease the match percentage of TM suggestions based on specific conditions. This feature helps when you want to fine-tune the relevance of TM suggestions to your specific requirements.  You can configure the penalties using the following options: * **Auto-substitution Applied** – penalize TM suggestions to which an auto-substitution was applied. * **Multiple Identical TM Matches** – penalize TM suggestions where multiple identical TM matches are found. * **TM Priority Less Than** – penalize TM suggestions that originate from a TM with a priority lower than a specified value. Besides a penalty value, you can also set the preferred TM priority threshold. * **TM Suggestion Last Modified More Than** – penalize TM suggestions that were last modified more than a specified number of months ago. Besides a penalty value, you can also set the threshold in months. * **TM Suggestion Last Used More Than** – penalize TM suggestions that were last used more than a specified number of months ago. Besides a penalty value, you can also set the threshold in months. ## [Assigning TM](#assigning-tm) [Section titled “Assigning TM”](#assigning-tm) To assign a TM to your project, in the **Assigned Translation Memories** section, select the needed TMs from the list.  ## [Prioritizing TM](#prioritizing-tm) [Section titled “Prioritizing TM”](#prioritizing-tm) When you assign a few TMs to the project, you can set the needed priority for each of them. As a result, TM suggestions from the TM with the higher priority will be displayed in the first place. The default TM priority value is set to 1. A higher number has a higher priority (for example, 5 has a higher priority than 1). For example, if you assigned four TMs to your project, you can set the priority of 4 to the most important TM, the one that should be used in the first place. And respectively set lower priorities to other TMs. To set the priority for TMs, in the **Assigned Translation Memories** section, set the preferred priority for assigned TMs from the respective drop-down list.  ## [Changing Default TM](#changing-default-tm) [Section titled “Changing Default TM”](#changing-default-tm) To change your project’s default TM, in the **Assigned Translation Memories** section, click the icon next to the needed TM in the list. # Roles > Learn about the roles and permissions that users can have in Crowdin Roles in Crowdin define the level of access and control users have within the platform. By assigning roles, you can manage user permissions across the Editor, project settings, and resources. Below you can find descriptions of each role and its associated permissions. ## [Owner](#owner) [Section titled “Owner”](#owner) Owner is the user who created the project and has complete control over it. The owner can invite users to the project and manage their access, work with source and translation files, configure project settings, and manage account-level resources such as AI providers, MT engines, and more. ## [Manager](#manager) [Section titled “Manager”](#manager) Manager has similar rights to the project owner within assigned projects. They can manage project members, files, localization resources (i.e., TMs and Glossaries), tasks, integrations, reports, and other project-specific resources. Managers can’t delete projects or configure the project owner’s account-level resources such as AI providers or MT engines. **Use case:** Suitable for trusted team members who manage the full localization process within specific projects. ## [Developer](#developer) [Section titled “Developer”](#developer) Developer can upload source files, edit translatable text, connect integrations, and access the API. They don’t have permissions to manage project members, tasks, or reports. **Use case:** Suitable for users handling the technical aspects of localization, such as file management, integration setup, or automation. ## [Language Coordinator](#language-coordinator) [Section titled “Language Coordinator”](#language-coordinator) Language Coordinator can manage certain project features only for their assigned languages. They can translate and approve strings, manage project members and join requests, generate project reports, create tasks, and pre-translate content. Language Coordinators cannot access other project settings such as source files, integrations, or project configurations. **Use case:** Suitable for users coordinating translations across specific project languages. ## [Proofreader](#proofreader) [Section titled “Proofreader”](#proofreader) Proofreader can translate and approve strings within assigned projects. They do not have access to project settings or management functions. **Use case:** Suitable for users focused on finalizing translations and ensuring quality. ## [Translator](#translator) [Section titled “Translator”](#translator) Translator can add translations and vote on suggestions made by others. They do not have the ability to approve translations or access project settings. **Use case:** Suitable for users responsible for providing translations without additional management responsibilities. ## [Blocked](#blocked) [Section titled “Blocked”](#blocked) Blocked users cannot access the project and are restricted from performing any actions. **Use case:** Used when a user’s access to the project needs to be revoked. ## [See Also](#see-also) [Section titled “See Also”](#see-also) [Changing Roles ](/project-members/#changing-role)Learn how to change the role of a project member. # Screenshots > Provide translators with additional context for the source strings Screenshots are a great way to provide translators with additional context for the source strings in your project and, as a result, get more relevant and consistent translations. With screenshots, your team can see which strings are used together on the same page, whether short texts stand for titles, buttons, etc. [Translate Your UI with Crowdin's Screen Translation Feature ](https://crowdin.com/translate-ui-with-crowdin)Crowdin's Screen Translation simplifies UI localization by allowing users to translate interface elements with a real-time preview of your app design. Tag source strings to the screenshots to display them to translators in the Editor in the context section below the source string.  ## [Upload Screenshots](#upload-screenshots) [Section titled “Upload Screenshots”](#upload-screenshots) To upload screenshots into your project, follow these steps: 1. Open your project and go to the **Screenshots** tab. 2. Drag images from your machine, or click **Upload**.  ## [Tag Strings](#tag-strings) [Section titled “Tag Strings”](#tag-strings) To show translators where certain strings are located in the UI tag strings on the screenshots. In Crowdin, you can tag strings using the following methods: * Auto tag * Text recognition * Drag and drop ### [Tag Strings Automatically](#tag-strings-automatically) [Section titled “Tag Strings Automatically”](#tag-strings-automatically) Texts within an image will be detected automatically. Then the matching strings will be searched in the project according to the selected filter. As a result, the ones found will be tagged on the screenshot. 1. Open the screenshot with a double-click. 2. Click . 3. Once the strings are tagged on the screenshot, click **Save**.  To tag strings automatically on a single screenshot without opening it: 1. Click on the needed screenshot. 2. Select **Auto tag**. You can also tag strings automatically on multiple screenshots at once: 1. Select multiple screenshots by holding `Ctrl` or `Shift` . 2. Click **Auto tag**. If you use In-Context, you might find helpful its integrated feature for taking screenshots of the website pages. [Adding Screenshots via In-Context ](/developer/in-context-localization/#adding-screenshots-via-in-context)In-Context Localization is a feature that allows you to preview your website or application in Crowdin and translate strings directly in the context. ### [Tag Strings with Text Recognition](#tag-strings-with-text-recognition) [Section titled “Tag Strings with Text Recognition”](#tag-strings-with-text-recognition) The system will search for a string that matches the text you select among all the strings in your project. If several similar strings are found, you will see all of them and be able to select the best-matching one. 1. Open the screenshot with a double-click. 2. Highlight the text on the screenshot. 3. Once finished tagging all the strings, click **Save**.  If text highlighting is inactive, the **Text recognition** feature might be unavailable for your project’s source language. ### [Tag Strings Manually](#tag-strings-manually) [Section titled “Tag Strings Manually”](#tag-strings-manually) Drag the listed strings to the text on the screenshot manually. 1. Open the screenshot with a double-click. 2. Click **Strings** to open the string list panel. 3. Sort and filter the listed strings. You can select all or specific files and search strings by text or context. 4. Drag the needed string from the list in the right panel to the corresponding text on the screenshot. Alternatively, click on the strings to tag them in the screenshot without specifying the exact place where they should appear. 5. *(Optional)* To view additional string details or edit them: * Click the button above the string list to show more details (file name and string context). * Hover over a string and click the to open the **Edit String** dialog. You can: * Update the identifier. * Update the source text. * Add or update the context. * Add or update the labels. * Set the **Max. length of the translated text**. * Click **Save** after making the changes. 6. Click **Save** when you finish tagging. Read more about [String Editing](/string-management/#string-editing).  To tag all the strings from the selected file to your screenshot, follow these steps: 1. Select the file you need. 2. Click **Tag All** > **Save**. ### [Drag and Scroll Screenshots](#drag-and-scroll-screenshots) [Section titled “Drag and Scroll Screenshots”](#drag-and-scroll-screenshots) When tagging high-resolution screenshots, you can hold `Ctrl` to drag and scroll the screenshot with a mouse revealing the remaining part. Alternatively, click to drag and scroll the screenshot without holding `Ctrl` . ### [Removing Tagged Strings from Screenshot](#removing-tagged-strings-from-screenshot) [Section titled “Removing Tagged Strings from Screenshot”](#removing-tagged-strings-from-screenshot) If you need to remove all the strings tagged on the screenshot, click . ## [Labels](#labels) [Section titled “Labels”](#labels) Use labels in your project for an easy way to organize screenshots by certain topics. Once you add labels to your screenshots, you can filter them by added labels. If you already use labels for your source strings, you can also use the same labels for screenshots. [Managing Project Labels ](/project-settings/labels/)Learn how to make your Crowdin project labels. ### [Adding Labels to Screenshots](#adding-labels-to-screenshots) [Section titled “Adding Labels to Screenshots”](#adding-labels-to-screenshots) There are a few possible ways you can add labels to the screenshots. ##### [Add labels to one screenshot at a time](#add-labels-to-one-screenshot-at-a-time) [Section titled “Add labels to one screenshot at a time”](#add-labels-to-one-screenshot-at-a-time) 1. Open the screenshot with a double-click. 2. Click . 3. Select needed labels in the **Labels** field. 4. Click **Save**.  ##### [Add labels to multiple screenshots](#add-labels-to-multiple-screenshots) [Section titled “Add labels to multiple screenshots”](#add-labels-to-multiple-screenshots) 1. Select multiple screenshots you want to add the same labels to holding `Ctrl` or `Shift` . 2. Click **Labels**. 3. Select needed labels in the **Labels to be added** field. 4. Click **Save**.  ## [Update Screenshots](#update-screenshots) [Section titled “Update Screenshots”](#update-screenshots) You can upload a new screenshot that will replace the current one. The already tagged strings that are relevant would remain tagged. If the text on the screenshot changed its location, strings would remain tagged but on the new locations. To update the screenshot, follow these steps: 1. Open the screenshot with a double-click. 2. Click and select a new screenshot from your machine or use Drag\&Drop. 3. Click **Save**. ## [Rename Screenshots](#rename-screenshots) [Section titled “Rename Screenshots”](#rename-screenshots) To rename a screenshot, follow these steps: 1. Click on the needed screenshot and select **Rename**. 2. Specify a new name. 3. Press `Enter` . ## [Download Screenshots](#download-screenshots) [Section titled “Download Screenshots”](#download-screenshots) You can download screenshots and reuse them in other projects or elsewhere. To download screenshots, follow these steps: 1. Select one or multiple screenshots holding `Ctrl` or `Shift` . 2. Click **Download**. Alternatively, click on the needed screenshot and select **Download**. ## [Delete Screenshots](#delete-screenshots) [Section titled “Delete Screenshots”](#delete-screenshots) To delete a screenshot, follow these steps: 1. Select one or multiple screenshots holding `Ctrl` or `Shift` . 2. Click **Delete screenshot**. # Information Security Policy > Crowdin Information Security Policy objectives and basic principles Crowdin Information Security Policy (hereinafter the Policy) defines the objectives and basic principles of information security. Information security means implementation and maintenance of the appropriate level of its properties. The Policies requirements apply to the entire Crowdin organization and all business processes, and are available mandatory for all employees as well as those involved in these business processes. Compliance with the requirements of the Policy is an important aspect for achieving Crowdin’s strategic goals and objectives. Crowdin information security policy meets the requirements of ISO / IEC 27001: 2022. This policy sets up: * The context of the Organization * Internal and external issues relevant to the purpose of Crowdin * Interested parties that are relevant to the Information security management systems (hereinafter ISMS) * The requirements of these interested parties relevant to the ISMS * Information security objectives * Information security policy commitments * Responsibilities for Information Security * Measurement Information security processes are described, formally defined and approved, Crowdin’s guidance in the form of standards, policies, regulations and other internal regulatory documents. ## [Context of the organization](#context-of-the-organization) [Section titled “Context of the organization”](#context-of-the-organization) According to ISO, defining the context of an Organization is a “business environment”, “a combination of internal and external factors and conditions that may influence the organization’s approach to its products, services and investments and interested parties”. Crowdin is a product company with more than 2 million user accounts. Crowdin’s software solution empowers companies of any shape and size to accelerate their growth by reaching people who speak different languages. Crowdin team works passionately toward a shared goal: to expand the potential of agile localization. From day one till now, Crowdin’s mission has always been to keep it simple and wow Crowdin’s customers with an outstanding user experience and the latest technology solutions. Crowdin’s main industrial sector is Software as a service. The purpose of the ISMS is to ensure that Crowdin is still able to meet its defined business objectives and comply with its policies in the face of potential and actual security incidents. Policies have been set by the organization in a variety of areas and these must be taken account of during the information security planning process to ensure that they are met. The main relevant policies are: * Business Continuity Plan * Information Security Management Framework * Risk Assessment Methodology * Risk Treatment Guideline * Incident Response Plan * Acceptable Use Policy * Access Control Policy * Clear Desk and Clear Screen Policy * Control Against Malware Policy * Cryptography Policy * Human Resources Security Policy * Information Backup Policy * Information Classification and Labeling Policy * IS Risk Management Policy * Logging and Monitoring Policy * Monitoring and evaluating the effectiveness of ISMS Policy * Network Security Policy * Password Policy * Physical Security Policy * Security in Development and Maintenance Processes Policy * Segregation of Duties Policy * Supplier Relationship Security Policy * Workstation Security Policy * Сhange Management Policy * Communication Procedure * Corrective and Preventive Actions Procedure * Disciplinary procedure * Document control procedure * Internal Audit Procedure * Inventory and assessment of information assets procedures * Risk Management Procedure * Maintaining confidentiality in the work * Management Review Procedure * User Access Management Procedure * Vulnerability Management Policy * Security in Customer Support Policy ## [Internal and external issues](#internal-and-external-issues) [Section titled “Internal and external issues”](#internal-and-external-issues) There are a number of internal and external issues that are relevant to the purpose of Crowdin and that affect the ability of the ISMS to achieve its intended outcomes. Internal issues: * Adopted standards, guidelines and models * Significant organizational changes * Governance and organizational structure * Contractual relationships * Resources and knowledge (e.g. capital, people, processes and technologies) * Relationship with staff and stakeholders, including partners and suppliers * etc. External issues: * Changes in technology * Government regulations and changes in the law * Competition * Economic shifts in the market * Supply chain * Society and culture * Interest and inflation rate * Data protection * Supporting technologies and infrastructure * Automation and artificial intelligence * Military conflicts and political changes * etc. These general internal and external issues will be considered in more detail as part of the risk assessment process and will be regularly reviewed and monitored. ## [The interested parties that are relevant to the ISMS of Crowdin have been determined below with their individual expectations.](#the-interested-parties-that-are-relevant-to-the-isms-of-crowdin-have-been-determined-below-with-their-individual-expectations) [Section titled “The interested parties that are relevant to the ISMS of Crowdin have been determined below with their individual expectations.”](#the-interested-parties-that-are-relevant-to-the-isms-of-crowdin-have-been-determined-below-with-their-individual-expectations) An interested party is defined as a person or organization that can affect, be affected by, or perceive themselves to be affected by a decision or activity. The following are defined as interested parties that are relevant to the ISMS: * Business Owners * Governance * Customers * Suppliers and partners * Regulatory bodies * Customer user groups * Emergency Services * Employees of the Organization * Contractors providing services to the Organization * Competitors * Investors * The media * Emergency Services * Auditor | Interested party | Expectations | Requirement | | -------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- | | Owners of the business | Effective information security influences the organization’s financial success | Return on capital | | Governance | Organisational reputation must be protected | Documentary and practical confirmation of the implementation of ISMS | | Customers, Customer user groups | The confidentiality, integrity and availability of data is secured at all times | ISMS ISO 27001 Certificate | | Suppliers and partners | Adhering to agreements and payment terms | Evidence of adhering to agreements and payment terms | | Regulatory bodies | The activities of the Organization comply with current legislation | Official confirmation of legal requirements (reports, certificates, etc.) | | Employees of the Organization | Personal data security, social welfare benefits, appropriate remuneration, training & support, safe working environment etc. | Legislative documents and regulations, NDA terms & conditions, clear instructions on how to handle sensitive data etc. | | Contractors providing services to the Organization | Adhering to agreements and payment terms; Personal data security, social welfare benefits, appropriate remuneration | Evidence of adhering to agreements and payment terms; Legislative documents and regulations, NDA, clear instructions on how to handle sensitive data etc. | | Competitors | The Organization responding to rival marketing campaigns with its own initiatives and set prices competitively | Results of market monitoring | | Investors | Profitability, expected return on investment | Return on investment, Financial Statements | | The media | Transparency regarding security incidents | Coverage of data breaches and a wider public interest in the way organisations protect personal information | | Auditors | Expect that a proportionate level of security controls are in place at all times to protect assets | Documentary and practical confirmation of the implementation of ISMS | | Emergency Services | Safe working environment etc. | Fire Safety, First aid provision etc. | ## [Information security objectives:](#information-security-objectives) [Section titled “Information security objectives:”](#information-security-objectives) * Ensure compliance with the requirements of ISO / IEC 27001: 2022 which will allow Crowdin to be a certified company and trusted supplier for its customers. ([View Certificate](/Certificate_ISO_27001_2024_12_12.pdf)). Ensure compliance with relevant laws, regulations (legislation of Estonia, Ukraine), contractual agreements, and organizational policies related to information security. * Ensure the availability, integrity and confidentiality of both customer and employee data, confidentiality of internal business processes. * Continuously reduce risks within the organization’s ISMS. * Prevent or minimize potential IS incident damage. This strategic objectives are supported by annual KPIs, described in more detail in the *ISMS-PL-Monitoring and evaluating the effectiveness of ISMS Policy* policy: * Availability time of the service (>99,95% yearly) * Data confidentiality incidents count (goal: 0) * Data integrity incidents count (goal: 0) * Physical security incidents count (goal: 0) * Prioritized issues to be fixed immediately (goal: <100) * Vulnerabilities count found during pentest (security level: strong or very strong) * Vulnerabilities count found via reporting program (goal: no critical reports) * Planned ISMS tasks done in previous period (goal: 100%) * Quantity of unsuccessful or defective system updates (goal <25) * Active risks distribution (decrease or increase of identified risks number) (goal <10 risks classified as very high) * Phishing testing: percentage of compromised users (goal: 0%) ## [What will be done](#what-will-be-done) [Section titled “What will be done”](#what-will-be-done) Current policies, processes, and security measures will be continuously reviewed. Any gaps in alignment with ISO/IEC 27001:2022 standards will be identified and addressed. A proactive risk management strategy will be maintained. This strategy includes conducting regular risk assessments, vulnerability scans, and security audits. Identified risks will be analyzed, and continuous mitigation measures will be implemented. ## [What resources will be required](#what-resources-will-be-required) [Section titled “What resources will be required”](#what-resources-will-be-required) * Professionals with expertise in information security, data protection, and risk management. * Security technologies, including secure data storage solutions, device management solutions, encryption technologies, vulnerability assessment tools. * Skilled auditors and analysts to assess the effectiveness of implemented security measures and identify areas for improvement. * Access to up-to-date threat intelligence sources * Adequate budget allocation to support investments in security technologies, personnel, training programs, and processes improvements. ## [Who will be responsible](#who-will-be-responsible) [Section titled “Who will be responsible”](#who-will-be-responsible) The ISMS Committee has the final responsibility for Information Security Risks across Crowdin. Detailed information about the functions, regulation, duties and responsibilities of the ISMS Committee is in the Regulation on ISMS Committee. Managers/Head of Departments are responsible for information security within their departments/teams. They must ensure that the department/team has communicated their own informational security needs to the CISO. CISO is clearly accountable for the provision of appropriate, timely advice to the management to ensure that an effective information risk management framework is implemented, operated and maintained in alignment with the business strategy, the business and the legal requirements. All personnel, regardless of function, level and role, shall have explicit personal responsibilities for Information Security Management. Responsibilities are described in detail in the *ISMS-FR-Information Security Management Framework*, and in other corresponding policies. ## [When it will be completed](#when-it-will-be-completed) [Section titled “When it will be completed”](#when-it-will-be-completed) Continuous monitoring and improvement of ISMS will be an ongoing task to maintain compliance. Regular risk assessments and mitigation activities will be scheduled periodically. Vulnerability assessments will be conducted regularly as part of the organization’s ongoing security practices. Proactive measures will be implemented immediately upon identification of vulnerabilities to ensure continuous protection. The Incident Response Plan is annually reviewed, updated and tested to ensure its effectiveness in minimizing potential damage in the event of a security incident. ## [How the results will be evaluated](#how-the-results-will-be-evaluated) [Section titled “How the results will be evaluated”](#how-the-results-will-be-evaluated) Systems, processes and activities that can be monitored in the ISMS include, but are not limited to: * Audit; * Risk assessment process; * Risk management of third parties; * Business continuity management; * The maturity of implementation of ISMS processes; * Incident management; * Vulnerability management; * Configuration management; * Training and level of awareness raising activities; * Access control, firewall and other event logs; * Management of physical and environmental safety; and * System monitoring. The organization’s compliance with ISO/IEC 27001:2022 is evaluated through internal audit, management review, ISMS committee meetings. Annual external audits conducted by certification bodies will further validate our compliance status. Key performance indicators defined will be closely monitored. Any security breaches or incidents will trigger immediate investigation and corrective action to ensure the security of customer and employee data, as well as our internal business processes. Monitoring and evaluating the effectiveness of ISMS processes is described in the *ISMS-PL-Monitoring and evaluating the effectiveness of ISMS Policy*. # Sketch Plugin > Start localizing at the design stage With the Crowdin plugin for Sketch, you can use texts from Crowdin in your designs to save time for both designers and developers. These could include original or translated texts. If necessary, you can add new ones (e.g., dialog titles, button labels) and send them to translators in Crowdin. ## [Use Cases](#use-cases) [Section titled “Use Cases”](#use-cases) * Quickly generate multilingual creative assets. * Translate mockups and test them in different languages before the programming starts. * Stop using ‘Lorem Ipsum’, add real texts from Crowdin to your prototypes instead. * Create and upload source strings from your designs to your Crowdin project. This way, uploaded strings could be used by developers, which reduces time spent on development. * Upload tagged screenshots to your Crowdin project. ## [Installation](#installation) [Section titled “Installation”](#installation) You can [download the latest release](https://github.com/crowdin/sketch-crowdin) from our GitHub repository. 1. Download the installation file. 2. Unzip it. 3. Double-click on the *sketch-crowdin.sketchplugin* file for auto installation. Crowdin plugin for Sketch can also be installed with [Sketch Runner](https://sketchrunner.com/). ## [Configuration](#configuration) [Section titled “Configuration”](#configuration) ### [Setting up Credentials](#setting-up-credentials) [Section titled “Setting up Credentials”](#setting-up-credentials) To specify your Crowdin credentials in Sketch, follow these steps: 1. Click **Plugins > Crowdin**. 2. Switch to **Settings**. 3. Provide your Personal Access Token. 4. Click **Connect to Crowdin**.  To generate a new token in Crowdin, follow these steps: 1. Go to *Account Settings > API* tab, *Personal Access Tokens* section, and click **New Token**. 2. Specify *Token Name* and click **Create**. ### [Selecting a Project](#selecting-a-project) [Section titled “Selecting a Project”](#selecting-a-project) To select the Crowdin project you’d like to work with, click the **Select Project** drop-down menu in **Settings**, and select a project from the list. Later on, you can use the same drop-down menu to switch to another project if needed. Additionally, you can select the specific branch your content will be uploaded to.  ## [UI Localization](#ui-localization) [Section titled “UI Localization”](#ui-localization) Use the *Strings* tab when localizing UI and working on dynamic pages with your development and marketing teams. In this tab, you can add source strings from Crowdin to your designs in Sketch in a click. After the texts are used in the designs, you can automatically upload tagged screenshots for translators’ reference back to Crowdin. ### [Using Source Strings from Crowdin in Sketch](#using-source-strings-from-crowdin-in-sketch) [Section titled “Using Source Strings from Crowdin in Sketch”](#using-source-strings-from-crowdin-in-sketch) 1. Open the Crowdin plugin for Sketch. 2. In the *Strings* tab, use the *Search* field to find the specific copy. You can search strings by source text, string identifier, or context. 3. Select the text layer you want to add text to and click on the needed string.  After using the source strings from Crowdin in your designs, you can [preview translations](#previewing-strings) for these strings in Sketch and [upload screenshots](#uploading-tagged-screenshots-to-crowdin) for them to your Crowdin project. ### [Adding Source Strings from Sketch to Crowdin](#adding-source-strings-from-sketch-to-crowdin) [Section titled “Adding Source Strings from Sketch to Crowdin”](#adding-source-strings-from-sketch-to-crowdin) You can add the strings that are already used in the designs or create and add completely new strings. 1. Open the Crowdin plugin for Sketch. 2. To add the strings used in the designs, select the whole artboard, multiple artboards, or the needed strings on the artboards. Alternatively, skip this step if you want to add a new string. 3. In the *Strings* tab, click **Add String**. 4. In the appeared dialog, fill in the required fields. 5. (Optional) To add labels to the strings, alternately select them from the **Label** drop-down menu and click **Save**.  To add the same strings into multiple files in Crowdin, alternately select the needed files from the **File** drop-down menu. If some artboards contain hidden elements that should not be added to Crowdin, clear the **Push hidden elements** option. Added strings will be transferred to your Crowdin project and also will be displayed in the list of the **Strings** tab. You can edit or delete the strings from the same list anytime. The respective changes will also be applied to the strings in your Crowdin project. ### [Key Naming Pattern Settings](#key-naming-pattern-settings) [Section titled “Key Naming Pattern Settings”](#key-naming-pattern-settings) To simplify adding strings from Sketch to the Crowdin project, you can set up the desired key naming pattern for the source string identifiers in the plugin settings. The Crowdin plugin for Sketch will suggest the string identifiers for new strings based on the selected pattern. While adding new source strings, you can always edit the suggested identifier to the preferred look. To select the key naming pattern, follow these steps: 1. Open the Crowdin plugin for Sketch. 2. Switch to **Settings**. 3. In the *Key naming pattern* section, select the preferred option from the drop-down menu. ### [Uploading Tagged Screenshots to Crowdin](#uploading-tagged-screenshots-to-crowdin) [Section titled “Uploading Tagged Screenshots to Crowdin”](#uploading-tagged-screenshots-to-crowdin) 1. Open the Crowdin plugin for Sketch. 2. In the *Strings* tab, use texts from the Crowdin project in your designs. Click **Upload Screenshots** to upload screenshots of the artboards that include the used texts. 3. To update screenshots on Crowdin, click **Upload Screenshots** again.  Read more about [Screenshots](/screenshots/). ### [Previewing Strings](#previewing-strings) [Section titled “Previewing Strings”](#previewing-strings) Preview translations from Crowdin for the strings used in the designs in Sketch. You can preview translations in the new frames or the original ones. When previewing translations in the new frames, you can populate them with the actual translations or with string keys for further use by developers. To preview strings populated with translations, follow these steps: 1. Open the Crowdin plugin for Sketch. 2. In the *Strings* tab, *Preview Strings* section, select *Preview in duplicated artboards* or *Preview in the current artboards*. 3. Select *Create with language*. 4. Select the target language you want to preview translations for. You can also choose *All languages*. 5. Choose the content you want to preview in Sketch. Select *Page* or *Artboard*.  To preview strings populated with key names, follow these steps: 1. Open the Crowdin plugin for Sketch. 2. In the *Strings* tab, *Preview Strings* section, select *Preview in duplicated artboards*. 3. Select *Create with key names*. 4. Choose the content you want to preview in Sketch. Select *Page* or *Artboard*.  ## [Marketing Visuals Localization](#marketing-visuals-localization) [Section titled “Marketing Visuals Localization”](#marketing-visuals-localization) Use the *Translation* tab to localize static pages, like brochures and banners. In this tab, you can send texts with context for translators to Crowdin and upload translated copies back to Sketch. ### [Sending Texts for Translation to Crowdin](#sending-texts-for-translation-to-crowdin) [Section titled “Sending Texts for Translation to Crowdin”](#sending-texts-for-translation-to-crowdin) You can send text for translation either from selected or all artboards from a Sketch file. Translators will work with those texts in the list view and use designs as an additional context for even higher translation quality. In Crowdin, a root folder *Sketch plugin* will be created. It will contain a subfolder named after your Sketch file with HTML files for each artboard inside. If needed, you can disable content segmentation in the plugin **Settings** so the long texts will not be split into sentences. To send Sketch designs for translation, follow these steps: 1. Open the necessary Sketch file. 2. Go to **Plugins > Crowdin**. 3. In the *Translation* tab, *Send Texts* section, select content you’d like to translate. Select *Page* or *Artboard*.  When the source files are uploaded to your Crowdin project, you can invite contributors to translate and proofread them. Read more about [translation strategies](/translation-strategies/). ### [Uploading Translations from Crowdin to Sketch](#uploading-translations-from-crowdin-to-sketch) [Section titled “Uploading Translations from Crowdin to Sketch”](#uploading-translations-from-crowdin-to-sketch) You can synchronize texts between Sketch and Crowdin projects whenever you want to test the translated copy inside Sketch or generate multilingual assets. To upload translated copies to Sketch, follow these steps: 1. Open the necessary Sketch file. 2. Go to **Plugins > Crowdin**. 3. In the *Translation* tab, *Get Translations* section, select the target language you want to upload translations for. You can also Select *All languages*. 4. Select the content you want to preview in Sketch. Select *Page* or *Artboard*.  After uploading translations to Sketch, the modified file will contain a separate artboard with translations for each target language. The newly uploaded translated versions won’t override the ones you uploaded previously. You can always delete the translated copies you no longer need. If you’d like the newly uploaded translated versions to override the previously uploaded ones, open the plugin **Settings** and select **Override existing translations**. # String Management > Manage source strings in your translation project You can view all the project’s strings and manage strings settings via **Sources > Strings**. ## [Changing Strings Visibility](#changing-strings-visibility) [Section titled “Changing Strings Visibility”](#changing-strings-visibility) If some strings contain data that is not supposed to be translated (e.g., placeholders, other technical entities), you can hide them from translators. To do this: 1. Open your project and go to **Sources > Strings**. 2. Select the necessary strings by clicking the checkbox next to each one. 3. Click **Hide**.  ## [Filtering Strings](#filtering-strings) [Section titled “Filtering Strings”](#filtering-strings) By default, all source strings of the project are displayed in **Sources > Strings**. If necessary, you can filter out strings using the available filter options (Issues: Show All, With Unresolved Issues, Without Unresolved Issues; Comments: Show All, With Comments, Without Comments; Screenshots: Show All, With Screenshots, Without Screenshots; Visibility: Show All, Hidden and Visible) and project labels.  ## [Adding Strings](#adding-strings) [Section titled “Adding Strings”](#adding-strings) You can add strings to your projects directly in Crowdin. To add a new string, follow these steps: * File-based project 1. Open your project and go to **Sources > Strings**. 2. Click **Add String**. 3. In the appeared dialog, enter the necessary details for the string: * *String* – specify the text that needs translation. * *(Optional)* *Plurals* – select this option to add plural forms and enter the text for each form based on the project’s source language requirements. * *Identifier* – specify a unique key for the string, often used for referencing the translated text in the application. * *(Optional)* *Context* – add additional information to help translators understand the intended meaning. * *(Optional)* [*Labels*](#labels) – specify labels to organize strings or provide extra context. * *(Optional)* *Maximum Translation Length* – set a character limit for the translation. * *(Optional)* File-specific identifiers – specify unique keys for each file format when adding the string to multiple files. This ensures that the string meets the different identifier requirements based on the file formats it will be used in. * *Files* – choose the source files where this string should be added. 4. Click **Add** to add the new string to your project. * String-based project 1. Open your project and go to the **Strings** tab. 2. Click **Add String**. 3. In the appeared dialog, enter the necessary details for the string: * *Branches* – choose the branches where this string should be added. * *String* – specify the text that needs translation. You can leave this field empty to create placeholder strings for future content or development purposes. * *(Optional)* *Plurals* – select this option to add plural forms and enter the text for each form based on the project’s source language requirements. * *Identifier* – specify a unique key for the string, often used for referencing the translated text in the application. * *(Optional)* *Context* – add additional information to help translators understand the intended meaning. * *(Optional)* [*Labels*](#labels) – specify labels to organize strings or provide extra context. * *(Optional)* *Maximum Translation Length* – set a character limit for the translation. * *(Optional)* File-specific identifiers – specify unique keys for each branch when adding the string to multiple branches. This ensures that the string meets the different identifier requirements based on the file formats it will be used in. 4. Click **Add** to add the new string to your project. Read more about [project types](/creating-project/#project-types). Limitations The maximum identifier length is 512 characters. ## [String Editing](#string-editing) [Section titled “String Editing”](#string-editing) You can add context to the string, add or remove labels, set the max. length of the translation. Once the translation limits are exceeded, the system notifies the contributor that the translation should be shorter.  To edit some particular word or phrase that appears in multiple source strings, you can use the **Find & Replace** feature in **Sources > Strings**. Caution When editing the identifier of a string contained in a group of strings (string array for Android XML, segments for XLIFF), the existing translations will be removed for all group strings but the edited one. ### [Formats That Support Online Editing](#formats-that-support-online-editing) [Section titled “Formats That Support Online Editing”](#formats-that-support-online-editing) Some file formats allow editing (adding, deleting, and modifying) of the source text and string identifiers directly in Crowdin, so you can make the necessary corrections without having to update the source file via **Sources > Files**. The following file formats support editing the source text and string identifiers directly in Crowdin: * [Android XML](https://store.crowdin.com/android-xml) * [iOS Strings](https://store.crowdin.com/strings) * [Apple Strings Catalog](https://store.crowdin.com/string_catalog) * [JSON](https://store.crowdin.com/json) * [i18next JSON](https://store.crowdin.com/i18next-json) * [Chrome JSON](https://store.crowdin.com/chrome-json) * [XLIFF 1.2](https://store.crowdin.com/xliff) * [XLIFF 2.0](https://store.crowdin.com/xliff2.0) * [Angular XLF](https://store.crowdin.com/angular) * [GNU Gettext PO](https://store.crowdin.com/gnu-gettext) * [Unreal Engine Gettext PO](https://store.crowdin.com/gettext-unreal) * [YAML](https://store.crowdin.com/yaml) * [RESX](https://store.crowdin.com/resx) * [CSV](https://store.crowdin.com/csv) * [XLSX](https://store.crowdin.com/xlsx-excel) * [ARB](https://store.crowdin.com/arb) * [Java Properties](https://store.crowdin.com/java-properties) * [Properties Play](https://store.crowdin.com/properties-play) * [Properties XML](https://store.crowdin.com/properties-xml) ### [Labels](#labels) [Section titled “Labels”](#labels) Use labels in your project for an easy way to add context to the strings or organize them by certain topics. Labels are also useful while creating translation and proofreading tasks or searching for specific strings in the Editor with the help of [Advanced Filter](/online-editor/#advanced-filter). [Managing Project Labels ](/project-settings/labels/)Learn how to make your Crowdin project labels. There are a few possible ways you can add labels to the strings. ##### [Add labels to one string at a time via the *Edit String* dialog](#add-labels-to-one-string-at-a-time-via-the-edit-string-dialog) [Section titled “Add labels to one string at a time via the Edit String dialog”](#add-labels-to-one-string-at-a-time-via-the-edit-string-dialog) 1. Click **Edit** on the string in the list. 2. Select needed labels in the *Labels* field.  3. Click **Save**. ##### [Add labels to multiple strings via the *Manage Strings Labels* dialog](#add-labels-to-multiple-strings-via-the-manage-strings-labels-dialog) [Section titled “Add labels to multiple strings via the Manage Strings Labels dialog”](#add-labels-to-multiple-strings-via-the-manage-strings-labels-dialog) 1. Select a few strings you want to add the same labels to. 2. Click **Labels**. 3. Select needed labels in the *Labels to be added* field.  4. Click **Save**. ##### [Add labels to the source strings in CSV and XLSX files using a dedicated column for labels](#add-labels-to-the-source-strings-in-csv-and-xlsx-files-using-a-dedicated-column-for-labels) [Section titled “Add labels to the source strings in CSV and XLSX files using a dedicated column for labels”](#add-labels-to-the-source-strings-in-csv-and-xlsx-files-using-a-dedicated-column-for-labels) Read more about [Configuring Columns for Import](/csv-xlsx-configuration/#configuring-columns-for-import). # List of Sub-processors > Learn about Crowdin's sub-processors and their purpose Effective date: May 31, 2024 Crowdin provides a great deal of transparency regarding how we use your data, how we collect your data, and with whom we share your data. To that end, we provide this page, which details our sub-processors, how we use cookies, and where and how we perform any tracking on Crowdin. ## [Crowdin Sub-processors](#crowdin-sub-processors) [Section titled “Crowdin Sub-processors”](#crowdin-sub-processors) When we share your information with third party sub-processors, such as our vendors and service providers, we remain responsible for it. We work very hard to maintain your trust when we bring on new vendors, and we require all vendors to enter into data protection agreements with us that restrict their processing of Users’ Personal Information. | Sub-processor | Purpose and Description | Entity Country | | ------------------------ | ----------------------------------------------------------------- | ------------------------ | | Amazon Web Services | Hosting services, file storage and backup services | United States of America | | FastSpring | Subscription credit card payment processor | United States of America | | Google Workspace | Internal company infrastructure | United States of America | | Google Analytics | Website analytics and performance | United States of America | | Google Cloud | Screenshots Processing | United States of America | | HubSpot | Customer relations management | United States of America | | Apollo | Sales intelligence software | United States of America | | Help Scout | Customer support ticketing system | United States of America | | Amazon QuickSight | Business intelligence software | United States of America | | Xero | Corporate billing system | United States of America | | Atlassian Inc. - Jira | Proprietary issue tracking product developed by Atlassian | United States of America | | Slack Technologies, Inc. | Communication software | United States of America | | Crowdin LLC | Provides a portion of product services for Crowdin | Ukraine | | Sentry | Application monitoring and error management | United States of America | | Docusign | Service for storing signed documents | United States of America | | Open AI | Provides AI models in support of Crowdin’s AI/ML-powered features | Ireland | | Microsoft Corporation | Business analytics tool and a suite of ERP and CRM applications | United States of America | ## [Crowdin Feature Specific Sub-processors](#crowdin-feature-specific-sub-processors) [Section titled “Crowdin Feature Specific Sub-processors”](#crowdin-feature-specific-sub-processors) These are only available to Crowdin customers who have opted in to the use of certain Crowdin features. | Sub-processor | Purpose and Description | Entity Country | | --------------- | ----------------------------------------------------------------- | ------------------------ | | Google Gemini | Provides AI models in support of Crowdin’s AI/ML-powered features | United States of America | | Microsoft Azure | Provides AI models in support of Crowdin’s AI/ML-powered features | United States of America | | Mistral AI | Provides AI models in support of Crowdin’s AI/ML-powered features | France | | Anthropic | Provides AI models in support of Crowdin’s AI/ML-powered features | United States of America | | DeepL | Machine translation services | Germany | | Convertio | Processing of PDF files uploaded by users | Cyprus | ## [Sub-processor Updates](#sub-processor-updates) [Section titled “Sub-processor Updates”](#sub-processor-updates) Prior to engaging any sub-processors, we perform due diligence to evaluate their privacy, security and confidentiality practices, and execute an agreement with them that implements their obligations. When we bring on a new vendor or other sub-processor who handles our Users’ Personal Information, or remove a sub-processor, or we change how we use a sub-processor, we will update this page. If you have questions or concerns about a new sub-processor, we’d be happy to help. Also, if you’d like to be notified when we add a new sub-processor, please contact us and we’ll add you to the email list. Please contact us at # Supported Formats > Explore the list of localization formats supported by Crowdin Crowdin supports a wide range of localization formats, including but not limited to files for mobile, software, documents, subtitles, and graphic assets. ## [Localization Formats and Documents](#localization-formats-and-documents) [Section titled “Localization Formats and Documents”](#localization-formats-and-documents) * Mobile application formats * Web and desktop software formats * Documentation and video subtitles  50 Supported Formats [View on Store ](https://store.crowdin.com/categories/file-formats) ## [Graphics and Assets](#graphics-and-assets) [Section titled “Graphics and Assets”](#graphics-and-assets) Localize images associated with your product to improve your product’s user experience. 1. Upload graphics to Crowdin. 2. Add all the necessary references for a translator to understand how these graphics should be handled. 3. Wait for translators to upload localized files. 4. Download the localized graphics and use them in production.  ## [Converted File Formats](#converted-file-formats) [Section titled “Converted File Formats”](#converted-file-formats) On import, some file formats are automatically converted into other formats to be further parsed and processed. You can see the list of the initial file formats and the file formats they’re being converted into in the table below. | Initial file format | Converted file format | | ------------------- | --------------------- | | DOC | DOCX | | PPT | PPTX | | RTF | DOCX | | PDF | DOCX | ## [Custom Services](#custom-services) [Section titled “Custom Services”](#custom-services) ## [Custom File Formats](#custom-file-formats) [Section titled “Custom File Formats”](#custom-file-formats) File formats that are not officially supported will be recognized as plain text files (if they contain text) or as graphic assets. Our team can add special code to support your original file formats and ensure that translators see only translatable text rather than the entire file content. This approach allows you to manage custom file formats more effectively. [Contact](https://crowdin.com/contacts) our support team to start working with custom file formats in your project. Alternatively, you can implement support for a custom format yourself by developing a [Crowdin app](/developer/crowdin-apps-about/) incorporating the [Custom File Format](/developer/crowdin-apps-module-custom-file-format/) module. ## [Custom File Export](#custom-file-export) [Section titled “Custom File Export”](#custom-file-export) By default, we export the translations in the same format as the source files. For example, if you upload an XML file to Crowdin, you’ll have the XML file exported. Our developers can create a special processor if you want to configure custom settings for your file export. For example, you upload a key-value file that doesn’t support [string editing](/string-management/#string-editing) by default and want to modify it directly in Crowdin. We can temporarily convert your file to CSV file format to allow you to add strings online. The exported file will remain in the original format. [Contact](https://crowdin.com/contacts) our support team, and we’ll gladly help you set custom export options based on your needs. ## [Custom Placeholders](#custom-placeholders) [Section titled “Custom Placeholders”](#custom-placeholders) Crowdin supports all the placeholders typical for the supported file formats. They are all automatically highlighted in the Editor, so translators know that they shouldn’t be translated. Even if the translator tries to save the translation with some modified or missing placeholder, enabled QA checks will notify the translator about the mistake. As various file formats allow the creation of custom placeholders, we can also add support for the custom ones you use in your project. To request the support of your custom placeholders, [contact](https://crowdin.com/contacts) our support team. # Project Tasks > Create and assign tasks for translating or proofreading content Create and assign tasks for translating or proofreading content to specific project members or vendors. You can set due dates, split words among assignees, receive notifications about task changes and updates, and discuss tasks with other project members in the comments. ## [Creating New Task](#creating-new-task) [Section titled “Creating New Task”](#creating-new-task) To create a new task, follow these steps: * File-based project 1. Open your project and go to the **Tasks** tab. 2. Click **Create Task**.  3. Set the task parameters: * *Title* – specify the name of the task that will be visible to translators or proofreaders. * *Description* (optional) – add any additional details that may be helpful. * *Type* – select between *Translate by own translators*, *Proofread by own proofreaders*, *Translate by vendor*, and *Proofread by vendor*. * *[Create a pending proofreading task](#sequential-tasks)* (only for Translate by own translators) – creates a separate proofreading task that starts once the translation is completed. * *[Preceding task](#sequential-tasks)* (only for Proofread by own proofreaders) – link the task to a previously created translation task to inherit its scope and language settings. * *Skip strings already included in other tasks* – skip strings that are already assigned to other tasks. * *[Create Cost Estimate Report](#generating-cost-estimate-report-for-tasks)* – automatically generate a cost estimate based on selected content and the rates template. * *Rates template* – select the template to be used for calculating the estimate. * *String filters* – filter which strings should be included in the task: * *Strings* – select whether to include all untranslated or not approved strings, or only those modified within a specific period. * *Filter by labels* (optional) – include only strings with specified labels. Additionally, choose how selected labels should be matched: * *All selected labels* – includes only strings that have all selected labels (AND logic). * *Any selected label* – includes strings that have at least one of the selected labels (OR logic). * *Exclude by labels* (optional) – exclude strings with specified labels. Additionally, choose how selected labels should be matched: * *All selected labels* – excludes only strings that have all selected labels (AND logic). * *Any selected label* – excludes strings that have at least one of the selected labels (OR logic). * *Include pre-translated strings only* (only for Proofread by own proofreaders) – include only strings that were previously pre-translated. * *Files* – select files to include in the task. * *Languages* – select target languages (a separate task will be created for each selected language). 4. Click **Assign** to assign users to the task for each language separately. 5. *(Optional)* Use a saved [template](#task-templates) to apply language and member assignment settings, or save the current configuration for future use. 6. Click **Create Task**.  * String-based project 1. Open your project and go to the **Tasks** tab. 2. Click **Create Task**.  3. Set the task parameters: * *Title* – specify the name of the task that will be visible to translators or proofreaders. * *Description* (optional) – add any additional details that may be helpful. * *Type* – select between *Translate by own translators*, *Proofread by own proofreaders*, *Translate by vendor*, and *Proofread by vendor*. * *[Create a pending proofreading task](#sequential-tasks)* (only for Translate by own translators) – creates a separate proofreading task that starts once the translation is completed. * *[Preceding task](#sequential-tasks)* (only for Proofread by own proofreaders) – link the task to a previously created translation task to inherit its scope and language settings. * *Skip strings already included in other tasks* – skip strings that are already assigned to other tasks. * *[Create Cost Estimate Report](#generating-cost-estimate-report-for-tasks)* – automatically generate a cost estimate based on selected content and the rates template. * *Rates template* – select the template to be used for calculating the estimate. * *String filters* – filter which strings should be included in the task: * *Strings* – select whether to include all untranslated or not approved strings, or only those modified within a specific period. * *Filter by labels* (optional) – include only strings with specified labels. Additionally, choose how selected labels should be matched: * *All selected labels* – includes only strings that have all selected labels (AND logic). * *Any selected label* – includes strings that have at least one of the selected labels (OR logic). * *Exclude by labels* (optional) – exclude strings with specified labels. Additionally, choose how selected labels should be matched: * *All selected labels* – excludes only strings that have all selected labels (AND logic). * *Any selected label* – excludes strings that have at least one of the selected labels (OR logic). * *Include pre-translated strings only* (only for Proofread by own proofreaders) – include only strings that were previously pre-translated. * *Branches* – select branches to include in the task. * *Languages* – select target languages (a separate task will be created for each selected language). 4. Click **Assign** to assign users to the task for each language separately. 5. *(Optional)* Use a saved [template](#task-templates) to apply language and member assignment settings, or save the current configuration for future use. 6. Click **Create Task**.  Read more about [project types](/creating-project/#project-types). ### [Splitting Content](#splitting-content) [Section titled “Splitting Content”](#splitting-content) Splitting content between several members allows you to speed up the translation or proofreading process. While in string-based and file-based projects this option is called differently (i.e., **Split strings** and **Split files**), the basic principle of its behavior remains the same. To split content between several members select **Split files** (in file-based project) or **Split strings** (in file-based project) in the **Assign users** dialog. You can set the approximate amount of words for each assignee.  ### [Generating Cost Estimate Report for Tasks](#generating-cost-estimate-report-for-tasks) [Section titled “Generating Cost Estimate Report for Tasks”](#generating-cost-estimate-report-for-tasks) To automatically estimate the cost of translation or proofreading for a task, select the **Create Cost Estimate Report** option during task creation. Once selected, a required [**Rates Template**](/project-reports/#rate-templates) drop-down will appear. Choose a saved template to calculate the cost estimate based on the selected strings or files. After the task is created, a Cost Estimate report will be generated automatically and become available in the [Archive](/project-reports/#archive) section. The estimated cost will also be displayed on the task card in the Board section. You can open the task to view the **Estimated Cost** section, which includes the following details: * The calculated cost based on the selected rates template * A clickable report title (e.g., Report #123) that links to the full report in the Archive section * The report generation date If the task scope changes (e.g., files or strings are modified), a new Cost Estimate report will be generated automatically to reflect the updated estimate. ### [Task Templates](#task-templates) [Section titled “Task Templates”](#task-templates) Use task templates to save the configuration of the **Languages** section, including target languages and member assignments. Templates help you quickly apply these configurations when creating new tasks, saving time and ensuring consistency. #### [Saving Templates](#saving-templates) [Section titled “Saving Templates”](#saving-templates) To save the language and member assignment settings as a template, follow these steps: 1. In the **Languages** section, click **Save as**. 2. Select **New template** from the drop-down menu. 3. In the dialog that appears, enter a name for your template. 4. Click **Save**. Your template is now saved and available for future tasks.  #### [Applying Templates](#applying-templates) [Section titled “Applying Templates”](#applying-templates) To apply a saved template to a new task, follow these steps: 1. In the **Languages** section, click on the template name to apply it immediately. 2. Alternatively, click next to the template name and select **Apply**. #### [Managing Templates](#managing-templates) [Section titled “Managing Templates”](#managing-templates) To rename or delete a saved template, follow these steps: 1. In the **Languages** section, click next to the template name. 2. Select one of the following options: * **Rename** – Enter a new name for your template. * **Delete** – Permanently remove the template.  ## [Project Tasks](#project-tasks) [Section titled “Project Tasks”](#project-tasks) In the **Tasks** tab, you can view all the project tasks in the following two sections: *Board*, *All Tasks*. ### [Board](#board) [Section titled “Board”](#board) In the *Board* section, tasks are organized into three columns: To Do, In Progress, and Done. This layout provides a clear view and visualization of the current status of all tasks. Within each column, tasks are further grouped by target languages. Each target language group can be collapsed to hide task cards or expanded to display them. This feature is particularly useful for decluttering the view and focusing on specific languages. Use the **Search tasks** field to search for tasks by name or [filter tasks](#filtering-tasks) using various filter options. To view the task details, open it by clicking on the task name.  ### [All Tasks](#all-tasks) [Section titled “All Tasks”](#all-tasks) The All Tasks section provides a list view of all project tasks. It is particularly useful for efficiently managing large volumes of tasks. The All Tasks section also allows you to select multiple tasks and perform bulk actions. These include changing the assignee, updating the status, or deleting tasks in a single operation. Similar to the Board section, the All Tasks also allows you to use the **Search tasks** field and [filter](#filtering-tasks). Additionally, you can sort the task list in ascending or descending order using the available sort options (ID, Created at, Resolved at, Due Date). ### [Editing Task](#editing-task) [Section titled “Editing Task”](#editing-task) To change the task details, follow these steps: 1. Open your project and go to the **Tasks** tab. 2. Click on the name of the task you want to change either in the Board or All tasks section. 3. Click in the upper-right corner and select **Edit**.  4. Make the necessary edits and click **Save**. ### [Filtering Tasks](#filtering-tasks) [Section titled “Filtering Tasks”](#filtering-tasks) By default, all project tasks are displayed in the **Tasks** tab either in the Board or All Tasks sections. If necessary, you can filter tasks using the available filter options: * Assignee: All users or particular user. * Created by: All users or particular user. * Language: All languages or particular language. * File: All files or particular file or folder. * Due date: All, Overdue now, Custom Range. * Type: All types, Translate by own translators, Proofread by own proofreaders, Translate by vendor, Proofread by vendor. * Status: All statuses, To Do, In Progress, Done, Closed.  ### [Changing Task Status](#changing-task-status) [Section titled “Changing Task Status”](#changing-task-status) To change the task status in the Board section, select the task assigned to you and drag it to the column with the status you need.  To change the task status in the All Tasks section, select the needed task, click **Change status**, and select the new status. Alternatively, in either of the two sections, you can change the task status directly in the task itself using the respective buttons: To Do, In Progress, Done. ### [Closing Task](#closing-task) [Section titled “Closing Task”](#closing-task) To close the task when it’s finished, move it to the **Done** column and click **Close**.  To view the list of closed tasks, open the All Tasks section and use the filter **Status: Closed**. ## [Sequential Tasks](#sequential-tasks) [Section titled “Sequential Tasks”](#sequential-tasks) Sequential tasks streamline the management of translation and proofreading processes in a structured, step-by-step manner. This feature is particularly useful for managing content that requires translation followed by proofreading, ensuring a smooth workflow. Once created, sequential tasks are represented on the Tasks Board, displaying both the translation task and its linked pending proofreading task.  ### [Key Approaches](#key-approaches) [Section titled “Key Approaches”](#key-approaches) The concept of sequential tasks is based on two primary approaches: * **Creating a translation task with its associated pending proofreading task:** * Start by creating a translation task and specifying the target languages and work scope. * Select **Create a pending proofreading task** to generate the associated proofreading task. You can set separate due dates for the translation and proofreading tasks if needed.  * While translators work on the translation task, the linked proofreading task remains pending. * When the translation task is completed, the status of the associated proofreading task changes from Pending to To Do. Proofreaders will then receive notifications that it’s ready for review. * **Creating a proofreading task and linking it to a translation task:** * Create a proofreading task and select the translation task you want to link it with from the **Preceding task** drop-down menu. You can link it to either a completed or an active translation task.  * The languages and work scope are automatically inherited from the linked translation task. * The proofreading task remains pending until the linked translation task is completed. * As with the first approach, proofreaders receive notifications when the proofreading task is ready for review. ### [Task Types Supported](#task-types-supported) [Section titled “Task Types Supported”](#task-types-supported) Sequential tasks are available for the following task types: * Translate by own translators * Proofread by own translators * Translate by vendor: * Crowdin Language Services * Vendors that manage the translation process with a dedicated manager * Proofread by vendor: * Crowdin Language Services * BLEND * Vendors that manage the translation process with a dedicated manager ### [Sequential Task Management](#sequential-task-management) [Section titled “Sequential Task Management”](#sequential-task-management) * When editing a pending proofreading task, changes are limited to fields that do not affect the scope of the task. * Pending proofreading tasks can be deleted if necessary. In this case, linked translation tasks are preserved. * Deleting a translation task with an associated sequential proofreading task results in the deletion of both tasks simultaneously. ## [See Also](#see-also) [Section titled “See Also”](#see-also) [Task-based access control ](/project-settings/privacy-collaboration/#privacy)Allow project members to work with tasks they are assigned to, even if they do not have full access to the language in the project. [User Tasks ](/user-tasks/)Learn how to view, filter, and manage tasks assigned to you. [Crowdin Language Services ](/crowdin-language-services/)Order professional translations and proofreading services. # Terms > Crowdin Terms of Service Last revised on July 20, 2020 ### [In This Article](#in-this-article) [Section titled “In This Article”](#in-this-article) * [1. DEFINITIONS](#1-definitions) * [2. AUTHORITY TO ENTER INTO THESE TERMS WITH SUPPLIER](#2-authority-to-enter-into-these-terms-with-supplier) * [3. MODIFICATIONS TO TERMS](#3-modifications-to-terms) * [4. OUR RESPONSIBILITIES](#4-our-responsibilities) * [5. USING THE CROWDIN SERVICES](#5-using-the-crowdin-services) * [6. PAYMENT](#6-payment) * [7. CLIENT DATA](#7-client-data) * [8. SERVICES](#8-services) * [9. DATA PROCESSING CONTRACT](#9-data-processing-contract) * [10. RESTRICTIONS](#10-restrictions) * [11. PRIVACY](#11-privacy) * [12. INTELLECTUAL PROPERTY RIGHTS](#12-intellectual-property-rights) * [13. THIRD-PARTY SITES, PRODUCTS AND SERVICES](#13-third-party-sites-products-and-services) * [14. DISCLAIMERS; NO WARRANTY](#14-disclaimers-no-warranty) * [15. INDEMNIFICATION](#15-indemnification) * [16. LIMITATION OF LIABILITY](#16-limitation-of-liability) * [17. TERMINATION OF THESE TERMS](#17-termination-of-these-terms) * [18. WHO YOU ARE CONTRACTING WITH](#18-who-you-are-contracting-with) * [19. GENERAL PROVISIONS](#19-general-provisions) *** Welcome to [www.crowdin.com](https://crowdin.com). These Terms of Service contain the terms and conditions that govern all use of our Platform (as defined below) and Services (as defined below) and all content, services and/or products available on or through the Platform (collectively, the “Crowdin Services”). The Crowdin Services are offered to you subject to your acceptance, without modification (other than Special Terms (as defined below) agreed by the parties pursuant to these Terms of Service), of all of the terms and conditions contained herein and all other operating rules, policies (including, without limitation, our [Privacy Policy](/privacy-policy/), the Guidelines (as defined below) and any future modifications thereof, and procedures that may be published from time to time on the Platform or made available to you on or through the Crowdin Services (collectively, the “Terms”). When accepted by you (as defined below), these Terms form a legally binding contract between you and Supplier (as defined below). If you are entering into these Terms on behalf of an entity, such as your employer or the company you work for, you represent that you have the legal authority to bind that entity. PLEASE READ THESE TERMS CAREFULLY. BY REGISTERING FOR, ACCESSING, BROWSING, AND/OR OTHERWISE USING THE CROWDIN SERVICES, YOU ACKNOWLEDGE THAT YOU HAVE READ, UNDERSTOOD, AND AGREE TO BE BOUND BY THESE TERMS. IF YOU DO NOT AGREE TO BE BOUND BY THESE TERMS, DO NOT ACCESS, BROWSE OR OTHERWISE USE THE PLATFORM OR THE CROWDIN SERVICES. Supplier may, in its sole discretion, elect to suspend or terminate access to, or use of the Crowdin Services to anyone who violates these Terms. If you register for a free trial of the Crowdin Services, the applicable provisions of these Terms will govern that free trial. The original language of these Terms is English. Supplier may make available translations for convenience. In case of conflicts between the original English version and any translation, the English version shall prevail. ## [1. DEFINITIONS](#1-definitions) [Section titled “1. DEFINITIONS”](#1-definitions) | | | | ------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Account | the primary means for accessing and using the Crowdin Services, subject to payment of a Fee designated in the selected Plan. | | Activity | translation and proofreading activities, builds, setting updates, source strings updates, comments, and issues, tasks that are associated with a Project. | | Authorization | the set of rights and privileges on the Web Site assigned to a User by a Client. | | Client | a natural or legal person who has accepted these Terms with the Supplier. | | Client Data | Files and any other digital data and information, including translations which are subjected to the Crowdin Services or otherwise inserted to the System by the Client. | | Content | any data and information, other than Client Data, available through Crowdin Services or contained within the structure of the System, articles, documents, brochures, presentations, pictures, images, audiovisual works, other informational materials owned by Crowdin. | | Crowdin Enterprise User | a natural or legal person who has accepted these Terms with the Supplier under Crowdin Enterprise. | | Fee | regular payment for using the activated Account. | | Files | documents of any kind (images, spreadsheets, text files, etc.) that are inserted to the System by the Client, and usually associated with particular Projects. | | Free Trial | temporary access for the purposes of trying out the Web Site and Crowdin Services in accordance with any selected Plan without paying a Fee. | | Guidelines | additional guidelines or rules applicable to specific features, applications, products, or services which may be posted from time to time on the Platform or otherwise made available on or through the Crowdin Services. | | Crowdin OÜ | Crowdin OÜ, a private limited company established under the laws of the Republic of Estonia, having its principal place of business at Mustamäe tee 44/1, Kristiine linnaosa, Tallinn, Harju maakond, Republic of Estonia, 10621 Register under code 14479905. | | Crowdin Materials | the visual interfaces, graphics, design, systems, methods, information, computer code, software, services, “look and feel”, organization, compilation of the content, code, data, and all other elements of the Crowdin Services. | | Crowdin Services | the Web Site, System, Content, Platform, and all content, services and/or products available on or through the Platform, subject to the plan selected by the Client. | | Plan | various criteria related to the use and functionality of the Crowdin Services and on which the Fee is based. | | Platform | the Crowdin Localization management application. | | Private Project | a Project for which the terms of participation are established by the Project Owner. | | Project | the planned set of interrelated Localization and translation tasks to be executed over a fixed period and within certain cost and other limitations. | | Project Owner | the Client that created the Project. | | Public Project With Open Policy | a Project which any Client can join without a confirmation from the Project Owner. Any Client Data posted may become public at the discretion of the Project Owner. | | Public Project with Moderated Policy | a Project which a Client can join only after the confirmation from the Project Owner. Any Client Data posted may become public at the discretion of the Project Owner. | | Reseller | third party entity that (i) purchases Crowdin Services from Supplier and resells such Crowdin Services to Clients, (ii) bills such Clients directly and (iii) provides such Clients with customer service. | | Special Terms | any particulars, specifications and conditions by which the parties have agreed to deviate from these Terms. | | Supplier | as the context requires, Crowdin OÜ. | | System | the integrated cloud computing solution for providing the Crowdin Services, including applications, software, hardware, data bases, interfaces, associated media, documentation, updates, new releases, and other components or materials provided therewith. | | User | a natural person granted with the Authorization to use the Account on behalf of a Client. | | Web Site | the compilation of all web documents (including images, php, and html files) made available via [www.crowdin.com](http://www.crowdin.com) or its sub domains or domains with identical names under other top domains and owned by Supplier. | | Workflow | the movement of tasks through a work process that ensures that specific Users perform activities in a specific sequence. | ## [2. AUTHORITY TO ENTER INTO THESE TERMS WITH SUPPLIER](#2-authority-to-enter-into-these-terms-with-supplier) [Section titled “2. AUTHORITY TO ENTER INTO THESE TERMS WITH SUPPLIER”](#2-authority-to-enter-into-these-terms-with-supplier) The use of the Crowdin Services is subject to acceptance of these Terms. To accept these Terms for itself or on behalf of a Client, a person must have the legal capacity to do so. In the case of an individual, the individual must be at least 18 years of age or have valid authorization from his/her legal representative or custodian. Special terms may apply for special education accounts (see section [GitHub Student Developer Pack. Special Educational Account Terms](/terms/#special-educational-account). In the case of a legal entity, the entity must be duly incorporated and in good standing. The Terms are accepted as soon as one of the following occurs first: the person has received the confirmation of the creation of the Account and necessary credentials from Supplier in order to log in to his/her/its Account; or for those Crowdin Services and parts of the Web Site the use of which is not dependent on creating an Account, upon the moment of gaining access to such services. You may not, without Supplier’s prior written consent, access the Crowdin Services (i) for production purposes, (ii) if you are a competitor of Crowdin, (iii) to monitor the availability, performance or functionality of the Crowdin Services or (iv) for other benchmarking or competitive purposes. Once accepted, these Terms remain effective until terminated as provided for herein. ### [2.1 GitHub Student Developer Pack. Special Educational Account Terms.](#special-educational-account) [Section titled “2.1 GitHub Student Developer Pack. Special Educational Account Terms.”](#special-educational-account) For the use of the Special Student Account, the person must be at least 13 years old and be a verified member of the GitHub Student Developer Pack. By using the Special Education Account, the person represents that he or she has a parent’s or guardian’s permission to use the Special Education Account and they jointly read and accepted these Terms and Conditions. ## [3. MODIFICATIONS TO TERMS](#3-modifications-to-terms) [Section titled “3. MODIFICATIONS TO TERMS”](#3-modifications-to-terms) Supplier reserves the right, at its sole discretion, to change, modify, add, or remove portions of the Terms at any time by posting such changes on or through the Platform or the Crowdin Services. Please check these Terms periodically for changes. Your continued use of the Crowdin Services after such changes have been posted as provided above constitutes your binding acceptance of such changes. Such amended Terms will automatically be effective upon the earlier of (i) your continued use of the Crowdin Services, or (ii) 30 days from posting of such modified Terms on or through the Platform. Notwithstanding the foregoing, the resolution of any dispute that arises between you and Supplier will be governed by the Terms in effect at the time such dispute arose. ## [4. OUR RESPONSIBILITIES](#4-our-responsibilities) [Section titled “4. OUR RESPONSIBILITIES”](#4-our-responsibilities) ### [4.1. Provision of Crowdin Services.](#41-provision-of-crowdin-services) [Section titled “4.1. Provision of Crowdin Services.”](#41-provision-of-crowdin-services) Supplier will (a) make the Crowdin Services, Content and Client Data available to a Client pursuant to these Terms, (b) provide applicable standard support for the Crowdin Services to Client at no additional charge, and/or upgraded support (for an additional charge, if applicable), (c) use commercially reasonable efforts to make the Crowdin Services available 24 hours a day, 7 days a week, except for: (i) planned downtime (of which Supplier shall give advance electronic notice as provided in the Guidelines), and (ii) any unavailability caused by circumstances beyond Supplier’s reasonable control, including, for example, an act of God, act of government, flood, fire, earthquake, civil unrest, act of terror, strike or other labor problem, Internet service provider failure or delay, or denial of service attack. ### [4.2. Protection of Client Data.](#42-protection-of-client-data) [Section titled “4.2. Protection of Client Data.”](#42-protection-of-client-data) Supplier will maintain administrative, physical, and technical safeguards for protection of the security, confidentiality, and integrity of Client Data, as described in the Guidelines. Those safeguards will include, but will not be limited to, measures for preventing access, use, modification or disclosure of Client Data by Supplier personnel except (a) to provide the Crowdin Services and prevent or address service or technical problems, (b) as compelled by law in accordance with Section 7.4 (Compelled Disclosure) below, or (c) as a Client or User expressly permit in writing. The Services may be performed using equipment or facilities located in the European Union, the United States, and Ukraine. The Supplier’s service providers located outside the EU are either Privacy Shield compliant or have executed Standard Contractual Clauses (as approved by the European Commission) that provide legal grounds for assuring that, when processed outside the European Union, the personal data of EU citizens when using the Crowdin Service will receive from the Supplier and its service providers located outside the EU an adequate level of protection within the meaning of Article 46 of Regulation (EU) 2016/679 (General Data Protection Regulation). By agreeing to these Terms, the Client grants the Supplier a general authorization in the meaning of Article 28 (2) of Regulation (EU) 2016/679 to engage processors for the purposes of providing the Crowdin Services. For more information about processors or if you want to subscribe to an email list and receive updates on the changes to the list of sub-processors, please see our [List of Sub-processors](/sub-processors/) ## [5. USING THE CROWDIN SERVICES](#5-using-the-crowdin-services) [Section titled “5. USING THE CROWDIN SERVICES”](#5-using-the-crowdin-services) ### [5.1 Establishing an Account.](#51-establishing-an-account) [Section titled “5.1 Establishing an Account.”](#51-establishing-an-account) Certain features, functions, parts or elements of the Crowdin Services can be used or accessed only by holders of an Account. The person who wishes to create an Account must: 1. complete the sign-up form on the Web Site or alternative process provided by a Reseller if access to the Crowdin Services is purchased from a Reseller; 2. and accept these Terms by clicking “Sign up” or other similar button. Each Client may have only one Account. If several persons need to use an Account on behalf of Client, Client must designate such persons as Users. Each such User shall be subject to the restrictions set forth in these Terms. If Client has designated Users and granted them Authorization, such Users will be deemed to be authorized to act on behalf of Client when using the Account. Supplier is not responsible for and shall have no liability for verifying the validity of Authorization of any User. However, Supplier may, in its discretion, request additional information or proof of the person’s credentials. If Supplier is not certain if a User has been granted Authorization, Supplier may, in its sole discretion, prevent such User from accessing the Crowdin Services and/or suspend or terminate the Account. A User may be associated with multiple Clients and Accounts. Blocking a User from one Account or Project will not remove the User from the Platform if he/she is connected to multiple Accounts. The Client and any User associated with an Account must provide Supplier with true, accurate, current, and complete information about the Client, Users and Account and keep it up to date. ### [5.2 Logging Into an Account.](#52-logging-into-an-account) [Section titled “5.2 Logging Into an Account.”](#52-logging-into-an-account) Client creates a username and password (“Login Credentials”) to be used to log in to its Account unless the Client uses the single sign-on feature or another service to log in. These Login Credentials must not be used by multiple persons. If Client has designated several Users, each User should create separate Login Credentials. Client and each User are responsible for keeping confidential all login credentials associated with an Account. Client must promptly notify Supplier of any disclosure, loss or unauthorized use of any Login Credentials. ### [5.3 Termination of Account.](#53-termination-of-account) [Section titled “5.3 Termination of Account.”](#53-termination-of-account) Client may terminate these Terms by terminating the Account at any time as provided in Section 17. Supplier shall permanently delete the Account within six months of the effective date of the termination. ### [5.4 Fees.](#54-fees) [Section titled “5.4 Fees.”](#54-fees) The use of an Account is subject to a Fee. Different rates apply to different Plans. The applicable Fee is charged in advance on monthly or annual payment intervals, unless agreed otherwise between parties. In case of cancellation by Supplier, Supplier shall refund due amount of money paid by the Client for the unused Software Services except the amounts of the discount provided to the Client for the Annual Subscription. If, after signing up, Client elects to upgrade to a more expensive Plan, the unused portion of any prepaid Fees shall be applied to the Fee of the more expensive Plan. All Fees are stated net and are exclusive of all taxes, VAT, levies, fees, withholdings, or duties applicable under any applicable law, unless stated otherwise stated herein. Client is solely responsible for the payment of such taxes, VAT, levies, fees, withholdings, or duties. The Client shall not make any deductions, withholdings or reduction of the Fees without first obtaining Supplier’s written consent. In the event the net amount received by Supplier is less than the Fee, Supplier shall have the right to stop providing the Services. ### [5.5 Changing Plans.](#55-changing-plans) [Section titled “5.5 Changing Plans.”](#55-changing-plans) Any Client has the right to upgrade or downgrade a current Plan at any time by selecting a new Plan among the collection of Plans determined by the Supplier. In such an event, the Client’s credit card on file with the Supplier will automatically be charged with a Fee for the next payment interval with the rate stipulated in the new Plan. Downgrading of the current Plan may cause the loss of features or capacity of the Account. ### [5.6 Free Trial.](#56-free-trial) [Section titled “5.6 Free Trial.”](#56-free-trial) A new Client may be entitled to a Free Trial, unless the Client has applied for the Account as a result of an ongoing marketing campaign organized by the Supplier in cooperation with its partners. The Client is not required to provide any credit card information during the period of Free Trial. If the period of Free Trial has expired, the Account will be automatically deactivated. In order to prevent deactivation or to reactivate the Account, the Client is required to select a suitable Plan and pay the first Fee. If the Client does not pay the first Fee within 2 weeks as of the expiry of the Free Trial, Supplier has the right to permanently delete the Account, including all Client Data therein. ## [6. PAYMENT](#6-payment) [Section titled “6. PAYMENT”](#6-payment) The following provisions are applicable only if you purchase access to the Crowdin Services directly from Supplier. If you purchase access to the Crowdin Services through a Reseller, the payment terms are set forth in the agreement with your Reseller. ### [6.1 Credit Card Authorization.](#61-credit-card-authorization) [Section titled “6.1 Credit Card Authorization.”](#61-credit-card-authorization) Supplier’s payment processing partner listed in the list of processors may seek pre-authorization of Client’s credit card account prior to your purchase of Crowdin Services in order to verify that the credit card is valid and has the necessary funds or credit available to cover your purchase. You authorize such credit card account to pay any amounts described herein, and authorize Supplier to charge all sums described in these Terms to such credit card account. You agree to provide Supplier updated information regarding your credit card account upon Supplier’s request and any time the information earlier provided is no longer valid. ### [6.2 Electronic Invoice.](#62-electronic-invoice) [Section titled “6.2 Electronic Invoice.”](#62-electronic-invoice) In case the Client is willing to pay via Purchase Order or Wire Transfer, the invoice for payment will be issued on request, all requests should be sent to . The electronic invoices are available only for annual and semi-annual payment intervals. Client must pay the invoice by the due date indicated on the invoice. ## [7. CLIENT DATA](#7-client-data) [Section titled “7. CLIENT DATA”](#7-client-data) ### [7.1 Uploading Client Data to Platform.](#71-uploading-client-data-to-platform) [Section titled “7.1 Uploading Client Data to Platform.”](#71-uploading-client-data-to-platform) If the Client uploads Client Data to the Platform, such Client Data and any processing of such Client Data must be in compliance with these Terms and applicable law. By uploading Client Data to the Platform and/or using Crowdin Services, the Client represents that the Client has all necessary legal rights, title and interest in and to the Client Data whether posted and/or uploaded by the Client or with Client’s authorization or made available on or through the Crowdin Services by Supplier. By uploading Client Data to the Platform, Client authorizes Supplier to process the Client Data. The Client is responsible for ensuring that: * the Client and any of the Users associated with the Account do not create, transmit, display or make otherwise available any Client Data that violates the terms of these Terms, the rights of Supplier or is harmful (for example viruses, worms, malware and other destructive codes), offensive, threatening, abusive, harassing, tortuous, defamatory, vulgar, obscene, invasive of another’s privacy, hateful or otherwise unlawful; * and the Client and all of the Users associated with the Account have the necessary rights to use the Client Data, including to insert it into the Platform and process it by means of the Account. * the Account or Client Data is not used for any illegal or unlawful activities. ### [7.2 No Guarantee of Accuracy.](#72-no-guarantee-of-accuracy) [Section titled “7.2 No Guarantee of Accuracy.”](#72-no-guarantee-of-accuracy) Supplier does not guarantee any accuracy with respect to any information contained in any Client Data, and strongly recommends that you think carefully about what you transmit, submit or post to or through the Crowdin Services. You understand that all information contained in Client Data is the sole responsibility of the person from whom such Client Data originated. This means that Client, and not Supplier, is entirely responsible for all Client Data that is uploaded, posted, transmitted, or otherwise made available through the Crowdin Services, as well as for any actions taken by the Suppliers or other Clients or Users or third parties as a result of such Client Data. Supplier has no obligations to monitor the use of or ensure that the Client Data does not infringe upon the intellectual property rights of other Clients, Users or third parties. Client or User (as the case may be) is solely responsible for securing all necessary rights to the Client Data. ### [7.3 Unlawful Client Data.](#73-unlawful-client-data) [Section titled “7.3 Unlawful Client Data.”](#73-unlawful-client-data) Supplier is not obliged to pre-screen, monitor or filter any Client Data or acts of its processing by the Client in order to discover any unlawful nature therein. However, if such unlawful Client Data or the action of its unlawful processing is discovered or brought to the attention of Supplier or if there is reason to believe that certain Client Data is unlawful, Supplier has the right to: * notify the Client of such unlawful Client Data; * demand that the Client bring the unlawful Client Data into compliance with these Terms and applicable law; * temporarily or permanently remove the unlawful Client Data from the Web Site or Account, restrict access to it, suspend it or delete it. If Supplier is presented convincing evidence that the Client Data is not unlawful, Supplier may, at its sole discretion, restore such Client Data, which was removed from the Account or access to which was restricted. In addition, in the event Supplier believes in its sole discretion Client Data violates applicable laws, rules or regulations or these Terms, Supplier may (but has no obligation), to remove such Client Data at any time with or without notice. Crowdin OÜ as the data processor will assist the Client as the data controller in meeting the Client’s obligations under Regulation (EU) 2016/679, providing subject access, and allowing data subjects to exercise their rights under Regulation (EU) 2016/679. ### [7.4 Compelled Disclosure.](#74-compelled-disclosure) [Section titled “7.4 Compelled Disclosure.”](#74-compelled-disclosure) Supplier may disclose a Client’s confidential information to the extent compelled by law to do so. In such instance, Supplier will use commercially reasonable efforts to provide Client with prior notice of the compelled disclosure (to the extent legally permitted) and Client shall provide reasonable assistance, at its cost, if Client wishes to contest the disclosure. If Supplier is compelled by law to disclose Client’s confidential information as part of a civil proceeding to which Supplier is a party, and Client is not contesting the disclosure, Client will reimburse Supplier for its reasonable cost of compiling and providing secure access to that confidential information. ## [8. SERVICES](#8-services) [Section titled “8. SERVICES”](#8-services) ### [8.1 Use of the Crowdin Services.](#81-use-of-the-crowdin-services) [Section titled “8.1 Use of the Crowdin Services.”](#81-use-of-the-crowdin-services) Subject to these Terms, and the payment of the applicable service Fee, Supplier grants Client and its authorized users a non-exclusive, non-transferable, non-sub-licensable license to use the Crowdin Services to: * collect, store and organize Client Data, such as add new Localization resources, create Projects and add Workflows into these Projects, generate reports based on Client Data, invite Translation Vendors into Projects and monitor translation progress, add Files to be offered for context through Localization process; * organize communication though Comments and Discussions; * add new Users and grant them Authorizations, assign Activities to a particular User; * modify and delete Client Data; * customize the standard features of the Crowdin Services; * receive reasonable help and guidance and from Supplier regarding the use of the Crowdin Services. ### [8.2 Technical Support.](#82-technical-support) [Section titled “8.2 Technical Support.”](#82-technical-support) Supplier shall provide reasonable technical support to Client and its authorized User at the reasonable request of the Client. Supplier shall respond to enquiries of support from a Client utilizing the contacts set forth below as soon as reasonably possible. The contacts for all enquiries of support are: chat application on the Web Page, or e-mail: Notwithstanding the foregoing, if you purchased access to the Crowdin Services from a Reseller, then first-line technical support will be provided by the Reseller and not by the Supplier. ### [8.3 Modifications to Service.](#83-modifications-to-service) [Section titled “8.3 Modifications to Service.”](#83-modifications-to-service) Supplier reserves the right to modify the Crowdin Services or any part or element thereof from time to time without prior notice, including, without limitation: * rebranding the Crowdin Services at its sole discretion; * ceasing providing or discontinuing the development any particular Crowdin Service or part or element of the Platform temporarily or permanently; * taking such action as is necessary to preserve Supplier’s rights upon any use of the Crowdin Services that may be reasonably interpreted as violation of Supplier’s intellectual property rights, distribution of Internet viruses, worms, Trojan horses, malware, and other destructive activities or illegal activity. As applicable, Client may be notified of such modifications when logging in to the Account. Modifications, including change in applicable rates for the Crowdin Services, will become effective thirty (30) days before the effective date of such modification. If the Client does not accept the modification, the Client shall notify Supplier or Reseller (if Client purchased access to the Crowdin Services from a Reseller) before the effective date of the modification, and these Terms will terminate on the effective date of the modification. The Client’s continued use of the Crowdin Services, or any part or element thereof, after the effective date of a modification shall indicate its consent to the modifications. Supplier shall not be liable to the Client or to any third party for any modification, suspension or discontinuance of the Crowdin Services, or any part or element thereof. ## [9. DATA PROCESSING CONTRACT](#9-data-processing-contract) [Section titled “9. DATA PROCESSING CONTRACT”](#9-data-processing-contract) For the purposes of Article 28 of Regulation (EU) 2016/679, these Terms constitute the data processing contract between the Client as the data controller and the Supplier as the data processor. The Client hereby instructs the Supplier to process the data as described in these Terms. ### [9.1 Subject matter and nature of processing.](#91-subject-matter-and-nature-of-processing) [Section titled “9.1 Subject matter and nature of processing.”](#91-subject-matter-and-nature-of-processing) The Supplier provides the Platform where the Client, as the data controller, can collect, store and organize the personal data of data subjects determined by the Client. The Platform has been designed to work as a Localization management tool but, to the extent not regulated by these Terms, the Client decides how they use the Platform. ### [9.2 Duration.](#92-duration) [Section titled “9.2 Duration.”](#92-duration) The Supplier will process data on behalf of the Client until the termination of the Crowdin Services in accordance with these Terms. Upon termination, Crowdin will store the Client’s data for a period of six months, should the Client wish to reopen the Account to resume the use of the Crowdin Services or to export Client Data, unless instructed otherwise by the Client. The Supplier deletes or returns all the personal data to the controller after the end of the provision of services relating to processing, and deletes existing copies unless Union or Member State law requires storage of the personal data. ### [9.3 Parties’ rights and obligations.](#93-parties-rights-and-obligations) [Section titled “9.3 Parties’ rights and obligations.”](#93-parties-rights-and-obligations) The Client’s rights and obligations regarding Client Data are provided in sections 4 through 10 of these Terms. The Supplier ensures that persons authorised to process the personal data have committed themselves to confidentiality or are under an appropriate statutory obligation of confidentiality. The Supplier takes all measures required pursuant to Article 32 of Regulation (EU) 2016/679. The Supplier undertakes to make available to the controller all information necessary to demonstrate compliance with their obligations and to allow for and contribute to audits, including inspections, conducted or mandated by the Client as the data controller. ## [10. RESTRICTIONS](#10-restrictions) [Section titled “10. RESTRICTIONS”](#10-restrictions) ### [10.1 Prohibited Activities.](#101-prohibited-activities) [Section titled “10.1 Prohibited Activities.”](#101-prohibited-activities) Client and its authorized Users may use the Crowdin Services and any part or element thereof only in the scope, with the means and for purposes as identified in these Terms and applicable law. By way of example, neither the Client nor any User may: * use the Crowdin Services or any part or element thereof to commit a crime, breach any applicable law or entice or invite others to carry out such illegal actions; * copy, duplicate, distribute, modify, adapt, hack, create derivative works, reverse engineer or decompile the Crowdin Services or any part or element thereof, or attempt to extract the source code thereof, unless (i) it is expressly allowed under applicable law, and (ii) to the extent that the Supplier is not permitted by that applicable law to exclude or limit the foregoing rights; * use the Crowdin Services or any part or element thereof unless it has agreed to these Terms. ### [10.2 Certain Uses Require Supplier Consent.](#102-certain-uses-require-supplier-consent) [Section titled “10.2 Certain Uses Require Supplier Consent.”](#102-certain-uses-require-supplier-consent) The Client or any User may not, without Supplier’s prior express written consent (e-mail, fax, Skype, etc.): * sell, resell, lease, license, sublicense, distribute, provide, disclose, divulge, exploit or otherwise grant Access or make the Crowdin Services available in whole or in part to any third perties, unless such third party is another authorized User of the same Client; * use the Crowdin Services or any part or element thereof in a scope, with means or for purposes other than those for which their functionality was created; * use the Crowdin Services or any part or element thereof by means of programs that send them automatic enquiries or requests, unless such program has been made available by Supplier; ## [11. PRIVACY](#11-privacy) [Section titled “11. PRIVACY”](#11-privacy) Supplier takes the privacy of its Clients and Users very seriously. Supplier’s [Privacy Policy](/privacy-policy/) is hereby incorporated into these Terms by reference. Please read the Privacy Policy carefully as it governs Supplier’s collection, use, and disclosure of Client’s or User’s personal information. ## [12. INTELLECTUAL PROPERTY RIGHTS](#12-intellectual-property-rights) [Section titled “12. INTELLECTUAL PROPERTY RIGHTS”](#12-intellectual-property-rights) ### [12.1 Crowdin’s Intellectual Property Rights in the Crowdin Services.](#121-crowdins-intellectual-property-rights-in-the-crowdin-services) [Section titled “12.1 Crowdin’s Intellectual Property Rights in the Crowdin Services.”](#121-crowdins-intellectual-property-rights-in-the-crowdin-services) The Crowdin Services, Crowdin Materials, Crowdin trade names and trademarks, and any parts or elements thereof are solely and exclusively owned and operated by Supplier and its third party vendors and hosting partners. Crowdin Materials are protected by copyright, trade dress, patent, trade secrets, and trademark laws, international conventions and treaties, and all other relevant intellectual property and proprietary rights laws. Supplier, its affiliates and licensors retains all right, title and interest in such Crowdin Services, Crowdin Materials, Crowdin trade names and trademarks, and any parts or elements. Your use of the Crowdin Services and Crowdin Materials, and any parts or elements does not grant to you any ownership right or intellectual property rights therein. Any commercial or promotional distribution, publishing or exploitation of the Crowdin Materials is strictly prohibited unless you have received the express prior written permission from Supplier or the otherwise applicable rights holder. Supplier reserves all rights to the Crowdin Services, Crowdin Materials and Crowdin trade names and trademarks not expressly granted in the Terms. ### [12.2 Content Owned by Crowdin.](#122-content-owned-by-crowdin) [Section titled “12.2 Content Owned by Crowdin.”](#122-content-owned-by-crowdin) Subject to these Terms and the payment of the applicable service Fee, Supplier grants Client and its authorized users a non-exclusive, non-transferable, non-sub-licensable license to download a single copy of any part of the Content solely for your personal, non-commercial use if you retain all copyright and proprietary notices that are contained in such part of the Content. You expressly acknowledge that you do not acquire any ownership rights by downloading any copyrighted material from or through the Platform or the Crowdin Services. You shall not copy, distribute or publish any Content or any information obtained or derived therefrom except as permitted on or through the Crowdin Services or as otherwise permitted by applicable law. ### [12.3 Client Data.](#123-client-data) [Section titled “12.3 Client Data.”](#123-client-data) 1. Special Terms apply to Crowdin Enterprise Users as specified in Section 12.3.3. Supplier may use Client Data in an aggregated or anonymized format for research, educational and other similar purposes. Supplier may not otherwise use or display Client Data without Client’s written consent. Supplier respects your right to exclusive ownership of your Client Data. Unless specifically permitted by you, your use of the Crowdin Services does not grant Supplier the license to use, reproduce, adapt, modify, publish or distribute the Client Data created by you or stored in your Account for Supplier’s commercial, marketing or any similar purpose. Client expressly grants Supplier the right to use and analyze aggregate system activity data associated with use of the Crowdin Services by Client and its Users for the purposes of optimizing, improving or enhancing the way the Crowdin Services operate, and to create new features and functionality in connection with the Crowdin Services in the sole discretion of Supplier. 2. Client is solely responsible for its own Client Data and the consequences of posting or publishing them on or through the Crowdin Services. In connection with Client Data, Client affirms, represents, and warrants that: (i) Client either owns its Client Data or has the necessary licenses, rights, consents, and permissions to use and authorize the Suppliers to display or otherwise use the Client Data under all patent, trademark, copyright, trade secrets, or other proprietary rights in and to your Client Data in a manner consistent with the intended features of the Crowdin Services and these Terms, and to grant the rights and license which are necessary to perform services hereunder, and (ii) Client Data, Supplier’s or any Crowdin Licensee’s use of such Client Data pursuant to these Terms, and Supplier’s or any Crowdin Licensee’s exercise of the license rights which are necessary to perform services hereunder. Client further affirms, represents, and warrants do that the Client does not and will not: (a) infringe, violate, or misappropriate any third-party right, including any copyright, trademark, patent, trade secret, moral right, privacy right, right of publicity, or any other intellectual property or proprietary right; (b) violate any applicable law or regulation anywhere in the world; or (c) require obtaining a license from or paying any fees and/or royalties by Supplier to any third party for the performance of any Crowdin Services Client has chosen to be performed by Supplier or for the exercise of any rights granted in these Terms, unless Client and Supplier otherwise agree. 3. Special Terms for Crowdin Enterprise Users. (For Crowdin Users Only) As part of your voluntary contribution to any Crowdin project, by agreeing to these terms, you are acknowledging and agreeing that your name, username and email address will become embedded and part of the project and organization, which may be available to organization admins. You understand the removal of this information would be impermissibly destructive to the project and the interests of all those who contribute, utilize, and benefit from it. Therefore, in consideration of your participation in any project, you understand that retaining your name, username and email address, as described above, does not require your consent and that the right of erasure, as spelled out in the GDPR Article 17 (1) b does not apply. The legal basis for our lawful processing of this personal data is Article 6 (1) f (“processing is necessary for the purposes of the legitimate interests pursued by the controller”). ### [12.4 Feedback.](#124-feedback) [Section titled “12.4 Feedback.”](#124-feedback) If Client or a User provides Suppliers with any comments, bug reports, feedback, or modifications for the Crowdin Services (“Feedback”), Supplier shall have the right to use such Feedback at its discretion, including, but not limited to the incorporation of such suggested changes into the Crowdin Services. Client or User (as applicable) hereby grants Supplier a perpetual, irrevocable, nonexclusive, royalty free license under all rights necessary to incorporate, publish, reproduce, distribute, modify, adapt, prepare derivative works of, publicly display, publicly perform, exploit and use your Feedback for any purpose. Supplier shall have the right to modify or remove any Feedback provided in the public areas of the Web Site if the Supplier deems, at its discretion, harmful, offensive, threatening, abusive, harassing, tortuous, defamatory, vulgar, obscene, invasive of another’s privacy, hateful or otherwise unlawful. ### [12.5. Public Projects.](#125-public-projects) [Section titled “12.5. Public Projects.”](#125-public-projects) Client or User (as the case may be) understands and agrees that any Client Data posted publicly and/or via Public Projects on the Crowdin Platform, may be viewed by others and Client or User agrees to allow others to view and use such Client Data. Client or User hereby grants Supplier and other Clients a perpetual, irrevocable, nonexclusive, royalty free license under all rights necessary to incorporate, publish, reproduce, distribute, modify, adapt, prepare derivative works of, publicly display, publicly perform, exploit and use such Client Data, unless otherwise is stated in a written contract between Client or User and a respective party. ### [12.6. Responsibilities of Project Owners.](#126-responsibilities-of-project-owners) [Section titled “12.6. Responsibilities of Project Owners.”](#126-responsibilities-of-project-owners) Project Owner is solely responsible for obtaining all necessary rights, licenses, agreements, authorizations and consents, by whatever name called, to display, publish, reproduce, distribute, modify, adapt, prepare derivative works of, perform, exploit, process and use all Client Data posted on the Project, regardless of whether it is posted by the Project Owner or a third party. ## [13. THIRD-PARTY SITES, PRODUCTS AND SERVICES](#13-third-party-sites-products-and-services) [Section titled “13. THIRD-PARTY SITES, PRODUCTS AND SERVICES”](#13-third-party-sites-products-and-services) The Crowdin Services may include links to other websites or services (“Linked Sites”) solely as a convenience to Clients. Unless otherwise specifically and explicitly indicated, Supplier does not endorse any such Linked Sites or the information, material, products, or services contained on or accessible through Linked Sites. Furthermore, Supplier makes no express or implied warranties with regard to the information, material, products, or services that are contained on or accessible through Linked Sites. ACCESS AND USE OF LINKED SITES, INCLUDING THE INFORMATION, MATERIAL, PRODUCTS, AND SERVICES ON LINKED SITES OR AVAILABLE THROUGH LINKED SITES, IS SOLELY AT YOUR OWN RISK. Any content referred to as community provided is provided by third parties and not developed or maintained by Crowdin. By using any community marked code or libraries in your software development, you acknowledge and agree that Crowdin is not in any way responsible for the performance or damages caused by such community provided code or library. ## [14. DISCLAIMERS; NO WARRANTY](#14-disclaimers-no-warranty) [Section titled “14. DISCLAIMERS; NO WARRANTY”](#14-disclaimers-no-warranty) UNLESS OTHERWISE EXPRESSLY STATED BY SUPPLIER, THE CROWDIN SERVICES, CROWDIN MATERIAL, AND ANY CONTENT, SERVICES, OR FEATURES MADE AVAILABLE IN CONJUNCTION WITH OR THROUGH THE CROWDIN SERVICES ARE PROVIDED “AS IS” AND “AS AVAILABLE” WITHOUT WARRANTIES OF ANY KIND EITHER EXPRESS OR IMPLIED. TO THE FULLEST EXTENT PERMISSIBLE PURSUANT TO APPLICABLE LAW, SUPPLIER AND ITS AFFILIATES DISCLAIM ALL WARRANTIES, STATUTORY, EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, IMPLIED WARRANTIES OF MERCHANT ABILITY, FITNESS FOR A PARTICULAR PURPOSE, NON-INFRINGEMENT OF PROPRIETARY RIGHTS, CORRECTNESS, ACCURACY, AND RELIABILITY. UNLESS OTHERWISE EXPRESSLY STATED BY SUPPLIER, SUPPLIER AND ITS AFFILIATES DO NOT WARRANT THAT THE CROWDIN SERVICES AND ANY CONTENT, CLIENT DATA SERVICES, OR FEATURES MADE AVAILABLE IN CONJUNCTION WITH OR THROUGH THE CROWDIN SERVICES WILL BE UNINTERRUPTED OR ERROR-FREE, THAT DEFECTS WILL BE CORRECTED, OR THAT THE CROWDIN SERVICES AND ANY CONTENT, CLIENT DATA, SERVICES, OR FEATURES MADE AVAILABLE IN CONJUNCTION WITH OR THROUGH THE CROWDIN SERVICES OR THE SERVER THAT MAKES THEM AVAILABLE ARE FREE OF VIRUSES OR OTHER HARMFUL COMPONENTS. UNLESS OTHERWISE EXPRESSLY STATED BY SUPPLIER, SUPPLIER AND ITS AFFILIATES DO NOT WARRANT OR MAKE ANY REPRESENTATIONS REGARDING THE USE OR THE RESULTS OF THE USE OF THE PLATFORM, THE Crowdin SERVICES, Crowdin MATERIAL OR ANY LINKED SITES, IN TERMS OF CORRECTNESS, ACCURACY, RELIABILITY, OR OTHERWISE. THE LAWS OF CERTAIN COUNTRIES AND STATES DO NOT ALLOW LIMITATIONS ON IMPLIED WARRANTIES OR THE EXCLUSION OR LIMITATION OF CERTAIN DAMAGES. IF THESE LAWS APPLY TO YOU, SOME OR ALL OF THE ABOVE DISCLAIMERS, EXCLUSIONS, OR LIMITATIONS MAY NOT APPLY TO YOU, AND YOU MIGHT HAVE ADDITIONAL RIGHTS. ## [15. INDEMNIFICATION](#15-indemnification) [Section titled “15. INDEMNIFICATION”](#15-indemnification) You agree to defend, indemnify and hold harmless Supplier and its affiliates, and their respective directors, officers, employees and agents, from any claims, losses, damages, liabilities, including attorney’s fees, arising out of your use or misuse of the Crowdin Services, Crowdin Materials, representations made to the Supplier, its affiliates and/or third parties, violation of these Terms, violation of the rights of any other person or entity, or any breach of the foregoing representations, warranties, and covenants. Supplier reserves the right, at its own expense, to assume the exclusive defense and control of any matter for which you are required to indemnify Supplier, and you agree to cooperate with such defense of these claims. ## [16. LIMITATION OF LIABILITY](#16-limitation-of-liability) [Section titled “16. LIMITATION OF LIABILITY”](#16-limitation-of-liability) ### [16.1 No Liability:](#161-no-liability) [Section titled “16.1 No Liability:”](#161-no-liability) Supplier shall not be liable to the Client or User for any consequences resulting from: * any modifications in these Terms, calculation and rates of Fees, the Crowdin Services, Crowdin Material, or any part or element thereof (including but not limited to Account), * including any error, permanent or temporary interruption, discontinuance, suspension or other type of unavailability of the Crowdin Services or Crowdin Material; * deletion of, corruption of, or failure to store any Client Data; * use of Client Data by the Client or any of the Users associated with the Account; * upgrading or downgrading the current Plan; * any disclosure, loss or unauthorized use of the login credentials of Client or any authorized User due to Client’s failure to keep them confidential; * the Client’s use of the Account or the Crowdin Services by means of browsers other than those accepted or supported by the Supplier; * the application of any remedies against the Client or authorized Users by the Supplier, for example if the Client or User has committed a crime or conducted a breach of applicable law by using the Crowdin Services or any part or element thereof; * the differences between technologies and platforms used for access, for example if certain features, functions, parts or elements of the Crowdin Services are designed for use on a personal computer or laptop and do not function on a mobile platform or a tablet; * the Supplier’s application of the remedies described in these Terms, even if the reasonable grounds or legal basis for the application of these remedies turned out to be unfounded or invalid afterwards. In addition, Supplier and its affiliates shall not be liable to the Client for any claim by any User, person, Organization or third parties against the Client arising out of the Client’s failure to: * provide Supplier with accurate information about the Client, Users or Account; * notify Supplier of any reasons due to which a User does not have the right to use the Account on behalf of the Client; * provide any Products which it has agreed to provide to such a person or Organization (whether such failure arises as a result of Supplier’s negligence, breach if these Terms or otherwise); * ensure the lawfulness of the Client Data; * obtain the necessary rights to use the Client Data; or * abide by any of the restrictions described in these Terms. ### [16.2 Limitation of Liability.](#162-limitation-of-liability) [Section titled “16.2 Limitation of Liability.”](#162-limitation-of-liability) IN NO EVENT SHALL THE AGGREGATE LIABILITY OF CROWDIN AND ITS AFFILIATES ARISING OUT OF OR RELATED TO THESE TERMS EXCEED THE TOTAL AMOUNT PAID BY CLIENT HEREUNDER FOR THE CROWDIN SERVICES GIVING RISE TO THE LIABILITY IN THE SIX MONTHS PRECEDING THE FIRST INCIDENT OUT OF WHICH THE LIABILITY AROSE. THE FOREGOING LIMITATION WILL APPLY WHETHER AN ACTION IS IN CONTRACT OR TORT AND REGARDLESS OF THE THEORY OF LIABILITY, BUT WILL NOT LIMIT CLIENT’S PAYMENT OBLIGATIONS UNDER THE “PAYMENT” SECTION ABOVE. ### [16.3 Exclusion of Consequential and Related Damages.](#163-exclusion-of-consequential-and-related-damages) [Section titled “16.3 Exclusion of Consequential and Related Damages.”](#163-exclusion-of-consequential-and-related-damages) IN NO EVENT WILL EITHER PARTY OR ITS AFFILIATES HAVE ANY LIABILITY ARISING OUT OF OR RELATED TO THESE TERMS FOR ANY LOST PROFITS, REVENUES, GOODWILL, OR INDIRECT, SPECIAL, INCIDENTAL, CONSEQUENTIAL, COVER, BUSINESS INTERRUPTION OR PUNITIVE DAMAGES, WHETHER AN ACTION IS IN CONTRACT OR TORT AND REGARDLESS OF THE THEORY OF LIABILITY, EVEN IF A PARTY OR ITS AFFILIATES HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES OR IF A PARTY’S OR ITS AFFILIATES’ REMEDY OTHERWISE FAILS OF ITS ESSENTIAL PURPOSE. THE FOREGOING DISCLAIMER WILL NOT APPLY TO THE EXTENT PROHIBITED BY LAW. ## [17. TERMINATION OF THESE TERMS](#17-termination-of-these-terms) [Section titled “17. TERMINATION OF THESE TERMS”](#17-termination-of-these-terms) ### [17.1 For Convenience.](#171-for-convenience) [Section titled “17.1 For Convenience.”](#171-for-convenience) These Terms may be terminated for convenience upon written notice to the other party as indicated in the “Notice” Section below: * by the Client any time by clicking the no-questions-asked cancellation link on the Web Site, when logged in to the Account, or if the Client is paying for the Service with a PayPal account, by revoking the billing agreement on its PayPal profile; or if the client is paying for the Service via a Reseller, by means agreed upon between the Client and the Reseller; * by Supplier upon decision to end provision of the Crowdin Services and close the Platform; or * immediately by either party, if proceedings are initiated for the other party’s liquidation or insolvency or a negotiated settlement with the other party’s creditors is concluded or an assignment is made on behalf of the other party for the benefit of creditors. ### [17.2 For Cause.](#172-for-cause) [Section titled “17.2 For Cause.”](#172-for-cause) These Terms may be terminated for default upon written notice to the other party as indicated in the “Notice” Section below: * by either party in case of breach of these Terms by the other party, if the breach has not been cured within 30 days of receipt of a notice from the non-breaching party; or * immediately by either party if the other party breaches its obligations, as applicable under Sections 12 **Intellectual Property Rights** and 15 **Indemnification** of these Terms. * immediately by the Supplier, in its sole discretion, in the event of material breach of these Terms or to prevent any unlawful or illegal activity or use. ### [17.3 Effect of Termination.](#173-effect-of-termination) [Section titled “17.3 Effect of Termination.”](#173-effect-of-termination) Upon termination of these Terms, Supplier shall deactivate and permanently delete the Account, within six months of the effective date of termination of these Terms. If the Client has specifically requested for an earlier deletion of the Account, Supplier shall fulfill such request within 1 month of its receipt of such request. Client must: * stop using and prevent the further usage of the Crowdin Services, including, without limitation, the Platform; * pay any amounts owed to Supplier under these Terms; and * discharge any liability incurred by the Client before under these Terms prior to their termination; and The following provisions shall survive the termination of these Terms: Sections 1, 7.4, 10, 11, 12, 14, 15, 16, 18 and 19. ### [17.4 Remedies.](#174-remedies) [Section titled “17.4 Remedies.”](#174-remedies) If Supplier terminates these Terms as a result of an uncured breach by a Client or User, Supplier is entitled to use the same or similar remedies against any other persons who use the Crowdin Services in conflict with these Terms. Notwithstanding the foregoing, Supplier may also apply any other remedies available to it under the applicable law. Upon application of any remedies, the Client or User may lose Access or suffer a loss of certain features, functions, parts or elements of the Crowdin Services. If Supplier has reasonable grounds to believe that the Client’s or User’s use of the Crowdin Services, including the Account may harm any third parties, Supplier has the right to take adequate measures under its control to prevent, stop and eliminate the harm, where possible, in order to protect those third parties. ## [18. WHO YOU ARE CONTRACTING WITH](#18-who-you-are-contracting-with) [Section titled “18. WHO YOU ARE CONTRACTING WITH”](#18-who-you-are-contracting-with) ### [18.1 General.](#181-general) [Section titled “18.1 General.”](#181-general) By accepting these Terms, the Client is contracting with the Supplier Crowdin OÜ, registered at Mustamäe tee 44/1, Kristiine linnaosa, Tallinn, Harju maakond, Republic of Estonia, 10621 ### [18.2 Governing Law and Jurisdiction.](#182-governing-law-and-jurisdiction) [Section titled “18.2 Governing Law and Jurisdiction.”](#182-governing-law-and-jurisdiction) This Agreement shall be governed by and construed and enforced in accordance the substantive law of the Republic of Estonia. In the event of a dispute, controversy or claim arising out of or in relation to these Terms, including but not limited to the formation, validity, breach or termination thereof, the parties shall attempt to solve the matter amicably in mutual negotiations. In the event a mutually acceptable resolution cannot be reached within a reasonable time, either party will be entitled to seek all available remedies, including legal remedies subject to the terms and conditions set forth below. Notwithstanding the foregoing and subject to the terms and conditions set forth below, either party may seek injunctive relief with respect to any disputed matter to the extent possible under applicable law. Should an amicable settlement between parties not be possible, the dispute shall be finally solved in court or by arbitration as designated herein subject to the terms and conditions set forth below. The United Nations Convention on Contracts for the International Sale of Goods (Vienna Convention of 1980) shall not be applied to these Terms. Any questions relating to these Terms which are not expressly or implicitly settled by the provisions contained in these Terms shall be governed by and construed in accordance with the laws of the Republic of Estonia, without giving effect to any principles of conflicts of law. Court having exclusive jurisdiction is Harju County. We each agree that we shall bring any dispute against the other in our respective individual capacities and not as a plaintiff or class member in any purported class, representative proceeding or as an association. In addition, we each agree that disputes shall be arbitrated only on an individual basis and not in a class, consolidated or representative action. The arbitrator does not have the power to vary these provisions. If any part of this provision is ruled to be unenforceable, then the balance of this provision shall remain in full effect and construed and enforced as if the portion ruled unenforceable were not contained herein. Use of the Crowdin Services is not authorized in any jurisdiction that does not give effect to all provisions of these Terms, including without limitation, this section. Notwithstanding the foregoing, you and the Suppliers agree that nothing herein shall be deemed to waive, preclude, or otherwise limit either party’s right to (i) pursue enforcement actions through applicable federal, state, or local agencies where such actions are available, (ii) seek injunctive relief in a court of law, or (iii) to file suit in a court of law to address intellectual property infringement claims. ## [19. GENERAL PROVISIONS](#19-general-provisions) [Section titled “19. GENERAL PROVISIONS”](#19-general-provisions) ### [19.1 Relationship of the Parties.](#191-relationship-of-the-parties) [Section titled “19.1 Relationship of the Parties.”](#191-relationship-of-the-parties) The parties will act solely as independent contractors. These Terms shall not be construed as creating an agency, partnership, joint venture, fiduciary duty, or any other form of legal association between the Client and either Supplier, and the Client shall not represent to the contrary, whether expressly, by implication, appearance or otherwise. These Terms are not for the benefit of any third parties. ### [19.2 Severability.](#192-severability) [Section titled “19.2 Severability.”](#192-severability) If any term, condition or provision of these Terms is held to be invalid, unenforceable or illegal in whole or in part for any reason, that provision shall be enforced to the maximum extent permissible so as to effect the intent of the parties. The validity and enforceability of the remaining terms, conditions or provisions, or portions of them, shall not be affected. ### [19.3 Entire Agreement.](#193-entire-agreement) [Section titled “19.3 Entire Agreement.”](#193-entire-agreement) These Terms are the entire agreement between Client and Supplier regarding Client’s use of the Crowdin Services and supersedes all prior and contemporaneous agreements, proposals or representations, written or oral, concerning its subject matter. Except as otherwise provided herein, no modification, amendment, or waiver of any provision of these Terms will be effective unless in writing and signed by the party against whom the modification, amendment or waiver is to be asserted. ### [19.4 Assignment.](#194-assignment) [Section titled “19.4 Assignment.”](#194-assignment) Client may not, directly or indirectly, in whole or in part, by operation of law or otherwise, assign or transfer these Terms or delegate any of its rights and/or obligations under these Terms without Supplier’s prior written consent. Any attempted assignment, transfer or delegation without such prior written consent will be void and unenforceable. Notwithstanding the foregoing, the Client, or its permitted successive assignees or transferees, may assign or transfer these Terms or delegate any rights or obligations hereunder without consent: (1) to any entity controlled by, or under common control with the Client, or its permitted successive assignees or transferees; or (2) in connection with a merger, reorganization, transfer, sale of assets or product lines, or change of control or ownership of the Client, or its permitted successive assignees or transferees. ### [19.5 No Waiver.](#195-no-waiver) [Section titled “19.5 No Waiver.”](#195-no-waiver) Failure of either Party to exercise or enforce any provision of or any of its rights under these Terms shall not be deemed a waiver of future enforcement of that or any other provision or right. ### [19.6 Notices.](#196-notices) [Section titled “19.6 Notices.”](#196-notices) Except as otherwise specified in these Terms, all notices related to these Terms will be in writing and will be effective upon (a) personal delivery, (b) the second business day after mailing, or (c), except for notices of termination or an indemnifiable claim (“Legal Notices”), which shall clearly be identifiable as Legal Notices, the day of sending by email. Billing-related notices to you will be addressed to the relevant billing contact designated by you. All other notices to you will be addressed to the relevant Services system administrator designated by you. *** Your Crowdin Team. # Translation Consistency > Hints regarding how the source words were previously translated Translation consistency is a feature designed to provide translators with informative hints regarding how the source words were previously translated. These hints show previous translations for individual words and the number indicating how many times each translation was used in the project. As the feature’s name states, its main task is to improve the consistency of translations within the project. As a result, you get higher-quality translations that will be used in your applications, websites, etc. ## [Overview](#overview) [Section titled “Overview”](#overview) Translation consistency is handled by an experimental machine learning technology. As soon as you start translating your project, machine learning algorithms engage, and the system shows previous translations for the source words and how often they were used in the project. The previous translation lists are formed based on the translations with the highest priority (approved, most voted, or last added ones) within the project. ## [Using Translation Consistency in Editor](#using-translation-consistency-in-editor) [Section titled “Using Translation Consistency in Editor”](#using-translation-consistency-in-editor) Hover over the source words underlined with the light dashed line to see the previous translations formed by the translation consistency feature. You can also search previous translations for specific source words using the *Search TM* tab.  ## [Supported Languages](#supported-languages) [Section titled “Supported Languages”](#supported-languages) Currently, translation consistency is available for the following source and target languages: **Source languages** * English * English, United States * English, United Kingdom **Target Languages** * Czech * Danish * Dutch * Finnish * French * German * Italian * Norwegian * Norwegian Bokmal * Polish * Portuguese * Romanian * Russian * Spanish * Swedish * Ukrainian New languages are added regularly. # Translation Memory > Learn how to manage Translation Memories in Crowdin A Translation Memory (TM) is a database that stores translation units, which are segments of source text paired with their corresponding translations in different languages. It improves and speeds up the translation process by providing suggestions for identical or similar strings in your projects. A project TM is created automatically for each Crowdin project. By default, each translation made within the project is automatically added to the project’s TM. This behavior can be customized in the [project settings](/project-settings/translation-memories/) to save only approved translations. ## [Creating TM](#creating-tm) [Section titled “Creating TM”](#creating-tm) In addition to the project TMs that are automatically created with each project, you can create separate TMs and populate them with content by uploading your existing TMs in TMX, XLSX, or CSV formats. These TMs can then be assigned to the relevant projects as needed. To create a TM, follow these steps: 1. Open your profile home page and select **Translation Memories** on the left sidebar. 2. Click **Create TM**.  3. In the appeared dialog, name your TM and select a default language that will be displayed first in the table of translation units. 4. *(Optional)* Assign the TM to the needed projects. You can skip this step and assign a TM later. 5. Click **Create**.  [Assigning TM ](/project-settings/translation-memories/#assigning-tm) [Prioritizing TM ](/project-settings/translation-memories/#prioritizing-tm) [Changing Default TM ](/project-settings/translation-memories/#changing-default-tm) ## [Managing Translation Units and Segments](#managing-translation-units-and-segments) [Section titled “Managing Translation Units and Segments”](#managing-translation-units-and-segments) You can create translation units from scratch, edit and delete existing translation units or segments of a particular TM or all available TMs. [Translation Memory Generator ](https://store.crowdin.com/tmg)Use this app to create a TM based on the translated Crowdin project. ### [Creating Translation Units](#creating-translation-units) [Section titled “Creating Translation Units”](#creating-translation-units) To create a translation unit, follow these steps: 1. Open your profile home page and select **Translation Memories** on the left sidebar. Alternatively, open your project and go to **Settings > Translation Memories**. 2. Select the needed TM and click **View Records**. 3. Click **Add Translation Unit**.  4. In the appeared dialog, select the language from the drop-down menu and type the translation of the segment. 5. Click **Add segment** to add more translations for the translation unit. 6. Click **Create**.  ### [Viewing and Filtering Translation Units and Segments](#viewing-and-filtering-translation-units-and-segments) [Section titled “Viewing and Filtering Translation Units and Segments”](#viewing-and-filtering-translation-units-and-segments) Once you open a translation memory, you can view and filter its translation units and segments using either the Translation Units or Segments pages. On the Translation Units page, you can view TM content grouped as translation units (one translation unit per row, each segment displayed in a separate language column).  On the Segments page, you can view TM content as individual segments (one segment per row) with the following details: * Segment – contains either source or target language text. * Language – specifies the language of the segment. * Usage count – specifies the number of times a segment has been used. * Created – specifies the date of the segment creation. * Last modified – specifies the date of the last modification of the segment. * Author – specifies the user who created the segment.  By default, all translation units and segments are displayed in the Translation Units and Segments pages. To filter the translation units or segments displayed, click and use the available filter options: * Created: All, Custom Range. * Modified: All, Custom Range. * Author: All, particular user. * Languages (Specific to the Segments page): All, particular language. * Usage (Specific to the Segments page): All, Used, Unused. To sort translation units or segments, click the column header you want to sort by: * Translation Units page – click a language column (e.g., English, French, etc.) to sort the translation units by that language’s text. * Segments page – click the Segment column to sort by segment text. Click once to sort in ascending order and click again to sort in descending order. ### [Editing Translation Units](#editing-translation-units) [Section titled “Editing Translation Units”](#editing-translation-units) You can edit both the source and translation parts of the existing translation unit. To edit a translation unit, follow these steps: 1. Open your profile home page and select **Translation Memories** on the left sidebar. Alternatively, open your project and go to **Settings > Translation Memories**. 2. Select the needed TM and click **View Records**. Alternatively, click **All Records** to view translation units of all available TMs in one list.  3. Open a translation unit with a double-click or click **Edit**. 4. In the appeared dialog, edit or delete the segments of the needed languages. For each segment, you can see additional details like the language, creation date, last modified date, and, if available, the name of the contributor who originally submitted the translation. 5. Click **Save**.  In addition to editing translation units via the **Translation Memories** page, you can also do it in the Editor. Read more about [Editing TM Suggestions in the Editor](/online-editor/#editing-tm-suggestions-in-the-editor). Another way to edit translation units in your TM is to download it (e.g., in TMX format), make the necessary changes locally on your device, and then reupload the modified TM back to Crowdin. Depending on what you modify in your TM, there could be different outcomes: * If you edit both the source and translation segments of a translation unit, then when you upload the TM to Crowdin, the locally modified translation unit will be treated as new upon re-upload, leaving the original translation unit unchanged. * If you only edit the translation segment of a translation unit, then when you upload the TM to Crowdin, the locally modified translation segment will be added as an alternative version segment to the existing translation unit, keeping the original translation intact but providing another option. If you want to have only the modified version of the translation units, follow these steps: 1. [Download](#downloading-tm-for-offline-management) the complete version of your TM to your device. 2. Make the necessary changes locally on your device. 3. Completely [clear the content of your TM](#deleting-translation-units-and-segments) in Crowdin. 4. [Upload](#downloading-and-uploading-tm) your locally modified TM to Crowdin. ### [Replacing in Segments](#replacing-in-segments) [Section titled “Replacing in Segments”](#replacing-in-segments) You can easily find and replace translations in segments within a selected TM using the *Find & Replace* feature. To replace current translations with the new ones, follow these steps: 1. Open your profile home page and select **Translation Memories** on the left sidebar. Alternatively, open your project and go to **Settings > Translation Memories**. 2. Select the needed TM and click **View Records**. 3. Click . 4. In the appeared dialog, select the language in which you want to search. *(Optional)* Use filters if necessary. 5. Enter the word, phrase, or sentence you want to substitute and the text to replace it with. *(Optional)* Use the *Match case* and *Exact match* options to refine the search results. 6. Click **Find** to preview the segments that will be replaced.  7. Select the segments you want to replace and click **Replace Selected** to finish. ### [Deleting Translation Units and Segments](#deleting-translation-units-and-segments) [Section titled “Deleting Translation Units and Segments”](#deleting-translation-units-and-segments) You can delete one, multiple, or all the translation units or segments at once. To delete all the translation units from TM, follow these steps: 1. On the Translation Units page, select the top checkbox above the translation unit list. 2. Confirm the selection of all translation units. 3. Click .  To delete all the segments from TM for only one particular language, follow these steps: 1. On the Segments page, click and select the needed language. 2. Select the top checkbox above the segment list. 3. Confirm the selection of all segments. 4. Click .  When dealing with the removal of translation units and translations, there could be three possible outcomes: * When deleting a translation unit from TM, the related translation won’t be deleted for a string in your Crowdin project. * When you cancel the translation activity for a string via the Activity tab, the translation for a string will be deleted, but the related translation unit will be preserved in TM. * When deleting a translation for a string in the Editor, both the translation and the related translation unit will be deleted. [TM Cleaner App ](https://store.crowdin.com/tm_cleaner_app)Use this app to clean your TM from duplicates and outdated translation units. ## [Downloading and Uploading TM](#downloading-and-uploading-tm) [Section titled “Downloading and Uploading TM”](#downloading-and-uploading-tm) To download or upload TMs, follow these steps: 1. Open your profile home page and select **Translation Memories** on the left sidebar. Alternatively, open your project and go to **Settings > Translation Memories**. 2. Click **View Records** on the needed TM. 3. Click and select **Download** or **Upload**.  The project owner and managers can download and upload TM in the following file formats: TMX, XLSX, or CSV. Limitations The maximum file size is 200 MB. If your file exceeds this limit, it is recommended to split it into several smaller files, and upload them one at a time. If you upload a TM in CSV or XLS/XLSX file formats, match columns with the corresponding languages in the configuration dialog.  ### [Automatic Column Identification for TM in CSV and XLSX File Formats](#automatic-column-identification-for-tm-in-csv-and-xlsx-file-formats) [Section titled “Automatic Column Identification for TM in CSV and XLSX File Formats”](#automatic-column-identification-for-tm-in-csv-and-xlsx-file-formats) Once you upload your TM file in CSV or XLSX formats, the system automatically detects the file scheme based on the column names specified in the first row. The identification is performed in a case-insensitive manner. Columns that weren’t detected automatically will be left as **Not chosen** for manual configuration. Automatic column identification is especially helpful when you upload TM spreadsheets that contain many languages. To get the most out of the automatic column detection, we recommend that you name the language columns in your CSV or XLSX TM files using the values displayed below: * [Language name](/developer/language-codes/) (e.g., Ukrainian) * [Crowdin language code](/developer/language-codes/) (e.g., uk) * Locale (e.g., uk-UA) * Locale with underscore (e.g., uk\_UA) * Language code ISO 639-1 (e.g., uk) * Language code ISO 639-2/T (e.g., ukr) To redetect the TM file scheme, click **Detect Configuration**. ### [Downloading TM for Offline Management](#downloading-tm-for-offline-management) [Section titled “Downloading TM for Offline Management”](#downloading-tm-for-offline-management) When downloading a TM from Crowdin in TMX format, you can get some additional metadata that might be useful for different usage scenarios with offline tools. Additional TM attributes provided by translation memory downloaded in TMX format: * `x-crowdin-metadata` – String identifier hash. * `creationid` – Translation author’s full name and username in Crowdin. * `creationdate` – Translation creation date. * `changeid` – Full name and username of the person who updated a translation. * `changedate` – Translation update date. * `usagecount` – Translation suggestion’s number of usages in Crowdin. * `lastusagedate` – The last date a translation suggestion was used in Crowdin. Often translation vendors that work in Crowdin export TMs from projects to manage them for their clients in various desktop applications (e.g., for cleaning TMs from irrelevant translations and further reimport back to Crowdin). The TM attributes listed above allow better navigation and filtering of TM segments based on different criteria. Also, you might use cleaned and refreshed TMs to train MT engines only on product-specific data to ensure a higher quality of translations as a result. ## [Sharing TMs](#sharing-tms) [Section titled “Sharing TMs”](#sharing-tms) Using the shared TMs, you can pre-translate any of the projects you own. Also, TM suggestions from all TMs will appear in the Editor. To share TMs between all of the projects you own, follow these steps: 1. Open your profile home page and select **Translation Memories** on the left sidebar. 2. Select **Share TMs**.  ## [Applying Translation Memory via Pre-translation](#applying-translation-memory-via-pre-translation) [Section titled “Applying Translation Memory via Pre-translation”](#applying-translation-memory-via-pre-translation) Pre-translation via TM allows you to leverage a minimum of 100% and Perfect matches. [TM Match Calculation ](#tm-match-calculation) [Pre-translation ](/pre-translation/) ### [Prioritizing TM Suggestions during the Pre-translation via TM](#prioritizing-tm-suggestions-during-the-pre-translation-via-tm) [Section titled “Prioritizing TM Suggestions during the Pre-translation via TM”](#prioritizing-tm-suggestions-during-the-pre-translation-via-tm) During the pre-translation via TM, the system considers multiple parameters to select the most relevant TM suggestion. If the system finds only one suitable TM suggestion for a string, it will be applied during the pre-translation via TM. If the system finds two or more TM suggestions for one string, they will be sorted based on multiple parameters and applies the most suitable one. The following parameters are listed in the order the system uses them to decide which TM suggestion works better. If the decision can’t be made using the first parameter (i.e., two TM suggestions with 100% match), the system will use the next parameter until the decision is made. 1. Relevance – also known as TM match. Read more about [TM Match Calculation](#tm-match-calculation). 2. Auto-Substitution usage – verifying whether the TM suggestion was improved by the auto-substitution. Read more about [Auto-substitution](#tm-auto-substitution). 3. Assigned TM Priority – the priority of the TM a TM suggestion is stored in. Read more about [Prioritizing TM](/project-settings/translation-memories/#prioritizing-tm). 4. Primary or dialect language – the primary or dialect language usage in TM suggestion’s source text (e.g., a TM suggestion from English will have a higher priority than English, Canada). 5. TM suggestion creation date – the date a TM suggestion was created (a TM suggestion with a more recent creation date will have a higher priority). To better understand how TM suggestions are prioritized during the pre-translation via TM, let’s go through a few hypothetical scenarios. Let’s imagine you have an untranslated string in your project with the following source text `Welcome!`. Once you run the pre-translation via TM, the system starts to search for TM suggestions in your TMs. * The system finds two TM suggestions with the source text `Welcome` and `Welcome!`. The translation from the `Welcome!` TM suggestion will be used since it has a higher TM match. * The system finds two TM suggestions: `Welcome!` and `Welcome!`. Both have the same source text, so the system checks whether the auto-substitution was used to improve these TM suggestions and picks the one that wasn’t improved by the auto-substitution. * The system finds two TM suggestions: `Welcome!` and `Welcome!`. Both have the same source text, and both weren’t improved by the auto-substitution. Then the system checks the priority of the TMs these TM suggestions are stored in and picks the one stored in the TM with higher priority. * The system finds two TM suggestions: `Welcome!` and `Welcome!`. Both have the same source text, both weren’t improved by the auto-substitution, and both are stored in the TMs with the same priority. Then the system checks the source languages of the TM suggestions and picks the one that uses the primary language. * The system finds two TM suggestions: `Welcome!` and `Welcome!`. Both have the same source text, both weren’t improved by the auto-substitution, both are stored in the TMs with the same priority, and both use primary source languages. Then the system checks the TM suggestion creation date and picks the one with the latest date. In rarer cases, there could be a situation when two or more TM suggestions are identical based on all the parameters listed above. In this case, the system picks the first one among identical. To improve accuracy, Crowdin minimizes the influence of HTML tags when determining TM matches. Instead of matching based on the original strings, the matching is conducted on strings where HTML tags are replaced with placeholders, similar to the behavior in the Editor. For example, a string `Hello world!` will match 100% with a string `Hello world!`. ## [TM Suggestions for Dialect Languages in the Editor](#tm-suggestions-for-dialect-languages-in-the-editor) [Section titled “TM Suggestions for Dialect Languages in the Editor”](#tm-suggestions-for-dialect-languages-in-the-editor) When the [**TM Suggestions for Dialects**](/project-settings/translation-memories/) option is enabled, Crowdin will show TM suggestions from the primary language for dialect languages in the Editor. For instance, if you have Spanish and Spanish, Argentina as your target languages, and the option is enabled, the Editor will display TM suggestions from Spanish for Spanish, Argentina (indicated as “English -> Spanish” in the TM and MT Suggestions section). However, this behavior does not apply to the **Search TM** functionality. If you search for TM suggestions from the primary language in the Search TM tab while working with a dialect language, you will not find any results. ## [TM Match Calculation](#tm-match-calculation) [Section titled “TM Match Calculation”](#tm-match-calculation) Crowdin calculates the TM match by comparing the source string to be translated and TM’s existing segments. There are three main types of TM matches: * Perfect Match - TM segment’s text and context completely match the source string * 100% Match - TM segment’s text matches the source string, but the context is different * Fuzzy Match (99% and less) - TM segment’s text is different to a certain extent compared to the source string If the calculations for Perfect and 100% TM match is relatively straightforward, the fuzzy matches’ calculation may not be so obvious. There are multiple different factors that affect the calculation of fuzzy matches, for example: * Word order * Punctuation * Formatting tags * Matches that are longer than the source string  ## [TM Auto-Substitution](#tm-auto-substitution) [Section titled “TM Auto-Substitution”](#tm-auto-substitution) Auto-Substitution is aimed to increase the benefit of using the translation memory (TM) by suggesting translations with a higher similarity match. The feature substitutes the non-translatable elements (such as tags, HTML entities, placeholders, numbers, and more) in translations suggested by TM by the ones used in the source strings. To enable the Auto-substitution feature, open your project and go to **Settings > Translation Memories**. ### [Non-translatable Elements that can be Auto-substituted](#non-translatable-elements-that-can-be-auto-substituted) [Section titled “Non-translatable Elements that can be Auto-substituted”](#non-translatable-elements-that-can-be-auto-substituted) Auto-substitution feature can substitute the following non-translatable elements: | Non-translatable elements | Source string example | TM suggestion (German) | Improved TM suggestion | | ------------------------------------------------- | ------------------------------------------------- | -------------------------------------------------- | --------------------------------------------------- | | Tags | `Help` | `Hilfe` | `Hilfe` | | HTML entities | `Currency €` | `Währung ¥` | `Währung €` | | Line breaks | `Profile` | `Profil
` | `Profil` | | Escape sequences (\r\n, \r, \n, \t, unicode, hex) | `Translation \x42` | `Übersetzung \u4242` | `Übersetzung \x42` | | Non-escaped equivalents of \r\n, \r, \n, \t | `Translated by \n TM` | `Übersetzt vom Übersetzungsspeicher` | `Übersetzt vom \n Übersetzungsspeicher` | | Placeholders | `Example %s` | `Beispiel %1$s` | `Beispiel %s` | | Numbers | `Attempt 2` | `Versuch 5` | `Versuch 2` | | Letter case | `Log in` | `einloggen` | `Einloggen` | | Special characters | `Help?` | `Hilfe!` | `Hilfe?` | | URLs | `More Information: https://crowdin.com/features` | `Weitere Infos: https://crowdin.com/` | `Weitere Infos: https://crowdin.com/features` | | ICU syntax | `Get {discountPercent, number, percent} discount` | `Erhalte {discountValue, number, currency} Rabatt` | `Erhalte {discountPercent, number, percent} Rabatt` | ### [Auto-substitution for Pre-translation](#auto-substitution-for-pre-translation) [Section titled “Auto-substitution for Pre-translation”](#auto-substitution-for-pre-translation) Once you enable the TM auto-substitution, you can leverage improved TM suggestions during [pre-translation](#applying-translation-memory-via-pre-translation). Be sure to set a minimum match ratio to 100%. This will result in including 100% TM matches along with the ones improved to 100% by TM auto-substitution. ### [Auto-substitution for TM Suggestions](#auto-substitution-for-tm-suggestions) [Section titled “Auto-substitution for TM Suggestions”](#auto-substitution-for-tm-suggestions) With the Auto-substitution feature, translators can see the improved TM suggestions in the Editor. The percentage below the improved suggestion shows the match percentage of the original TM suggestion and the improved one.  ### [Penalized TM Suggestions](#penalized-tm-suggestions) [Section titled “Penalized TM Suggestions”](#penalized-tm-suggestions) In some cases, you may want to apply penalties to TM suggestions to reduce their match percentage based on specific conditions. For example, you can set up a penalty for TM suggestions improved by the auto-substitution feature to prioritize exact matches over improved ones. The percentage below the improved and penalized suggestion shows the match percentage of the improved TM suggestion and the penalized one. Hover the cursor over the percentage to see more details.  Read more about [TM Suggestion Penalties](/project-settings/translation-memories/#penalties). ### [Cost Reports](#cost-reports) [Section titled “Cost Reports”](#cost-reports) Once the feature is enabled, it will affect how the [Costs Estimate](/project-reports/#cost-estimate) and [Translation Cost](/project-reports/#translation-cost) reports are calculated. **Costs Estimate** report would count TM suggestions that can potentially be improved by the auto-substitution feature based on the highest similarity match to which those strings can be improved. For example, a match that can be improved from a 75% match to a 100% match would be considered a 100% match. **Translation Cost** report would count TM suggestions improved by the auto-substitution feature as regular TM suggestions. For example, a match improved from a 75% match to a 100% match would be considered a 100% match. # Translation Strategies > Approaches for translating and proofreading your content effectively Once you’ve created your project and uploaded source files for localization, it’s time to decide who will translate and proofread your content. This article covers all the possible approaches you can mix and match to meet your personal needs and preferences. ## [Invite Your Team of Translators](#invite-your-team-of-translators) [Section titled “Invite Your Team of Translators”](#invite-your-team-of-translators) Invite as many translators and proofreaders to your project as needed. You can also give the language coordinator or manager access to trusted project members to manage the translation process for you (invite translators, meet deadlines, and maintain quality). Send email invitations or share invitation links with access to your localization project in Crowdin. You can invite: * In-house translators * Freelancers * Translation agencies you already work with Manage the project members in the **Members** tab. For example, you can invite translators, proofreaders, and language coordinators, granting them access to all or only specific target languages. Read more about [Inviting People](/inviting-people/). ## [Order Professional Translations](#order-professional-translations) [Section titled “Order Professional Translations”](#order-professional-translations) Crowdin Vendors Store includes professional translation agencies you can hire to translate and proofread your project files. See the list of all available vendors in **Store > Vendors**. Some of the transition agencies are integrated with Crowdin via API. When you decide to work with them, Crowdin forwards your untranslated data directly to the agency, and once completed, the translations are uploaded back to the project. Read more about [Ordering Professional Translations](/ordering-professional-translations/). [Crowdin Language Services ](/crowdin-language-services/)Crowdin Language Services is a solution that allows you to order professional translations and proofreading services in a few clicks. [BLEND Integration ](/blend-integration/)Integrate your Crowdin projects with the BLEND agency and allow BLEND translators to work with translation files in Crowdin Editor. Professional translation is a paid service where the approximate cost for your project is calculated or negotiated during the purchase. ## [Configure Crowdin AI](#configure-crowdin-ai) [Section titled “Configure Crowdin AI”](#configure-crowdin-ai) Enhance your translation process with Crowdin AI, which leverages advanced AI-powered translations from leading providers such as OpenAI, Google Gemini, Microsoft Azure OpenAI, and more. Crowdin AI offers two main prompt types for use in different scenarios: * **Pre-translate**: Generate initial AI translations that can be later reviewed by human proofreaders. * **AI in Editor**: Provide AI-powered suggestions directly within the Editor to help translators with translation and proofreading tasks. By considering additional context at various levels, Crowdin AI ensures contextually accurate translations, improving overall efficiency and quality. Read more about [Crowdin AI](/crowdin-ai/). ## [Configure Machine Translation Engines](#configure-machine-translation-engines) [Section titled “Configure Machine Translation Engines”](#configure-machine-translation-engines) Crowdin integrates with the most popular Machine Translation (MT) engines such as Microsoft Translator, Google Translate, Google AutoML Translation, DeepL Translator, and Amazon Translate. Configure these engines to use manual or automated pre-translation via MT. A human translator can also review those translations and do post-editing if needed. Otherwise, you can configure an MT of your choice so the machine translations will be shown in the Editor as suggestions to assist your translators. Read more about [Pre-Translation](/pre-translation/). ## [Engage Your Community](#engage-your-community) [Section titled “Engage Your Community”](#engage-your-community) If you have a popular product and an active community eager to help you with translations, feel free to start crowdsourcing. It’s an excellent practice to cooperate with members on a volunteer basis and reward their efforts, providing them with some goods, discounts, or any other way that works for both parties. When working with community translators, a good workflow looks like the following: community translators translate the project, and once the translations are finished, you can order professional proofreading from a translation agency to ensure high translation quality. # Uploading Source Files > Learn how to upload source files to your project for translation Once you’ve [created a project](/creating-project/), the next step would be preparing source files for upload. Crowdin supports a wide range of [file formats](/supported-formats/), including Android XML, iOS Strings, JSON, etc. When you have your files prepared, you can add them to your Crowdin project for translation. Crowdin offers a few options for adding content to a project: * Manually via the web interface (UI). * Integrate your Crowdin project with the tools you already use. Explore available integrations on the [Crowdin Store](https://store.crowdin.com/). * Use the [API](/developer/api/) or [Developer Tool](/developer/dev-tools/) of your choice. Usually, this task is accomplished by developers. You can [invite your colleague developer](/inviting-people/) to assist you with this step. You can also use Crowdin sample files to test the translation workflows before starting your project with the actual source files. ## [Uploading Files](#uploading-files) [Section titled “Uploading Files”](#uploading-files) To upload files via the web interface, follow these steps: * File-based project 1. Open your project and go to **Sources > Files**. 2. Drag and drop files from your machine anywhere within the **Files** tab — to the root of the project or directly into an existing folder. You can upload ZIP archives if you want to add a structured set of folders and files. 3. *(Optional)* Click **Upload Files** or **Add File** to add files, **Use Samples** to test translation workflows, **Set Up Integration** to synchronize content automatically, or **Invite Developer** if content uploads will be handled by your developer teammate. You can also click the drop-down arrow next to the **Add File** button to access additional options, such as **Create String Vault** (adds an empty CSV file) or another **Set Up Integration** shortcut.  * String-based project 1. Open your project and go to the **Upload** tab. 2. Select the target branch to which you’re uploading source files. By default, the `main` branch is selected. Create new branches if needed. 3. Drag and drop files from your machine, or click **Select Files**. You can also upload ZIP archives if you want a set of files to be added. 4. Crowdin automatically tries to detect whether you’re uploading source content or translations. Verify the detection is correct and adjust the language settings if needed (e.g., English (source) should be selected for source files if the project’s source language is English). 5. *(Optional)* In the **Source files** section, to the right of the uploaded file list, configure [advanced source file import settings](#advanced-import-settings). 6. Click **Upload** to finish uploading the source content.  Read more about [project types](/creating-project/#project-types). Limitations The maximum file size is 100 MB. If your file exceeds this limit, it is recommended to split it into several smaller files, and upload them one at a time. ### [XML, CSV, and XLSX Files](#xml-csv-and-xlsx-files) [Section titled “XML, CSV, and XLSX Files”](#xml-csv-and-xlsx-files) Some file formats, such as XML, CSV, XLSX, and others, might require additional configuration. * [CSV/XLSX File Configuration](/csv-xlsx-configuration/) * [XML File Configuration](/xml-configuration/) * [Parser Configuration](/project-settings/parser-configuration/) Limitations The XLSX/XLS file size is limited to 2 000 000 cells. ### [HTML Files with Relative URLs](#html-files-with-relative-urls) [Section titled “HTML Files with Relative URLs”](#html-files-with-relative-urls) To display images and styles in the HTML file used outside of the website, where it belongs, add the `` tag to specify the base URL/target for all relative URLs in a document. ```html

Please note that we only specified a relative address for the image. Since we specified a base URL in the head section, the browser will look for the image at "https://www.w3schools.com/images/stickman.gif".

``` Once you add the `` tag, translators will see images in the HTML files when translating in the Editor.  Limitations HTML files are not supported in [string-based](/creating-project/#string-based-project) projects. ## [Advanced Import Settings](#advanced-import-settings) [Section titled “Advanced Import Settings”](#advanced-import-settings) You can configure the desired system behavior for uploaded source files in string-based projects using the available options: * **Update strings** – update strings with the same identifiers. By default, this option is selected. * **Cleanup mode** – remove previously uploaded strings not present in the newly uploaded file. By default, this option is cleared. * **Add labels** – tag uploaded strings with the selected labels. When uploading source files, Crowdin also adds system labels that include the source file name. ## [See Also](#see-also) [Section titled “See Also”](#see-also) [Uploading Existing Translations ](/uploading-translations/)Learn how to upload existing translations to your project. [File Management ](/file-management/)Manage and configure source files in your project. [Versions Management ](/version-management/)Learn how to manage different versions of your project. [Import Settings ](/project-settings/import/)Configure how placeholders, duplicates, and word counts are handled. # Uploading Existing Translations > Learn how to upload existing translations to your project If you have existing translations ready to integrate into your Crowdin project, you can upload them directly. For [file-based](/creating-project/#file-based-project) projects, this can be done through the **Translations** tab or directly from a specific file in the Editor. For [string-based](/creating-project/#string-based-project) projects, use the **Upload** tab or access the target language in the Editor to upload XLIFF translations. The best practice is to upload translated files with the key-value structure. Limitations The maximum file size is 100 MB. If your file exceeds this limit, it is recommended to split it into several smaller files, and upload them one at a time. ## [Uploading Translations via Project page](#uploading-translations-via-project-page) [Section titled “Uploading Translations via Project page”](#uploading-translations-via-project-page) To upload translations to your project, follow these steps: * File-based project 1. Open your project and go to the **Translations** tab. 2. Click **Upload existing translations** to expand the respective section.  3. Drag and drop files from your machine, or click **Select Files**. You can upload ZIP archives to add multiple folders and files. 4. Crowdin automatically matches uploaded translations with appropriate source files and languages. Check it manually to make sure everything is matched correctly.  5. *(Optional)* Click the button under the uploaded file list to view the advanced import settings. 6. Click **Import** to apply the translations to the source files. * String-based project 1. Open your project and go to the **Upload** tab. 2. Drag and drop files from your machine, or click **Select Files**. You can also upload ZIP archives if you want a set of files to be added. 3. Crowdin automatically tries to detect the target language to which you’re uploading translations. Check it manually to make sure target languages are matched correctly towards translation files. 4. *(Optional)* In the **Translations** section, to the right of the uploaded file list, configure advanced translation import settings. 5. Click **Upload** to apply translations to the source strings.  ## [Uploading Translations via Language Page](#uploading-translations-via-language-page) [Section titled “Uploading Translations via Language Page”](#uploading-translations-via-language-page) * File-based project 1. Select the language on the project page. 2. Click next to the file translations should be uploaded to. 3. Select **Upload Translations**.  * String-based project Limitations Uploading Translations via Language Page is not supported in [string-based](/creating-project/#string-based-project) projects. ## [Uploading Translations via Editor](#uploading-translations-via-editor) [Section titled “Uploading Translations via Editor”](#uploading-translations-via-editor) To upload a file with translations via [Online Editor](/online-editor/), follow these steps: 1. Click on the Main menu in the upper-left corner. 2. Go to **File > Upload Translations**.  If you are in the [Multilingual (Grid)](/online-editor/#multilingual-mode-grid) mode of the Editor, click the drop-down arrow next to a target language’s column and select **Upload Translations**.  ## [Uploading XLIFF Translations](#uploading-xliff-translations) [Section titled “Uploading XLIFF Translations”](#uploading-xliff-translations) You can do the offline translation for all file formats and strings by downloading existing content in the XLIFF format; once the offline translations are finished, use **Upload XLIFF Translations**. To upload XLIFF translations for a specific target language, follow these steps: 1. Select the language on the project page. 2. Click and select **Upload XLIFF Translations**.  For string-based projects, you can upload XLIFF translations using the [Online Editor](#uploading-translations-via-editor). ## [Key-value Formats](#key-value-formats) [Section titled “Key-value Formats”](#key-value-formats) You can easily upload translations for source files with a key-value structure. This includes the following file formats: Android XML, macOS/iOS Strings, Stringsdict, JSON, Chrome JSON, GO JSON, i18next JSON, FBT JSON, XLIFF, XLIFF 2.0, Java Properties, Play Properties, Java Properties XML, RESX, RESW, RES JSON, YAML, INI, Joomla INI, JS, FJS, PO, TS, QT TS, TOML, Coffee, XAML, SRT, VTT, VTT2, SBV, SVG, DTD, CSV, RC, WXL, Haml, XLSX, PLIST, PHP, ARB, VDF. The system maps uploaded translations according to the string keys. ## [Text and HTML-based Formats](#text-and-html-based-formats) [Section titled “Text and HTML-based Formats”](#text-and-html-based-formats) For files that do not have a defined structure, translation upload is handled by an experimental machine learning technology. This includes the following file formats: HTML, Front Matter HTML, Markdown, Front Matter Markdown, TXT, Generic XML, Web XML, DOCX, HAML, IDML, DITA, Wiki, and ADOC. To achieve the best results, we recommend uploading translation files with the same or as close as possible file structure as in source files. Currently, this feature is available for the following languages (not depending on the language pair combination): Arabic, Chinese Simplified, Chinese Traditional, English, French, German, Italian, Japanese, Korean, Dutch, Polish, Portuguese, Portuguese Brazilian, Spanish, Thai, Turkish, and Russian. [Try Document Aligner application ](https://store.crowdin.com/aligner)Translation alignment, facilitated by the app, allows you to upload existing translations of non-key-value documents to Crowdin or create an editable XLSX Translation Memory. ## [Upload Summary](#upload-summary) [Section titled “Upload Summary”](#upload-summary) After uploading a translation file, a summary appears with the results of the import. Depending on the file content and your project settings, you may see one of the following outcomes: * **All translations imported** – All translations were uploaded without issues. If the **Approve added translations** option was enabled, the translations were also marked as approved. * **Partially imported** – Some translations were imported, while others were skipped. The summary lists the specific reasons for skipped translations, such as being identical to the source text, hidden strings, or failed QA checks. If translations were skipped due to QA issues, the summary provides a detailed breakdown of each QA issue type (e.g., *Duplicate translation*, *Numbers mismatch*, etc.) based on the QA checks configured in [**Settings > QA Checks**](/project-settings/qa-checks/#qa-check-parameters). * **All translations skipped** – None of the translations were imported. The summary provides a detailed list of reasons. For failed QA checks, you’ll see a breakdown of the specific issues that caused the translations to be skipped. * **No translations imported** – No translations were imported or skipped with a specific reason. This typically happens when the **Approve added translations** option is enabled, QA warnings are ignored, and the file contains only translations that are already present in the project. Since duplicates are not uploaded, the summary shows *No translations imported*. To update progress after the upload, click **Reload** in the summary dialog. # User Tasks > Learn how to view, filter, and manage tasks assigned to you The Tasks is one of the essential tools for managing the localization process in Crowdin. As a contributor (translator or proofreader), you can view and manage your assigned tasks, track progress, access content assigned within the task, and communicate with project managers or other contributors. ## [Task Notifications](#task-notifications) [Section titled “Task Notifications”](#task-notifications) To stay informed about new task notifications and the latest task updates, enable the Task event type in your account’s Notifications settings. You’ll receive notifications about any updates or changes to your tasks. These might include: * A task being assigned to you. * A task deleted. * Changes to task details like due dates, content, or status. * Mentions and comments related to the task. There are four channels through which you can receive notifications. You can enable the ones that work best for you and disable unnecessary ones. Read more about [Notifications](/account-settings/#notifications). ## [Managing Assigned Tasks](#managing-assigned-tasks) [Section titled “Managing Assigned Tasks”](#managing-assigned-tasks) You can view, filter, and manage tasks assigned to you, allowing for efficient tracking and completion of your work in Crowdin.  ### [Viewing and Filtering Assigned Tasks](#viewing-and-filtering-assigned-tasks) [Section titled “Viewing and Filtering Assigned Tasks”](#viewing-and-filtering-assigned-tasks) To view and filter all tasks assigned to you, open your profile and select **To Do** on the left sidebar You can view your tasks in the following two sections: * *All* – all the tasks assigned to you. * *Archived* – the tasks you archived. On the **To Do** page, you can view tasks with the following details: * ID – the unique identifier for the task. * Name – the title of the task. * Task type label – indicates whether the task is for translation or proofreading. * Status – the current status of the task. * Project name – indicates the project in which the task is created. * Target language – the target language involved in the task. * Words left – the number of words left to be translated or proofread. * Due date – the deadline for task completion, if specified by the project manager. By default, all tasks are displayed on the **To Do** page. To filter the tasks displayed, click and use the available filter options: * Projects: All, specific projects. * Status: All statuses, To Do, In Progress, Done, Closed, Pending * Languages: All languages, specific language. * Due date: All, Overdue now, Custom range. * Type: All types, Translate by own translators, Proofread by own proofreaders, Translate by vendor, Proofread by vendor. To search for a particular task, type its name in the **Search tasks** field. To sort tasks, click **Sort by** and select one of the available options: * ID * Created at * Resolved at * Due date ### [Viewing Task Details](#viewing-task-details) [Section titled “Viewing Task Details”](#viewing-task-details) Before starting your work on a task, you can review task details to understand its scope. To view task details, follow these steps: 1. Go to your **Workspace** and select **Tasks** on the left sidebar. 2. Click on the task you want to view. The task will open directly within the project it’s associated with. Alternatively, you can access your assigned tasks by navigating to the specific project’s **Tasks** tab and selecting yourself using the **Assignee** filter parameter. Click on any task in your list to view its details. In addition to the details available when [viewing all of your assigned tasks](#viewing-and-filtering-assigned-tasks), you will also see these details: * Created by – the user who created the task. * Created and modified dates – when the task was created and modified. * Started and resolved dates – timestamps indicating when you started and completed the task. * Files – files associated with the task. * Members – details like the number of words assigned to and remaining for each member. You can also open the task in the Editor by clicking **Translate** or **Proofread**, depending on the task type. If you prefer to work offline, click in the upper-right corner and select **Export in XLIFF**. When you are finished translating, use **Upload XLIFF translations** to upload your translations. ### [Starting and Working on Your Tasks](#starting-and-working-on-your-tasks) [Section titled “Starting and Working on Your Tasks”](#starting-and-working-on-your-tasks) Once you’re ready to start working on a task: 1. Click on the task to open it. 2. Review the strings or files assigned to you. 3. Click **Translate** or **Proofread** to start translating or proofreading as needed. As you work on the task, change its status from **To Do** to **In Progress**. Once your work is complete, update the status to **Done**. [Working on Tasks in the Editor ](/online-editor/#tasks-in-the-editor)Learn how to efficiently handle your translation and proofreading tasks in the Editor. [Changing Tast Status ](/tasks/#changing-task-status)Learn how to update task statuses to keep track of your progress. ## [Discussions and Comments](#discussions-and-comments) [Section titled “Discussions and Comments”](#discussions-and-comments) If you encounter issues or need assistance with your assigned task, leave a comment in the task for project managers or other contributors to see and respond. ## [Splitting Tasks](#splitting-tasks) [Section titled “Splitting Tasks”](#splitting-tasks) If a large task needs to be divided among multiple contributors, your project manager may split the content. You’ll receive only a portion of the task to work on. Focus on completing your assigned section and mark it as done when finished. ## [Sequential Tasks](#sequential-tasks) [Section titled “Sequential Tasks”](#sequential-tasks) In some cases, tasks may be part of a sequence where one needs to be completed before the next can begin. For example: * You may complete a translation task, after which a proofreading task becomes available. * If you’re assigned a proofreading task linked to a translation task, it will remain pending until the translation is finished. Sequential tasks help streamline the process, ensuring that each step is completed in the correct order. Read more about [Sequential Tasks](/tasks/#sequential-tasks). ## [Q\&A](#qa) [Section titled “Q\&A”](#qa) # Using the Crowdin Logo > The Crowdin logo is one of the essential parts of Crowdin’s identity and recognizability. To ensure that our brand is communicated effectively and consistently, we’ve prepared some simple rules for those cases when you’ll be using the Crowdin logo. ## [Crowdin Logo](#crowdin-logo) [Section titled “Crowdin Logo”](#crowdin-logo) We encourage you to check out the following guidelines that provide clear instructions and standards for using our logo, color palette, and other design elements.  #### Logo The full version of the Crowdin logo is for use on the web and in printed materials. DOWNLOAD **Dark:** [SVG](/assets/logos/core-logo/svg/crowdin-core-logo-cDark.svg), [EPS](/assets/logos/core-logo/eps/crowdin-core-logo-cDark.eps), [PNG](/assets/logos/core-logo/png/crowdin-core-logo-cDark.png) **White:** [SVG](/assets/logos/core-logo/svg/crowdin-core-logo-cWhite.svg), [EPS](/assets/logos/core-logo/eps/crowdin-core-logo-cWhite.eps), [PNG](/assets/logos/core-logo/png/crowdin-core-logo-cWhite.png)  #### Stacked Logo This version is used for optimizing vertical space. DOWNLOAD **Dark:** [SVG](/assets/logos/stacked-logo/svg/crowdin-stacked-logo-cDark.svg), [EPS](/assets/logos/stacked-logo/eps/crowdin-stacked-logo-cDark.eps), [PNG](/assets/logos/stacked-logo/png/crowdin-stacked-logo-cDark.png) **White:** [SVG](/assets/logos/stacked-logo/svg/crowdin-stacked-logo-cWhite.svg), [EPS](/assets/logos/stacked-logo/eps/crowdin-stacked-logo-cWhite.eps), [PNG](/assets/logos/stacked-logo/png/crowdin-stacked-logo-cWhite.png)  #### Mark Use the logo mark only where space constraints don’t allow the horizontal full version logo. DOWNLOAD **Dark:** [SVG](/assets/logos/symbol/svg/crowdin-symbol-cDark.svg), [EPS](/assets/logos/symbol/eps/crowdin-symbol-cDark.eps), [PNG](/assets/logos/symbol/png/crowdin-symbol-cDark.png) **White:** [SVG](/assets/logos/symbol/svg/crowdin-symbol-cWhite.svg), [EPS](/assets/logos/symbol/eps/crowdin-symbol-cWhite.eps), [PNG](/assets/logos/symbol/png/crowdin-symbol-cWhite.png)  #### Badge logo Suitable for all types of background DOWNLOAD [SVG](/assets/logos/plate/svg/crowdin-logo-with-plate.svg), [PNG](/assets/logos/plate/png/crowdin-logo-with-plate.png)  #### Small-scale Logo Use when the logo mark should be between 16 to 48 pixels in width or height. DOWNLOAD **Dark:** [SVG](/assets/logos/small-scale-logo/svg/smallscale-logo-cDark.svg), [PNG](/assets/logos/small-scale-logo/png/smallscale-logo-cDark.png) **White:** [SVG](/assets/logos/small-scale-logo/svg/smallscale-logo-cWhite.svg), [PNG](/assets/logos/small-scale-logo/png/smallscale-logo-cWhite.png) ## [Logo Spacing](#logo-spacing) [Section titled “Logo Spacing”](#logo-spacing) Preserve the correct logo spacing to maintain visual balance and keep the logo proportional.  * Allow correct white space * Keep the logo sharp by choosing the proper resolution * Use light neutral backgrounds * Keep the logo easily visible - Don’t alter the logo in any way - Don’t add drop shadows ## [Using the Logo in Various Shapes](#using-the-logo-in-various-shapes) [Section titled “Using the Logo in Various Shapes”](#using-the-logo-in-various-shapes) Below are examples of how to use the Crowdin logo when it is inscribed in different shapes, such as circles or squares. The alignment of the logo is achieved visually, considering the asymmetrical shape of the mark.  #### Logo in a Round Shape To place the logo in a round shape, use visual alignment by placing the logo approximately 5-8% to the right. Ensure that the logo is scaled proportionally, making it 20% smaller than the background area.  #### Logo in a Square Shape When placing the logo in a square shape, use visual alignment by placing the logo approximately 5-8% to the right and make it 25-30% smaller than the background area. ## [Logo Colors](#logo-colors) [Section titled “Logo Colors”](#logo-colors) Color examples cDark Hex: 263238 RGB: 38 50 56 Pantone: 433 CP cWhite Hex: ffffff RGB: 255 255 255 Pantone: P 179-1 C ## [Correct Logo Applications](#correct-logo-applications) [Section titled “Correct Logo Applications”](#correct-logo-applications) Examples of the correct use of the logo on plain surfaces and photos.    ## [Incorrect Logo Applications](#incorrect-logo-applications) [Section titled “Incorrect Logo Applications”](#incorrect-logo-applications) Examples of the incorrect use of the logo, not maintaining proportions, using the wrong logo color, etc.  Avoid Using the Old Crowdin Logo  Avoid Stretching  Avoid Low Contrast  Using on Busy Background ## [Badge](#badge) [Section titled “Badge”](#badge)  Use the badge when you want to show our partnership or let others know that you use Crowdin to localize your own project.     DOWNLOAD [.zip (all badges)](/assets/badges/localization-at-crowdin–badges.zip)  ### Brand Guidelines Explore our guidelines for properly using and applying our brand’s visual elements. [ Download Brandbook](/crowdin_brand_guidlines_4q_2024.pdf) # Version Management > Learn how to manage different versions of your project Maintain an agile localization process and prevent translation delays for added texts or new product features. Integrate your project branches with Crowdin and allow translators to access all new texts immediately. When several people work on product development, branches help manage different content versions. If you have a continuous project, you can add project branches to Crowdin and allow translators to translate the texts in parallel with development to prevent deployment delays. Branches in Crowdin look like regular folders marked with a specific icon and have special behavior for duplicate strings. Example of branch structure in the version control system (VCS) and Crowdin:  ## [Managing Branches](#managing-branches) [Section titled “Managing Branches”](#managing-branches) You can create, clone, merge, rename, prioritize, or delete branches in Crowdin to streamline localization alongside development. Use the available UI options, API, or CLI depending on your workflow and project type. ### [Creating Branches](#creating-branches) [Section titled “Creating Branches”](#creating-branches) You can create branches manually using the web interface (UI), automatically by connecting your project to a version control system, or by using CLI or API. The method you choose may depend on your project type or integration preferences. #### [Creating Branches via VCS Integration](#creating-branches-via-vcs-integration) [Section titled “Creating Branches via VCS Integration”](#creating-branches-via-vcs-integration) Integrate Crowdin projects with [GitLab](/gitlab-integration/), [GitHub](/github-integration/), [Bitbucket](/bitbucket-integration/), or [Azure Repos](/azure-repos-integration/). When you select branches for localization in your VCS, they’ll be created automatically in Crowdin. #### [Creating Branches via Web Interface](#creating-branches-via-web-interface) [Section titled “Creating Branches via Web Interface”](#creating-branches-via-web-interface) To create branches via the web interface (UI), follow these steps: * File-based project 1. Open your project and go to **Sources > Files**. 2. Click **New Version Branch**. 3. In the appeared dialog, enter the branch name. 4. In the **Duplicate Strings** section, select how duplicated strings should be handled. 5. Click **Create** to finish. * String-based project 1. Open your project and go to the **Branches** tab. 2. Click **New Version Branch**. 3. In the appeared dialog, enter the branch name. 4. Select **Create empty branch** or **Clone existing branch**. 5. If cloning, select the source branch from the dropdown that appears. 6. Click **Create** to finish. #### [Branch Creation using API](#branch-creation-using-api) [Section titled “Branch Creation using API”](#branch-creation-using-api) You can use the Crowdin API to programmatically create branches. The available method depends on the project type: * [Add Branch (File-based)](https://support.crowdin.com/developer/api/v2/#tag/Source-Files/operation/api.projects.branches.post) * [Add Branch (String-based)](https://support.crowdin.com/developer/api/v2/string-based/#tag/Branches/operation/api.projects.branches.post) #### [Branch Management using CLI](#branch-management-using-cli) [Section titled “Branch Management using CLI”](#branch-management-using-cli) With the Crowdin CLI, you can manage branches directly from your local environment, using the dedicated commands. You can also create a branch automatically during file upload. Read more about [Branch Management with CLI](https://crowdin.github.io/crowdin-cli/commands/crowdin-branch). ### [Cloning Branches](#cloning-branches) [Section titled “Cloning Branches”](#cloning-branches) You can create a copy of an existing branch using the **New Version Branch** dialog or the **Clone** option in the context menu. To clone a branch, follow these steps: 1. Open your project and go to the **Branches** tab. 2. Do one of the following: * Click **New Version Branch**. * Hover over the needed branch, click (or right-click), and select **Clone**. 3. In the appeared dialog, enter the name for the new branch. 4. If cloning via **New Version Branch**, select **Clone existing branch** and choose the source branch from the dropdown. 5. Click **Create** to finish. Limitations Branch cloning is only available for [string-based](/creating-project/#string-based-project) projects. ### [Merging Branches](#merging-branches) [Section titled “Merging Branches”](#merging-branches) You can merge one branch into another directly from the **Branches** tab using the context menu. During the merge process, Crowdin displays a summary of changes and allows you to resolve any conflicts before completing the merge. 1. In the **Branches** tab, hover over the source branch you want to merge. 2. Click (or right-click), and select **Merge**. 3. In the appeared dialog, choose the target branch to merge into. 4. Click **Continue** to proceed to the Merge Summary page. On the **Merge Summary** page, you’ll see: * A summary of string changes — how many were added, removed, or changed. * An optional checkbox to **Delete the source branch after merge**. If any strings were changed, a conflict resolution step will follow. For each conflicting string, choose whether to keep the version from the source or the target branch. You can also: * Click **Accept all from `{source_branch}`** to apply all changes from the source. * Click **Accept all from `{target_branch}`** to keep all existing strings in the target. The **Merge** button becomes active only after all conflicts are resolved. Once the merge is complete, translations, approvals, and votes from both branches will be preserved. Limitations Branch merging is only available for [string-based](/creating-project/#string-based-project) projects. ### [Prioritizing Branches](#prioritizing-branches) [Section titled “Prioritizing Branches”](#prioritizing-branches) You can set priorities to branches in file-based projects to help translators focus on the most important content first. Branches appear sorted by priority on the language page and in the Editor. Available priorities: * – low * – normal * – high To set a priority for your branches, follow these steps: 1. Open your project and go to **Sources > Files**. 2. Click the arrow icon next to the needed branch to set the preferred priority. Limitations Branch prioritization is only available for [file-based](/creating-project/#file-based-project) projects. ### [Other Actions from the Context Menu](#other-actions-from-the-context-menu) [Section titled “Other Actions from the Context Menu”](#other-actions-from-the-context-menu) In addition to cloning and merging, the context menu for each branch includes the following options: * **Rename** – Allows you to change the name of the selected branch. * **Add Task** – Opens the task creation dialog with the branch preselected. * **Cost Estimate** – Opens the cost estimation dialog scoped to the branch. * **Delete** – Permanently deletes the branch from the project. Use with caution. ## [Duplicates](#duplicates) [Section titled “Duplicates”](#duplicates) Because branches are different versions of the same product feature, their localization content is usually duplicated. To help translators translate versions consistently and avoid additional translation costs, Crowdin offers the **Show within a version branch** option, which hides duplicate strings between branches. When this option is applied, only the original strings (usually from the master branch) need to be translated. All duplicates in other branches automatically receive translations from those originals. * File-based project In file-based projects, you can configure how duplicates are handled in **Settings > Import > Source Strings**. If your source files contain clear identifiers (keys), it’s recommended to use the *Strict* version of the **Show within a version branch** option. Otherwise, the *Regular* option will work well for most use cases.  * String-based project In string-based projects, the **Show within a version branch (regular detection)** behavior is applied automatically and cannot be changed. This ensures translations are reused between branches without requiring any additional configuration. Read more about [Duplicates settings](/project-settings/import/#duplicate-strings). ## [Suggested Workflow](#suggested-workflow) [Section titled “Suggested Workflow”](#suggested-workflow) To ensure smooth collaboration between developers and translators, version branches in Crowdin can be used in different ways depending on how you manage source content and what project type you’re using. ### [Managing Content Outside Crowdin](#managing-content-outside-crowdin) [Section titled “Managing Content Outside Crowdin”](#managing-content-outside-crowdin) In both file-based and string-based projects, you can treat your external system (e.g., file storage or version control) as the source of truth. In this setup: * Source files are managed and updated outside of Crowdin. * You upload project content using the web interface (UI), API, CLI, or integrations. * Selected branches are created in Crowdin accordingly. * Translations are delivered back to your system once completed. To implement this approach for your Crowdin project, we recommend the following workflow: 1. Upload your project files to the Crowdin project using one of the [available methods](#creating-branches). 2. In file-based projects, open your project and go to **Settings > Import > Source Strings**. 3. Set the **Duplicate Strings** option to **Show within a version branch**. The screenshot below visualizes how this workflow works in practice. All texts from *Master*, *Branch 1*, and *Branch 2* are transferred to the translation server immediately after they appear, even though the branches are not merged into the *Master* branch yet.  ### [Managing Content in Crowdin (String-based Projects Only)](#managing-content-in-crowdin-string-based-projects-only) [Section titled “Managing Content in Crowdin (String-based Projects Only)”](#managing-content-in-crowdin-string-based-projects-only) For string-based projects, you can also manage branches directly in Crowdin without relying on an external system to define structure or content updates. In this setup: * Source content can be added the web interface (UI), API, CLI, or integrations. * Version branches are created, cloned, and merged within Crowdin using the UI or API. * Translations are optionally synced back to any connected integration, if used. This approach gives more flexibility for teams who prefer to organize content and manage version flows entirely within Crowdin. ### [Translation Download](#translation-download) [Section titled “Translation Download”](#translation-download) Translations from all version branches are placed in one ZIP archive when downloaded through the web interface. Use the CLI or API to download the translations for each branch individually. #### [Translation Download using API](#translation-download-using-api) [Section titled “Translation Download using API”](#translation-download-using-api) To download translations of the specific version branch with API, you can use the following API methods: * [Build Project Translation](/developer/api/v2/#operation/api.projects.translations.builds.post) - make sure to use the `CrowdinTranslationCreateProjectBuildForm` schema. * [Check Project Build Status](/developer/api/v2/#operation/api.projects.translations.builds.get). * [Download Project Translations](/developer/api/v2/#operation/api.projects.translations.builds.download.download). #### [Translation Download using CLI](#translation-download-using-cli) [Section titled “Translation Download using CLI”](#translation-download-using-cli) Download translations of the specific version branch: ```shell crowdin download -b branch_name ``` Read more about [`crowdin download` command](https://crowdin.github.io/crowdin-cli/commands/crowdin-download). ### [Merging Branches Outside Crowdin](#merging-branches-outside-crowdin) [Section titled “Merging Branches Outside Crowdin”](#merging-branches-outside-crowdin) The *Master* branch will contain new texts from the *Feature* branches as soon as they are merged. While synchronizing with Crowdin, texts in the *Master* branch are populated with translations from the appropriate branch. After synchronizing the updated *Master* branch with Crowdin, you can remove the *Feature* branch from Crowdin. All translations stored in the *Master* branch will remain. This approach is commonly used in file-based projects but can also apply to string-based ones if content is managed outside of Crowdin.  ### [Branch Translation Verification](#branch-translation-verification) [Section titled “Branch Translation Verification”](#branch-translation-verification) You can verify translations on production using only the *Feature* branch before changes are merged with your *Master* branch. Such test deployment allows you to quickly revert to the original Master branch version if needed.  # Vulnerability Reporting Policy > Crowdin Vulnerability Reporting Policy Crowdin is transitioning to managing its bug bounty program through HackerOne. The program is currently private. To request an invitation, contact and provide your HackerOne handle. Details about the vulnerabilities we’re looking for, exclusions, and program conditions are available directly on HackerOne. # Webhooks > Integrate Crowdin with your services by configuring webhooks Webhooks allow you to receive information about the key events that happen in your Crowdin project, like completed translations or proofreading. After you configure a webhook, Crowdin will start sending POST or GET requests with data to the webhook URL via HTTP. ## [Use Cases](#use-cases) [Section titled “Use Cases”](#use-cases) You can add webhooks to build integrations with the services or with your backend. For example: * Set up a webhook to send notifications to the system you use. * Pass information to the third-party services with the specific request requirements (for example, HTTP method, content type). * Create custom integrations with Crowdin. ## [Events](#events) [Section titled “Events”](#events) You can configure webhooks for different events that occur in the project, e.g., when a file is translated, proofread, or when a string is added or updated. Read more about [Webhook Events](/developer/webhooks/#events) on Crowdin Developer Portal. ## [Adding Webhooks](#adding-webhooks) [Section titled “Adding Webhooks”](#adding-webhooks) To configure webhooks in Crowdin, follow these steps: 1. Open your project and go to the **Tools** tab (for Account-level webhooks, open your **Account Settings**). 2. Select **Webhooks** and click **Add Webhook**.  You will need to provide the following information to register a webhook: * The webhook name (for example, “App Project Translated”). * The events to post to the URL. You can select either one event or a specific set of events. * The URL to which the webhook callbacks are sent as direct requests. Redirects are not supported and will result in a failed delivery. The endpoint must return a 2XX response within 30 seconds. * The request method that indicates the desired action to be performed for a given resource (use either `GET` or `POST`). * The content type for the POST request method (`multipart/form-data`, `application/json`, or `application/x-www-form-urlencoded`). * For the `application/json` content type, you can select **Batch webhooks** to merge multiple events into a single request. Optionally, you can add special headers to your webhook. They can be used for additional security, as an authorization method, and more. For example, if you add headers, your webhook endpoint can check them to ensure that information is coming from Crowdin. Limitations You can configure up to 20 webhook endpoints for project-level events. Depending on your approach to webhook management, you might need to add dedicated Crowdin IP addresses to your firewall to allow Crowdin to open the pre-configured webhook URLs. Read more about [IP Addresses](/developer/ip-addresses/#webhooks-ai-providers-and-mt-engines). ## [Custom Payloads](#custom-payloads) [Section titled “Custom Payloads”](#custom-payloads) Each event type in Crowdin has a specific payload format with the relevant event information. You can customize the webhook payload to add and organize the elements the way your system requires. To check the event’s possible variables, hover over the *Info* icon in the *Payload* section’s right upper corner. ## [Edit or Delete Webhooks](#edit-or-delete-webhooks) [Section titled “Edit or Delete Webhooks”](#edit-or-delete-webhooks) Within a specific project, you can access and manage configured webhooks by editing or deleting them directly from the displayed list.  ## [Calls History](#calls-history) [Section titled “Calls History”](#calls-history) In the **Calls History** section, you can view the list of calls of all the configured webhooks. Use the filter to view all or only unsuccessful webhook notifications.  ## [Failing Webhooks](#failing-webhooks) [Section titled “Failing Webhooks”](#failing-webhooks) Webhooks that fail 100 or more times in the last 24 hours with response codes in the 4xx or 5xx ranges are automatically disabled. ### [Disabled Webhooks](#disabled-webhooks) [Section titled “Disabled Webhooks”](#disabled-webhooks) Disabled webhooks are listed in the **Webhooks** section with a cleared check mark, indicating that they are currently inactive due to persistent failures. To discover more about failed webhooks, navigate to the **Calls History > Unsuccessful** section. Here you can explore detailed information about the issues encountered by each failed webhook. ### [Manual Re-enabling](#manual-re-enabling) [Section titled “Manual Re-enabling”](#manual-re-enabling) Once you have identified and resolved the cause of the webhook failures, you can manually re-enable the webhooks to restore their functionality. In the **Webhooks** section, locate the disabled webhook and select it for re-enabling. ## [Sending Webhooks to Slack](#sending-webhooks-to-slack) [Section titled “Sending Webhooks to Slack”](#sending-webhooks-to-slack) With the help of Crowdin webhooks, you can send notifications about pre-configured event types directly to a specific Slack channel. To configure the webhooks’ sending to Slack, you’d need to create a simple Slack app. Read more about [Sending messages to Slack using Incoming Webhooks](https://api.slack.com/messaging/webhooks). As soon as you create and configure your Slack app, you’ll have a Webhook URL that should be used for the Webhooks configuration in Crowdin. # Word Counter > Learn how Crowdin counts words in your files Below are the principles due to which Crowdin counts words: * A word is a combination of letters, punctuation marks, and special characters (e.g.:@ # $ % ^ & \* – \_ \` ‘ “) followed by space. * A sequence of punctuation marks or special characters is not considered a word. * By default, HTML tags are considered separate words for most formats, except the following ones: HTML, Front Matter HTML, HAML, MD, Front Matter MD, XML, WEBXML, IDML, XLIFF, XLIFF 2.0, ADOC, DOCX, MIF, DITA. You can change the default word count settings in your project’s **Settings > Import > Word count**. * URLs (e.g. `https://crowdin.com`) and emails (e.g. `support@crowdin.com`) are considered one word. * Hieroglyphs in Chinese, Japanese, and other hieroglyphic languages are counted as one word/hieroglyph. For example, “ライフ・イン・トウキョウ。” is counted as ten words. Other examples of how the words are counted: | **String** | **Words** | | --------------------------------------------- | ---------------------------------------- | | Number is -123.45 | 3 | | `here` | 1 / 7 (if non-HTML-based format is used) | | 0 – 1 at 2 | 4 | | two-in-one | 1 | | 2-in-one | 1 | | two-in-1 | 1 | | `%file_type%` | 1 | | hello?world | 1 | | hello ? world | 2 | | `☂ ☃ ☀⚤` | 0 | | © %company% | 1 | | 01/01/1980 | 3 | | Monday, August 8, 2011 | 4 | | `https://ka-graphie.example.com/6d8b.png` | 1 | | Let’s look | 2 | | Let’s look | 3 (another type of apostrophe is used) | | Word(s) | 2 | ## [Translatable HTML Attributes](#translatable-html-attributes) [Section titled “Translatable HTML Attributes”](#translatable-html-attributes) When working with HTML-based file formats, depending on the file structure, some HTML attribute values may be considered translatable while others not. You can see the list of attributes and situations when their values are considered translatable in the table below. | **Attribute** | **Details** | **Example** | | ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------- | | `title` | translatable if contained in any HTML tag | `

Text

` | | `src` | translatable if contained in `img`, `iframe`, `embed`, `video`, `audio`, `source`\*, `track`\* tags \* – if nested in the parent tags `video`, `audio` | `` | | `href` | translatable if contained in `a` tag | `Site name` | | `data` | translatable if contained in `object` tag | `` | | `value` | translatable if contained in `input`, `button` tags | `` | | `placeholder` | translatable if contained in `input`, `textarea` tags | `` | | `alt` | translatable if contained in `img` tag | `` | | `label` | translatable if contained in `optgroup`, `track`\* tags \* – if nested in the parent tags `video`, `audio` | `` | | `content` | translatable if contained in `meta` tag | `` | # XML File Configuration > Configure XML files to import the content for translation The XML files, similar to CSV and XLSX files, require additional configuration after uploading to the project so the system could import the content of these files. To configure XML files, follow these steps: 1. Open your project and go to **Sources > Files**. 2. Click **Configure** next to the file to open the configuration window. 3. Select which content should be translated and click **Save & Import** to proceed.  [XML translation with Crowdin ](https://store.crowdin.com/xml) Limitations XML files are not supported in [string-based](/creating-project/#string-based-project) projects. ## [Configuration Options for XML Files](#configuration-options-for-xml-files) [Section titled “Configuration Options for XML Files”](#configuration-options-for-xml-files) When configuring XML files, you’ll have the following options: **Basic Configuration** and **Advanced Configuration**. Additionally, you can use the **Content Segmentation**, which is available for both configuration options. ### [Basic Configuration](#basic-configuration) [Section titled “Basic Configuration”](#basic-configuration) Basic Configuration allows you to select all nodes and/or all attributes to be available for translation.  ### [Advanced Configuration](#advanced-configuration) [Section titled “Advanced Configuration”](#advanced-configuration) Advanced Configuration allows you to select the specific nodes and specific attributes to be available for translation.  The file structure is depicted with the help of icons: * – Node * – Attribute [XSL Transformer for XML ](https://store.crowdin.com/xslt-preview)Preview your XML file directly in Editor with the XSL Transformer for XML application. ### [Configure All XML Files at the Same Time](#configure-all-xml-files-at-the-same-time) [Section titled “Configure All XML Files at the Same Time”](#configure-all-xml-files-at-the-same-time) To configure all XML files at once, click **Configure All** at the top of the **Files** tab. When using **Configure All**, ensure that all XML files contain the same structural elements. Otherwise, some nodes that require translation might be unavailable during configuration and won’t be imported into the project. In this case, it would be necessary to configure each XML file separately. In the configuration window, you’ll be able to switch between the selected files to preview and verify if the applied configuration is correct for all files. ## [Content Segmentation](#content-segmentation) [Section titled “Content Segmentation”](#content-segmentation) You can use **Content Segmentation** to split the source file’s content into shorter text pieces, mostly sentences and short paragraphs. This is helpful when translating content units consisting of several sentences because it will be easier to translate smaller pieces of text. Segmentation Rules eXchange (SRX) are used for automatic content segmentation. Read more about [Custom segmentation](/custom-segmentation/). ## [See Also](#see-also) [Section titled “See Also”](#see-also) [Uploading Source Files ](/uploading-files/)Learn how to upload source files to your project for translation. [File Management ](/file-management/)Manage and configure source files in your project.