The ORI file: how to read, back up and send it properly

What is an ORI file?

The ORI file (short for "original") is a copy of the engine ECU's factory content, read before any modification. It is the reference every tuning file is built from, and it is also your only way back if a vehicle has to return to stock.

A good modified file always starts with a good ORI. If the read is incomplete, corrupted or already modified, all the calibration work that follows sits on a faulty foundation.

Full read vs calibration-only read

Depending on the ECU and the tool, you will not always get the same content.

Full read

A full read captures the entire flash memory: program, calibration and, in some cases, other areas. It is usually done on the bench or in boot mode. It is the safest backup because it allows a complete restore of the ECU if something goes wrong.

Calibration-only read

Over OBD, many tools only read the calibration area (the maps), sometimes with part of the program. It is quicker and often enough for a standard remap, but the backup is less complete.

Criteria	Full read	Calibration only
Content	Full flash (program + calibration)	Calibration area
Typical mode	Bench or boot	OBD
Duration	Longer	Shorter
Restore capability	Complete	Limited to what was read
ECU removal	Often required	No

The right choice depends on the ECU and on what your tool supports. For more detail, see ECU reading modes: OBD, bench and boot.

Whenever possible, a full read, plus a copy of the EEPROM or microcontroller data, remains the best insurance.

Why back up the original before anything else

Before writing a single byte, the ORI must be stored safely. This is not a theoretical precaution:

• if a write fails, you need to be able to restore the ECU;
• for an inspection or a sale, the customer may ask you to put the car back to stock;
• after a dealer visit, a manufacturer software update can overwrite the remap, and you need to know your starting point;
• in a dispute, the original shows the state of the ECU before you worked on it.

Good practice is at least two copies, one local and one online. An ORI that only lives on the workshop laptop will eventually go missing.

Common mistakes

Partial read or wrong memory area

Some ECUs have several memory areas. Reading the wrong one, or only part of it, produces a file that cannot be used for calibration. Check the file size and what your tool reports at the end of the read.

Interrupted read

A loose cable, a laptop going to sleep or an ECU that resets mid-read all leave you with an incomplete file. Read again rather than sending a doubtful file.

Low battery voltage

This is one of the most frequent causes of failed reads, and above all failed writes. Always connect a charger or stabilised power supply with the ignition on.

An already modified file sent as ORI

A used car may have been remapped in the past. If you send that file as the ORI, the new calibration is applied on top of modified data, with a risk of inconsistent values. If in doubt, say so, or order a file analysis (3 credits at ChiptuneFile) before ordering a modification.

Missing EEPROM or micro data

With some ECUs read on the bench or in boot mode, the tool produces several files: flash, EEPROM, microcontroller data. Sending only one of them can block processing or the write. Keep every file the read produces and include the ones that are requested.

Renamed or converted file

Opening a file and saving it again in other software can change its format. Send the file exactly as your tool produced it.

Naming your ORI file

A clear file name saves time, especially when the same car comes back two years later. A simple format:

Make_Model_Engine_Year_ECU_Tool_Mode_Plate-or-partial-VIN_ORI.bin

For example: VW_Golf_2.0TDI_2016_EDC17C64_KESS_OBD_AB123CD_ORI.bin.

Avoid generic names such as "read.bin" or "ori2_final.bin". Keep a short text note alongside it with the mileage, date and any remarks.

What to send with the file

When you upload an ORI to a file service, always include:

1. Vehicle: make, model, engine, stock power output, year.
2. Gearbox: manual or automatic, and the model if known.
3. ECU: hardware part number and software number if your tool shows them. Our ECU database can help you identify it.
4. Read tool and mode: for example Autotuner on the bench, KESS over OBD, K-TAG in boot mode.
5. Vehicle condition: mileage, modified hardware, stored fault codes (see our fault code database).
6. History: whether the car has been remapped before, as far as you know.

This lets automated processing identify the file correctly, and lets a calibration engineer step in quickly if the job is unusual. The full workflow is explained in how a tuning file service works.

How ChiptuneFile fits in

Keep your ORI close at hand: at ChiptuneFile you can order a back to original (3 credits) or a simple checksum correction (1 credit), which is essential whenever a file has been modified. To understand why, read checksums and CRC: why they are critical.

The platform accepts files from the common tools: Autotuner, KESS, K-TAG, CMD, Flex and more. If you are still choosing your hardware, see our comparison of Autotuner, KESS and K-TAG.

Checklist before sending

• Battery on a stable power supply during the read
• Read completed without errors, file size consistent
• Every generated file kept (flash, EEPROM, micro)
• ORI backed up in two places
• File named clearly
• Vehicle and ECU information complete
• Any doubt about a previously modified file flagged

Once you have the modified file, remind your customer that a remap used on the road should be declared to their insurer.

Send your ORI

Is your read ready? Create your account and upload your ORI file: automated processing sends back the modified file in under a minute, 24/7. Visit the pricing page to see the available credit packs.