Usage and costs
Linguana separates translation usage, hosted build time, and running-preview time. Check the pricing page for current Free, Pro, Team, and Enterprise plans and allowances. It reads the public pricing catalog, as does its Markdown representation. Your checkout or existing subscription determines your commercial terms.
What counts as a translated character?
Translation usage counts newly generated, accepted target-language output using Unicode code points. It counts output for each target language, rather than source length or provider tokens. Exact compatible translation-memory reuse does not create another accepted-character charge or consume the translation allowance. Rejected output is not committed as accepted-character usage. Accepted new translations count even before publication.
Local extraction and local builds use no hosted build minutes. New translations requested during a local preview still count as translation work; cached or exact-memory results do not count again.
Hosted builds and running previews
Hosted builds and running previews have separate usage meters and allowances. The current hosted-usage workflow reserves capacity before starting work and settles measured usage afterward. Waiting in the queue is different from a running build or preview. A local build does not become a hosted build simply because it takes time.
Review the maximum usage shown in the dashboard before starting a hosted build. A preview can keep consuming its own runtime allowance after the build finishes, until the preview stops. See Local preview for the local development workflow.
Included allowances and additional usage
For organizations using current hosted-usage pricing, the usage ledger separates included and additional quantities for translated characters, hosted builds, and running previews. Reservations account for authorized work that has not finished yet.
Additional usage requires authorization and resource spending limits. If the included allowance is exhausted and additional usage is disabled, new work is rejected. Free organizations cannot authorize paid overages. Resource, organization, and configured project limits can also stop a request before it starts.
These controls limit authorized usage; they do not turn a resource estimate into a final invoice. Subscription fees, taxes, discounts, adjustments, and your contract can affect the amount billed. Existing subscriptions retain their agreed terms; changing the public catalog does not by itself migrate a subscription.
Verify costs before expanding a translation
- Run local extraction and inspect the text the compiler found.
- Choose the target languages and review the translation estimate.
- Check your current subscription, included allowances, reservations, and additional-usage settings in the dashboard.
- Translate, review, and publish deliberately. Restoring an earlier catalog changes what users see; it does not undo translation work already performed.
- Review invoices through the billing controls available to your organization owner.
The pricing estimator covers translation usage. Account for hosted build and preview usage separately when evaluating a workflow.
Usage and billing
Open Usage & billing:
- Usage shows included and additional consumption, reservations, and spending limits.
- Plans compares available plans and reviews changes before checkout or a subscription change.
- Billing shows subscription status, payment methods, and invoices. Payment method updates open Dodo Payments' secure portal.
Organization spending limits authorize additional usage. A limit of $0 blocks additional usage even when its switch is on. Subscription fees, tax, discounts, and provider adjustments are separate from these usage limits. Per-project limits further restrict work. Already-published languages remain available when new work stops.
The legacy gross translation-value display measures accepted output at the ledger rate before included allowances. It is distinct from additional usage charges. Preserve that distinction when comparing older exports.
Subscription changes
An upgrade requests an immediate prorated change. A failed upgrade payment retains the current plan. A downgrade takes effect at renewal. Cancellation normally ends the plan at the current period's end. Keep plan removes that scheduled cancellation.
The verified provider webhook synchronizes access. Returning from checkout does not grant access by itself.
Continue with Automate translations in CI.
Understand translation usage, hosted builds, running previews, allowances, and additional spending limits.
Last updated November 17, 2026
Did this page get you to a working result?