Phrase QPS scores each translated segment from 0 to 100 inside Phrase, so teams can route low scores to post-editing or LQA before anything ships. Loqalit checks the rendered product in every language after strings are deployed, and posts accepted fixes back into Phrase as comments with a screenshot. They work at different stages, and they work best together.
Last reviewed:October 2026
Numbers in brackets link to the source for each claim about the other product.
| Phrase quality features | Loqalit | |
|---|---|---|
| Where it runs | Inside Phrase TMS and Phrase Strings, on translated segments[1] | On your live or staging pages, in a real browser |
| When | At translation time. Strings scores a translation when it is saved[1]. | After deployment, on a schedule you set |
| Score | QPS predicts an MQM-derived score from 0 to 100 per segment[1][2] | An MQM category and severity per finding. Page scores from 0 to 100, normalized per 1,000 words. |
| Workflow | Route segments to LQA or post-editing by QPS threshold[1][2] | Accepted fixes are posted to your Phrase project as comments with a screenshot |
| Rule-based checks | Tags, placeholders and UI length overruns[2] | Placeholders, number formats and missing required disclosure text, on the rendered page |
| What it sees | Translated segments[4] | The page your users see: overflow, text that never entered the TMS, mixed-language screens, wrong context |
| Human review step | An LQA workflow step with the DQF-MQM typology[5] | Every fix is a proposal a person approves |
Keep QPS on for every segment. Add Loqalit after release, and accepted fixes come back to the Phrase string your translators already work in.
No. QPS scores segments inside Phrase before anything ships. Loqalit checks the rendered product after release. Keep QPS on for segments, and add Loqalit for the page.
When you accept a fix in Loqalit, it is posted to your Phrase project as a comment with a screenshot, so translators see the problem and the proposed fix in context.
No. They keep working in Phrase. Accepted fixes arrive there as comments with a screenshot.
Phrase deprecated Auto LQA on June 30, 2026 and pointed to Quality Profiles. Its support docs say Quality Profiles were due to be deprecated on October 20, 2026, with Content Groups as the successor. See the sources below.
Claims about other products come from their own public pages. Product names belong to their owners.
We scan your live site in up to 3 languages and email you a PDF with screenshots, MQM severities and suggested fixes.