Build the converter
Delphi 12 and Delphi 13/13.1 are the officially verified development environments.
Delphi compatibility
VCL2FMXConverter v6.0 Navigator is built and validated with Delphi 12 and Delphi 13/13.1. It can also analyze many projects created with earlier Delphi releases because it works directly with Pascal source, form definitions, project files, and related resources.
Delphi 12 and Delphi 13/13.1 are the officially verified development environments.
Many earlier VCL projects may be analyzed. Their components, dependencies, source format, and architecture matter more than their original Delphi version alone.
The generated FireMonkey project is intended to be opened, reviewed, compiled, and tested in a modern Delphi environment.
Converter build compatibility
The distinction is deliberate. A version is not advertised as supported merely because the source appears likely to compile.
| Delphi 12 Athens | Officially supported and validated. Verified |
|---|---|
| Delphi 13 and 13.1 | Officially supported and validated. The current release is built with Delphi 13.1. Verified |
| Delphi 11 Alexandria | The converter source is likely to be compatible, but this version has not completed the full build and validation suite. Possible—not yet verified |
| Delphi 10.4 Sydney | Compatibility appears possible, but it has not been established by the complete build, form-loading, and contract tests. Possible—not yet verified |
| Delphi 10.3 Rio | This is the theoretical language-syntax floor because the source uses inline variables and for var declarations introduced in Delphi 10.3. Other project, form, and API differences may still prevent a clean build.Theoretical—not supported |
| Delphi 10.2 and earlier | The current converter source will not compile as-is. Supporting these development environments would require source modifications. |
Original VCL project compatibility
Navigator examines Pascal units, form definitions, project files, include files, resources, and component declarations. This makes many projects from earlier Delphi generations possible candidates for analysis.
What the application contains matters more than its original version number. A conventional older application using standard VCL controls may be easier to convert than a newer project built around unsupported libraries or Windows-specific behavior.
Factors affecting legacy projects
Older applications may use technologies with no direct FireMonkey equivalent or dependencies that are no longer available in modern Delphi.
A clear meaning of compatibility
VCL and FireMonkey are different application frameworks. Some behavior has a direct equivalent, some can be translated with a warning, and some requires a developer to redesign the feature for FireMonkey or for multiple platforms.
VCL2FMXConverter identifies automatically converted items, warnings, mapping gaps, Windows-specific behavior, and manual-review work. Its purpose is to produce a useful, inspectable FireMonkey starting point without hiding the remaining engineering work.
Recommended legacy-project workflow
Navigator keeps the original source separate from the generated output and provides a dry-run path for understanding the likely work first.
Not sure about your project?
Use the project scan and dry-run preview to inventory the application, identify conversion risks, expose mapping gaps, and locate areas likely to require manual attention.