RemappingData.com exists because most remapping websites are built to sell a remap, not to answer the question honestly. It pulls together standard ECU remap (Stage 1) figures for thousands of engines across around 70 makes, built from independent research rather than a single tuning company’s own claims. The aim is simple: find a vehicle fast, get a realistic figure, and see the risks as well as the benefits.
I’ve spent hundreds of hours over almost a year building RemappingData.com opens in a new tab.
That probably sounds excessive for a website about ECU remapping figures.
It would have been, if all I wanted was another website where somebody chooses a make, model and engine and gets told their car could gain another 30 BHP.
That wasn’t really the problem I wanted to solve.
The problem was everything around those numbers.
The idea came from working on remapping websites
I didn’t wake up one morning and randomly decide the internet needed another automotive website.
The idea grew out of work I’d already done for remapping specialists.
I’ve worked with PP Tuning, TH Performance and Pendle Performance, all three businesses I’d happily recommend.
PP Tuning has been the biggest influence simply because of the amount of work I’ve done with them. Building and developing their website, researching articles and looking at the questions their customers ask has given me a much deeper understanding of remapping than I would ever have gained from reading tuning websites from the outside.
I also carried out website work for Pendle Performance, mainly around layout and presentation. While doing that, I saw some of the same usability issues I’d already been thinking about elsewhere, particularly around how quickly somebody could get from a vehicle search to the information they actually wanted.
Jason at PP Tuning had mentioned that problem to me countless times too.
None of that means these are bad websites or bad businesses. Quite the opposite.
The interesting thing was that I was seeing the sector from several angles, and the same thought kept coming back.
There is loads of remapping information online. The problem is finding the right information, for the right vehicle, quickly, and without everything being shaped around making a sale.
That distinction started bothering me.
A remapping business has a perfectly reasonable objective
There’s nothing sinister about a remapping company wanting its website to sell remapping.
That’s what the business does.
It needs enquiries and bookings. It needs somebody looking at a particular vehicle to think, “Yes, that sounds worthwhile.”
So naturally the website concentrates on the benefits. More power. More torque. Better throttle response. Potential fuel economy improvements. Perhaps a graph showing how much better things could become after the ECU has been remapped.
What it probably won’t spend quite as much time discussing is whether a particular engine has known weaknesses, whether the likely gain is modest, whether the transmission needs consideration, or whether published figures elsewhere look optimistic.
It’s a consequence of the website’s purpose, not a criticism of it.
I started wondering what the same subject would look like if the website didn’t have to sell the remap.
That became RemappingData.com.
The data was the starting point
I started compiling the underlying data towards the end of 2025.
That involved building large datasets from publicly available information, then spending a lot of time cleaning, checking, reorganising and questioning what I’d collected.
That process is still ongoing.
The site currently contains more than 7,600 individual engine records across around 70 vehicle makes and hundreds of models. Those numbers will keep changing as existing data is refined and new vehicles are added.
A row of data sounds simple enough. Make, model, variant, engine, standard BHP, remapped BHP, standard torque, remapped torque.
But vehicles don’t organise themselves as neatly as spreadsheets would like them to.
The same model can span several generations. The same engine capacity can exist in several factory outputs. The same model name can mean very different vehicles depending on generation, fuel type, turbo type and year.
A Volkswagen Golf Mk5 is not a Golf Mk8.
A Transporter owner is far more likely to think T5 or T6 than whatever terminology happens to make the database convenient.
The data can become complicated very quickly.
My job was to make sure using it didn’t.
Then I built it once. And rebuilt it.
The first full version of RemappingData.com was built in January 2026 using Advanced Custom Fields Pro.
There was nothing inherently wrong with that.
ACF is a very capable WordPress tool and I’ve used it extensively.
But as the project developed, I kept thinking of things I wanted the website to do. Faster searching. Better relationships between the data. Saved vehicles. Curated routes into commonly researched models. More flexible ways of using the same information in different places.
By May and June, I had a choice.
I could keep writing more code around the structure I’d already built, or accept that I’d outgrown it.
So I rebuilt it.
The ACF-based structure went and the main architecture was rebuilt in custom code.
Custom Post Types, taxonomies, relationships, data handling and most of the important site features are now controlled by purpose-built code and a small set of custom plugins.
That meant throwing away work.
It also meant cleaning up plenty of leftovers from the first build.
But keeping the wrong architecture simply because you’ve already invested time in it is a good way of spending even more time fighting it later.
I became slightly obsessed with the search
Search sounds like a boring feature.
Until you use a bad one.
I’ve used vehicle lookup systems where you select the make, wait, select the model, wait again, choose another option, wait again, then eventually reach the information you wanted several clicks earlier.
It technically works.
That doesn’t make it good.
RemappingData.com has thousands of engine records, so finding the right one needed to feel immediate.
The search page lets somebody rapidly narrow the database by Make and Model, then filter it further using text.
Frequently remapped Makes are also placed in a small section at the top of the selector.
Volkswagen still appears in its normal alphabetical position, but somebody looking for it can also get to it immediately.
The same applies to commonly remapped Models.
Choose Volkswagen and models such as Golf and Transporter are available at the top while still appearing in their normal alphabetical position.
A tiny detail.
But tiny details are usually what separate a good website from an annoying one.
Sometimes the best search is not having to search
I’ve also been building manually curated pages around important makes and groups of vehicles.
The VAG and Volkswagen sections are already live, with more planned.
These aren’t simply automatically generated archive pages.
They’re deliberate routes into the data.
A page can contain links to a particular vehicle group which take somebody straight into the search system with the relevant criteria already applied.
Click the link and the useful results are already there.
That becomes particularly valuable where people naturally think in generations.
A Transporter owner might want T4, T5, T6 or T6.1.
A Golf owner might be looking for a particular Mk generation.
They shouldn’t need to understand how I’ve structured the database.
The database should do that work for them.
The answer is often already in the search result
I didn’t want somebody opening a dozen engine pages just to compare a handful of vehicles either.
The result cards give an immediate summary.
They show the vehicle details, variant and engine, together with the standard and typical remapped BHP and torque figures.
For somebody doing a quick comparison, that may be everything they need.
If they want more, they can open the full engine page.
Again, none of this is technically revolutionary.
It’s simply designing around what somebody is actually trying to do.
My Garage came from the same thinking
The other feature I particularly wanted was My Garage.
People can register for free and save a Make, Model or individual Engine.
Those saved items then live on their own My Garage page, separated into saved Makes, Models and Engines.
Saved engines use the same quick-reference style as the search results, so somebody can return later and immediately see the important figures.
That may be useful to somebody researching their own cars.
It could be even more useful to a remapping specialist who regularly works with certain Makes, Models or engines and wants them close at hand.
Registration also gave me a clean way of providing persistent saved information without relying heavily on cookies or browser storage.
The figures still need questioning
None of this is useful if the underlying information is rubbish.
Remapping figures are surprisingly inconsistent.
Look at enough tuning websites and you’ll find different claimed outputs for the same engine.
Sometimes the differences are small.
Sometimes they most definitely aren’t.
There are legitimate reasons for variation. Different vehicles, different dynos, different software, different conditions and different tuning approaches can all produce different results.
But there is also an obvious commercial incentive to publish the bigger number.
“Up to” has done a lot of work in marketing over the years.
So when something looks questionable, I research it.
I compare figures across different remapping businesses.
I look at specialist discussions.
I look at forums and Reddit where owners talk about what they actually achieved.
I’m trying to determine what looks like a sensible, typical number, not the biggest one.
Stage 1 is complicated enough
RemappingData.com concentrates on what most people mean when they ask about remapping: a standard ECU remap, commonly called Stage 1.
Stage 2 and Stage 3 may be discussed where relevant editorially, but I deliberately haven’t tried to build the same kind of comparison database around them.
Once hardware modifications become part of the equation, the variables multiply rapidly. Different exhausts, different intercoolers, different turbos, different supporting modifications, different tuning objectives.
Trying to turn all of that into one neat universal figure would undermine what I’m trying to do.
Stage 1 gives me quite enough to argue with already.
Not everything I find is positive
This is one of the biggest differences between RemappingData.com and a remapping sales website.
I don’t need the answer to be positive.
If research suggests a particular engine has a weakness worth knowing about, I can say so.
If a transmission needs consideration, I can say so.
If the likely gain is disappointing, there is no reason to dress it up.
And if changing regulations could affect modified vehicles, that belongs there too.
I recently spent most of a day going through proposed 2026 changes relating to in-use vehicle emissions and considering what they could mean for modified vehicles and the remapping sector.
That doesn’t produce another exciting “Look how much power you can gain” page.
But it might be considerably more useful to somebody deciding whether modifying their vehicle is sensible.
Remapping is mostly a positive story.
That doesn’t mean the inconvenient bits should disappear.
It has become much bigger than an engine database
That’s probably the thing I hadn’t fully appreciated when I started.
The engine figures are still the spine of RemappingData.com.
But the project has gradually become a broader reference resource. There’s the engine data, research into what remapping actually does, reliability, insurance, previously modified vehicles, emissions systems, legal considerations, changing regulations, engine-specific issues, and manually researched pages connecting those subjects to particular vehicles.
The interesting part for me is organising all of that without making the website feel enormous.
Because there’s a fairly simple rule behind most of my website work:
The complicated bit should be my problem, not the visitor’s.
Hundreds of hours later
I started collecting the first data towards the end of 2025.
It’s now September 2026.
I couldn’t tell you exactly how many hours have gone into RemappingData.com without making a number up, but it’s comfortably in the hundreds.
Some of those hours produced code. Some produced thousands of rows of cleaned data. Some produced articles. Some produced features. Quite a lot produced nothing visible at all because they were spent deciding an idea wasn’t good enough, undoing something I’d already built, or working out how to make a process simpler.
That’s website development too.
Probably more of it than people realise.
What I was trying to build
The easiest description of RemappingData.com is still that it’s a website containing ECU remapping performance data.
It just doesn’t explain it very well.
What I’ve actually been trying to build is the resource I kept wanting to find while working in the remapping sector. Somewhere that makes it quick to find a particular vehicle. Somewhere that gives useful figures without trying to turn every visitor into a sales lead. Somewhere that can say a claimed gain looks unrealistic. Somewhere that can discuss risks as well as benefits. And somewhere that treats usability as part of the information rather than something added afterwards.
There is still plenty left to build.
That’s probably inevitable.
The more useful the resource becomes, the more obvious the next useful thing becomes.
But after nearly a year of collecting, cleaning, researching, coding, rebuilding and occasionally wondering why I gave myself quite such a ridiculous project, it now looks much more like the thing I had in my head when I started.
Only considerably bigger.
