What files can I upload?
A tune file or a raw ECU image as a .bin. You do not need to unpack anything yourself first — hand it over as it came off the vehicle.
What you can upload, how the editor works, and what the assistant can do. If your question is not here, get in touch.
14 questions
A tune file or a raw ECU image as a .bin. You do not need to unpack anything yourself first — hand it over as it came off the vehicle.
Uberdata works it out from the file itself, so you never pick from a dropdown. A tune somebody has already modified still resolves to the right ECU. If nothing matches, you are told the file is not supported rather than being given a wrong guess.
The supported-vehicles page lists every one, and it is generated live from the engine, so it cannot drift from what the software actually supports. If your vehicle is not on it, uploading a file from it will tell you so by name rather than pretending the file is broken.
Nothing at the moment. Uberdata is in early access: there is no billing, no credit packs and no per-flash fee. If that changes it will be announced before it applies to anything you have already uploaded.
Tables, single settings and option codes are all editable, each with a description rather than a bare address. They are filed into one category tree that is consistent across manufacturers, so fuel is in the same place on a KTM as on a BMW.
Your edits are written back into a copy of the ROM and stored as a new immutable revision. The previous one is never modified. The Revisions panel in the editor lists them all: you can open any earlier one read-only, restore it (which copies its values forward as a new revision rather than destroying what came after), or delete ones you no longer want. The first revision is always kept, so there is always a way back to stock.
Yes. Any revision downloads as a .bin, or re-encoded back into the container format you uploaded.
It is a set of real calibrations you can open and read without having pulled an image off your own ECU first — useful for learning how a tune is put together, or for looking at a vehicle before you buy one. They are preview-only: edit and explore freely, compare one against another or against your own tunes, but nothing is stored on our side and there is no save and no download. A file you can actually use has to be built on the image from YOUR vehicle, because that image carries the VIN and other data specific to it.
Prepared changes you can apply in one click, each with a written description of exactly what it does. You see a full preview of every affected value before anything is committed, and applying one creates an ordinary revision you can compare or roll back. Where a vehicle has none, everything is still editable by hand.
Yes. On a phone the editor shows one map at a time instead of floating windows: browse the tree, open a section, edit cells, run the tuning tools and save. It is genuinely usable on a screen the size of an iPhone 11, though a wide map is naturally easier on a laptop.
Any current Chrome, Edge, Firefox or Safari, desktop or mobile. The 3D surface view needs WebGL, which those all have; if it is unavailable the 2D grid still works.
It can read the tune you have open — values, descriptions and structure — answer questions about it, and make edits on your behalf. Anything it changes is saved as a normal revision with the author recorded, so you can see exactly what it did, compare it, and undo it.
No. Its edits go through the same revision system as yours — nothing is applied silently and nothing is overwritten.
When you use the assistant, yes: your messages and the parts of the tune needed to answer them are sent to the third-party provider of the underlying model. If you never open the assistant, your tune data is not sent to any third party. This is covered on the privacy page.