Lokalise Reviews & Product Details

I like the user interface, as it is intuitive, easy to use and contains a bunch of helpful tools for making my job as a translator easier, such as access to the translation memory, able to see previous translations of the same or similar phrase, and also, the thing that is very helpful is the ability to see screenshots and comment sections which the client leaves which reduce the time I have to spend guessing what the source text meant. Review collected by and hosted on G2.com.

I noticed a couple of bugs while working in Lokalise, but these are workflow bugs and not feature or functionality bugs that hinder me from delivering a quality translation. For example, the ctrl+enter function does not confirm the translation. Review collected by and hosted on G2.com.

Lokalise makes an extremely tedious task such as internationalisation actually enjoyable to implement as a developer. Furthermore the end users have an easy time of understanding the UI, when they are managing their translations.

I am working with Lokalise on a daily basis both as a developer but also as support for our Marketing department. For all of our frontend solutions (Next.js, React.js and React Native) we are utilizing Lokalise for internationalization in three different ways:

For our Next.js website, Lokalise is connected via a webhook that I have set up for every domain. This means that any changes made by our franchise users are shown on the website in about 10 seconds. The integration of the webhook and connection to the Next.js API worked flawlessly and was very easy to do. Furthermore, the use of the useTranslation() hook makes it extremely easy to use the translations in your code on a day2day basic.

For our React.js integration we are mostly using Lokalise for storing all of our text content (everything is in English here). At one point we expect to do a proper localization of this application and I am sure that Lokalise will make it just as easy for us. One thing that we do not have in the client-side React.js app is the use of server-side API routes to trigger via the webhook and update the stored translations. I am excited to see how we will solve this challenge other than rebuilding and redeploying the project.

In the React Native application we are currently utilizing App Center to trigger a small in-app update for the users whenever a translation is changed. Review collected by and hosted on G2.com.

For our franchise solution we need to have different variants of e.g. the english texts. While this can be solved on the web with our headless CMS solution it is not as intuitive in our app, where we have to rely on creating multiple sub-versions of every locale in Lokalise. This means that the multilangual view can get cluttered very quickly.

Some of the franchise users also have a hard time understanding the use of {{brackets}} for dynamic variables in the text, which sometimes causes UI bugs until it is noticed - maybe this could be done in a more user friendly way? Review collected by and hosted on G2.com.

I've been using Lokalise for about 5 years as a localization manager, and everything seems good to me. I might not use all of its features in my work, but here are the key upsides I'd like to share:

The interface is user-friendly. It's quite easy to find anything I need, as well as to handle all 40 languages on the platform, they are well shown on a single page.

The support team is great. They are always ready to help, respond quickly. I've never had any issues when interacting with the support team of lokalise.

It's very convenient to use the lokalise grammar checker which really helps not to miss mistakes or any other moments. As well as the issue notitifier in general. Review collected by and hosted on G2.com.

It would be great if more languages had access to the grammar checker.

Sometimes the file import is very long, and there might be some small bugs (for example, name of the copied key) and we also have difficulties importing plural keys with excel (it requires the complex form that might be broken easily by any occasional move. However, these issues have insignifican impact on the workflow. Review collected by and hosted on G2.com.

Lokalise provides useful data to understand the context of translations and offers robust features for managing Translation Units (TUs). The platform is powerful and well-suited for managing large-scale translation projects. Review collected by and hosted on G2.com.

The interface feels very developer-oriented, which can be challenging for translators and editors who may not be familiar with Markdown or HTML. A preview of the final document below the translation area would be helpful, eliminating the need to interpret codes manually.

Additionally, organizing TUs alphabetically would streamline workflows, and a simpler way to view matches and fuzziness percentages is necessary. This is especially relevant for editors who are paid based on match percentages and need to work efficiently on higher matches. Review collected by and hosted on G2.com.

The Figma-Lokalise integration allows me to establish a design driven flow. This means that I don't have to wait for developers to create the keys, as development can happen in parallel with localization, and therefore I have more generous localization turnaround times while still meeting all deadlines. Moreover, with the integration it's possible to automatically generate screenshots so provide crucial visual context to translators.

Another great thing is the Customer Support for Enterprise clients. They are always very helpful and responsive. Review collected by and hosted on G2.com.

Unofrtunately Lokalise doesn't offer many option for customization. One example is the handoff notification, where I cannot add custom fields and therefore have to rely on the task Description to add important task information.

Another issue is that I cannot connect Lokalise with any external AI tool. Although I can run machine translation within the tool with DeepL free for example, I cannot connect it with DeepL Pro to have higher quality outputs. Review collected by and hosted on G2.com.

Lokalise is a great CAT tool with user friendly interface and its features such as translate with AI make it even better. Many a times during translation, we have character limits, the 'shorten' feature in Lokalise allows me to meet that limit without changing the meaning of the source text. It also has features such as 'Rephrase' and 'suggest variants' which I use often. Review collected by and hosted on G2.com.

Two minor issues that I would like Lokalise team to fix are:

1) I can't see exact number of tasks I am working on, if they are more than 9. It will only show 9+.

2) If I save and complete a segment using keyboard shortcuts then it does not move the cursor to next segment, I have to use mouse for that every time. Review collected by and hosted on G2.com.

We've been using Lokalise to manage our front-end changes and keep our Intercom help center updated across four languages, and it has been a game changer for our team. Lokalise makes it incredibly easy to centralize our translations and collaborate with my teammates. It integrates seamlessly with our system.Highly recommend it to any team looking to scale their localization efforts. It just works. My team loves the new AI translation offerning, which allows us to keep our costs down. Review collected by and hosted on G2.com.

As a new user unfamiliar with translation management system, it took me a couple tries to feel comfortable using it, but I appreciate the resources that were available to me to get help. Review collected by and hosted on G2.com.

Lokalise has an intuitive UI and offers many options for your project, such as setting up file directories, auto-generating PRs, and self QA features. Plus, when you get an error or run into a problem you don't recognize, you can connect with an agent and they'll respond promptly and kindly. Lokalise is the best, it's the best on the market. Review collected by and hosted on G2.com.

The downside of Lokalise is that sometimes things like error logs aren't immediately communicated to users. For example, I had a minor issue today where I sent out a PR and it didn't respond, so I thought it was a bug, but after connecting with an agent, I realized that the commit hadn't gone out because there were no changes. It would be nice if this could be fixed because it's hard for users to see it right away! Review collected by and hosted on G2.com.

Integration with other tools we use, such as Gitlab, Jira, or Wordpress, has made it even easier and smoother. In addition, thanks to string management and advanced translation options, we have maintained the consistency and quality of our texts in all languages. Review collected by and hosted on G2.com.

Automations, for example, are very useful but cannot be configured by adapting them to all needs. Review collected by and hosted on G2.com.

Responsive support with high quality guidance, namely screenshots, relevant examples and links. In addition, the implementation team are highly competent and greatly assisted our implementation of a new content design process through their Figma plugin. Review collected by and hosted on G2.com.

As a UX writer, it isn't a strong content management system for source language. We're attempting to use it for its basic offering and hope that's sufficient. The Figma plugin tool of linking keys could be improved. Review collected by and hosted on G2.com.