A GPX file is the universal souvenir of movement: your watch, your bike computer, a hiking app, a route a friend planned, all of them speak GPX. So the frustration is understandable when Google Maps, the place you want to see it, offers no button that opens one. The trick is that "Google Maps" the app is only half the product. The other half, Google My Maps, is Google's custom map editor, it imports GPX natively, and anything you build there can be opened as a layer inside the Google Maps app. This guide does the whole job: the import itself, the limits Google documents that explain most failures, how to view the result on your phone, and what to do when a track is too big or imports strangely.
How to Import a GPX File Into Google Maps: The My Maps Route, Step by Step

Photo: Maël Balland / Pexels
Import It Clean: The GPX Checklist
Check off each step as you finish it. Your progress stays on this page.
0 of 8 complete
0% done
The Honest Route: My Maps Is the Importer
Set expectations first, because half the confusion online comes from skipping this. The Google Maps app and website have no GPX import, and no setting unlocks one. Google My Maps, at mymaps.google.com, signed in with the same Google account, is the importer: it accepts GPX files directly, alongside KML, KMZ, CSV, XLSX, and Google Sheets. What you build there is a custom map with layers, and custom maps appear inside the Google Maps app under your saved places, which is how the GPX ends up "in Google Maps" in every practical sense. If your end goal is turn-by-turn navigation along the track, know the limit now: My Maps shows your track as a drawn line you can follow visually; it does not convert it into a navigable Google route. For visual following, planning, and sharing, which is most of what people want, the route below is the whole answer. Our guide to creating a custom map covers the editor itself in depth; this guide is specifically the GPX path through it.
Step by Step: From File to Map
One, open mymaps.google.com and choose Create a new map. Two, in the layer panel, click Import. Three, drag your GPX file onto the window or browse to it; My Maps reads the file and draws its contents, tracks as lines, waypoints as points, onto a new layer. Four, if the file contains several tracks or many waypoints, they arrive together in that layer; rename the layer and the map to something you will recognize on your phone. Five, style as needed: line color and width, point icons, and the base map underneath, satellite view often makes a trail track easiest to read. Six, set sharing if anyone else needs it, from private to link-shared, in the Share panel. That is the complete import. The map saves automatically to your Google Drive as you work, which is also where you will find it later. If your GPX came from a source that offers several formats, note that KML imports equally well and sometimes preserves styling better; GPX carries the geometry and waypoints, not colors.

