Azure AI Translator offers a free tier that appears generous compared to some competitors, but the pay-as-you-go pricing can surprise developers as usage scales. Here is a breakdown of the actual costs and limits, verified against the official pricing page as of 24 September 2026.
The short version
Azure AI Translator's S1 (pay-as-you-go) tier costs $10 per 1 million characters for standard text translation. S1 and the free F0 tier are two separate Azure resources and cannot be combined. If you use S1, you pay from the first character, with no free volume included. The free 2 million characters per month are only available through a separate F0 resource, which is throttled: requests above 2 million characters are refused or throttled. A production workload above 2 million characters per month runs on S1 and pays for the full volume, not just the portion above 2 million.
Azure AI Translator pricing breakdown
| Tier | Price per 1M characters | Free quota (per month) | Expiration |
|---|---|---|---|
| F0 (Free) | N/A | 2 million characters | No expiration |
| S1 (Pay-as-you-go) | $10 | None | N/A |
Source: Azure AI Translator pricing page, verified 24 September 2026.
The 50,000-character request limit
Each translation request is capped at 50,000 characters across all target languages combined. If you need to translate a longer document, you must split it into multiple requests. This adds overhead for batch processing large files, since your application needs to handle chunking and reassembly on its own.
Character counting: what actually counts
Azure counts every Unicode code point as one character. This includes the text itself, HTML and XML tags, individual letters, punctuation, spaces, and whitespace. If you send a request with format=html, all those HTML tags count toward billing.
This is the same behavior as Google Translate API. However, AWS Translate does not count HTML tags toward the character total when you use the appropriate content-type setting. If you work with HTML-heavy content, Azure's pricing can become more expensive than AWS for the same raw text volume.
Azure vs Langbly: cost comparison
Langbly charges $5 per 1 million characters after the first 500,000 free characters per month, with no expiration date and no base fee. Langbly is drop-in compatible with the Google Translate v2 API. HTML tags count toward the total if you use format=html, just like Azure and Google, but not if you use format=text. Note: Azure S1 has no free volume, so costs start from character 1. If you only want to experiment within 2 million characters per month, you can use the separate Azure F0 resource for free, but that is not a production solution.
| Volume (characters/month) | Azure S1 (no free volume) | Langbly (includes 500K free) |
|---|---|---|
| 1 million | $10.00 | $2.50 |
| 5 million | $50.00 | $22.50 (4.5M charged at $5/M) |
| 20 million | $200.00 | $97.50 (19.5M charged at $5/M) |
| 100 million | $1,000.00 | $497.50 (99.5M charged at $5/M) |
Staying under 2 million characters per month and using the free F0 resource instead of S1 is a valid option for evaluation, low-volume tools, or side projects, but it is a hard cap with no overage, not a discount on production pricing.
Frequently asked questions
Does the Azure free tier expire?
No. The F0 tier provides 2 million characters per month permanently, as is standard for Azure free tiers. Unlike AWS Translate's 12-month free tier, Azure's does not have a time limit.
Can I combine the free tier with pay-as-you-go?
No. F0 and S1 are separate Azure resources. You use one or the other: F0 for free, capped at 2 million characters per month with no overage, or S1 for pay-as-you-go at $10 per million characters from the first character. You cannot mix them on one resource.
Is the character limit per request or total?
Per request. You can send unlimited total characters per month (subject to billing), but each individual request cannot exceed 50,000 characters across all target languages.
Does Langbly support Azure's API format?
Langbly is drop-in compatible with the Google Translate v2 API, not directly with Azure's API. You would need to adjust your integration if you are currently using Azure's SDK or endpoint.
Bottom line
Azure's free F0 resource is genuinely permanent and generous for staying under 2 million characters per month, but it is a separate, capped resource, not a discount that carries into production usage. Any workload that needs more runs on S1, paying $10 per million characters from the first character, twice Langbly's $5 per million rate. For HTML-heavy workloads, Azure's tag-inclusive character counting also costs more than AWS Translate's tag-exclusion rule.