Independent AEM Translation Plug-in

Send translations to LSP or TMS of your choice
AEM translation automation

AEM logoOne of the major challenges of the translation industry is the interchange of data between different systems that are involved in the translation process, for example from Adobe Experience Manager to TMS.

Xillio LocHub was created to help automate multilingual content delivery processes between CMS and TMS, so your content can be FREE to be localized in the best way possible for your business.

Use LSP/TMS of your choice

LocHub AEM translation plug-in enables AEM users to manage and deploy multilingual web contents directly within the AEM environment. The integration is pre-built and can be installed with minimal IT knowledge. As we integrate LocHub into your AEM version, there is no need to log into another system, you and your teams can experience a swift, seamless and controlled translation process.

LocHub AEM translation plugin allows you to send translations to the LSP or TMS of your choice.


  • Seamless exchange of contents between AEM and TMS;
  • Contents are pushed into translation and retrieved in AEM automatically;
  • No manual file export or handling required;
  • Freedom of choice – work with your preferred LSP.
  • Content Managers can launch translations directly from their AEM environment;
  • Localization Managers can track project status in AEM (or TMS);
  • LSP team can directly process projects in TMS;
  • Supports preview.

Watch in action?

How does it work?

In this video, we show how the LocHub AEM translation plug-in helps content teams to accelerate turnaround times for translation content. In an AEM demo environment we show how easy it is to create translation jobs, and send, retrieve, review and publish translations as well as managing the whole process.  

Video file
Installation prerequisites

Have Xillio AEM plug-in ready to install             

Supported versions

At least AEM 6.2 or higher                                     

More information


Find Answers to Your Questions

We submit whatever AEM supports and is selected at project creation: assets, pages, l18n dictionaries and tags.

Yes, it does. For example, by transferring the html of a page as long as the content owner allows for it.

The content manager would create a new project to translate the new page version or the updated page.

No, there is no limit and no noticeable slowdown.

Our connector transfers pages or assets, depending on what the content manager decides to be translated via AEM function. LocHub submits the whole page, it will be the translation memory to identify the specific segment that needs to be updated.

The status in AEM will be updated. In addition, the content manager / localization manager can access the project overview in LocHub for more details.

There is a page view function in AEM that the content manager can use to sign-off the page before publishing (no connection to the translation memory). LocHub also supports in-context review function on TMS side.

Request a quote

Fill out the form and we will contact you as soon as possible.

Xillio is committed to protecting and respecting your privacy, and we’ll only use your personal information to administer your account and to provide the products and services you requested from us. From time to time, we would like to contact you about our products and services, as well as other content that may be of interest to you. If you consent to us contacting you for this purpose, please tick below to say how you would like us to contact you:

You may unsubscribe from these communications at any time. For more information on how to unsubscribe, our privacy practices, and how we are committed to protecting and respecting your privacy, please review our Privacy Policy.

By clicking submit below, you consent to allow Xillio to store and process the personal information submitted above to provide you the content requested.