DevExpress UI Localization Service (Maintenance Mode)

• Dec 18, 2025
• 4 minutes to read

This topic describes how to use the DevExpress Localization Service to obtain and edit translated resources (strings) for DevExpress UI Controls.

Log into the DevExpress website to get started.

Important

We released a new powerful localization utility - the Localization Tool. The UI Localization Service is currently in maintenance mode. Until we ensure that the new Localization Tool addresses most existing customer needs effectively, the UI Localization Service will remain available, and you can use it to modify translation resources.

Add a Translation

Open the DevExpress Localization Service. Click Add a Translation. Specify the DevExpress version and the language in the pop-up dialog.

Modify, Delete or Copy Translation

You can perform the following actions for every translation that you create:

• Modify translated strings

• Delete a translation from your language set

• Copy a translation

Customize Localization Resources

If you choose to Modify a translation, you are directed to the Customize Localization Resources page. This page allows you to do the following:

• Filter the values in the translation table

• Modify and Save individual translations

• To navigate to the list of languages you selected in Step 2, click Return to Your Translations List.

Download Your Translations

Once you make changes to translations, click the Download button. Note that this button does not start the download immediately.

The Localization Service first builds required resources and then sends an email to the address associated with your DevExpress.com account. Open the email and click the link that will direct you to a signed self-extracting archive:

To unpack a self-extracting archive on your Mac/Linux PC, you can use the same CLI as with regular archives:

7z x windowsfile.exe
OR  
unzip windowsfile.exe

The archive contains folders with localization resources you requested (satellite assemblies and JSON files):

• /Framework - satellite resources for .NET Framework projects.
• /NetCore - satellite resources for .NET projects.
• /json resources - JSON files for DevExtreme-based web components.

Use the resources from the folder that matches your application’s target platform. For additional information, review help topics listed in the following section.

Platform-Specific Information

• Localization for ASP.NET Controls
• Localization for Blazor Components
• Localization for WinForms Controls
• Localization for WPF Controls
• Localization for Dashboard Controls
• Localization for Reporting
• Localization for eXpressApp Framework

Localize DevExpress Controls of Versions Prior to v12.1

The Localization Service supports DevExpress .NET components starting with v12.1. If you use an older version, you can use the following links to download default satellite assemblies:

• DXperience_v11.2_(2012-07-25)
• DXperience_v11.1_(2011-12-09)
• DXperience_v10.2_(2011-09-19)
• DXperience_v10.1_(2011-06-16)
• DXperience_v9.3_(2010-10-08)
• DXperience_v9.2_(2010-10-28)
• DXperience_v9.1_(2009-09-10)
• DXperience_v8.3_(2009-09-10)
• DXperience_v8.2_(2009-01-13)
• DXperience_v8.1_(2009-01-13)
• DXperience_v7.3_(2008-10-22)
• DXperience_v7.2_(2008-02-25)
• DXperience_v7.1_(2008-02-29)
• DXperience_6.3_(2007-06-19)
• DXperience_6.2_(2007-02-27)
• DXperience_6.1_(2007-02-09)
• WinForms_2.2.5_(2006-03-17)
• WinForms_1.3.1_(2005-12-09)

Modify Satellite Assemblies in Versions Prior to v12.1

Follow the steps below to modify satellite assemblies:

1. Download the archive for the version of the suite you use.
2. Modify the *.resx files.
3. Build assemblies and sign them as DevExpress as described below.

Sign Satellite Assemblies as DevExpress

Satellite assemblies must be signed with the same strong key as DevExpress main assemblies. After you re-build the satellite assemblies, assemblies are signed with a different key (since DevExpress do not share their strong key). To resolve this issue, do the following to perform “delayed signing”:

1. Extract a public key token (use the Strong Name Tool (Sn.exe)):

2. Follow instructions in the following Microsoft topic: Delay-sign an Assembly.

3. Create a new Support Center ticket and attach your partially signed assemblies. We will sign your assemblies with our strong key.