Library Settings

Change how your Project is Configured

Library Settings

You can change the following Localize Library settings to customize Localize functionality in your Project.

These settings can be enabled/disabled from the Project Settings: Library Settings page.

  • Simply toggle on/off the following settings and select Save.

Automatically detect visitor's language preference

By default, Localize will automatically detect the visitor's preferred language from their browser settings and select that language (if your website supports it).

Archive unused phrases

By default, Localize will automatically archive phrases that have not been seen on your website in over 14 days. This option improves performance by minimizing the translation file size delivered to your website visitors. The phrases are moved to the Archive: Deprecated bin.

If you don't want your phrases to be deprecated, simply deselect this option and click Save.

Translate meta tags

Select this checkbox to have Localize bring any meta tags found in the <head> of your website into the dashboard where they can be translated. (this option is enabled by default)
See which tags are supported and read more about the importance of translating meta tags here...

Translate aria-label Attributes

Select this checkbox to automatically translate aria-label attributes found on your website.

  • Any content found in an aria-label attribute will be brought into the dashboard as a new phrase, allowing it to be translated.
  • This is useful when you are working to support screen readers.

Localize images

Select this checkbox to enable the localization of images in your Project. (this option is disabled by default)

  • Image URLs will appear as phrases which will allow you to provide an alternate image for different languages.
  • The system label lz-image will be automatically added to all image "phrases" so you can easily filter your phrases to find all images.

Send debug information

Enabling this setting will save additional debug information, including:

  • The browser user agent that requested the phrase
  • The HTML surrounding the phrase when it was saved

To view this information, click on the drop-down arrow at the top/right of a phrase and select the "Information" link. For more information on what's available in the information panel, click here.

By default this option is disabled. The Localize team may ask you to turn this on when you are experiencing problems using Localize, in an effort to track down the problem. Normally this option should remain disabled for performance reasons.

Ignore Pages of your Website

You can ignore parts of your website for which you won't be needing translations. This will help to keep unwanted phrases/content out of your phrases bins.

  • Simply add the areas that you would like to ignore using the instructions in the panel.

Ignore Phrases of your Website

You can block specific words or phrases in your website from being brought into the Localize dashboard by adding regular expressions in your library settings.

Some examples of where this might be useful include:

Regular Expression

Date With Slashes


1/2/2020, 12/15/1963

Countdown Timer (HH:mm:SS)


12:42:22, 01:18:33

Brand name


Any phrase whose content contains "Localize" anywhere in it

Specific ID #s
(e.g. US social security #)



Specific word: dog


Any phrase whose content is exactly "dog"

Specific word: cat


Any phrase whose context contains "cat" anywhere in it

  • Simply add the words or phrases, separated by new lines.
  • You can use regular expressions
  • The expressions are case-sensitive

Existing Phrases

This feature will only block new phrases from coming into the Localize dashboard.

If phrases already exist in the dashboard, they won't be blocked after adding a word/phrase to the ignore list. They will have to be manually deprecated or trashed.

Updated 19 days ago

Library Settings

Change how your Project is Configured

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.