Your team’s quotas are determined by the subscription plan you’ve selected. This article outlines the different quotas available and explains how they are calculated.
Viewing team usage limits
To view your team’s quotas, you’ll need to have at least team admin access rights.
Click on your team avatar in the bottom-left corner and select Team settings.
View image
View image
Navigate to the Usage overview page, where you’ll see your current quotas and usage displayed.
Quotas
Lokalise enforces fixed quotas for each billing metric. If a limit is exceeded, the affected feature will stop working until usage returns within the limit or the subscription is adjusted.
Processed words
Processed words represent translation-related actions performed in Lokalise. This metric counts how many words are actively processed across your projects — for example, when you import text or manually translate texts in the visual editor.
Processed words are based on output, meaning Lokalise counts the words that are actually produced or updated in your project.
For example, if you add a key with an English source containing 5 words and then manually translate it into two target languages producing 4 words in German and 6 words in Spanish, Lokalise will count:
Processed words total: 10 words
(4 German + 6 Spanish)
A few things to note:
Lokalise remains a key-based platform, but with the new pricing plans, billing is based on processed words, not stored keys.
Key storage is unlimited meaning you can host as many words as you need.
When words are processed
Words are counted as processed when you:
When a key is deleted and then re-imported, even if the key name and value are identical to the previous version. Deleted keys are treated as new content when re-created.
Translate a key for the first time
Re-translate due to:
base language changes
AI/MT usage (workflows, tasks, automations) — see section below
API or import operations
Accept a TM suggestion with less than 100% match
Generate or modify translations in a branch
When words are not processed
Words are not counted as processed when you:
Manually edit target translations without changing the base language
Accept a TM suggestion with 100% match
Re-imports of the same content with no changes (determined by key–value comparison)
This applies only if the keys already exist in the project. If a key was deleted and then re-imported, it is treated as new content and will be counted as processed words.
This applies only to re-imports within the same project, since the word count is based on key-specific content.
Create or merge branches
Update metadata or key attributes
Copy or move keys between projects
Clear translations
Run AI LQA tasks
Execute AI-powered translation scoring
Standard AI/MT
Standard AI/MT uses machine translation engines such as Google Translate and DeepL. It is optimized for speed and high-volume translation of repetitive content where perfect tone is not essential.
Standard AI/MT operations consume two quotas:
Standard AI/MT quota — based on the input characters sent to the engine
Processed words quota — based on the output words produced by the translation
These operations do not consume any Pro AI words.
How Standard AI/MT counting works
Standard AI/MT measures input in characters. This means the text you send for translation determines how much of your Standard AI/MT quota is used.
Processed words, on the other hand, are counted from the output — the number of words generated by the MT engine.
For example, if you send a source sentence of 120 characters to be translated into two languages and the output contains:
6 words in German
8 words in Spanish
then Lokalise will count:
Standard AI/MT quota: 120 input characters × 2 target languages = 240 characters
Processed words: 6 + 8 = 14 words
Pro AI translation words
Pro AI operations consume your Pro AI words quota. They do not use the Standard AI/MT character quota.
Pro AI relies on advanced LLMs (such as ChatGPT or Claude) that support context awareness, dynamic routing, terminology handling, and tone control.
Usage is calculated based on the input words — the number of source-language words multiplied by the number of target languages. Pro AI translations also generate output, and therefore every operation consumes processed words as well.
How counting works
Pro AI words — counted based on input: the number of source language words × the number of target languages.
Processed words — counted based on output: the total number of words the model produces across all target languages.
For example, if you translate a 50-word English source into four target languages:
Pro AI words:
50 (source words) × 4 (languages) = 200 Pro AI wordsProcessed words:
Depends on the output.
For example, if the results contain:48 words in German
52 in Spanish
47 in French
50 in Italian
Then processed words = 48 + 52 + 47 + 50 = 197 processed words
When words are processed and Pro AI words are consumed
Translation activity | Does it consume Processed Words? | Does it consume Pro AI Words? | What gets counted? |
Pro AI in Automations | ✔ Yes | ✔ Yes | Processed Words = base words + generated target words. Pro AI Words = source words × number of automated target languages. |
Standard AI/MT in Automations | ✔ Yes | ✖ No | Processed Words = base words + generated target words. Standard AI/MT does not consume Pro AI quota. |
Pro AI Translation Task | ✔ Yes | ✔ Yes | Processed Words = base words + generated target words. Pro AI Words = source words × number of target languages. |
Standard AI/MT Translation Task | ✔ Yes | ✖ No | Processed Words = base words + target words generated via MT. No Pro AI quota used. |
Pro AI Workflow (scheduled) | ✔ Yes | ✔ Yes | Same as Pro AI tasks: Processed Words = base + target; Pro AI Words = source × languages. |
Standard AI/MT Workflow | ✔ Yes | ✖ No | Same as MT tasks: Processed Words only. |
AI LQA Task (review existing translations) | ✖ No | ✔ Yes | No Processed Words (LQA does not create new translations). Pro AI Words = max(source words, target words) × number of reviewed languages. |
AI Suggestions in the Editor | ✖ No | ✔ Yes | Pro AI Words = source words. Processed Words unaffected. |
Human edits to translations | ✔ Yes (if modifying target) | ✖ No | Processed Words = updated target words only. |
TM suggestion <100% match | ✔ Yes | ✖ No | Processed Words = target words inserted. |
TM suggestion 100% match | ✖ No | ✖ No | No quota used. |
Re-import identical content (no changes) | ✖ No | ✖ No | No changes → no counts. |
Import/update base language content | ✔ Yes | ✖ No | Processed Words = updated base words. |
Branch merge / metadata edits | ✖ No | ✖ No | No translation changes → no counts. |
Note on AI LQA tasks
AI LQA tasks do not consume processed words because they do not generate or modify translated content. However, they do consume Pro AI words, since the AI model evaluates and scores the existing translations without producing new target text.
Note on AI suggestions
AI suggestions do not consume any quotas. Neither processed words nor Pro AI words are counted.
Integrations
Lokalise integrates with popular tools like Figma, Contentful, Braze, GitHub, and many others helping you connect translation workflows with your existing stack.
Each plan includes a limited number of available integrations. Some integrations may be unavailable depending on your plan. Check your plan details to see which integrations are included and how many you can connect.
For setup instructions and supported platforms, see the Apps collection.
Automations
This quota controls the total number of automation rules you can create. Every time you create or remove an automation rule, the total number of automations is updated. Automation rules are counted across all team projects, and each language pair counts as a separate automation.
To manage project automations:
Go to More > Automations.
You’ll see the total number of automations created across your team.
To delete an automation rule, click Remove this rule, which decreases the number by one.
OTA
OTA (Over-the-Air) is a service provided by Lokalise that allows developers to deliver the latest translations to their mobile app users without needing to submit a new app version for approval by Apple or Google.
OTA requests are unlimited on paid plans, but data transfer is subject to plan-specific limits (with the option to top up if needed).
For more details on OTA pricing, refer to the OTA pricing FAQ.
To learn about OTA best practices and tips on optimizing usage, check out our blog post.
Projects
This quota controls how many translation projects your team can have. Each time a new project is created, the number increases.
To delete a project:
Make sure you have Manage project settings permission within the target project.
Open its Settings.
Make sure you understand what happens when the project is deleted.
Scroll to the bottom of the page and click Delete project.
Languages
Some plans include a limit on the number of target languages per team. This limit applies across all projects within the same team.
Example: If you have two projects with two target languages each, you’ve used four out of your available quota.
Higher-tier plans offer unlimited target languages. Check your plan details to confirm whether this limit applies.
To remove a language in a project:
You’ll need the Manage languages permission in that project.
Open the project.
Click the language dropdown in the top bar.
Click More next to the language name.
Click Delete.
Deleting a language will also permanently remove all related translations.
Advanced seats
This quota defines how many advanced users your team can have.
All plans include unlimited basic seats used for translators and reviewers. Only advanced seats (used by managers, developers, admins, etc.) count toward your team’s seat limit.
How it works
Users are managed at the team level. When someone is added to a project as a contributor, they automatically become a team user.
Each user has a team role (member, admin, biller, owner).
Member → may occupy basic seat.
Admin, Biller, Owner → always occupy an advanced seat, even if the user does not belong to any project
At the project level, users (called "contributors") have project-specific roles or permissions.
A user occupies a basic seat only if:
their team role is Member, and
their project permissions are limited to Translator or Reviewer.
If a user has any additional project permissions or a team role higher than Member, they occupy an advanced seat.
Managing team users
To view and manage your team’s users:
Click on your team avatar in the bottom-left corner and select Team settings.
Open the Team tab — it lists all users in the team.
Enable the Advanced seat users toggle to display only users currently occupying advanced seats.
To free up a seat, click Remove next to a user’s name. Once removed, the user immediately loses access to all projects within the team.
Freeing up advanced seats
TL;DR
You can free up an advanced seat by reducing a user’s project permissions, changing their team role to Member, or removing them from the team.
To switch a user to a basic seat, make sure their team role is Member and their project permissions are limited to Translator or Reviewer.
If your team reaches the advanced seat limit, you can free up a seat in three ways.
Reduce project permissions
You can reduce the user's project permissions so they only act as a Translator or Reviewer, provided they have the Member role within the team.
Enable the Advanced seat users toggle on the Team members page.
Find the user and click the X projects link next to their name.
A menu will appear showing the projects where the user participates.
Click a project name to open the project editor.
Go to the Contributors page and update the user’s permissions to Translator or Reviewer.
Once the user no longer has additional permissions, they will move from an advanced seat to a basic seat.
Note on groups and advanced seats
If a group has elevated permissions and the user is a member of that group, the user will occupy an advanced seat once the group has been added to at least one project.
Users can also occupy advanced seats through groups. Groups are created on team level, and can then be added to projects and assigned permissions, similar to individual contributors.
If a group is added to a project with permissions beyond Translator or Reviewer, all users in that group will occupy advanced seats. For example, if a group with elevated permissions contains two users and is added to one or more projects, both users will count toward the advanced seat quota.
To check whether a user occupies an advanced seat through a group:
Go to the Team members page and click the X projects link next to the user’s name.
Open the project from the list.
In the Contributors tab, find the Groups section.
You'll see the group's permissions.
In the example above, every group member will have Manager access within the project meaning they'll occupy advanced seats.
Expand the group to view its members.
Note however, that if a user is added to the same project both individually and as part of a group, the user’s individual permissions override the group permissions. For example, if a user is assigned the Translator role directly in a project but also belongs to a group with elevated permissions in that project, their effective permissions remain Translator, and they will not occupy an advanced seat.
Change the user’s team role
If the user does not need elevated team permissions, you can change their team role to Member. Users with the Member role can occupy a basic seat, but only if their project permissions are limited to Translator or Reviewer.
If the user still has advanced permissions in any project, they will continue to occupy an advanced seat.
Remove the user from the team
Click Remove next to the user’s name on the Team members page. This immediately removes the user from the team and revokes their access to all projects within it.
Use this option only if the user no longer needs access to the team.
What's not limited
Some features are unlimited across all plans. They don’t count toward your quota:
Stored content — unlimited keys and hosted words. You can store as much content as you need; billing is based only on processed words.
Basic seats — unlimited translators and reviewers. Only advanced seats (managers, developers, etc.) count toward seat limits.
Over-the-air (OTA) delivery — unlimited requests on paid plans. Data transfer may be subject to plan-specific limits.