питання
ερωτήσεις
سوالات
Frequently Asked Questions
What folks usually want to know about the POEditor translation management system and localization platform
POEditor
POEditor is a translation management system (TMS) for collaboratively localizing software strings across many file formats, with an API, an official MCP server, and integrations for wiring it into a build pipeline. It's built to work for both technical and non-technical users — developers can automate strings in and out via the API, Git integrations, or MCP, while translators and other non-technical contributors can do everything they need directly in the browser-based editor, with no code or file handling required.
Teams use POEditor to translate software and other digital assets — apps, websites, themes, plugins, games, and more — mixing human and AI translation, and to reduce manual work by automating steps in the localization workflow.
Register for free — no payment info required. You can immediately manage up to 1,000 strings, create unlimited projects, and add up to 5 contributors. A 10-day free trial (raising your limit to 30,000 strings) starts automatically on your first project. Moving to a paid plan is just as low-friction: no credit card required to sign up, and no sales call needed to subscribe — upgrading is self-serve from Account Settings.
No — POEditor doesn't offer a self-hosted/on-premise copy. It's used as a service, so you benefit from continuous improvement and support without managing your own instance.
POEditor doesn't count words or characters — it counts strings. In an account (or organization), the string count is the sum of terms and translations across all hosted projects: each term counts once, and each language's completed translations add on top. For example, one project with 100 terms, fully translated into one language and 50% into a second, comes to 250 strings (100 terms + 100 for the fully translated language + 50 for the half-translated one). Translating in someone else's project never counts against your own limit — it counts against the project owner's account.
File a request for free localization of an OSI-approved open-source project directly from the project’s Settings page.
POEditor is ISO 27001 certified and GDPR compliant, hosted on its own physical infrastructure within the EU (no third-party clouds), with TLS in transit and encryption at rest for sensitive data, and a DPA available on request.
You connect your preferred LLM provider — OpenAI, Anthropic, or Google — with your own API key, or a custom model. POEditor also integrates with Azure AI and Amazon Bedrock. You own the data, the cost, and the model choice — POEditor never marks up tokens.
No. When you trigger an AI translation, the source string is sent directly to the provider you chose using your own API key — POEditor itself never trains on your data.
POEditor doesn't manage or centralize the individual localization projects hosted on the platform, and doesn't hire translators or connect them with clients directly. To join a specific project, you'd need to be invited by its owner/admin, or find its public join page.
Account
Plans are differentiated by string limit and by feature access; the subscription must sit on the account or organization actually hosting the projects. Current standard monthly-billing rates (i.e. paying month-to-month, no prepay discount): Free ($0/mo, 1,000 strings), Start ($20/mo), Plus ($60/mo, most popular), Premium ($160/mo), and Enterprise ($260/mo, 100,000 strings, or custom for higher volume). On top of that, prepaying 6 months brings a 10% discount, and prepaying a full year brings 15% off.
Both are handled from your account settings — see how to upgrade and how to downgrade.
Strings only count against the account/organization that actually hosts the project, so the upgraded plan must be on that same hosting account, not a different one.
AT characters aren't included in subscriptions because the feature relies on paid third-party APIs (Google, Azure, DeepL) that charge by character. Every account gets 10,000 free AT characters; more can be purchased from Account Settings > Profile > Automatic Translations Characters Left > Manage.
AT characters live on the purchasing account by default. To share them with contributors, enable "Contributors Can Use Your AT Characters" in Account Settings > Preferences.
Depends on the setup. For an individual account, if you can still reach the departing owner, ask them to change the email address on their POEditor account to yours, effectively handing it over. For an organization, the proper mechanism is different: the owner goes to Account Settings > Organizations > Leave, and can leave it directly to another existing member (who becomes the new owner) rather than changing emails. Separately, anyone can also be assigned as an Alternative Payer (Account/Organization Settings > Billing > Payment Info) to handle billing specifically, without taking over ownership. If you can't reach the departing owner at all, contact info@poeditor.com.
Assign up to 5 Additional Invoice Recipients in Billing settings (Account Settings > Payment Info), and each will receive a copy of every future invoice. If your account has an assigned Payer, add the recipients on the payer's account instead.
Set a password for your account using the recovery form.
Downgrade your account to the Free plan; cancellation takes effect at the end of the current billing cycle. See downgrading a POEditor account.
Click your username in the navigation bar → Account Settings, then find the "Remove account" link at the bottom of the Profile section. Click it, enter your password, and press Send — you'll receive an email with a link that deletes your account once you click it. If you signed up via a third-party service (Google, GitHub, etc.) and don't have a password, get one from the recovery form first. (Note: this is separate from canceling a subscription — canceling downgrades you to Free, while this permanently deletes the account.)
An organization centralizes management of projects, subscriptions, billing, and integrations across a team in one place — useful once a single project owner no longer makes sense (e.g., the owner leaves, or multiple people need billing/management access). Individual accounts can migrate their projects into an organization once created.
Go to Account Settings > 2FA and enter your POEditor password to begin. Scan the QR code with your authenticator app (or enter the alphanumeric code manually if you can't scan), then enter the 6-digit code from the app to finish enabling 2FA. You'll also be given a backup code at setup — save it somewhere safe, since it's the only way back in if you lose your authenticator device. Organizations can additionally require 2FA for all members via Organization Settings > Preferences > Security > Require 2FA.
Yes. Backups work through both in-platform modules and export tools, plus optional manual/automated backups you configure yourself.
In-platform backup features:
- History Module — automatically tracks changes and lets all users recover translation data.
- Translation Memory — automatically saves translation units in the background (available on paid plans).
Manual and automated backups:
- Manual ZIP export — download your project files as a ZIP anytime from Account or Organization Settings > Backups.
- Automated backups — schedule automatic exports of your translation files to an integrated third-party storage service from Backups Settings (available on paid plans).
Projects
Several ways, depending on your role:
- Manually on the Terms page: click the + button at the top of the Terms page (or use the + keyboard shortcut) to add one term at a time — no file needed.
- Project page import (owners, admins, organization managers): upload a file, with options to also import translations to a language, overwrite existing translations, mark strings as fuzzy in other languages, and tag imported strings. For formats like XLIFF holding both source and target text, you choose which to import as the translation.
- Language page import (any contributor with access): translations only — the terms/keys must already exist in the project.
- Git integrations (owners/organization managers set up; admins can use if shared access is granted): import terms, terms+translations, or translations only, manually or via webhooks.
- API / MCP server: projects/upload, projects/sync, terms/add, terms/update, languages/update, translations/add, translations/update — or, from an AI-enabled IDE or agent tool (Claude Code, Claude Desktop, Cursor, and others), the same via POEditor's official MCP server, which covers the full v2 API.
- Plugins: official WordPress and Figma plugins, plus community-built ones.
A few options, without needing to assign contributors: make the project public and crowdsource translations from your community via its public join page; use Automatic Translation (Google, Azure AI, or DeepL machine translation); use AI translation with your own connected LLM; or order human translation through the translation options page, which sends strings to professional translators via an integrated order system — no external accounts needed. Machine and AI translation output can also be checked afterward with the AI-powered QE (Quality Evaluation) feature.
On the Contributors page, the project owner and admins can Approve, Block, or Remove contributors. See how to manage contributors.
Yes — the "Notify contributors" button can be used to alert them to review fuzzy translations after a source update, and they get an email when added to a private project. For automated, rule-based notifications, use the Notify step in Workflows.
Yes, via the comment button next to each translation box — comments are color-coded (green if last posted by an admin/owner, orange if by a contributor).
Make sure you're using Import on the main project page, not inside a translation/language page — only the project-page import can add new terms. Also, only admins, the project owner, or organization managers can import terms; contributors can't.
No — a project can only have one owner. To centralize management of projects, subscriptions, billing, and integrations across a team, create an organization and migrate your projects into it.
On free accounts, projects inactive for about 6 months get auto-archived (you're warned by email beforehand) and become invisible to everyone except the owner. Archiving also deletes the project's Change History, though nothing else on the account is affected. The owner can restore it anytime by logging in and clicking "Restore project."
From the project's own Settings page — any project you host can be deleted there.
Use the "Add languages" option on the Project page — this works the same way for private and public projects. You can also copy the full language setup from another project when creating a new one, add languages via the API (languages/add method) or the MCP server, or add a language through the WordPress or Figma plugins. To add languages across multiple projects at once, click "Add languages" on any project, select the languages, and choose "Add to more projects" (or "All projects"). Separately, for public/crowdsourced projects, the "Contributors Can Add New Languages" option lets contributors add languages themselves from the public Join page.
It's the same comment system used for general communication, not a separate one — you can add comments and screenshots directly on a string's comment thread to guide how it should be translated. To keep this guidance visible and distinct from ordinary back-and-forth, you can pin a comment: pinned comments stay easy to find, and get carried through the localization workflow (e.g. exported and re-imported with the term). For terminology-level guidance that applies across a whole project rather than a single string, a glossary is the better tool.
Translations
Yes — POEditor saves your work the moment you click outside the translation box; there's no Save button.
POEditor supports 20+ localization file formats, including JSON, XLIFF, ARB, RESX, .strings, YAML, and CSV — see export options for the full list and export-time filters. Several ways to export, depending on need:
- Language page export (any user with access to that language): the basic Export button, with filtering options for specific groups of strings.
- Git integrations: owners/organization managers can export manually or via webhooks/PR presets; admins can use shared export links. The Git export step in Workflows sends strings to your connected repo files, inheriting your integration settings and export rules.
- API: pull all languages at once via languages/list + the export endpoint (projects/export), useful for scripting scheduled or triggered exports (e.g. only exporting when a language is marked complete, using callbacks).
- Backups feature: export all languages in a project to a ZIP, manually or on an automated schedule to a connected storage service (paid plans).
- MCP server: if you're working in an AI-enabled IDE or agent tool, POEditor’s official MCP server can also pull translations directly into that environment — confirmed to support export alongside import.
Yes — no limit on contributors per language, and a real-time system shows who else is connected or translating the same string. To see a specific contributor's work, use the filter by contributor option.
Yes — the search bar in a language page searches terms, translations, context, reference, and the Reference Language; a global search option covers all projects you have access to.
Fuzzy is a flag signaling a translation needs revision. On a translation page, toggle it per string with the F button, or select multiple terms' checkboxes and choose Toggle Fuzzy from the bottom menu to flag several at once. To bulk-clear fuzzy flags, filter the language page by Show > Fuzzy, select all the filtered results, then Toggle Fuzzy again to remove them. Fuzzy can also get set automatically: when an owner/admin edits a term (to prompt contributors to recheck other languages), on import when overwriting a translation (with the option to mark the same term fuzzy in other languages), or when editing a string in the Default Reference Language, if that project setting is enabled.
Multiple translation tabs on a term typically correspond to plural forms enabled on that term. Plurals can be enabled per term in its Attributes on the Terms page, and are supported for formats including PO/POT, Android XML, iOS XLIFF, Xcode String Catalogs, Flutter ARB, JSON, Key-Value JSON, YAML, and i18next JSON (only exported if the target format supports plurals). If a source string uses ICU message syntax for plural rules, POEditor detects it automatically and shows an eye icon in the translation box that opens a dedicated ICU editor for entering each plural form. Separately, Fallback Languages (set at the project level, or per-language under Export > Advanced options) fill any empty translations — plural or not — in an export with translations from another chosen language; this isn't specific to Android or to plurals.
Yes — project owners, administrators, or organization managers/owners can flag a term as Non-translatable from its attributes on the Terms page. Once enabled: existing translations are kept but locked from editing; empty translations inherit the source text if a Default Reference Language (DRL) is set (also locked); if no DRL is set, the term itself is copied into the translation and locked; if a DRL is set but has no value for that term, the translation box stays empty and locked. Android XML projects also get this automatically when importing terms flagged translatable="false" — the source language must be set as DRL, or the flag is ignored.
Yes — the online translation editor supports right-to-left languages.
POEditor runs a set of configurable QA checks across four categories — Formatting (e.g. consecutive/leading/trailing spaces, new lines, max/min translation length, markup), Consistency (emails, glossary items, numbers, word repetitions, identical translations, URLs), Placeholders (curly brackets, percent-style, Python, YAML, square brackets, and more), and Punctuation (colons, quotes, parentheses, question marks, etc.) — plus HTML/Markdown preview. All checks are on by default; project owners and admins can toggle individual checks under Project Settings > Advanced > QA Checks. Checks run in real time as translations are saved (can be turned off in Account Settings), or in bulk via the "Run QA Checks" button on any translation page. Proofread translations, plural forms, ICU-syntax strings, and strings with no counterpart in the Default Reference Language are excluded from checks. QA also plugs into Workflows (combine with the Notify step for automated QA reports by email). For AI-based review instead of rule-based checks, there's a separate Quality Evaluation feature that scores translations using your connected LLM against the MQM framework.
Connect a provider under Integrations with your API key, pick a model, and set it as default. Default prompts are optimized for performance and cost, but you can fully customize tone, audience, terminology, and forbidden patterns per project — every AI translation in that project follows those instructions.
Owners, organization managers, and admins can restore the last recorded translations for a language via the Change History module; contributors can view previous versions via the History link next to each translation, if the term was translated on POEditor before. Deleting a term also deletes its translations, but re-adding the term lets you recover them via Translation Memory.
Translation Memory (available from the Start plan up) stores every translation the moment it's saved, and finds exact matches for reuse — matched against the Default Reference Language text if one is set on the project, or against term/string IDs if not. It works across projects, not just within one: if the same string was translated anywhere else in your account, TM can surface it. It stores one entry per user per term (so multiple contributors' variants can coexist), and ranks suggestions by how often each was used. You can use it two ways: as inline suggestions under empty translation boxes (enable "Translation Memory Suggestions" and "Translation Memory Access" in Account/Organization Settings), or as a bulk "Start searching" load from a language's translation page, which fills every matching empty box at once and lets you remove any you don't want. Entries can be filtered and deleted from Account/Organization Settings > Preferences > Translation Memory > Manage. It also lets you recover translations for a term that was previously deleted and re-added to the project.
Glossaries have their own section in Account/Organization Settings (available from the Premium plan up), where you manually add terms and definitions or import them from a CSV file. They enforce consistency in multiple ways: directly in the Language page editor while translating; in AI translation and Quality Evaluation, where an assigned glossary's terms and definitions are automatically sent to the connected LLM to follow — no separate setup needed; in QA checks, which flag when glossary terms aren't translated consistently; and in Automatic Translation for Google specifically — Google will search-and-replace glossary terms in the machine-translated output, provided the glossary has definitions for every target language.
Proofreading rights are granted to contributors by the project owner or admins in the project's Settings page; once granted, hitting the check button marks a string as Proofread. Owners can also enable "Lock Proofread Translations" so contributors without proofreading rights can't edit or delete already-proofread strings.
Yes — POEditor integrates with Slack and Microsoft Teams for chat notifications, WordPress for themes and plugins, and Figma for design files. The WordPress and Figma plugins specifically let you send content from those tools into your POEditor localization projects for translation, and fetch it back once translated.
Yes — POEditor has an official, hosted MCP server (https://mcp.poeditor.com/mcp, Streamable HTTP transport, no installation required) that connects any MCP-compatible AI assistant to your account. It covers a broad set of tools spanning the full POEditor v2 API — projects, terms, translations, languages, contributors, progress tracking, QA checks, and Automatic Translation (Google, Microsoft, DeepL) — so both reading/importing and exporting data are supported. Authentication is via OAuth 2.1 (supported by Claude Code, Claude.ai Connectors, and other OAuth-capable clients) or a POEditor API token for clients that don't support OAuth; tokens inherit the role of the user who created them. Full setup snippets per client, the tool list, and troubleshooting are in the MCP server KB article.
Yes. Here's why:
- Compliance & data residency: ISO 27001 certified, GDPR compliant, hosted on POEditor's own infrastructure within the EU (no third-party clouds), with TLS in transit and encryption at rest, and a DPA available on request.
- Access control at scale: SAML-based SSO (with dedicated setups for Okta, OneLogin, Ping Identity, and Microsoft Entra), 2FA with an organization-wide "Require 2FA" enforcement option, and granular project roles (owner, admin, contributor) plus organization-level roles (owner, manager, with restrictable billing rights).
- Governance & auditability: an Audit Log (available from the Plus plan) tracking translation activity, project management actions, API calls, integration events, and settings changes — retained 15 days generally, 30 days for deletions — available at both the account and organization level.
- Centralized management: Organizations consolidate billing, subscriptions, projects, and integrations under one roof, with unlimited managers and no limit on the number of projects or contributors beyond the plan's string limit.
- Flexible AI integration on your own terms: bring your own API key for OpenAI, Anthropic, or Google, connect via Azure AI or Amazon Bedrock, or use a custom model of your choice — POEditor never marks up tokens or trains on your data, which matters for enterprises with data-handling requirements around AI vendors.
- Fits existing engineering workflows: API, official MCP server, Git integrations (GitHub, GitLab, Bitbucket, Azure DevOps) with webhooks and configurable Workflows automation, so localization can sit inside an existing CI/CD pipeline rather than as a bolt-on tool.
- Scale headroom: the Enterprise plan (100,000 strings) can be customized further for higher volume, and IP addresses are available to whitelist POEditor's traffic through a corporate firewall.
Oops, couldn't find anything for that search. Get in touch to tell us what you're looking for.
