Somewhere in your files is a list: names down one column, latitudes and longitudes down the next two. Field sites, customer addresses, photo locations, sampling points, the campsites from a trip. The list is data, but it is not yet a map. QGIS turns it into one in about ten minutes, and the job is 90 percent preparation: if the file is clean and you set two dialog fields correctly, the points land exactly where they should. This guide does the whole job slowly enough to get right the first time, including the one mistake nearly every beginner makes once, and the ten-second test that catches it. If you have never opened QGIS at all, our QGIS tutorial for beginners gets you oriented first; this article assumes the program is installed and open.
Home / Coordinates and Location Formats
Add GPS Coordinates to QGIS: From Spreadsheet to Map Points in Ten Minutes

Photo: Teona Swift / Pexels
Add GPS Coordinates to QGIS: Import Checklist
Check off each step as you finish it. Your progress stays on this page.
0 of 6 complete
0% done
Step 1: Prepare the CSV File
QGIS reads coordinates from a plain text file in CSV format, commas separating the columns. Build it in any spreadsheet program and save or export as CSV. Three rules make the import painless.
- One header row, simple names. Use short headers with no spaces or symbols: name, latitude, longitude works perfectly. Avoid degree symbols, accents, and merged title rows above the headers; the importer reads the first row as field names and chokes quietly on decoration.
- Decimal degrees, plain numbers. Coordinates must look like 40.6892, not 40 degrees 41 minutes, and not 40,6892 with a decimal comma, which collides with the column separator and produces nonsense. If your numbers live in degrees minutes seconds, convert them first with our coordinate converter guides.
- One row per place, no blank rows in the middle.
Here is a working example file, the same five famous places our other guides use, which makes it perfect for a first import because you already know where every point should land:
| name | latitude | longitude |
|---|---|---|
| Statue of Liberty | 40.6892 | -74.0444 |
| CN Tower | 43.6426 | -79.3871 |
| Big Ben | 51.5007 | -0.1246 |
| Eiffel Tower | 48.8582 | 2.2945 |
| Sydney Opera House | -33.8568 | 151.2153 |
Type or paste those five rows into a spreadsheet, save it as places.csv, and you have a practice file whose correct result you can verify by eye: four northern points in a familiar pattern and one far south in Sydney.
Step 2: Import With the Delimited Text Layer Dialog
- In QGIS, go to Layer, Add Layer, Add Delimited Text Layer. (The Data Source Manager button on the toolbar opens the same dialog.)
- Click the browse button next to File name and choose
places.csv. QGIS previews the file at the bottom of the dialog; check that the columns line up under the headers. - Under File format, CSV is normally detected automatically. If the preview shows one long column, the separator is wrong; set it explicitly.
- Under Geometry Definition, choose Point coordinates. Now the two fields this whole article exists for: set X field to longitude and Y field to latitude.
- Set the Geometry CRS to EPSG:4326 - WGS 84. This tells QGIS what the numbers mean: ordinary GPS latitude and longitude. A CSV file carries no information about its coordinate system, so this choice is yours, and it matters.
- Click Add, then Close.
Five points appear on the canvas. If a base map is loaded (our tutorial shows how to add OpenStreetMap as a backdrop), the points should sit on their landmarks: one in New York harbor, one in Toronto, one in London, one in Paris, one in Sydney harbor. That visual check is not a formality; it is the verification step, and the next section is for when it fails.

