Multilizer alternative
A Multilizer alternative for Windows desktop software.
Multilizer is no longer developed or sold. Lingobit Localizer 10 localizes compiled Windows applications in Delphi, C++Builder, MFC, WinForms, and WPF, and takes the translations from the localized files Multilizer built for you.
- Approach
- Localize the compiled files, without source code
- Your translations
- Imported from the localized files Multilizer built
- Delphi
- Forms in the DFM preview, resource modules such as
MyApp.DEU - .NET
- .NET Framework 4.8 and .NET 5–10
Multilizer and Lingobit Localizer 10 compared.
Multilizer as it was last released; Lingobit as it ships today.
| Topic | Multilizer | Lingobit Localizer 10 |
|---|---|---|
| Development | No longer developed or sold | Localizer 10.0, released in 2026; updates and support with Annual Maintenance |
| Licenses | No longer sold | Perpetual licenses in Standard, Professional, Enterprise, and Enterprise Multi-User. Pricing |
| Binary localization | Resource DLLs, localized files, or a multilingual EXE | A localized EXE for each language, resource-only DLLs and Delphi resource modules, or multilingual Win32 and MFC files |
| Runtime components | Localization components with .mld dictionaries for Delphi and C++Builder | None for Delphi: the application loads resource modules the standard way. For MFC, an optional language menu library |
| Delphi and C++Builder | VCL scanners for binaries and projects | Forms and resource strings in EXE, DLL, and BPL files; DFM preview; resource modules that Delphi loads by itself |
| Your existing translations | In .mpr or .m7p projects, .mld dictionaries, and the localized files | Imported from the localized files, with positions and sizes from the same version. Multilizer projects and dictionaries are not opened |
How you used Multilizer decides the path.
Multilizer had two ways to localize a Delphi application. Lingobit follows the first one.
Binary localization
Multilizer read the compiled files and wrote resource DLLs, localized EXE files, or a multilingual EXE. Lingobit works the same way and imports the translations from those files, layout included.
Localization components
The application translated itself at runtime from .mld dictionaries. There are no localized files to import. Export the translations from Multilizer if it still runs, use them as translation memory, and ship a localized EXE or resource modules instead of the components.
Where Lingobit differs from Multilizer.
Lingobit is a localization tool for Windows desktop software in general, not a VCL component set. For most Delphi applications with standard forms and resource strings, it covers what binary localization needs. Check the points below before you switch.
Covered
- Forms, resource strings, and their properties in the EXE, DLL, and BPL files you ship
- Custom VCL controls mapped to preview controls in the VCL form editor settings
- A localized EXE per language, or resource modules such as
MyApp.DEUnext to the unchanged EXE - Scan for Changes on each new build, so only new and changed strings need translation
Check first
- The application uses the Multilizer components: plan the move to a localized EXE or resource modules
- The application changes the language at runtime: test it with the modules Lingobit writes
- Only the Multilizer project is left, no localized files
Your Multilizer translations come with you.
Add the release you shipped and import the translations from its localized files: every string gets its translation item by item, with positions and sizes. Then Scan for Changes brings in your current build. You do not need Multilizer running.
Multilizer alternative FAQ
Can Lingobit open Multilizer projects?
No. Lingobit does not open .mpr or .m7p projects or .mld dictionaries. It takes the translations from the localized files Multilizer built: localized EXE and DLL files, resource DLLs, and multilingual files. See Move from Multilizer.
Is Lingobit a replacement for the Multilizer localization components?
No. For Delphi and C++Builder, Lingobit does not provide runtime components. It localizes the compiled application: a localized EXE for each language, or resource modules that Delphi loads by itself.
Which applications can I localize with Lingobit?
Compiled Win32 and MFC applications, Delphi and C++Builder applications, WinForms and WPF applications on .NET Framework 4.8 and .NET 5–10, .NET resource files, Java .properties, Qt TS, and the further formats on the Supported formats page.
Can I try it on my own files first?
Yes. The free trial runs for 90 days. Add the release you shipped, import its translations, and see what comes over. See Download.
Bring a Multilizer release and see what comes over.
Your original files and their localized versions are enough. Import, scan your current build, and review what changed.