The Limits That Bite
Google documents hard edges for My Maps, and GPX files collide with two of them constantly. The import file size limit is 5 MB, and a layer holds at most 2,000 features. A weekend hike recorded at one point per second produces a track with tens of thousands of points inside one track feature, which imports as a single line; but multi-day expeditions, dense waypoint collections, and files bundling many routes can hit either ceiling. Two more documented numbers shape big projects: a map holds at most 10 layers, and a layer drawn by hand caps its elements as well, so splitting a huge file across layers is a real strategy, not a workaround. Be aware that third-party converter sites quote other figures for these limits; Google's own help pages state 5 MB and 2,000 features per layer, and those are the numbers to plan around. When a track simplifies visibly after import, that is My Maps reducing point density to keep the map responsive; the shape survives, the per-second detail does not, which matters if your purpose was analysis rather than display. Analysts should keep the original file and treat the map as the presentation copy.
See It in the Google Maps App
On your phone, open Google Maps, tap Saved, scroll to Maps, and your custom map is listed by the name you gave it. Open it and the GPX track renders over the standard map, with your position live on top of it, which turns the import into a field tool: follow the line, check where the trail you recorded, or the route a friend sent, actually goes relative to where you stand. Waypoints tap open with their names and notes. The layer can be toggled from the map legend, and closing the custom map returns Google Maps to normal. This is also the moment to check the import honestly: zoom to a known junction or trailhead and confirm the line sits on the real path, because a track recorded with poor GPS accuracy imports faithfully, errors included. If the line floats off the path everywhere by a similar offset, suspect the source file, not the import.
When the Import Fails
Work failures in this order. File too large: reduce the GPX before importing, simplify the track in a desktop tool, raise the point interval, or split the file by day or by route into several layers or maps; simplification tools exist in most GPS editors, and the file shrinks dramatically with no visible change at map zoom. Nothing appears after import: check the layer is enabled, zoom to the layer's extent using the map's zoom controls, and confirm the file actually contains tracks or waypoints rather than only a route your source exported oddly. Waypoints but no line: your file may store the path as a route of points instead of a recorded track; converting route to track in an editor before import fixes the drawing. Import rejected outright: re-export the GPX from its source app, since malformed XML from one exporter is a common silent cause, or convert GPX to KML and import that, which My Maps accepts with the same result. And if the whole project is really about navigating the line turn by turn, accept the boundary early: export the route to a dedicated outdoor app for the field, and keep the My Maps copy for planning and sharing, which is the division of labor this ecosystem actually supports.
Organize What You Import: Layers, Names, and Sharing
An import is the start of a map's life, not the end, and a few habits keep a growing collection usable. Name maps and layers for the phone, not the desktop: the list inside Google Maps shows bare titles, so "Alps crossing, day 3, rideable variant" survives in a way "track_final_v2" does not. Use the layer budget deliberately: a map holds up to ten layers, so group by day, by activity, or by person, and toggle whole days on and off in the field rather than excavating one mega-layer. Style for the conditions the map will be read in: thick, high-contrast lines survive sunlight on a handlebar mount, distinct colors per day prevent the classic error of following yesterday's line, and waypoint icons chosen from My Maps' set carry meaning faster than a field of identical pins. Share with intent: a link-shared map is the easiest way to hand a route to a group, but remember that anyone with the link can open it, so home addresses and private land waypoints deserve a private map of their own. Finally, keep the original GPX files in a folder of their own, because the map is a presentation of the data, simplified and restyled, while the file remains the evidence: if a line ever looks wrong, the argument is settled by reopening the source, not by squinting at the map. Import well, name honestly, and the collection becomes an atlas of everywhere you have actually been, which is what most people wanted from the GPX in the first place.
Where GPX Files Come From, and What Is Inside Them
A word about the file itself, because imports go better when you know what you are carrying. GPX is an XML text format, which means it is human-readable in a pinch: open one in a text editor and you will see waypoints as wpt elements with names and coordinates, routes as rte, and recorded tracks as trk with long chains of trkpt points, each stamped with time and often elevation. The three element types explain most import surprises. A file holding only a route imports as a series of points or a sparse line, because a route is a plan, a list of places to pass, not a recorded path; a file holding a track imports as the dense, faithful line people expect; a file of waypoints imports as pins with no line at all, which is correct behavior for a set of campsites or summits. Sources differ in their defaults: watches and bike computers export tracks, route-planning websites export routes or tracks depending on the button, and some apps bundle everything into one file that My Maps reads as a single layer. When an import looks wrong, open the file and count the element types before blaming the importer; nine times in ten the file simply contains a different animal than the one you pictured, and converting route to track in an editor, or exporting again with the other option, is the whole cure.
Related Guides
This guide does not stand alone. The map app guides below take up the questions it leads into:
- How to Avoid Tolls in Google Maps: Route Options on Phone and Desktop: Google Maps hides its toll avoidance in Route options, one layer deeper than most drivers dig.
- How to Blur Your House on Google Maps: What It Hides, What It Never Will, and How to File the Request: Blurring your house on Google Maps is permanent, takes minutes to request, and covers far less than most people assume: Street View only, never...
- How to Look at Older Images on Google Maps: Street View Dates, Step by Step: Google Maps quietly keeps the old photographs.
- How to Import a KML File Into Google Maps: My Maps Layers, Placemarks, and the Limits That Shape the Job: the sibling format, placemarks instead of tracks
Frequently Asked Questions
Can I import a GPX file directly into the Google Maps app?
No. The Google Maps app and website have no GPX import. The working route is Google My Maps, which imports GPX into a custom map, and that custom map then opens inside the Google Maps app under Saved and Maps.
What file formats does Google My Maps import?
Google documents GPX, KML, KMZ, CSV, XLSX, and Google Sheets as import formats. For recorded tracks and waypoints, GPX and KML are the practical choices.
Why did my GPX import fail or lose detail?
The documented limits are a 5 MB maximum file size and 2,000 features per layer, with up to 10 layers per map. Large recordings also get visually simplified on import. Simplify the track, split it across layers, or convert it before importing.
Will the imported GPX give me turn-by-turn directions?
No. My Maps draws your track as a line you can follow visually with your live position on top. It does not become a navigable Google Maps route. For voice-guided following of a track, use a dedicated outdoor navigation app in the field.
Where does the imported map live afterward?
In your Google account: the custom map saves to Google Drive, appears in My Maps for editing, and is listed in the Google Maps app under Saved, then Maps, on any device signed in to the same account.
Photo credits: Maël Balland (Pexels); Kamaji Ogino (Pexels). Photos are served from this site; follow the credit to the library page for the original.