How do you export AirTag location history?

Pick the tag, pick the date range that covers your dispute, and download one of three formats. CSV is the raw rows: one recorded report per line with its time and coordinates. GPX is the same route as a map file that mapping software opens. The timestamped PDF evidence report, on The Move pass and above, is the one you attach to a claim.

Can you export location history from Find My?

No. Find My has no export of any kind, whether CSV, GPX or report, because it holds nothing to export. It shows one pin at the most recent reported location and overwrites it when the next report arrives.

Apple keeps no readable location history on its servers either; reports are end-to-end encrypted to the owner's Apple ID. So an export only exists if something recorded the reports as they arrived. AirTag History polls the Find My network every 5 minutes and saves each report it gets back with latitude, longitude and timestamp.

How do you export a route, step by step?

1. Connect the Apple ID your AirTags are already on, if you have not already. Recording starts at that moment and not before.
2. Open the tag you need. Exports are per tag, so decide which one the dispute is actually about.
3. Set the date range to the window that covers the dispute, from pickup to delivery, rather than everything you have.
4. Choose the format: CSV for the rows, GPX for a map file, or the PDF evidence report if your pass includes it.
5. Download it and open it once before you send it. Check that the dates at both ends are the ones you meant.
6. Note which timezone the times are in, so you can state it in the covering email.
7. Keep the downloaded original untouched. If you need to highlight something, annotate a copy and say which is which.

Export while your tracking window is active so you have a standalone file stored locally whenever you need it.

What is in the CSV, and what do the columns mean?

One row per location report we actually received, in time order. It is the underlying data rather than a presentation of it, which is why it is the file to send to anyone who says they want to check for themselves.

• The timestamp: when that report was made, not when you exported it. This is the column every dispute turns on.
• Latitude and longitude: the position the Find My network reported, as decimal numbers. These are the fact; everything else is a label on them.
• The place name: reverse-geocoded from those coordinates, so a human reads "Bakersfield, CA" instead of a number pair. Convenience, not evidence.
• The tag: which AirTag the row belongs to, under the name you gave it. Name tags for the reader: "Kitchen boxes", not "AirTag 3".

What the CSV does not contain is a row for every five minutes. A report exists only when a passing Apple device relayed a sighting, so a dense city hour produces many rows and a quiet warehouse night can produce none. The quiet stretches appear as gaps between timestamps, because nothing is interpolated to fill them.

Any spreadsheet opens it, and so does any script. If a recipient wants to sort, filter, or plot the rows themselves, this is the file that lets them.

What is GPX for, and what opens it?

GPX is the plain XML format that GPS and mapping software has read for years. The same recorded points, structured as a track with times attached, so a map tool can draw the route without anyone retyping coordinates.

• Mapping and GIS applications, route viewers, and most GPS or outdoor software import it directly.
• Use it when somebody needs to see the shape of the journey rather than read individual rows.
• Use it to overlay your route against another one: a carrier's stated route, a planned route, a second tag in a second box.
• Use it as a portable copy. GPX is an open format, so a file you keep today stays readable without us.

It is the wrong file to attach to a claim. A dispute desk that receives a .gpx will not open it, and asking them to install something is how a claim stops moving.

What is the timestamped PDF evidence report?

A fixed, dated document built from the same saved reports: a header naming the tag and the period, one row per report with its time, place and coordinates, stops and dwell times flagged, and a footer stating how many snapshots it covers and across how many days.

It exists because the person who needs convincing is not going to log in. Adjusters, dispute desks and baggage offices work in email attachments and case files, and a link to a live map behind an account is not something they can file. The PDF is a copy of what the record said on the day you exported it, with the issue date printed on it.

It sits on The Move pass and above, which is also the tier where stops and dwell-time detection turn on, which is what makes the flagged rows possible. Free and Track give you live tracking, the timeline, and CSV or GPX export.

Which format do you send to whom?

The usual answer for a dispute is both ends at once: the PDF for the human who reads it, and the CSV underneath for whoever they hand it to. Offering the raw rows before being asked reads better than being asked.

What should you check before you send the file?

• That the range covers the whole dispute, not just the convenient hours. Cropping is the first thing a sceptical reader looks for.
• That you know the timezone, and that you use the same one in the file and the email.
• That you can explain the gaps, such as the overnight warehouse silence or the mid-ocean stretch, before somebody points at them.
• That the tag name on the export means something to a stranger.
• That the original stays unedited, with any annotation on a clearly labelled copy.

None of this makes an export more authoritative than it is. It is a record of where a tag reported from and when, not proof of what was in the box, and not certified by anyone. Sending it clearly and describing it accurately is the whole job.