How FluentC keeps translation costs down
Local caching, translation memory and batched requests mean the same text is not translated twice. FluentC is priced per site, per language, not per word.
By FluentC1 min read
Translation costs grow with the amount of content you have and with how often it gets translated again. FluentC works on the second part: it reuses what has already been translated.
Reuse what is already translated
- Local caching. Translations are stored locally, so FluentC does not need to call an external translation service again for content it already has. See how FluentC caches translations.
- Translation memory. FluentC saves previously translated phrases and sentences. Once a phrase has been translated, it can be reused across your site instead of being translated again.
Send fewer requests
Many translation services charge by the number of API calls. Caching and translation memory reduce how many calls are needed. FluentC also supports batch processing, so several phrases can be translated in one API call.
In the WordPress plugin, only the necessary translation data is sent, and less data moves between your server and the translation service. On a high-traffic site, that lowers bandwidth use.
Keep translations up to date
FluentC's translation management tools make it easier to maintain and update translations. Keeping them organized and current means you do not have to re-translate content that has gone out of date.
Sites that benefit most are the ones with a lot to reuse: a store with many similar products, or a corporate site that updates often.
Pricing
FluentC charges a flat price per site, per language, not per word. Current plans are on the pricing page.
