On this page


Generally, almost all metafields can be translated with langify. However, translating them requires special attention for several reasons:

  • Metafields may contain codes that need to be left untranslated.
    Many third-party apps use metafields to store their settings. These fields must remain untranslated to ensure the app continues to work properly.
  • Some metafields contain a mix of code and text.
    If you are using machine translations, these systems cannot always correctly differentiate between code and text and might accidentally translate the code portions. This can lead to unexpected behavior.



Where to find it in langify


You will find the metafield in langify attached to its resource. For example, if you're looking to translate Product metafields, please go to the product section in langify and open the parent product of the metafield. You'll find a "Metafield" tab on each product.


If you're looking for Shop metafields, you will find them at langify -> Shop -> Metafields. Please be especially careful here — since many third-party apps store their settings as shop metafields, translating them might break their functionality.


If you're not sure if a metafield should be translated or not, please check with the support team of the app that the metafield belongs to.

For clean communication, you can specify a metafield by its namespace and key which you will find at the top of each metafield.

In this example, the namespace of this Shop metafield is "beae" and the key is "colors":


Can't find your custom metafield in langify?

Our app tries to filter out metafields that we assume might belong to a third-party app and should remain untranslated. In some cases, this can affect your custom metafields, too.

If you have added a metafield in your store and it does not appear in langify, please don't hesitate to reach out to us at support@langify-app.com and we can add your custom metafield to our app's allowlist.



Bulk Translation


Metafields are unfortunately not included in langify's Bulk Translation tool.

Blindly translating them is likely to cause the store to break on specific pages. And fixing this would mean the user would have to look through all metafield translations and remove the problematic translation. This would be time-consuming for the user and might affect their sales as well.


Here are some examples of third-party app metafields that contain settings and should remain untranslated:


JSON metafields


If you need to translate metafields where the text is stored in a JSON format, this can look a bit daunting.

It is necessary for the translation to be valid JSON - otherwise the translation cannot be saved.


You can validate the JSON formatting by using any JSON-checker tool of your choice.
For example jsonchecker.com or jsonlint.com


Nowadays machine translations are usually smart enough to correctly translate such a field, but it can happen that the translation needs to be manually adjusted to fit the JSON format.


If you want to translate such a metafield manually, you can use the JSON-view editor in langify. You can find this when clicking on the icon in the upper right corner of the metafield:


The JSON viewer will appear like this:


Even when in the JSON viewer, please make sure to leave texts that look like code untranslated or just enter their original text in the translation field, like seen in the example above.