About DriveSize

DriveSize is an independent vehicle size and comparison website run by Ben and Laurence, based in England.

We started DriveSize in 2025 because car size information was often available, but not very useful in practice.

Our aim is to help people see the raw facts clearly, understand the context around them, and make better decisions about the cars they compare, buy, own, or park.

Why DriveSize exists

We built DriveSize to make vehicle dimensions easier to understand in real life.

Manufacturer brochures, review sites, and spec tables often tell you how long, wide, or tall a car is, but they do not always help answer the practical questions people actually have.

Questions like:

• Will this car fit my driveway or garage?
• Is it too wide or long for a parking bay?
• How much bigger is this SUV than the car I drive now?
• Is one boot space figure really comparable with another?
• Which model gives me more usable space without becoming harder to park?
• What do these measurements actually mean in everyday use?

Here at DriveSize, we try to answer those questions by combining the raw measurements with useful context.

What DriveSize does

DriveSize publishes vehicle size guides, side-by-side comparisons, visual overlays, and practical explainers focused on the measurements that affect everyday driving.

That includes:

• vehicle length, width, height, and wheelbase
• boot / cargo space
• width including mirrors where available
• parking fit context
• comparisons between two cars
• explainers for size-related terms and standards

Our aim is not just to list specs, but to help people understand what those specs mean when they are trying to choose the right car for their space and needs.

Where our data comes from

Here at DriveSize, we use official manufacturer documentation as our main source of car information wherever possible.

That usually means checking things like:

• official manufacturer spec sheets and technical specifications
• manufacturer brochures and model information pages
• official length, width, height, and wheelbase figures
• cargo, boot, and seating figures where available
• width including mirrors data where available
• other manufacturer-published measurements that help us compare cars properly

If an official figure is unclear, missing, or not directly comparable, we would rather be cautious than pretend the data is more certain than it is.

How we standardise and compare data

Manufacturer data is not always presented in the same way across markets, model years, or standards, so we standardise it as carefully as we can.

That includes:

• presenting metric and imperial units in a consistent format
• distinguishing between body width and width including mirrors where both are available
• keeping vehicle length, height, and wheelbase labels consistent across pages
• separating different cargo standards when they should not be treated as directly interchangeable
• using side-by-side comparisons, class benchmarks, and parking-fit context to make the numbers easier to interpret

Some of the figures shown on DriveSize are calculated from those published measurements. We explain those calculations because it should be clear which numbers come from a manufacturer and which ones come from us.

Footprint is overall length multiplied by body width, excluding the mirrors. It is a simple way to show how much rectangular ground space a car occupies, rather than a measurement of its exact body shape.

Where we show a class comparison, we compare the car with the DriveSize average for the same vehicle class and measurement. The number of cars behind an average can vary because manufacturers do not publish every measurement for every car.

Our DriveSize footprint comparison shows the percentage difference from the class average. A value of 0% matches the average, while positive values mean a larger footprint and negative values mean a smaller one.

A number on its own is rarely enough. A number compared with another car, against a parking space, or against a class average is much more useful.

When figures are not directly comparable, we try to say so clearly rather than force a neat comparison that could mislead people.

Which version of a car we use

As a rule, we use the base model as our default reference point unless a page clearly refers to a specific trim, body style, powertrain, cab type, or version.

That matters because measurements can vary by:

• market
• model year
• trim
• powertrain
• wheel and tyre setup
• mirrors folded or unfolded
• seating configuration

So while DriveSize is designed to be a practical guide, it should not replace checking the exact official specification for the precise vehicle you plan to buy, own, import, or park.

Cargo, seating and parking-fit methodology

Boot and cargo figures are useful, but they are not always measured under the same standard, so we try to be careful with them.

Where relevant, we distinguish between measurement methods such as VDA (commonly used globally) and SAE (used in the US) rather than treating them as if they mean exactly the same thing.

For some DriveSize calculations, we create a blended cargo figure using 65% of the standard published figure and 35% of the largest published figure. We use a complete VDA pair where one is available and a complete SAE pair otherwise. We do not mix figures from the two methods.

Cargo space versus length divides that blended cargo figure by the car's overall length. Cargo space versus footprint divides it by the car's footprint. DriveSize space efficiency then compares blended cargo space per square metre of footprint with the class average for the same cargo measurement method. A value of 0% is in line with that average; positive values mean more space efficient and negative values mean less.

Seating capacity is shown as a practical figure, but actual comfort and usable room can still vary depending on layout, body shape, and cabin design.

Our parking-fit checks are there to add practical context. They are not a guarantee that a car will fit every real parking space in every situation.

Our current parking-fit interpretation includes:

• regional parking-space presets for width and length
• side-clearance estimates based on body width where available
• length-clearance estimates based on overall vehicle length
• fit tiers that indicate whether a vehicle is comfortable, OK, tight, or too large for many bays

Where the figures are available, we use width including mirrors to check physical fit and body width to estimate side clearance. We round vehicle dimensions up and calculated clearances down, so the result does not suggest more room than the measurements support.

Real life is messier than a static model. Bay markings, walls, kerbs, pillars, nearby cars, and the shape of the space can all change how usable a parking spot actually feels.

How DriveSize manoeuvrability works

Turning circle and footprint tell you different things. Turning circle describes the room a car needs to complete a turn, while footprint describes the ground space taken up by its body. DriveSize manoeuvrability brings those two measurements together as a comparison aid.

The calculation gives 70% of the weight to turning circle and 30% to footprint. Smaller turning circles and footprints produce a higher underlying result. We then compare that result with the average for the same vehicle class. A displayed value of 0% is in line with the class average; positive values mean more manoeuvrable and negative values mean less.

This measure does not cover visibility, steering effort, handling, driver skill, or whether a car will fit a particular parking space. Our parking-fit checks are kept separate because they answer a different question.

Editorial principles

We want DriveSize to be clear, useful, and trustworthy.

That means we aim to:

• publish content that is written for people first
• make practical claims only where the underlying data supports them
• distinguish between direct measurements, estimates, and editorial interpretation
• avoid generic filler that does not help the reader to understand
• update pages when better or newer information becomes available
• correct errors when they are identified

Articles and model pages on DriveSize are written, edited, and reviewed by Ben and Laurence, with a focus on vehicle dimensions, comparison methodology, and consumer usability.

Important limitations

Even when we work from official manufacturer documentation, there is always the possibility of errors, missing figures, market differences, or pages that need updating.

We do not guarantee that every page on DriveSize is completely accurate, fully up to date, or free from mistakes.

The site should be used as a practical guide, and important decisions should always be checked against the official published specification for the exact vehicle in question.

Corrections and contact

We welcome corrections, feedback, and questions.

If you believe a page contains inaccurate or outdated vehicle data, or if you spot an error, please contact us at drivesize@drivesize.com with the page URL and the issue you spotted.

When appropriate, we review and update pages to improve accuracy and clarity.

Email: drivesize@drivesize.com

Instagram: @drivesize