Field level localization (beta)


This feature is currently in beta. Please reply to this post with questions and feedback


Currently, level localization requires using our React SDK, but is also supported to some level via our Angular and Vue SDK as well.


This post is for field level localization within content blocks in the Visual Editor, and does not cover localization for custom fields. For custom field level localization you can find more info in this post: Custom Field Localization (beta)



In order to use this feature, you need to pass a locale property to the data prop of the BuilderComponent. For example, to display localized values for 'en-US'

<BuilderComponent model={yourModel} context={{ locale: 'en-US' }} />

Now any values localized to en-US will be displayed in your rendered content. Learn more about context in our React SDK here


The same step in Angular can be achieved by passing in the locale through the options attribute on the BuilderComponent (and not the data). For example, to display content for the locale en-US, the following options object can be set as a property in your custom component:

options: any = {
    options: {
      data: {
        locale: "en-US"

Do note the options key inside the options property, it is important! Then, we can simply pass them to our BuilderComponent in the HTML:



Vue allows passing in the locale to the options attribute on the RenderContent element. Do take note of the options key inside the options property on the element. In order to render content for the locale en-US, use the following:

        options: {
          data: {
            locale: 'en-US',


To add localized values, select a layer and next to any option chose the binding icon (4 dots in a square). Then choose “localize values” and enter what value you want for each locale

To add locales choose “add locales here” and enter your new locale name.

To manage locales go to Drag and drop page builder and CMS and choose the pencil button next to “Custom targeting attributes” and you can add and remove locales next to the locale field

Up next

More docs will be coming soon :slight_smile:

HI @steve,
Any news on field level localization for custom fields?

Hey @AlexKiss - we have just finished a first beta implementation of this and hope to release it very soon (in the next week or so). We will follow up here when it is live!


Hi @steve . Will this be available for e.g: rich-text fields as well? Currently when I try to click on a richText field and localize it, the app freezes :worried:

@radikris correct! Though we should definitely figure out that freezing issue too - will try to find out how to reproduce on our side and reach out if we’re having trouble and it persists for you

1 Like

Localization is now available for CustomFields as well. I have written a similar description on how you can use it here: Custom Field Localization (beta)

Check it out and feel free to comment in the thread with any feedback, issues or questions!

cc @AlexKiss