Deadhead miles: the deductible miles the apps do not report

The single most overlooked deduction in gig driving has a trucking name: deadhead miles. In trucking, a deadhead is the distance a truck travels empty, with no load to haul. In rideshare and delivery, it is every business mile you drive without an active passenger or order: circling back after a drop-off, repositioning to a busier area, driving to your first pickup zone once you are working. These miles are deductible, and the platforms do not report them.

Understanding deadhead miles is the difference between deducting the miles you actually drove for business and deducting only the fraction the app happened to track. For most drivers, that gap is large.

What counts as a deadhead mile

The IRS lets you deduct miles driven for business purposes. For a gig driver, the active trip is obviously business, but so is a lot of the driving around it. Deadhead miles that generally qualify include:

• Repositioning between orders. Driving from one drop-off toward a busier zone or your next likely pickup, while you are actively working, is business driving even before the next order lands.
• Returning from a far delivery. If an order takes you well outside your usual area, the drive back to where you keep working is business mileage.
• Driving to refuel during a shift. A gas stop in the middle of an active shift is business driving.
• Waiting-area circling. Miles driven while actively available and working, moving between hot spots, generally count.

What does not count is the personal bookend of your day: the commute from home to where you start working, the drive home after you stop, and any personal errands you run while logged off. Those are personal miles even if they happen to sit right next to your working hours.

Why the platforms leave these miles out

Every major platform gives you a year-end mileage figure, but it is calculated narrowly. In general, the platforms count miles only while you have an active trip: from the moment you accept or start until the moment you complete. The stretches in between, when you have no active order but are still working, are invisible to their meter.

That is not the platforms being dishonest. Their number reflects what their systems can see, which is trip state. But it means their figure is a floor, not the full picture, and if you file using only that number you are leaving deductible miles on the table.

How big the gap actually is

For most drivers, deadhead driving adds up to roughly 15 to 30 percent more deductible miles than the platform-reported total. The exact share depends on how you work: drivers who chase surges across a wide area, or who deliver in spread-out suburbs, deadhead more than drivers working a dense downtown.

Put concrete numbers on it. Say a platform reports 24,000 active miles for your year, but with deadhead driving included you actually drove about 30,000 business miles. That extra 6,000 miles, deducted at the 2026 rate (72.5 cents per mile through June 30 and 76 cents from July 1 onward), is roughly $4,400 in additional deductions. For a driver who also owes 15.3 percent self-employment tax on top of a 22 percent income bracket, that is well over $1,500 in tax you would otherwise overpay, just from the miles the app never counted.

You are allowed to use your own number

A point that surprises a lot of drivers: you are not required to file using the platform's mileage estimate. The IRS requires you to keep your own contemporaneous mileage log, and if your records show more business miles than the platform reported, your records are what you file with, as long as you can substantiate them.

The catch is in that last clause. Deadhead miles are only worth claiming if you can back them up. Guessing at a percentage and adding it to the platform figure is not a log, and it will not hold up if you are ever asked. What holds up is a dated, trip-by-trip record that captured the driving as it happened.

How to capture deadhead miles the right way

There are two workable approaches:

• Manual odometer logging. Note your odometer at the start and end of each working session. The full session distance, not just the active-trip portion, is your business mileage for that shift. This captures deadhead by definition, because it measures the whole shift.
• Automatic shift-based tracking. An app that treats a working session as one continuous shift records every mile from the moment you start until you stop, including the repositioning and return miles between orders. This is the same idea as odometer logging, done automatically and with a GPS trail behind each trip for substantiation.

The common mistake is relying on an app that only logs discrete trips and then classifying each one, because that model tends to drop the gaps between trips, which is exactly where deadhead miles live. Shift-based tracking exists specifically to solve that. It is the approach MileShield is built around, and you can see how it works on the features page.

Keep it defensible

Two guardrails keep aggressive-but-legitimate deadhead claims safe. First, your total business plus personal miles cannot exceed the miles your odometer actually added during the year, so note your odometer at the start and end of the year. Second, your mileage should be plausible against your earnings; wildly high miles against low income is a classic audit flag. Deadhead miles are real and deductible, but they still have to be real.

The bottom line

The miles between your trips are business miles, and for most drivers they add 15 to 30 percent on top of what the platform reports. The only reason they go unclaimed is that they go unrecorded. Track your whole working shift, keep it dated, keep it defensible, and deadhead miles stop being the deduction you gave away without noticing.