In chip tuning the most valuable file is not the performance file. It is the original file first read from the car. Going back to stock, recovering an ECU and every future change all depend on it. This article explains why the original backup is essential, what it should include and how to store it.
Why does the original file matter so much?
- Returning to stock: before selling the car, an inspection, a warranty claim or a dealer software update, you may need to put the factory software back.
- Recovery: after an interrupted write or a checksum error, writing the original file back is the safest way to recover the ECU.
- The base for every new file: when you move from Stage 1 to Stage 2 or add an option, the new file is built from the original, not the modified file. This stops changes from stacking on top of each other.
- Comparison: when a problem appears, comparing the original and modified files shows whether the cause is the software or the hardware.
What should the backup include?
A single file is often not enough to say "I have a backup". Depending on your read method, keep:
- The full flash read: the ECU's program and calibration memory. If only the calibration area could be read, note that.
- The EEPROM: immobiliser, coding and adaptation data live here. Losing it can leave the car unable to start.
- Tool backup or ID files: some tools create extra files in their own format that are needed to write back.
- A photo of the ECU label: hardware (HW) and software (SW) numbers, ECU type and manufacturer part number.
- Vehicle details: make, model, engine code, model year and gearbox type.
We compare how complete each read method's backup is in ECU reading methods.
How to store backups
Use meaningful file names
Names like "ori.bin" or "new.bin" get mixed up within weeks. Put the vehicle and state in every file name, for example:
Volkswagen_Golf7_2.0TDI_CRLB_EDC17C64_SW123456_2026-11-03_ORI.bin
A suffix such as ORI, STG1 or STG2 shows at a glance whether the file is original or modified.
Keep it in at least two places
A single copy on the workshop PC is gone after one disk failure. Keep one copy on an external drive and another in reliable cloud storage.
Never change the file
Never open and save over the original file. Note its hash (for example MD5) so you can later confirm it is still identical.
The most common mistake: sending a modified file as "original"
On a used car, or an ECU that has been worked on by another shop, the file you read may not be original. If a new tune is built on top of it as if it were stock, changes stack up and the result becomes unpredictable. If you are not sure about the car's history, say so in your file request. Our engineers can check whether the file has been modified before.
What if I have no original backup?
If no backup was taken or it was lost, it may be possible to find an original file with the same hardware and software numbers. The ECU's HW and SW numbers are required for this. You can request one through our original file service. The most reliable route is still to take your own backup at the first read.
Frequently asked questions
Can I delete the original once the tuning file is delivered?
No. Keep the original for the life of the car; returning to stock and all future changes depend on it.
Why keep the EEPROM separately?
The EEPROM holds immobiliser and coding data specific to that car. Another car's EEPROM does not carry this data and cannot replace it.
How do I know if my file is original?
If the car's history is unknown, mention it in your request notes. The file can be checked against an original file with the same software number.