Before a single map is changed, every WinOLS job starts the same way: the original read from the car is imported into a new project. Get this step right and everything that follows (map search, versions, comparisons, checksums) works as intended. Get it wrong, for example by importing an already modified file as the “original”, and you can end up with wrong comparisons or a checksum module that does not recognise the data. This guide shows how to import an original ECU read and create a project in WinOLS, step by step, using the menus described in EVC’s own manual.
Facts checked on 27 October 2026 in EVC’s public WinOLS manual (version 5.94, dated 10 September 2026) and on the WinOLS product and download pages, linked in the sources at the end. The current WinOLS 5 release listed that day was 5.95. Menu names can change between versions, so check the built-in help of your version too.

What you need before you start
- A licensed WinOLS installation. EVC lists WinOLS 5 for Windows 10 (x64), Windows 11 (x64) and Windows 11 (ARM) (source). A free demo version is offered on the download page if you only want to practise the workflow (source). Use only genuine, licensed software.
- The unmodified original read from your reading tool, plus its identification data (ECU hardware and software numbers, read method). Our KESS3 OBD read guide and AutoTuner backup file guide explain how to get and keep that file safe.
- A copy of the file outside your working folder. Import from a copy, and keep the untouched file archived with the job.
Step 1: check which file format you have
WinOLS cannot edit external file formats directly. The manual explains that because WinOLS stores a lot of additional information, a file must first be imported into a WinOLS project and later exported (or written) again (source). The import dialog starts with the file format:
- Binary: the pure memory data without control information. Most tool reads you will handle are binary dumps.
- Intel-Hex (often
.hex, sometimes.pafor.daf) and Motorola-Hex (often.s19). - WinOLS files (
.ols) and older OLS files (.dat). - Further formats are added by plugins, and the manual notes that supported files can also be imported while compressed as
.zipor.rar(and.7zif 7-Zip is installed) (source).
If your tool saved an encrypted file (for example a Slave-tool file), it has to go to the person or service that can decrypt it. WinOLS is not a way around a tool’s licensing.
Step 2: create an empty project
Choose Project > New (keyboard: Ctrl+N). According to the manual, this creates an empty project into which data from a file, an EPROM or an ECU can then be read (source). The empty project window lists files from a folder you can choose with the […] button, and WinOLS hides files that are probably not useful, such as images. If you want to open a project you already have, use Open instead of New.
Step 3: import the original read
The manual gives two ways to bring the file in (source):
- Drag and drop the file into the empty project window, or
- Use Project > Ex- & Import > Import file (Ctrl+I), choose the file format, click OK and select the file.
Watch where you drop a file. The manual explains that a file dropped over an existing project window is imported as a version of that project, while a file dropped on the WinOLS frame window or an empty workspace background becomes a new project (source). Dropping a customer’s stock read onto the wrong open project is a classic way to mix up two cars.
Step 4: understand “Original” and enter the vehicle data
The first data imported into a project is automatically saved as the Original; anything imported after that is a Version. EVC warns that some checksums require the Original to contain the unmodified data from the ECU, and that otherwise a checksum may not be recognised or calculated correctly (source). So:
- Import the stock read first, never a tuned file.
- When the dialog asks for vehicle data after the import, fill it in. The manual describes it as the information that makes the project identifiable later.
- All later versions are compared with the Original automatically, and the differences are shown in colour (source).

Step 5: check the project properties
Open the project properties and check the fields that affect your work (source):
- Client and Vehicle (producer, chassis, model): useful for finding the project later. The online project search on the product page can fill in some fields automatically (source).
- ECU producer: the manual says this field matters for the automatic map search, because WinOLS uses producer-specific algorithms; an empty or wrong value can reduce the number of maps found.
- Software size: leave it alone unless you know why. Changing it affects all versions, cannot be undone, and making it smaller permanently loses data.
- Project type (complete binary file, partial map data, partial full length): set it to what the file really contains.
- Elements: one ECU can hold data in several memories (for example program flash, CPU-internal memory, EEPROM), and WinOLS manages these as elements. The map list, the differences window and binary export work on the active element only, so check which one is active (source).
Then save the project with Project > Save (Ctrl+S).
Step 6: let the map search run, then create your first version
After a new project is created, WinOLS starts searching for maps automatically after a few seconds; you can see the progress in the status bar, and found maps appear in a “potential maps” folder (source). Our WinOLS calibration editor explainer covers how maps, axes and factors are read once they are found.
Work in versions, never on the Original. EVC describes storing modifications as commented versions, with the original stored permanently, changes shown in colour, multi-level undo and the option to restore original values at any time (source). Give each version a clear name and comment (for example “Stage 1 draft” or “after log review”), and use version folders if you want to keep the list organised; the manual notes that folders only affect the display (source).
Checksums and export: the last steps
- WinOLS corrects checksums through separately purchased checksum plugins from EVC. The checksum dialog is under Edit > Checksum (F2), and if you do not own the right module you can have the project checked online to find out which one fits (source). A file written with a wrong checksum may not run.
- When exporting, choose the format your writing tool expects. If the format does not support elements, only the active element is exported, unless you select <All elements> first (source).
Common mistakes
- A tuned file imported as the Original. Comparisons become meaningless and some checksum modules can fail. Start a new project from the true stock read.
- A file dropped onto the wrong open project. It becomes a version of another car. Check the window title and version list after every import.
- A partial read treated as a full read. An OBD read is not always the full memory. See OBD, bench and boot reading methods.
- Wrong producer or software size in the project properties, which leads to poor map search results or lost data.
Prefer to send the file instead?
If you would rather not build the project yourself, upload your original read to ECU File Market with the vehicle, engine, ECU hardware and software numbers, the tool and the read method, the stage you want and any hardware already changed. Credits per ECU tier are listed on our pricing page, and most files are returned in under one hour during support hours. Checksum correction, where needed, is a paid extra.
Good practice: only work on vehicles you own or are authorised to work on, keep the original file for the life of the car, and keep all emission control systems fitted and working. This guide does not cover removing or disabling DPF, EGR, SCR/AdBlue or any other emission equipment.
Sources (checked 27 October 2026)
- EVC electronic, WinOLS manual (English PDF, version 5.94): evc.de/ftp/winols/WinOLS HelpEn.pdf (sections 1.7 Projects, 2.1 Creating a new project, 2.11 Correcting checksums, 3.8 Elements, 4.1 New, 4.7 Project properties, 4.12.1 Import file)
- EVC electronic, WinOLS software product page: evc.de/en/product/ols/software/
- EVC electronic, WinOLS download page (versions, demo, manual): evc.de/en/download/down_winols.asp
WinOLS is a registered trademark of EVC electronic. Other product and company names are trademarks of their respective owners. ECU File Market is an independent tuning file service and is not affiliated with, endorsed by or sponsored by EVC electronic. Names are used only to describe compatibility and workflow. Use only genuine, licensed tools and software.