Can I Use Google Maps for Mileage Tracking? (2026)

Yes, technically — but Google Maps Timeline is location history, not a mileage log, and on its own it fails the IRS substantiation rules under §274(d). It can support a real log; it can’t replace one.

Key takeaways

• Google Maps Timeline records where you were and how you got there — but never why, which is exactly what §274(d) requires.
• Since December 2024, Timeline data lives only on your phone. Lose the phone, lose the records.
• The default Timeline auto-delete is now three months. The IRS audit window is three to six years.
• No reported Tax Court decision has accepted Google Maps Timeline data, standing alone, as adequate §274(d) substantiation. Reconstructed logs lose (see Velez and Khan).
• Timeline is useful as a backup or cross-check — not as your primary mileage record.

What Google Maps Timeline actually tracks

When Location History is turned on (it’s off by default in 2026 and must be opted into), Timeline saves:

• The places your phone visited, with timestamps.
• The route between them on a map.
• An inferred mode of transport — driving, walking, biking, transit.
• An estimated distance per day.
• A daily “trips” view you can scroll through.

What it does not record: the business purpose of any trip. Timeline knows you went to a Target at 2:14 p.m. It doesn’t know you were picking up a Spark order, dropping off a Shipt batch, or buying socks for yourself.

That distinction is the whole article.

The 2024 Google change — Timeline now lives on your device only

On December 12, 2023, in the official Google blog post “Updates to Location History and new controls coming soon to Maps,” Google announced a fundamental change to how Timeline works — and it rolled out broadly through 2024. As 9to5Google reported on December 11, 2024, Google Maps is switching to a local, on-device approach: Timeline (previously called “Location History”) is now phone-specific, multiple devices cannot contribute to it, and the web version is no longer available.

Three consequences matter for taxes:

1. No more web access. You can’t open timeline.google.com on a laptop and view your routes. Timeline lives in the mobile Google Maps app.
2. Device-specific. If your phone is lost, broken, factory-reset, or replaced, your historical Timeline is gone unless you enabled the encrypted cloud backup before the loss.
3. New default auto-delete: three months. Per Google’s official December 12, 2023 announcement (Marlo McGriff, blog.google): when you first turn on Location History, the auto-delete control is set to three months by default; previously this option was set to 18 months.

The IRS general audit window is three years (IRC §6501(a)), six years if you’ve understated gross income by more than 25% (§6501(e)), and unlimited if you never filed (§6501(c)). A three-month default retention is not compatible with a three- to six-year audit window.

What the IRS actually requires — the §274(d) standard

Vehicle expenses are “listed property” under IRC §280F(d)(4), which means they’re governed by the strict substantiation rule of §274(d). For each business trip you must establish:

1. Amount — the business miles (or the dollar expense).
2. Time — the date of the trip.
3. Place — where you went.
4. Business purpose — why the trip was for your trade or business.

Temp. Treas. Reg. §1.274-5T(c)(2) calls this the “adequate records” standard: an account book, diary, log, statement of expense, trip sheet, or similar record, made “at or near the time” of the trip. Electronic logs qualify — but the four elements still have to be there. IRS Publication 463 (2025) restates the same rule.

The Cohan rule (Cohan v. Commissioner, 39 F.2d 540 (2d Cir. 1930)) — which lets courts estimate undocumented expenses — does not apply to vehicle expenses. The regulation itself overrides Cohan for §274(d) items, and the Tax Court has reiterated that point many times (e.g., Sanford v. Commissioner, 50 T.C. 823 (1968)). No log, no deduction.

Where Google Maps Timeline falls short

Timeline misses on at least four of the §274(d) elements.

No business purpose. This is the killer. Timeline cannot record why you drove anywhere. In Garza v. Commissioner, T.C. Memo. 2014-121, the taxpayer had calendars with locations and miles but no documented business purpose — the Tax Court denied his entire $20,085 deduction. Timeline is essentially the digital version of Garza’s calendar.

No business/personal split. Timeline treats your DoorDash run and your trip to your kid’s soccer game identically. There is no swipe-to-classify, no auto-categorization, no business folder.

No IRS-ready export. You can export individual days as KML, or pull a JSON file through the on-device “Export Timeline data” option, but neither is a mileage log. You’d have to manually translate raw location data into a date/place/miles/purpose log — and the moment you do that long after the trip, you’re in Velez territory (more on that in a moment).

Accuracy gaps. Timeline mis-identifies modes of transport, misses trips entirely, snaps to nearby addresses instead of the actual destination, and uses straight-line approximations in low-signal areas. The Register reported on December 13, 2024 (“Google Timeline location purge causes collateral damage”) that numerous threads on Reddit and in Google’s support forum documented widespread data loss; one affected user told the publication they would have been absolutely destroyed if they had accidentally selected the default option in the Google Timeline migration. For audit defense, “the app sometimes guesses” — and sometimes silently deletes — is not where you want to be.

Add the 2024 storage change and the three-month default deletion, and you have a record that may not even exist by the time you’re audited.

Recent Tax Court cases that should worry you

Three cases bracket the risk.

