What you’ll receive
Input One VBF firmware file File limit 64 MiB per file Your original stays separate from the result.
Using your download Encrypted or unsupported VBF encodings cannot be converted. Check the metadata for block addresses, checksum warnings and verification data.
Use files that match your ECU and software version. A converted container is not a tuned calibration.
How to convert your file
Choose the original factory container shown above. The filename extension must match the supported input. Upload the file and sign in to your free account. Processing continues after the upload has been saved. Open My uploads to download the original, converted files and report again. Ford, Jaguar and Land Rover containers
VBF files combine descriptive headers with firmware blocks. The converter extracts supported payload and verification blocks and records their addresses and any checksum warnings. Coverage depends on the encoding used inside the container.
Encrypted or unsupported encodings cannot be converted. Retain verification information with the output and compare the source software identification with your ECU before using an extracted block.
Working with addresses
For example, a block declared at address 0x800000 does not imply that the BIN contains eight megabytes of preceding data. Use the address recorded in the report when mapping the block into your editor.
After extraction, you can check a supported ECU checksum or extract map definitions for WinOLS using compatible files.
