Best AI for translation
This category exposes an architectural gap between two components: the model with Persian registered in its official language specification cannot be purchased or deployed directly, and the model you can run on your own infrastructure does not name Persian anywhere in its specification. The table below documents that gap, not which model produces the more elegant sentence.
- Seven candidates, five active ranked rows
- Openness criterion weighted 30 of 100
- A dedicated Iran-access column
Last checked: This is a reference page. It is re-checked against the vendor sources and updated when a new version ships. Change log
Where each tool's score comes from
The ring below is the same set of weights printed in the table headers further down.
- Persian in specification 35
- Licence openness 30
- Language coverage count 25
- Access from Iran 10
We chose these weights, and that is the only judgment call in the table. Weight them differently and the order changes.
Today ranking, built from each vendor language list and licence
The Persian column reports registration status only: whether the vendor lists Persian for that model, not translation output quality. A model whose vendor publishes no language list at all stays "unverified" in this column.
| Rank | Tool | Score | Persian in specification 35 | Licence openness 30 | Language coverage count 25 | Access from Iran 10 |
|---|---|---|---|---|---|---|
| 1 | Command A Translate Current pick | 70.0 | 2/2 | 0/3 | 23 languages Source: docs.cohere.com | blocked / no working route |
| 2 | Aya Expanse 32B | 67.5 | 1/2 | 1/3 | 23 languages Source: docs.cohere.com | blocked / no working route |
| 3 | Command A Reasoning | 35.0 | not verified | 0/3 | 23 languages Source: docs.cohere.com | blocked / no working route |
| 4 | Llama 4 Maverick | 30.0 | 0/2 | 2/3 | 12 languages Source: huggingface.co | not verified |
| 5 | Llama 4 Scout | 30.0 | 0/2 | 2/3 | 12 languages Source: huggingface.co | not verified |
An empty cell means we could not verify that number, not that the tool scored zero.
Behind each number
Every judged score in this table carries a written reason, and the Iran column says how it was checked. Those two are open here. The measurement trail behind each number, which row of which leaderboard and on how many votes, opens under the model it belongs to.
1 Command A Translate
Persian in specification 2/2 Cohere's documentation enumerates 23 supported languages one by one, with Persian as the last entry on that list; the same document designates this version as Cohere's official machine-translation infrastructure. Both the specification listing and the vendor declaration are present.
Licence openness 0/3 No weights are published to the public; the only integration surface is Cohere's proprietary API.
Access from Iran blocked / no working route The classification here traces to a legal artifact, not a network measurement: Cohere's SaaS agreement names Iran explicitly inside its Restricted Location definition and rules out customer access from that jurisdiction. Extracted from the contract text, not from a connectivity probe.
2 Aya Expanse 32B
Persian in specification 1/2 The model-card specification enumerates 23 supported languages, Persian included. Cohere own classification for this model is "multilingual research", not "translation", and that classification is what keeps it from reaching level two on this metric.
Licence openness 1/3 Model weights are provisioned on Hugging Face, but the governing licence is CC BY-NC 4.0 with an acceptable-use addendum; the NC clause places commercial production deployment outside the permitted envelope.
Access from Iran blocked / no working route The access restriction is defined at the contract layer, not the network layer: Cohere own commercial SaaS agreement names Iran in its Restricted Location clause and bars customer access to the Services from that location. This is derived from the contract text; no independent network-traffic measurement has been run.
3 Command A Reasoning
Licence openness 0/3 No weights are provisioned openly for this release; the only integration surface is Cohere own API.
Access from Iran blocked / no working route The access restriction is defined at the contract layer, not the network layer: Cohere own commercial SaaS agreement names Iran in its Restricted Location clause and bars customer access to the Services from that location. This is derived from the contract text; no independent network-traffic measurement has been run.
4 Llama 4 Maverick
Persian in specification 0/2 The published specification for Llama 4 defines a closed twelve-language coverage envelope: Arabic, English, French, German, Hindi, Indonesian, Italian, Portuguese, Spanish, Tagalog, Thai and Vietnamese. Persian sits outside this coverage, and the list is not left open with an including clause — this is a specification boundary, not an estimate. Turkish is outside the boundary as well.
Licence openness 2/3 The weights are publicly released and the Llama 4 licence authorizes commercial deployment, but the licence is a proprietary Meta specification rather than a recognized open standard: it embeds a ceiling of 700 million monthly active users and specifies mandatory display of a Built with Llama notice as a compliance requirement.
5 Llama 4 Scout
Persian in specification 0/2 The published specification for Llama 4 defines a closed twelve-language coverage envelope: Arabic, English, French, German, Hindi, Indonesian, Italian, Portuguese, Spanish, Tagalog, Thai and Vietnamese. Persian sits outside this coverage, and the list is not left open with an including clause — this is a specification boundary, not an estimate. Turkish is outside the boundary as well.
Licence openness 2/3 The weights are publicly released and the Llama 4 licence authorizes commercial deployment, but the licence is a proprietary Meta specification rather than a recognized open standard: it embeds a ceiling of 700 million monthly active users and specifies mandatory display of a Built with Llama notice as a compliance requirement.
Not enough verified data to rank
These are real tools we track, but more than half of their criteria have no verified number yet, so ranking them would be a guess.
- Command A+
- Mistral Large 3
How this ranking is calculated
Every criterion below has a weight and a source. Change a weight and the whole table recomputes. There is no hand-placed position anywhere in this hub.
| Criterion | Weight | Evidence |
|---|---|---|
| Persian in specification | 35 | defined scale, with a written reason per assignmentTranslation output is itself a target language; a model that does not register Persian in its specification is an operational guess for Persian text, not a dependable component |
| Licence openness | 30 | defined scale, with a written reason per assignmentThis criterion carries 30 points here and nowhere else in this reference, because in Iran the unusable layer of the supply chain is precisely the hosted API |
| Language coverage count | 25 | vendor stated specificationCounted only where the vendor publishes a complete language list or states a definite figure; a partial list is not counted |
| Access from Iran | 10 | our access column, with its method statedWeighted low because the primary discussion of this axis is documented on the dedicated "AI in Iran" page, though it is not zero |
The two components this architecture separates
Cohere carries a model named Command A Translate, and its technical documentation explicitly labels it as its own dedicated machine translation model. The same documentation lists all 23 supported languages one at a time: English, French, Spanish, Italian, German, Portuguese, Japanese, Korean, Chinese, Arabic, Russian, Polish, Turkish, Vietnamese, Dutch, Czech, Indonesian, Ukrainian, Romanian, Greek, Hindi, Hebrew and Persian.
All four languages this site publishes in sit inside that same 23-entry list. For any project deploying a bilingual or multilingual site, this is the most precise piece of documentation on language coverage anywhere in this reference.
On the other side of the architecture, Meta ships Llama 4 with open weights, and its licence permits commercial use — a component that can be deployed on internal infrastructure and whose output can be sold. Its technical specification carries a closed twelve-language list: Arabic, English, French, German, Hindi, Indonesian, Italian, Portuguese, Spanish, Tagalog, Thai and Vietnamese. No Persian. No Turkish. Meta does not leave the list open with an "including," so this is a closed, definite specification.
The ranking axis for this category is therefore not output quality. It is whether your target language is registered in the model specification, and whether the access path is open at all.
The context-window inversion in these two architectures
Command A Translate has an operating window of 8,000 tokens — the shortest capacity in this entire catalogue, shorter than any other component recorded here. Llama 4 Scout, on the other end, carries a 10-million-token window, the longest recorded value.
So the component that recognizes Persian has the processing capacity of a few pages, while the component that does not recognize Persian accepts an entire book in a single call. This is not an architectural coincidence: a dedicated translation model is engineered for the sentence and paragraph unit, not for the full document.
The operational consequence of this inversion is undocumented elsewhere: with a dedicated translation model, a site translation pipeline has to run page by page, not in a single unified pass. If your operational requirement is passing a long document through in one call, you are in fact selecting a component that was not engineered for that workload, and that choice needs to be made deliberately at the project-architecture stage.
Why licence openness carries 30 points in this category
In the other categories of this reference, licence openness is a secondary component in the scoring architecture. Not in this one.
The reason is direct: for a user based in Iran, the exact layer of the infrastructure that is unusable in practice is the hosted API. Cohere own commercial agreement explicitly names Iran in its Restricted Location definition. So a component whose weights are published under a licence that permits commercial use is a genuinely operational part of this architecture; the rest are documentation about a tool that cannot be deployed.
This same criterion exposes a distinction that a binary open/not-open flag hides. Aya Expanse publishes open weights but operates under a CC BY-NC licence — meaning that using it for a paid client-site translation job puts you in breach. Llama 4 permits commercial use but under Meta own proprietary licence, with a 700-million monthly-active-user ceiling and a mandatory "Built with Llama" notice requirement. Mistral Large 3 ships under Apache 2.0, the freest licence in this entire table, but does not register Persian in its specification.
Four criteria deliberately excluded from this rubric
A translation-quality score. Cohere describes Command A Translate as its "state-of-the-art machine translation model" without publishing any citable figure. No other vendor publishes one either. A column with no value for any candidate has no place in the rubric architecture.
Price. Of the seven candidates in this table, only two carry a published price. Cohere prints no rate for its current-generation models, Mistral publishes no model-level rate at all, and Meta ships weights with no attached price. A column with only two filled cells pulls the other five candidates down in rank for no technical reason.
Translation direction. Translation quality is not symmetric: the Persian-to-English path and the English-to-Persian path are not operationally equivalent, and every professional translator knows this. No vendor in this reference publishes separate data per direction, so this page makes no claim about it either. A language list is a set, not a directional pair.
And the context window, a criterion that was provisioned into the rubric on a trial basis and then removed — we document the reason here because it applies to future categories too. The ranking engine normalizes every numeric column between the candidates minimum and maximum. Here the minimum window is 8,000 tokens and the maximum is 10 million, a gap of three orders of magnitude. The practical result was that 256,000 tokens scored 0.4 out of a possible 15, and 128,000 tokens scored 0.2, while the real-world gap between 8,000 and 256,000 is a 32-fold difference. A column that renders a 32-fold difference as "0.4 versus 0.2" is not measuring that difference; it produces a systematic error. That is why the figure was removed from the table while the analysis remained in the prose above.
Two unranked rows in this architecture
Two candidates sit below the table because the ranking engine could not compute a rank for them, both for the same reason: the vendor has not published a language list for that specific model.
One is Command A+, Cohere own flagship product line. Cohere documentation records a "world-class translation capability" claim for this model but publishes no language list and no definite figure for it. There is a performance claim, with no data behind it to cite.
The other is Mistral Large 3, which carries the freest licence in this entire table: Apache 2.0, open weights, full commercial-use permission — exactly the property this category weights second highest. Yet Mistral publishes neither a language list nor a country list for Large 3, and the partial list it does provide is explicitly stated as non-exhaustive. The model that was the best licence option in this table was excluded from ranking purely for lack of these two documents.
This is not hidden, because that transparency is what makes the table trustworthy: a candidate with no documented evidence gets no rank, even where our working hypothesis is that its performance is good.
What this table does not measure
Every cell in the Persian column on this page states only that the vendor registered that language in its specification. No actual output has been read or evaluated.
This is the same methodological limit the voice-generation category carries, and it is the honest boundary of this entire methodology. We read and cite officially published lists; assessing how natural these models Persian output actually reads is a separate task, and we make no claim to have done it.
When our top pick is not the right fit
- If your workload runs only between English and European languages, this ranking is not optimized for you: the lower rows perform strongly in exactly those languages and rank lower solely for lacking Persian.
- If your operational requirement is passing a long document through in a single call, none of the top rows have the capacity for it, and you need the large-window models, on the understanding that they have not registered Persian in their specification.
- If you need certified or sworn translation, no component on this page is engineered for that task. That requirement needs a registered human translator, not a model.
Known weaknesses and limits
- The Persian column is read from each vendor official published list, not from evaluating real output. Translation quality has not been measured.
- Price has no dedicated column in this rubric, because only two of seven candidates carry a published rate.
- Translation direction is not measured. A language list is a set that indicates a pair is possible, not that both directions of that pair carry equal quality.
- The Iran-access column is read from each vendor contract text and stated policy, not from an actual network test conducted from inside Iran.
Technical verdict
If your infrastructure is multilingual and Persian, Arabic and Turkish all appear in your workload, Command A Translate is the only component that registers all three in its specification; account for the fact that its operating window is 8,000 tokens and that no official purchase route exists from Iran. If your operational requirement is local deployment, Aya Expanse covers Persian but its licence does not permit commercial use — that contradiction needs to be resolved in the project decision architecture before the build starts, not partway through it.
Frequently raised questions, with documented answers
What is the best AI for Persian translation
Based on the documentation on this page, Cohere Command A Translate, because it is the only component whose vendor both labels it a translation model and registers Persian in its 23-language specification. It carries two operational constraints also recorded in this table: its window is 8,000 tokens, and the Cohere commercial agreement explicitly names Iran.
Which translation model can be deployed on internal infrastructure
Three components. Aya Expanse 32B, which registers Persian but ships under CC BY-NC and does not permit commercial use; Llama 4, which has a commercial licence but no Persian in its twelve-language list; and Mistral Large 3, which ships under Apache 2.0 and whose language list does not name Persian.
Do these models translate Persian into Arabic
Cohere 23-language list covers both, so that pair falls within its documented coverage. But a language list is a set, not a quality guarantee for a specific pair, and no vendor publishes a separate figure per translation pair.
How good is the Persian output these models produce
That data is not available and we make no claim about it. This table only reports whether the vendor registered the language in that model specification. Evaluating quality requires reading and scoring actual output, which has not been done.
Which component should be selected to translate an entire site
With a dedicated translation model, the pipeline needs to run page by page, since an 8,000-token window does not have the capacity for more than a few pages. If the operational requirement is passing a long document through in a single call, the component being selected was not engineered for translation and has not registered Persian in its specification either.
Translating and localizing your site infrastructure is part of
our site translation service