Localizer 10 editions
Compare Localizer 10 editions
All editions include visual translation, translation reuse, validation, and the translator workflow. Professional adds translation memory, machine translation, pseudo-translation, and command-line automation; Enterprise adds terminology, Crash Finder, and help, database, and folder localization.
Localizer 10 feature matrix
Follow any capability name for more details.
- Standard€695 $795Buy
- Professional€1,150 $1,295Buy
- Enterprise€1,950 $2,195Buy
- TranslatorIncludedPrepared packages only
| Capability | Standard€695 $795Buy | Professional€1,150 $1,295Buy | Enterprise€1,950 $2,195Buy | TranslatorIncludedPrepared packages only |
|---|---|---|---|---|
| Core functionality | ||||
| Create and configure localization projectsAdd application files, select languages, and control which resources can be translated. | ✓ | ✓ | ✓ | — |
| Visual translationTranslate strings and application resources in context through desktop editors. | ✓ | ✓ | ✓ | ✓ |
| Scan for changesReuse translations across releases, translate only new content, and review only resources that changed. | ✓ | ✓ | ✓ | — |
| Straightforward migrationImport translations from localized binaries or resource files in a single step and bring existing work directly into the new project. | ✓ | ✓ | ✓ | — |
| Create localized filesGenerate translated application files, run the localized build, and verify the result in the real application. | ✓ | ✓ | ✓ | ✓ |
| Translation | ||||
| Work with external translatorsUse Prepare Translation Task to send translator projects, Delivery Bundles, XLIFF, or CSV, track translation progress, and bring completed work back with Import Translation Results. | ✓ | ✓ | ✓ | — |
| Included Translator EditionIncluded with every Localizer license; available features follow the main license. Translators work in the same visual context without buying Localizer. | ✓ | ✓ | ✓ | ✓ |
| Machine translation: DeepL, Google, AzureConnect to DeepL, Google Translate, and Microsoft Azure Translator for machine-assisted translation. | — | ✓ | ✓ | ✓ |
| CAT tool interoperabilityConnect Localizer to CAT tools through XLIFF or CSV, with TMX support in Professional and TBX support in Enterprise. | ✓ | ✓ | ✓ | — |
| Translation Memory and TMXReuse existing translations locally and exchange translation-memory data with CAT tools through TMX. | — | ✓ | ✓ | ✓ |
| Terminology management and TBXMaintain approved terminology, check consistency, and exchange termbase data with CAT tools through TBX. | — | — | ✓ | ✓ |
| Quality assurance | ||||
| ValidationFind missing translations, placeholder errors, shortcut conflicts, and layout problems before release. | ✓ | ✓ | ✓ | ✓ |
| Visual previews and editorsPreview translated dialogs, forms, supported UI resources, and layout while translations are being edited. | ✓ | ✓ | ✓ | ✓ |
| Pseudo-translationGenerate simulated translations in seconds to test text expansion, coverage, and localization readiness. | — | ✓ | ✓ | ✓ |
| Crash FinderIdentify which translation causes a localized application to fail without help from developers. | — | — | ✓ | — |
| AI translation and proofreadingUse AI assistance to translate content and review completed translations. | — | — | Coming soon | — |
| Advanced formats and workflows | ||||
| Command-line automationCommand Line License to automate scans, validation, updates, and localized output in build scripts. Not available in Standard. | —1 | ✓ | ✓ | — |
| Core binaries and resourcesLocalize Win32/MFC, .NET Framework 4.8 and .NET 5–10, Java, and related application binaries and resources. | ✓ | ✓ | ✓ | ✓ |
| Structured, source, web, and text formatsWork with XML, XAML, Qt, source code, PO, INI, HTML, and text content. | — | ✓ | ✓ | ✓ |
| Help and database localizationLocalize CHM/help systems and database content in Enterprise projects or prepared Translator packages. | — | — | ✓ | ✓ |
| Folder-based localizationAdd an entire directory to the project and bring new files into the localization workflow automatically as the folder changes. | — | — | ✓ | — |
| Multilingual rebrandingAdd a second dimension beyond language with product-, device-, or customer-specific names and terminology in each localized build. | — | — | ✓ | — |
1 Command-line automation is available from Professional. Translator Edition is included with every license, and command-line automation with Professional and higher. There is nothing extra to buy for either.
Translator capabilities apply only to prepared packages. See all supported formats for the complete parser and file-extension list.
Translator is a focused application for prepared packages. It can translate, run QA, use the translation tools enabled by the source edition, and generate localized files. Project creation, source scanning, package management, and importing completed work remain in Localizer.
✓ included, — not included. Multi-User licensing uses the Enterprise feature set.
License scope and included tools
Choose how many people can use Localizer. Translator Edition is included with every license, and the Command Line License with Professional and higher; neither requires a separate seat purchase.
Choose a Localizer license
Single-User License
1 named user
Choose Standard, Professional, or Enterprise for one named user on up to two computers. A Single-User License cannot be shared within a team.
Multi-User License
Multiple users
Enterprise capabilities for multiple users in one organization, including shared team and automation workflows.
Included licenses
Translator Edition
Included with every Localizer license
Translators working with prepared packages use it without buying Localizer. Available features follow the main license.
Command Line License
Included with Professional and higher
Professional, Enterprise, and Enterprise Multi-User include it, with no separate automation license to buy. Not available in Standard. Available commands follow the capabilities of the licensed edition.
Command-line automation
Automate the localization release workflow with Professional, Enterprise, or Enterprise Multi-User. Command-line automation is not available in Standard.
- Scan application files for changes. Update the localization project from a new build while preserving existing translations and grouping changes as New, Updated, and Removed.
- Import completed translations. Bring translated binaries or resource-only files back into the current project without a manual import workflow.
- Apply Translation Memory and terminology. Reuse approved translations, terminology, and duplicate matches automatically before translators review the remaining work.
- Run pseudo-translation and validation. Generate pseudo-translations, adjust translated bounds, and run validation with a non-zero exit code when issues are found.
- Import and export TMX. Import the TMX entries that match the project and export Translation Memory for other localization and CAT-tool workflows.
- Send and receive translation work. Create translator projects, Delivery Bundles, CSV, and XLIFF files, and receive completed work, without opening the desktop interface.
- Process selected languages and brands. Run localization for one language or brand, or process every configured target in a repeatable release job.
- Generate application files. Create localized builds after translation and QA, ready for automated testing, packaging, or release.
- Run unattended. Execute repeatable localization steps in silent mode from build scripts, build servers, and release automation.
Command availability follows the licensed edition. Terminology and brand automation require Enterprise. See the command-line reference in Help for technical syntax.
Try each Localizer 10 edition before you choose.
At startup, select Standard, Professional, or Enterprise in the Localizer Trial and evaluate the functionality included in that edition. Command-line automation always runs in Enterprise mode with Trial limitations so you can test your build process.