Phrase Localization Platform Pricing Overview

The ability to upload multiple keys at once from a simple spreadsheet. The Figma-integrated features where strings can be pulled and pushed from Figma to Phrase and vice-versa without manual work.

Update: I like the new interface that debuted last year. Previously, it resembled Microsoft Word but it looks sleek now — especially with dark mode. Love how I can see all translations along with the source content of a key easily. The different ways to search for keys are useful (by key name, key value, or Phrase tag), though it would be nice to have a way to search for keys tagged with a certain word or Phrase without providing the exact Phrase tag. Review collected by and hosted on G2.com.

The screenshot feature is buggy. When I try to tag keys to a screenshot, the tool crashes at times. Also, the size of the screenshot displayed during the key-tagging area is sometimes too big and cumbersome to tag keys efficiently — I don't know why this happens many times. Sometimes it works fine.

Update: the Phrase-Figma plugin works better now. Previously, it was impossible to run the plugin to pull content from multiple Figma screens to Phrase. Now, it's possible for our teams to use this plugin as our official process to update content between Figma and Phrase. There's still room to improvement here in terms of speed though. Review collected by and hosted on G2.com.

Phrase is a powerful tool for setting up multiple projects and managing translations efficiently. For a small company, it saves us a considerable amount of time. Once the initial setup is complete—which required some back and forth with support—Phrase fits our use cases perfectly. There are still a few aspects that could be better explained (e.g., the difference between "Jobs" for internal use and "Orders" for external translators) or improved in terms of clarity. However, overall, the platform meets our needs quite well. Review collected by and hosted on G2.com.

To provide some context, we synchronize our translation files from GitHub repositories with multiple Phrase projects (one or more per repository). These files are all in JSON format, and we use react-intl.

Given that my focus is solely on using react-intl with JSON files synced with GitHub, there’s no way to filter the documentation to show only the relevant information. Since Phrase offers various features, navigating the documentation can be overwhelming, especially when unrelated content 'pollutes' our search/reading of the documentations.This is probably worst for us if we consider we use it more on a feature basis, which implies we have a 'blitz' of the initial configuration but then we use Phrase only few times each few weeks.

Additionally, the documentation doesn’t provide a clear mental model of how things are managed on Phrase's side, leading to misconfigurations and frustrations. For instance, it wasn’t immediately clear that Phrase maintains a single file with the translation keys, which would have helped us understand the need for tags in certain cases. We also encountered confusion with the flag that controls updates being propagated to Phrase. When we deleted translation keys in our JSON files, they reappeared in the next export to GitHub. After realizing that deletions needed to occur both in the JSON files and in Phrase, things went more smoothly, though it still feels cumbersome to handle deletions in multiple places.

Furthermore, it would be helpful if there were a way to “copy” or reuse a style guide across multiple projects. In our case, we have several GitHub repositories for the same platform, which forced us to manually replicate the style guide for each Phrase project. This was tedious and time-consuming. Additionally, we’ve noticed inconsistencies between the various orders placed with external translators. Some translators have a better understanding of how react-intl handles plurals and variables in JSON files. It would be beneficial if translators could provide feedback on the style guide when something is unclear, and if we could consistently assign the same translators to maintain uniformity in future orders.

Finally, the GitHub Sync integration errors are somewhat hidden. It would be helpful to have access to the synchronization history on a per-project basis, as it was in the past. Currently, this information is buried in the Integrations section. From a UX perspective, offering multiple ways to access this data would be beneficial. A per-project sync history view would add great value.

Small note: I was confused for quite some time, are we using Phrase Strings or Phrase TMS product... It's confusing to us what Phrase Strings even means, that title doesn't give any context on what it's used for. Review collected by and hosted on G2.com.