Forms and components
Converts many standard VCL controls to FMX equivalents and preserves layout information where practical.
VCL2FMXConverter v7.0 Atlas
Your VCL to FMX converter.
Now in 35 languages.
VCL2FMXConverter V7 can now be viewed in 35 different languages. Language support is the major change for this version. The established conversion workflow is retained, with additional input, output and encoding safeguards.
Included with V7
Find your language.
All 35 included languages and regional variants, listed alphabetically. English names are followed by native names in parentheses.
- Arabic (العربية)
- Bengali (বাংলা)
- Bulgarian (Български)
- Chinese · Simplified (简体中文)
- Chinese · Traditional (繁體中文)
- Croatian (Hrvatski)
- Czech (Čeština)
- English (English)
- Filipino (Filipino)
- Finnish (Suomi)
- French (Français)
- German (Deutsch)
- Greek (Ελληνικά)
- Hebrew (עברית)
- Hindi (हिन्दी)
- Hungarian (Magyar)
- Indonesian (Bahasa Indonesia)
- Italian (Italiano)
- Japanese (日本語)
- Korean (한국어)
- Pashto (پښتو)
- Persian (فارسی)
- Polish (Polski)
- Portuguese · Brazil (Português do Brasil)
- Romanian (Română)
- Russian (Русский)
- Serbian · Cyrillic (Српски)
- Slovak (Slovenčina)
- Spanish (Español)
- Swedish (Svenska)
- Thai (ไทย)
- Turkish (Türkçe)
- Ukrainian (Українська)
- Urdu (اردو)
- Vietnamese (Tiếng Việt)
Machine translations — native-speaker review pending. The 35 language packs contain machine-generated translations that have not been reviewed by native speakers. Translations can be corrected or refined using the Delphi App Translation Studio. Translation errors and changes may be sent to the developer for adjustments.
The included languages were selected based on the countries and language preferences of users who have previously downloaded the converter.
Add a language. Make a translation your own.
Need another language or a translation correction?
Use the Delphi App Translation Studio to add more languages, edit existing translations, and edit the glossaries.
Download the manuals and guides along with the software. They explain how to work with language packs, translations, and glossaries.
Read the V7 translation editing and installation instructions.
Get Translation Studio
https://delphitranslate.github.io
V7 Atlas
The familiar workspace, in your language.
The Project Scan screen shown here uses English. Choose any of the 35 bundled languages in the converter.
What the converter does
Automate the routine work. Keep the important decisions visible.
The converter produces an editable FMX-oriented project and an honest report—not a black-box promise of one-click conversion.
Properties and events
Maps common VCL properties and event names when the translation is safe and meaningful.
Reports and review
Highlights unsupported APIs, Windows-specific code, third-party controls, conversion risks, and work that needs manual review.
Executable contracts
Uses 227 focused expectations to guard generated code, report behavior, project integration, and known conversion boundaries.
A practical workflow
From original VCL source to a reviewable FMX project
Select the source project
Point the converter at a Delphi VCL project. The original project remains the source of truth.
Convert to a separate folder
The converter analyzes Pascal and DFM files, applies supported mappings, and generates FMX-oriented output.
Compile, review, and test
Open the generated project in Delphi, work through the report, and validate real application behavior.
Third-party component support
Mapping packs make the rules transparent.
Optional JSON mapping packs can convert simple components, partially convert controls with warnings, detect complex controls, or preserve selected references. Developers can adjust packs without forcing unsafe assumptions into the converter core.
Repeatable engineering safeguards
Contracts turn known conversion problems into tests that must keep passing.
Each contract is a small Delphi test case plus an expected JSON result. Together they describe the generated Pascal, FMX, project, and report behavior that the converter must produce—or must deliberately avoid. Contracts are engineering safeguards, not files that normal conversions compare against at runtime.
Know the boundaries
FMX is a different framework, so developer review still matters.
Generated output is a migration starting point. Compiling, testing, UI inspection, and programmer review remain essential.
- Supported Delphi baseline: V7 is intended for modern Delphi/RAD Studio projects with FireMonkey support, specifically Delphi 12 or later. Very old source such as Delphi 3 may require manual modernization before the converter can be useful.
- No direct FMX equivalent: some VCL and third-party controls must be replaced or redesigned.
- Windows-specific code: handles, messages, GDI, and Windows API calls may need manual work.
- Custom drawing: owner-draw and VCL canvas logic do not map directly to FMX rendering.
- Behavior and layout: focus, scaling, keyboard handling, painting, and platform behavior can differ.
Considering a conversion product?
Know what you are getting before you pay.
Learn why form translation is not complete application migration, which claims deserve scrutiny, and what evidence a responsible converter should provide.
Contact and feedback
Found an issue or a conversion edge case?
Include the converter version, Delphi version, a short project description, and the generated HTML report when possible.
For a translation correction, include the language and locale, screen or Help topic, current wording and suggested wording. For clipped text, add the window size and Windows display scaling. Remove private details from screenshots and reports.