Your team’s quotas are determined by the subscription plan you’ve selected. This article explains the different usage limits and quotas and 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
What happens when you reach a quota
When a quota is reached, the affected feature may stop accepting additional usage until capacity becomes available again, you purchase an add-on where available, or upgrade your plan.
For resource-based limits such as advanced seats and integrations, you’ll need to free up capacity or upgrade before adding more.
Some limits, such as projects and languages, are handled more flexibly and may trigger notifications or require a plan adjustment.
Processed words
Processed words represent translation-related operations performed in Lokalise. This metric counts words in base and target language content when a countable operation creates or updates that content.
For example, if you add a key with an English source containing 5 words and then translate it into two target languages, producing 4 words in German and 6 words in Spanish, Lokalise will count:
Processed words total: 15 words
(5 English + 4 German + 6 Spanish)
A few things to note:
Lokalise remains a key-based platform, but processed word usage is based on translation-related operations rather than the number of stored keys.
Key and hosted word storage is unlimited on paid plans. Simply storing existing content does not consume your processed words allowance.
When words are processed
Words are counted as processed when you:
Create or update translation content through the API
Delete and then re-import a key, 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 the section below
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 an existing target translation in the translation editor without changing the base language
Accept a TM suggestion with 100% match
Re-import 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 fast, high-volume translation.
Standard AI/MT usage can affect two separate metrics:
Standard AI/MT quota — measured in characters sent for translation
Processed words — measured from countable translation content created or updated by the operation
On the Explorer plan, Standard AI/MT has a separate usage allowance. On Growth and higher plans, Standard AI/MT usage is unlimited.
Standard AI/MT operations do not consume Pro AI words.
How Standard AI/MT counting works
The Standard AI/MT quota is based on the number of source (base) characters translated. When content is translated into multiple target languages, the source character count applies to each target language.
For example, if you translate 120 source characters into 2 target languages, Standard AI/MT usage is:
120 × 2 = 240 characters
If the resulting translations contain 6 words in German and 8 words in Spanish, the operation also adds 14 processed words for those target translations.
Pro AI translated words
Pro AI relies on advanced LLMs such as ChatGPT and Claude and supports features such as context awareness, dynamic routing, terminology handling, and tone control.
Your Pro AI translated words allowance is used by Pro AI translation tasks, automations, workflows, and AI LQA tasks.
Pro AI translation operations can also consume processed words when they create or update translation content. Pro AI usage does not consume your Standard AI/MT allowance.
How counting works
For Pro AI translation tasks, automations, and workflows, Pro AI usage is based on the number of source-language words multiplied by the number of target languages.
For example, if you translate 50 source words into 4 target languages:
Pro AI translated words: 50 × 4 = 200 words
Processed words are tracked separately and depend on the translation content created or updated by the operation.
For example, if the existing source content is translated into four target languages and produces:
German → 48 words
Spanish → 52 words
French → 47 words
Italian → 50 words
the generated target translations add 197 processed words.
AI LQA uses the same Pro AI allowance but works differently: it evaluates existing source and target content instead of creating translations. Therefore, AI LQA consumes Pro AI words but does not consume processed words.
When processed words and Pro AI translated words are consumed
Translation activity | Processed words | Pro AI translated words | What gets counted? |
Pro AI in Automations | ✔ Yes | ✔ Yes | Translation content created or updated by Pro AI counts as processed words. Pro AI usage is calculated separately. |
Pro AI Translation Task | ✔ Yes | ✔ Yes | Translation content created or updated by Pro AI counts as processed words. Pro AI usage is calculated separately. |
Pro AI Workflow | ✔ Yes | ✔ Yes | Translation content created or updated by Pro AI counts as processed words. Pro AI usage is calculated separately. |
AI LQA task | ✖ No | ✔ Yes | Existing translations are evaluated without creating or modifying translation content. |
Manual edit of an existing target translation without a base-language change | ✖ No | ✖ No | No applicable usage is consumed. |
First manual translation of an empty target | ✔ Yes | ✖ No | The newly created target translation counts as processed words. |
TM suggestion below 100% match | ✔ Yes | ✖ No | The inserted target translation counts as processed words. |
TM suggestion with a 100% match | ✖ No | ✖ No | No applicable usage is consumed. |
Re-import identical content with no changes | ✖ No | ✖ No | No translation changes are made. |
Import or update base-language content | ✔ Yes | ✖ No | The created or updated base-language content counts as processed words. |
Branch merge or metadata edits | ✖ No | ✖ No | No translation content is created or updated. |
Integrations
Lokalise integrates with popular tools like Figma, Contentful, Braze, GitHub, and many others, helping you connect translation workflows with your existing stack.
Depending on your plan, you can use a set number of integrations or unlimited integrations. Some integrations do not count toward this quota, while others 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 unique languages enabled across your team. This quota includes both base and target languages across all projects. Custom languages are excluded from the count.
The same language used in multiple projects is counted only once.
For example, if two projects both use English as the base language and German and Spanish as target languages, your team uses 3 languages toward the quota.
Higher-tier plans offer unlimited 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 three dots 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 standard 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 standard 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 standard 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 standard 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 standard 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 standard 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 resources are unlimited on paid plans or don’t count toward specific usage quotas:
Stored content — unlimited keys and hosted words. Simply storing content does not consume your processed words allowance.
Standard seats — unlimited seats for translators and reviewers. Only advanced seats count toward the advanced seat limit.
Over-the-air (OTA) requests — unlimited on paid plans. Data transfer is subject to plan-specific limits.