• Velez v. Commissioner, T.C. Memo. 2018-46 — Ohio attorney with five offices reconstructed a mileage log from his iPad calendar and credit-card statements two days before trial. The court rejected the entire $18,946 deduction and sustained a $3,948 negligence penalty under §6662. Reconstructions after the fact don’t satisfy “adequate records.”
• Garza v. Commissioner, T.C. Memo. 2014-121 — Calendar showed locations and odometer readings but no business purpose. Entire deduction disallowed.
• Khan v. Commissioner, T.C. Summ. Op. 2025-5 (February 2025) — The petitioners (Safdar S. Khan and Maryam Tahir) offered generalized explanations and reconstructed spreadsheets, and the court held they did not maintain adequate books or records that support the claimed expenses under section 274(d). Vehicle and travel deductions evaporated. (As a Summary Opinion under §7463(b), Khan is non-precedential — but it shows how the court is currently applying the rule.)

The lone positive case in this cluster, Patitz v. Commissioner, T.C. Memo. 2022-99, is instructive in the other direction. Per the Journal of Accountancy (“Digital documentation: Avoiding a business deduction disallowance,” May 2023): the taxpayers in Patitz were able to adequately substantiate unreimbursed business travel expenses as employees for the 2015 and 2016 tax years, because the court found their testimony credible and their electronic logbooks documenting mileage were sufficient contemporaneous records to allow for a deduction. Note what won that case: an electronic logbook kept contemporaneously — not raw location pings pulled from a phone after the fact. Contemporaneous beats reconstructed, every time.

When Google Maps CAN help (and when it can’t)

Honest uses for Timeline data:

• Cross-check trips already captured by a dedicated tracker — useful if you want to confirm an address or a route.
• Reconstruct a small gap if your real tracker missed a few days. Annotate purpose contemporaneously from your gig-app history (DoorDash, Spark, Uber, Instacart all retain delivery records).
• Corroborate specific high-stakes trips during an audit — Timeline plus a delivery receipt plus a bank deposit is much stronger than Timeline alone.
• Demonstrate you did not drive somewhere — an alibi-style use that occasionally matters.

What Google Maps cannot do honestly:

• Serve as your sole mileage record for a tax year.
• Generate a Schedule C–ready report.
• Survive an audit after a phone replacement or factory reset.
• Provide the business-purpose element §274(d) requires.

The honest comparison

At the 2026 business standard mileage rate of 72.5¢ per mile (IRS Notice 2026-10, issued Dec. 29, 2025; IR-2025-128: 72.5 cents per mile driven for business use, up 2.5 cents from 2025), a gig worker who drives 15,000 business miles claims a deduction of $10,875. Losing that deduction in an audit because your records didn’t meet §274(d) is an expensive way to save $40 a year.

The fix

Google Maps Timeline is a useful supplement and a terrible primary record. EveryLastMile, an iOS mileage tracking app, does automatically — with business-purpose tags, automatic classification, IRS-formatted exports, and durable backups — what Google Maps Timeline does only by accident, only manually, and only for the last three months.

For the 2026 rate the deduction is calculated against, see the 2026 IRS Mileage Rate deep dive. For the §274(d) audit-response mechanics if a letter ever lands, the Mileage Audit Defense Playbook. The platform-specific pillars cover the rest of the Schedule C picture: Delivery Driver Mileage Tax Guide 2026, Uber & Lyft Driver Mileage Tax Guide 2026, Walmart Spark Driver Tax Guide 2026, Instacart Driver Tax Guide 2026. And if you’re weighing standard mileage against actual expenses — including whether insurance is a separately deductible line item — see Is Car Insurance Tax Deductible? (2026).

Frequently asked questions

Is using Google Maps Timeline for mileage tracking illegal?

No. There's no law against it. The risk is in an audit: a Timeline export does not, on its own, satisfy IRC §274(d). You're betting that the IRS won't ask — and that you'll still have the data if they do.

Can I just print my Timeline as my mileage log?

You can print it. It won't satisfy §274(d) because it has no business purpose field, no business/personal split, and (after Google's 2024 change) often only the last three months of data. Garza v. Commissioner lost on essentially these facts.

What about the 2024 on-device-only storage change?

It's a major issue for tax records. Since December 2024 your Timeline is stored locally on the phone where it was created — not in the cloud, not on the web, not accessible from another device. Default retention dropped to three months. Lose or replace the phone without enabling the encrypted backup, and historical Timeline data is gone permanently.

Has any court accepted Google Maps Timeline as a §274(d) record?

We're not aware of any reported Tax Court decision that has accepted Google Maps Timeline data, standing alone, as adequate §274(d) substantiation. Patitz v. Commissioner, T.C. Memo. 2022-99, accepted contemporaneous electronic logbooks — but those are records actively maintained by the taxpayer with business purpose noted, not raw location pings.

Will the IRS accept Timeline data at all?

As corroborating evidence next to a proper log? Probably. As your sole record? Per Temp. Treas. Reg. §1.274-5T(c) and cases like Velez and Khan, almost certainly not.