Once you open a project for editing, you will have a list of keys with their snapshots, translations and other attributes. Let’s take a closer look at the available controls and the key editor itself.

Icons next to the key name allow you to perform key-related actions with a single click.

Comments: team work usually involves discussions on particular keys. Once you leave a comment for a key, it is automatically emailed to the people who have the same contribution rights on the languages as you.

Copy link to clipboard: copy a link to the target key to your clipboard.

Duplicate this key: create a copy of the current key.

Google-translate empty values: click to populate all empty values of the current key with automatic translations provided by the Google translation engine. This may take a few moments depending on the job’s volume.

Hide from contributors: hide the target key from all other contributors/translators.

Delete key: remove the key and all related translations. Warning: you cannot undo this action so think twice before deleting keys.

Screenshots: link one or multiple screenshots to this key. Continue reading to learn more about the screenshot manager.

Key editor: click the key name to bring up the key editor. The key editor is described in more detail later in this article.

Key editor

To access the Key editor, click the key name itself. Read below to learn more about the key editor.

Lokalise supports four platforms – iOS, Android, Web and Other. Assigning a key to one or multiple platforms actually means that the key will only be associated with the platform-specific file formats when you export the localization files. For example, assigning a key to the iOS platform means it will be included with the Apple Strings and Apple Xliff file exports, and will be excluded from the JSON export (as JSON belongs to the Web platform).

Each key can be attributed to a single filename per platform. You can set the attribution using the key editor: click the key name in the editor, then navigate to the Advanced tab.


Use the built-in tagging of the editor to logically group your keys. Click the tag icon and either enter a new tag, or select from a list of tags you have already added.

Learn more about tags.

Key editor

Click any key name to bring up the key editor dialog box. Note that this option is only available to project admins and can be globally deactivated in the project settings.

You can also open the key editor by clicking the Add key button or pressing Ctrl+K on your keyboard. In this case, the key editor will contain the default setting values and you will be able to create the new key from scratch. Alternatively, you can copy existing keys by using the Duplicate key icon next to the key name, and then adjust only the required fields.

After you have finished editing, click the Save button in the bottom left corner of the floating box, or hit Ctrl+Enter on your keyboard.

General options

  1. Enter your key name here. You cannot create multiple keys with similar names. However, it is possible to have keys with similar names but different contexts (context is set in the advanced options, see below).

  2. The key value in the base language that you want to translate. This field may also contain reference to another key as shown in the screenshot above.

  3. Enable automations during key creation.

  4. Platforms to be associated with the key. Different platforms have different file export formats; each key can be assigned to one or multiple platforms. 

  5. A description to help project contributors understand the context.

  6. Add existing tags or create new ones to facilitate filtering and exporting.

  7. Turn on to keep the dialog window open after you click the Save button. This may be useful when adding/editing multiple keys in a row.

  8. Click the Save button or press Ctrl+Enter to apply the changes.

Advanced options

  1. Turn on if the target key has plural forms. Lokalise will automatically add the necessary plural forms for each language. 

  2. Option to assign each key to a file (one filename per platform).

  3. Turn on to hide this key from contributors (it will be visible to admins only).

  4. Context is used with some file formats (e.g. .po). You only need this if the context is actually used in the code, otherwise skip this setting. Also note that providing context enables you to create multiple keys with similar names (otherwise you can't do that).

  5. Set the character limit for this key values. Longer strings will not be accepted. However, this setting will not affect the existing translations.

Custom attributes

You can use custom attributes to define format-specific options for the target key. For example: Android Resources (XML) files can have a “translatable” attribute set to false.

Screenshots manager

To access the screenshot manager, simply click the Screenshots icon in the key icon menu. A floating box with the current key name in the header will appear.

Please note that this option is only available to project admins with the Manage screenshots permission.


In this tab, you will find all the screenshots that are linked to at least one key. You can perform the following actions:

  • Open any screenshot in the screenshot editor (this will be opened in the new tab)

  • Preview any screenshot — the key will be highlighted

  • Unlink any screenshot from the current key

Here, you can link the current key to screenshots uploaded earlier. To do this, simply click the desired screenshot(s) and then click the Link selected button in the top right corner. 

Tab functionality:

  • Only show specific screenshots, e.g. with tags or with linked keys

  • Search screenshots by name or partial name

  • Preview any screenshot

  • Open any screenshot in the screenshot editor

  • Link screenshots to the key one by one or simultaneously (multiple at once)


The screenshots you upload here will be automatically bound to the current key. You can drag and drop screenshots to the designated area or manually select a file from your computer. Select the Try to find keys on images option if you would like Lokalise to scan the screenshots for you.

Translation controls

Each translation value has several buttons next to it: these provide translation-related functionalities. Some of the available actions are flags — e.g. reviewed, unverified while others open an additional floating panel.

Spelling/grammar error

Lokalise automatically checks spelling and grammar in the editor as you upload or update the translation strings. If a spelling or grammatical error is found, a small icon will appear to the right of the translation field.

Mark as reviewed

Users with the reviewer role can mark translations as reviewed in the editor and approve any translations added by other contributors.


Use the Unverified flag to signal a translation you do not consider to be 100% correct. Unverified translations can be conveniently reviewed later using the preview filters in the editor.

Translation History

Translation history keeps all versions of each translation update you have ever made. Click the icon to see the translation history for the target item.

Did this answer your question?