If you are searching for how to translate MPG to L/100 km, how to translate fuel economy, or how to preserve km/L, miles per gallon, electric-vehicle consumption and MPGe-style figures across languages, the first problem is conceptual: some systems reward a larger number while others reward a smaller one. Higher MPG usually means better fuel economy, while lower litres per 100 kilometres usually means better fuel economy. A translator can preserve every numeral and still reverse the practical meaning if the unit logic is not understood.
Fuel-economy translation matters in vehicle specifications, car reviews, owner manuals, dealership listings, fleet reports, rental information, energy labels, automotive journalism and electric-vehicle comparisons. A target-language statement can become misleading if US and Imperial gallons are treated as the same, if km/L is confused with L/100 km, if a laboratory test figure is presented as guaranteed real-world consumption, or if an electric-energy value is converted without preserving the test procedure and driving context.
This guide explains how to translate fuel economy and vehicle-consumption data without changing what the numbers mean. It covers MPG, US versus Imperial gallons, L/100 km, km/L, litres per kilometre, energy consumption in kWh/100 km or Wh/km, MPGe-style equivalence metrics, city/highway/combined figures, test-cycle labels, range relationships and how to verify conversions mathematically before publication.
Why fuel economy is easy to reverse in translation
Fuel-economy systems do not all measure the same direction. MPG and km/L express distance travelled per unit of fuel, so higher values indicate greater distance from the same fuel amount. L/100 km expresses fuel used for a fixed distance, so lower values indicate better efficiency. A sentence such as “fuel economy increased” therefore needs careful interpretation when the unit system changes.
Gallons introduce another complication. A US gallon and an Imperial gallon are different volumes, so an MPG figure must retain which gallon definition the source uses. A numeric conversion performed with the wrong gallon basis produces a plausible-looking but incorrect target figure.
Vehicle consumption figures also belong to a test context. City, urban, highway, extra-urban, combined and standardized laboratory cycles describe different operating conditions. A translator should preserve those labels and avoid presenting one figure as universally representative of every trip.
The safest workflow is to identify the original unit, gallon definition, test context and vehicle-energy type first; calculate only when conversion is requested; and present the converted value as a secondary representation of the same measured or declared result.
A reliable translation method
1. Identify whether the source is distance-per-fuel or fuel-per-distance
MPG and km/L are distance-per-fuel measures. L/100 km is fuel-per-distance. Before translating comparative words such as better, worse, higher, lower, improved or reduced, identify which direction represents better efficiency.
2. Identify the gallon standard
If the source uses MPG, determine whether the gallon is US or Imperial. Do not infer from language alone when the document’s market or standard is ambiguous. Preserve the original label if necessary.
3. Preserve the original figure before conversion
Record the exact source value, decimal precision and test label. If a converted value is added, keep the original available for traceability rather than replacing it silently.
4. Use reciprocal conversion correctly
Converting between distance-per-volume and volume-per-distance is not a simple multiplication by a constant; it involves a reciprocal relationship. Verify formulas independently and test whether better efficiency still points in the correct numerical direction after conversion.
5. Keep test-cycle labels attached
City, highway and combined values are not interchangeable. Preserve the label that belongs to each value and maintain row order in tables.
6. Separate fuel consumption from energy consumption
Petrol, diesel and other fuels may be expressed in volume-based consumption, while electric vehicles are commonly described using electrical energy such as kWh/100 km or Wh/km. Translate the energy unit accurately rather than forcing all vehicles into fuel-volume language.
7. Treat equivalence metrics as named systems
MPGe-style metrics are designed to compare energy use through an equivalence convention. Preserve the named metric and its explanatory context rather than treating it as ordinary liquid-fuel MPG.
8. Verify comparative language after conversion
After converting, reread every phrase such as “higher efficiency,” “lower consumption,” “uses more fuel,” or “improved by.” The math and the prose must point in the same direction.
Twenty-four recurring fuel-economy translation problems
1. US MPG
A source value such as 30 mpg (US) expresses miles travelled per US gallon. The “US” qualifier is part of the measurement definition and should not disappear merely because the target language has a familiar word for gallon.
If conversion to L/100 km is requested, use the correct US-gallon basis and keep enough precision to reflect the source. If conversion is not requested, preserve mpg (US) and translate the explanatory wording.
For QA, verify that a higher MPG value still corresponds to a lower L/100 km value. That directional check catches many formula mistakes.
2. Imperial MPG
A value such as 30 mpg (Imp) uses a different gallon volume from US MPG. The same numeric MPG therefore does not represent the same litres-per-distance consumption.
Preserve the Imperial qualifier or market context. Never apply a US-MPG conversion constant to an Imperial-MPG source because the resulting target figure will be wrong even though it may look reasonable.
QA should explicitly record which gallon definition was used in the calculation.
3. Litres per 100 kilometres
L/100 km expresses fuel volume consumed to travel a fixed distance. Lower values generally indicate better fuel economy. Translators should not describe an increase from 6 to 8 L/100 km as an efficiency improvement.
Keep the denominator “100 km” visible. L/km and L/100 km differ by a factor of one hundred and should not be shortened into the same phrase.
QA should test a simple example: a vehicle at 5 L/100 km uses less fuel over the same distance than one at 10 L/100 km.
4. Kilometres per litre
km/L expresses distance per litre, so higher numbers indicate greater distance from the same fuel volume. It is directionally like MPG but uses metric distance and volume.
Do not translate km/L as litres per kilometre. The slash order matters because it changes which quantity is numerator and denominator.
QA should check that reciprocal conversions preserve the same physical efficiency.
5. Litres per kilometre
L/km is a fuel-per-distance measure and is not the same as L/100 km. Values are much smaller because the denominator is one kilometre rather than one hundred.
Preserve the denominator exactly and do not add “per 100 km” for familiarity unless the number is converted accordingly.
QA should multiply by one hundred only when intentionally converting to L/100 km.
6. City consumption
A city or urban figure belongs to a particular operating or test context. It should stay attached to that label and not be presented as the vehicle’s single universal consumption value.
Use the source system’s official localized term where available. Avoid rewriting city as “slow driving” unless the source defines the cycle that way.
QA should keep city, highway and combined rows aligned after translation or table reflow.
7. Highway consumption
A highway figure reflects another defined or advertised condition. Translate the label consistently and avoid combining it arithmetically with city data unless the source already provides a combined result.
Different markets may use terms such as extra-urban or motorway in different test systems. Preserve the source concept rather than assuming they are identical labels.
QA should trace each figure to the source row and test label.
8. Combined fuel economy
A combined figure is generally produced by a defined methodology or weighting, not necessarily a simple arithmetic average of city and highway values.
Translate combined as the official category and do not recalculate it from the other values unless the methodology is known and the task explicitly requires it.
QA should preserve the published combined value and its test-cycle context.
9. Test-cycle name
Vehicle specifications may cite a standardized test cycle by an acronym or official name. That identifier should remain intact because it tells readers how the number was produced.
Translate an explanatory expansion only from an authoritative source. Do not rewrite one cycle name as another market’s cycle because both measure fuel use.
QA should confirm that the same cycle label remains attached to the same figures.
10. Laboratory versus real-world wording
A source may distinguish a standardized laboratory result from owner-reported or observed real-world consumption. Those are different evidence types.
Preserve qualifiers such as rated, tested, certified, claimed, observed, average or real-world. Do not strengthen a laboratory figure into a promise of actual consumption for every driver.
QA should review modality and evidence language, not just numbers.
11. Petrol versus diesel consumption
The same L/100 km unit can describe different fuels, but the fuel type remains part of the vehicle specification. Keep petrol, gasoline, diesel or other fuel terms aligned with the source market and product.
Do not convert the fuel label merely because another term is more familiar in the target language if it could suggest a different fuel requirement.
QA should compare the engine variant and fuel type.
12. Hybrid consumption
Hybrid vehicles can have fuel-consumption figures influenced by battery charge, test procedure and driving mode. Preserve the source metric and any condition that explains how it was obtained.
Do not compare a charge-depleting hybrid result directly with a conventional-car fuel-only result unless the source methodology supports the comparison.
QA should keep electrical-energy and liquid-fuel figures in their own fields when both are present.
13. kWh per 100 km
kWh/100 km expresses electrical energy consumed per fixed road distance. Lower values generally indicate lower energy consumption under the same test context.
Keep kWh distinct from kW. One is energy; the other is power. Translating both as generic electrical output erases the physical quantity.
QA should preserve the denominator and test label.
14. Wh per kilometre
Wh/km expresses electrical energy per one kilometre. It can be converted to kWh/100 km, but the numeric value changes accordingly.
Do not merely swap the unit label. Convert value and denominator together if the project requires a different presentation.
QA should calculate the relationship independently and preserve decimal precision appropriately.
15. MPGe-style equivalence
An MPGe-style value is an energy-equivalence comparison, not a statement that an electric vehicle contains or burns gallons of petrol. Preserve the named metric and its explanatory purpose.
Do not translate MPGe as ordinary MPG or turn it into L/100 km without a verified equivalence method appropriate to the source system.
QA should keep energy-equivalence language visible so readers understand what is being compared.
16. Range and consumption
Driving range and energy consumption are related but different specifications. A vehicle with a larger battery can travel farther even if its consumption per kilometre is higher.
Keep range, battery capacity and consumption in separate fields. Do not describe greater range automatically as greater efficiency.
QA should check whether the source claims efficiency, capacity or range.
17. Fuel-tank capacity
Tank capacity is a stored volume, not a consumption rate. A 60-litre tank and 6 L/100 km fuel economy describe different quantities.
Translate capacity and consumption labels separately and keep the units distinct. Do not move a slash or denominator during layout cleanup.
QA should review units column by column.
18. “Improved by 10%”
Percentage improvement language is dangerous when converting between reciprocal measures. A ten-percent increase in MPG does not translate by simply reducing L/100 km by ten percent.
Preserve the original comparative claim unless the target document requires recalculation. If recalculating, compute from the before-and-after physical quantities rather than applying the same percentage to the reciprocal measure.
QA should test both endpoints numerically.
19. “Uses 20% less fuel”
A statement about fuel consumed is not identical to a statement that MPG is twenty percent higher. Reciprocal relationships make intuitive percentage wording easy to mishandle.
Translate the claim at the level it is made. If the source says less fuel over the same distance, preserve that consumption framing unless the conversion is explicitly calculated.
QA should reconstruct a simple sample trip to confirm the comparison.
20. Decimal precision
Vehicle specifications may report 6.4 L/100 km rather than 6 or 6.40. That precision may reflect the source publication style or test reporting.
Keep source precision unless the target style has a justified rule. Converted values should not imply more accuracy than the original measurement supports.
QA should round only after completing the calculation.
21. Decimal comma
Some target languages use a decimal comma. Localizing 6.4 to 6,4 can be appropriate in prose, but the rest of the unit and thousands-separator conventions must remain unambiguous.
Do not change standardized codes or machine-readable fields merely because target prose uses different punctuation.
QA should review human-readable tables separately from data exports.
22. Vehicle variant
Fuel economy can differ by engine, transmission, drivetrain, tyre, wheel and body variant. A source table may list several versions of the same model.
Keep every figure attached to the correct variant. Translation should not merge rows because model names look similar.
QA should trace the target row to the exact source configuration.
23. Model year or test version
A fuel-economy value can belong to a particular model year or testing regime. Preserve date/version context when the source provides it.
Do not silently combine results from different model years or standards into one target figure. A translation should remain a faithful representation of the source document.
QA should keep model year, test label and value together.
24. Estimated annual fuel or energy use
Some labels convert per-distance consumption into annual estimates using assumed mileage or energy prices. Those assumptions are part of the calculation.
Translate the annual estimate together with its assumed distance, price basis and conditions. Do not present it as a guaranteed cost or consumption figure.
QA should preserve every assumption stated in the source.
Common failure modes
1. Treating higher numbers as always better
Higher MPG can mean better efficiency; higher L/100 km means more fuel consumption. Check unit direction before translating comparisons.
2. Confusing US and Imperial gallons
They are different volumes. The gallon definition must be known before conversion.
3. Replacing L/100 km with km/L without calculation
They are reciprocal measures. The numeric value cannot stay the same.
4. Dropping city/highway/combined labels
Test context is part of the meaning. Keep each figure with its category.
5. Treating kWh as kW
Energy and power are different physical quantities. Preserve the hour component in energy units.
6. Treating MPGe as ordinary liquid-fuel MPG
It is an equivalence metric. Keep its explanatory context.
7. Rounding before converting
Early rounding can distort reciprocal conversions. Calculate first and round last.
8. Presenting test values as guaranteed real-world results
Preserve source qualifiers and test context rather than strengthening the claim.
Worked practice
Practice 1: US MPG to L/100 km
Situation: A US-market source reports fuel economy in mpg (US), while the target publication uses L/100 km.
Reasoning: Identify the US gallon, keep the original value for traceability, use the correct reciprocal conversion, round only at the end and verify that a higher MPG source value becomes a lower L/100 km target value.
Practice 2: Imperial MPG
Situation: A UK-oriented historical document reports mpg without an explicit gallon label but clearly belongs to an Imperial context.
Reasoning: Preserve the market context and use the Imperial-gallon basis if conversion is authorized. Do not reuse a US-MPG formula.
Practice 3: L/100 km comparison
Situation: Vehicle A uses 5.5 L/100 km and Vehicle B uses 7.0 L/100 km.
Reasoning: In the same conditions, A has lower fuel consumption. Do not describe B as more efficient merely because 7.0 is numerically larger.
Practice 4: Electric consumption
Situation: An EV specification lists 16.5 kWh/100 km.
Reasoning: Keep energy per distance as an electrical-consumption metric. Do not translate it as battery power or battery capacity.
Practice 5: Wh/km
Situation: A technical display shows 165 Wh/km, while the target article prefers kWh/100 km.
Reasoning: Convert value and denominator together, verify the arithmetic, and retain enough precision to represent the source accurately.
Practice 6: Combined figure
Situation: A manufacturer lists city, highway and combined values.
Reasoning: Translate all three categories and preserve the published combined result; do not average city and highway figures unless the source methodology calls for that calculation.
Practice 7: Hybrid data
Situation: A plug-in hybrid lists liquid-fuel use and electrical-energy use separately.
Reasoning: Keep the two energy streams distinct and retain the test condition that explains when each value applies.
Practice 8: Efficiency claim
Situation: Marketing copy says the new model uses 15% less fuel over the same distance.
Reasoning: Preserve the consumption framing. Do not convert it into “15% higher MPG” without calculating the reciprocal relationship correctly.
Calculators, test documents and AI
Official vehicle specifications, test labels and manufacturer data are the strongest sources for the original measurement and test context. Conversion calculators are useful only after the source unit and gallon definition are identified correctly.
AI can explain the relationship between MPG, L/100 km and km/L, but it may assume a US gallon when the source is Imperial or may round too early. Always state the source unit explicitly and verify the calculation independently.
When publishing converted values, consider showing the source figure as well. Dual presentation makes the translation auditable and reduces the risk that a target reader mistakes a derived number for the original certified or published figure.
How this fits the wider eduKate translation system
Fuel-economy translation combines reciprocal quantities, unit systems, comparative language and test context. The broader method is developed in Master Art of Translation | The Complete System for Moving Meaning Between Languages. Vocabulary depth connects to the Vocabulary Learning Hub, while comparison, proportion and measurement language connect to How English Works. The special rule here is directional: the target wording must preserve whether a larger or smaller number means better efficiency.
FAQ
Is higher MPG better?
For the same gallon definition and test context, higher MPG means more distance per gallon and therefore better fuel economy.
Is lower L/100 km better?
For the same conditions, lower L/100 km means less fuel used over the fixed distance.
Are US MPG and Imperial MPG the same?
No. The gallon volumes differ, so the same numeric MPG does not represent the same physical fuel consumption.
Is km/L the same as L/100 km?
No. They are reciprocal-style measures. Conversion changes the numeric value and reverses whether higher or lower is better.
Is kWh/100 km a battery-capacity number?
No. It is energy consumed per distance. Battery capacity is a stored-energy quantity.
Can MPGe be translated as MPG?
No. MPGe is an equivalence metric and should remain identified as such.
Should city and highway values be averaged?
Not unless the source methodology explicitly calls for that calculation. Use the published combined value when provided.
Can I compare figures from different test cycles directly?
Be cautious. Preserve the test-cycle labels because results can depend on methodology and conditions.
Should converted figures show many decimal places?
No more precision than the source and publication context justify. Calculate accurately, then round appropriately.
What is the simplest rule?
Identify the exact unit and test context first, convert only with the correct basis, and verify that better efficiency still points in the correct numerical direction.
Final checklist
- Is the source measure distance-per-fuel or fuel-per-distance?
- If MPG is used, is the gallon definition known?
- Is the original figure preserved for traceability?
- Are city, highway and combined values attached to the correct labels?
- Is the test-cycle or rated/real-world context preserved?
- Are liquid-fuel and electrical-energy quantities kept distinct?
- Are kW and kWh kept separate?
- Are reciprocal conversions calculated rather than relabelled?
- Was rounding done only after calculation?
- Does the target comparison still say correctly which vehicle uses less energy or fuel?
Fuel-economy translation succeeds when the target reader receives the same physical efficiency claim, the same test context and the same directional comparison as the source reader. Identify the unit family, protect gallon definitions and cycle labels, calculate reciprocal conversions carefully, and reread comparative language after every conversion so the meaning cannot flip while the numbers remain plausible.