The Swap: Diagnosing the Classic Mistake in Ten Seconds
The single most common beginner error in this dialog is setting X to latitude and Y to longitude. The rule that prevents it: X is the horizontal axis, and longitude runs horizontally across the map; Y is vertical, and latitude runs vertically. Longitude is X. Latitude is Y. Say it as "long, lat" in map order and you will never swap them again.
The swap has a signature you can spot instantly. Points appear in the ocean, mirrored into the wrong hemisphere or scattered along the wrong continent. A point that belongs at 28.6139 north, 77.2090 east (Delhi) plots, when swapped, at 77.2090 north, 28.6139 east, which is in the Barents Sea north of Russia: same numbers, wrong ocean. Some swapped points vanish entirely, because a latitude of 151 is impossible and QGIS quietly drops or misplaces the row. So the ten-second diagnostic is: do the points sit where the places are? If they are in an ocean that the place is not in, or the map looks like a funhouse mirror of the truth, delete the layer (right-click, Remove Layer), reopen the dialog, and fix the X and Y assignments. Nothing is damaged; the CSV is untouched, and the retry takes thirty seconds.
Step 3: Make It Permanent (Save the Layer)
The imported layer is temporary, a view of the CSV, not a real GIS file. If the CSV moves or gets edited, the layer follows or breaks. Promote it: right-click the layer, choose Export, Save Features As, set the format to GeoPackage, name the file, and save. GeoPackage is the modern, single-file, open format QGIS prefers, and the saved layer is now a proper dataset you can style, filter, and reuse in every future project. Keep the CSV as your editable master list if the points change often (survey rounds, delivery points), and re-export after edits; keep the GeoPackage as the stable published copy.
While you are here, two small upgrades make the layer genuinely useful. Open the layer's Properties, Labels and label points by the name field, so the map reads as a map instead of a constellation. And open Properties, Symbology to give the points a size and color that survive being printed. Neither affects the data; both affect whether anyone else can read your work.
The Other Route: GPX Files From a GPS or Phone
If your coordinates were recorded by a handheld GPS, a watch, or a phone app, they probably live in a GPX file rather than a spreadsheet. QGIS opens GPX natively: Layer, Add Layer, Add Vector Layer, choose the .gpx file, and QGIS offers its contents as separate layers: waypoints, tracks, and routes. Take waypoints for point locations, tracks for the path you walked. The CRS question answers itself here because GPX is always WGS 84 latitude and longitude by definition. Phone apps that record your walks export GPX from their share menus, which makes this the fastest bridge between a hike and a desktop map. If your coordinates are still trapped inside an app with no export, our guide to GPS coordinates apps covers reading and copying them out manually.
Working With Bigger Lists
Five famous places are a gentle start; real lists run to hundreds or thousands of rows, and three habits keep big imports clean. First, dedupe and sanity check in the spreadsheet before importing: sort by latitude and eyeball the extremes, because one row typed as 407 instead of 40.7 will stretch your map's zoom to a nonsense scale and hide the good points in a corner. Spreadsheet filters catch what eyes miss: filter latitudes outside -90 to 90 and longitudes outside -180 to 180, and any row that survives those filters with a value like 512.3 is a typo wearing a coordinate's clothes. Second, keep a source column: a short note per row (GPS unit, phone app, geocoded from address, customer form) costs nothing at collection time and is priceless six months later when two points disagree and you must decide which to trust. Third, save the project, not just the layer: a QGIS project file remembers your layers, styling, labels, and base map together, so reopening the project restores the whole working picture rather than a naked layer. Big-list work is mostly bookkeeping, and bookkeeping done early is the difference between a dataset and a pile of numbers.
Troubleshooting Table
| Symptom | Cause | Fix |
|---|---|---|
| Points in the ocean or wrong continent | X and Y swapped | Remove layer, re-import with X = longitude, Y = latitude |
| Only some points appear | A row has bad data: text in a number cell, decimal commas, empty cells | Clean the CSV, re-import |
| Points bunched at 0, 0 or in a line | Coordinates parsed as text, or separator wrong | Set CSV separator explicitly; make sure numbers are numbers |
| Points offset by a few hundred meters | Wrong CRS chosen at import | Re-import with EPSG:4326 for GPS coordinates |
| Layer breaks when reopened | It was the temporary CSV view and the file moved | Export to GeoPackage and use that layer |
| Longitudes beyond 180 or latitudes beyond 90 in preview | The columns are a projected system (meters), not degrees | Identify the source system; degrees never exceed those ranges |
The offset row deserves one extra sentence, because it frightens people: a uniform shift of a few hundred meters on every point is almost never your data being wrong; it is the map interpreting good numbers in the wrong reference system, and re-importing with EPSG:4326 cures it. Our explainer on converting latitude and longitude to UTM shows the most common projected system these numbers get confused with.
Related Guides
The closest companions to this guide are the coordinates guides below. Each one picks up a thread this page starts:
- GPS Coordinates With Altitude: Why the Third Number Disagrees With the Map: A GPS position has a third number, and it routinely disagrees with the elevation on signs and maps by tens of meters.
- GPS Coordinates Accuracy: What the Numbers Actually Promise: GPS accuracy is two different quantities wearing one name.
- Zoom to Coordinates in QGIS: The Lat Lon Tools Method, Without the Swap Trap: Someone hands you a coordinate pair and a QGIS project, and asks the simplest question in mapping: take me there.
- Geocoding in ArcGIS Pro: Build a Locator, Geocode a Table, and Rematch What Failed: the desktop-Pro counterpart to table geocoding
Frequently Asked Questions
Which field is X and which is Y in QGIS?
X is longitude, Y is latitude. X measures horizontal position across the map, and longitude is the horizontal coordinate; Y measures vertical position, and latitude is the vertical one. Setting them the wrong way round is the classic beginner mistake, and its signature is points landing in oceans or mirrored to wrong continents.
What CRS should I choose for GPS coordinates?
EPSG:4326, which is WGS 84, the system GPS satellites and phone locations use. A CSV carries no CRS information, so the dialog choice is the only place the meaning gets attached. If your numbers are in meters (six and seven digit values), they are not latitude and longitude at all, and they need their own projected CRS instead.
Why did QGIS only import some of my rows?
Rows fail individually when a cell is not a clean number: a degree symbol, a decimal comma, a note typed into the coordinate cell, or an empty value. Open the CSV, clean the offending rows, and re-import; the import preview at the bottom of the dialog shows parsed columns and is the fastest place to spot a row that will fail.
How do I add coordinates from an Excel file?
Save or export the sheet as CSV (File, Save As, CSV) and follow the same import; QGIS also reads Excel files directly through the vector layer dialog in recent versions, but the CSV route behaves identically on every version and strips out spreadsheet formatting surprises. Keep the Excel file as your master if you prefer editing there.
Can I add one single point without a file?
Yes. Create a new GeoPackage or shapefile point layer (Layer, Create Layer), toggle editing, and use the Add Point tool to click the location on the map; or use the Numerical Digitize or Lat Lon Tools plugins to type exact coordinates. For a handful of typed points, though, the CSV route in this guide is usually faster and leaves you a reusable file.
My points are correct but invisible. Where did they go?
Zoom to the layer: right-click it in the Layers panel and choose Zoom to Layer. Points imported without a base map can sit anywhere on a blank canvas, and a single point at small symbol size is easy to miss. Also check the layer is ticked visible and that its symbol size did not import as zero.
Photo credits: Teona Swift (Pexels); Marina Leonova (Pexels). Photos are served from this site; follow the credit to the library page for the original.