Google Cloud Translation, Amazon Translate, Azure Translator, and DeepL are all worth evaluating for Flutter and React apps, but there is no universal cheapest choice. Compare the same expected character volume, free-tier eligibility, required features, language coverage, and region-specific rates—and keep provider credentials out of public client code.
Translation API pricing at a glance
The figures below are from the vendors’ official pricing pages, accessed in 2026. Rates, offers, and availability can change; check the provider’s calculator for your region, billing currency, and account before estimating production costs.
As an Amazon Associate I earn from qualifying purchases.
| Provider | Published allowance or rate | What to verify |
|---|---|---|
| Google Cloud Translation | For NMT text translation, the first 500,000 characters per month receive a credit of up to $10. The pricing page lists $20 per million characters above that level. | The credit is shared by Cloud Translation Basic and Advanced, does not roll over, and does not apply to formatted document translation. Other methods and models may have separate meters. Google Cloud pricing. |
| Amazon Translate | Standard text translation is listed at $15 per million characters. The free tier lists two million characters per month for 12 months from the first translation request. | The monthly allowance does not roll over and offer restrictions apply. Confirm eligibility and the applicable terms. AWS pricing. |
| Azure Translator | F0 lists two million characters per month for standard translation and custom translation training. | The retrieved pricing page showed the S1 per-million-character cells as blank, so a paid rate cannot be compared from that page. Check the live regional price before budgeting. Azure pricing. |
| DeepL | DeepL provides developer API documentation and advertises a JavaScript SDK; the developer page does not state current API subscription prices. | Verify current plans and rates directly before including DeepL in a cost comparison. DeepL for Developers. |
How to choose the affordable option
Estimate translated characters, not just users
Forecast the source text sent each month, how many target languages each source is translated into, and peak usage. Count characters consistently across providers. A modest user base can still generate substantial volume if each piece of content is translated into several languages or repeatedly sent for translation.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Match the price meter to the features
Standard text translation is not necessarily priced like formatted documents, custom models, or other advanced methods. Google’s pricing page separates translation methods and models; check each provider’s current pricing for any feature your app needs, including document workflows, glossaries, language detection, or custom translation.
#1 Best Overall
Compare free allowances on equal terms
Google’s monthly credit and Azure’s F0 allowance are presented as monthly benefits, while Amazon’s listed free tier is limited to the first 12 months after the first translation request. Include eligibility, expiry, rollover rules, and likely paid usage in the same estimate; a free tier is not a reliable long-term cost forecast.
Validate language coverage and output quality
Check that each candidate supports the source and target language pairs your app actually needs. Then test representative product strings, including short UI labels, plural forms, and context-sensitive text, with human review. The pricing information here does not establish a quality winner, so do not select on an assumed ranking.
Rank #2
Using translation APIs safely in Flutter and React
Flutter mobile apps and React browser apps can call hosted translation services, but a provider secret embedded in a distributed app or public browser bundle should be treated as exposed. Put provider authentication behind a trusted server or a suitably protected backend boundary. The app can send translation requests to that service, which applies authentication, quotas, and any privacy controls before calling the provider.
Plan for network latency, retries, caching, and rate limits. Avoid blindly retrying failed requests: repeated calls can increase latency and may add billable usage. Review what text is sent to an external service, especially if users may submit personal or confidential content.
Check integration details for your stack
Confirm authentication, request and response formats, encoding, and SDK status in the current vendor documentation. Google documents REST access, and DeepL advertises a JavaScript SDK. The available documentation does not establish official Flutter or React SDK support across all four providers; an API being usable from an app does not mean a vendor maintains a framework-specific SDK.
Quick Recap
Best Value
A practical cost-comparison workflow
- Define one representative workload. Estimate monthly source characters, target languages per source, request peaks, and whether the app translates text or documents.
- List required capabilities. Identify language pairs and any needs such as glossaries, custom models, or document translation, then check their support and billing separately.
- Apply each provider’s allowance and rate. Use the relevant region and account offer; distinguish recurring monthly allowances from time-limited promotions and credits.
- Verify the implementation path. Review current authentication, REST or SDK options, quotas, and backend requirements before committing to a client integration.
- Recalculate before launch. Pricing and service terms change, so confirm the provider’s current calculator and pricing page for the production region and expected volume.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
