−10%10% off all files right now — originals €18, map packs from €54.
€18 / file−10%

VBF container · Ford, Volvo, Jaguar, Land Rover

VBF to BIN converter for Ford, Volvo and JLR

Unpack a Ford, Volvo or JLR .vbf into a plain .bin for WinOLS, and build your edited .bin back into the same .vbf.

  • Free file check first
  • No account
  • Your file is not kept

The file read from the car or received from the dealer. You get a plain .bin to open in WinOLS.

Log

Nothing yet. Attach a file.

Price

Free for now, in both directions.

Your file

Attach a file to see what is in it.

Buy the whole converter

Want this converter as a complete solution of your own, rather than file by file? The price and terms are on request.

Write to [email protected]

Correct the firmware checksums in WinOLS

If the firmware checksums are wrong, the ECU may refuse the file or the engine may not start. You need WinOLS with a checksum module for this ECU, or another tool that corrects them. If you cannot correct them, do not use this step.

This is the main step. This converter does not touch the firmware checksums: it only looks after the checksums of the VBF container itself. If you do not correct them in WinOLS, the ECU will not accept the firmware. BIN → VBF stays locked until you attach the edited .bin and confirm that the checksums are corrected.

This is a free tool, with no guarantee. By using it you confirm that you may use these files. Terms, section 17

How to convert a VBF for editing in WinOLS

  1. Attach the VBFThe file read from the car or received from the dealer.
  2. Press VBF → BIN and save itYou get a plain .bin.
  3. Edit it in WinOLSOpen the .bin in WinOLS and make your changes.
  4. Correct the firmware checksumsThis is the main step. If you skip it, the ECU will not accept the firmware.
  5. Save the edited BINWith the corrected checksums. The file size must stay the same.
  6. Press BIN → VBFAttach the original .vbf and your .bin, tick the box and build the file, in the same format.

Tested by the developer on real files

2,186 of 2,191real VBF files from a JLR database converted correctly in the developer's own test: 99.8%. The other 5 were damaged or encrypted.
43,625JLR VBF files were studied to work out the format.
Byte for byteIn the same test, a stock VBF unpacked to exactly the BIN that WinOLS gives. An edited BIN packed and unpacked again matches itself.

Every file is checked before you get it

The new file is built from your original .vbf: its header, addresses and block order stay as they are. Unchanged blocks are carried over byte for byte, changed blocks are packed again, and the CRC16 of each block and the file_checksum are recalculated.

Before you get the file, it is unpacked again and compared with your .bin. On any difference, no file is given.

Questions

Which files does it take?

VBF containers from Ford, Volvo and JLR. The test above used JLR files, so Volvo files have not been tested. Each block's storage is worked out from its own CRC16, so files without a data format field open too. Encrypted or signed files are not supported, and the converter does not always recognise them: if the check warns about a block, do not use the result. A damaged or cut-off file is reported by the check.

Why do I attach the original .vbf again?

The header, addresses and block order come from it. Nothing is kept between steps, so BIN → VBF needs both files.

Is my file kept?

No. It is read on our server for the length of the request and not saved or logged.

What does it cost?

It is free for now, in both directions, with no account.