P
Select the project
Detect the application identity, VCL or FMX framework, forms, source units, targets, and normal build outputs.
Open-source localization for Delphi
Build multilingual Delphi applications with no cloud dependency.
Delphi App Translation Studio scans VCL and FireMonkey projects, creates reviewable translations, validates the result, and exports compact JSON language packs that work offline in the finished application.
Production release
Read the guides before you download, build, or use the Studio.
Version 1.0.0 is ready for production development with the validated Windows and RAD Studio configuration described in the guides. Keep your Delphi project under version control, follow the Setup Wizard Guide, and review machine-translated wording and every deployed screen before shipping your application.
Localization remains a developer-owned process: short phrases, specialized terminology, dynamic text, right-to-left layouts, and custom controls can require corrections or additional integration.
Version 1.0.0 — production release
The current release brings together the Studio, VCL and FireMonkey integration packages, source, samples, and current guides. It includes the earlier RAD Studio shutdown correction, improved text scanning, spacing safeguards, and punctuation-aware translation.
October 4, 2026 — project scanning improvement: Project scanning now leaves bundled dependencies and test-contract files out of the translation catalog, while still including files explicitly referenced by the Delphi project. This keeps the translation review focused on the application's own text.
October 4, 2026 — safety backup improvement: The required pre-processing ZIP now skips temporary WebView2 browser caches and is checked for completeness before translation begins. Project source, forms, and other project files remain in the backup.
- Read the User and Setup Wizard guides before installing components or opening a target project.
- Download and extract the complete version 1.0.0 package to a new folder. Do not merge it with an older release.
- If upgrading, preserve your projects, language packs, glossaries, and translation memories. Replace the complete matching package set; do not mix BPLs from different builds.
- In RAD Studio, use Component → Install Packages → Add for the matching design-time BPL. Follow the package instructions in the guides.
VCL + FMXOne localization workflow
DeepL + GoogleDeveloper-time providers
Offline JSONNo end-user API key
Apache 2.0Open-source licensing
A development tool, not an EXE translator
Localization stays inside the development process.
Run the Studio while forms, resources, messages, and layouts can still be examined in Delphi. Rescan as the application changes, preserve translations that still match, and send only new or revised eligible text to the provider.
Machine translation can be very useful, but it cannot guarantee perfect wording or layout. The developer remains responsible for terminology, dynamic messages, custom controls, right-to-left behavior, and final visual review.
Guided from source to deployment
A controlled path from Delphi project to offline language pack.
The Setup Wizard handles the repeatable work and keeps the important decisions visible.
A
Scan and translate
Build a stable catalog from saved forms and approved Delphi text, then translate unresolved entries with DeepL or Google.
✓
Review and validate
Inspect terminology, placeholders, source changes, language direction, and conservative layout proposals before export.
{ }
Integrate and deploy
Generate the VCL or FMX component kit and place compatible source and target packs beside the intended executable.
Translation with application context
Short interface words need more than a dictionary.
“Play,” “Close,” “Schedule,” and “Enable” can mean different things in different applications. The Studio adds proper context, control roles, surrounding evidence, terminology, and review status with each entry.
- Preserves approved and reviewed work during later scans
- Protects Delphi placeholders, accelerators, identifiers, and markup
- Uses project glossary and translation-memory evidence
- Separates machine drafts from human review and approval
Designer-owned integration
Normal Delphi components. Offline application runtime.
Place one framework-appropriate language manager and one connected selector on the primary form. Their published properties remain visible in Object Inspector, and ordinary forms are managed through the application lifecycle.
Built around valuable source code
Safety is part of the workflow, not a final checkbox.
Read-only discovery
Project detection and scanning inspect saved source without executing it.
Explicit authorization
Final processing begins only after the project, backup, and intended actions are reviewed.
Atomic project data
Catalogs, packs, settings, glossaries, and preferences use validated replacement and recovery files.
Offline trust boundary
Provider keys stay on the developer computer and never belong in the target application.
Version 1.0.0 is available
Bring multilingual support into active Delphi development.
Download the matched software and guides, work from a backed-up project, and verify the generated language packs in the actual application. Report functional, layout, translation, RTL, and documentation issues without sharing private source or credentials.
Your feedback matters
Help us make Delphi App Translation Studio better.
Tell us what worked, what did not work, and what could be clearer. Errors that are not reported cannot be investigated or corrected, and the application cannot continue to improve without feedback from developers using it in real projects.
Please report translation problems, right-to-left display issues, unexpected program behavior, component or package problems, documentation questions, and anything that made the workflow confusing. Even a small observation can identify an improvement that benefits every user.
When reporting an issue, please include the Delphi framework, target platform, selected language, screen or workflow involved, and the steps needed to reproduce the problem. Screenshots are helpful, but please remove API keys, private source code, personal information, and other sensitive material before submitting them.