Home / GIS and Open Map Data for Beginners

QGIS Export Attribute Table to Excel: XLSX, CSV, and the Geometry Decision

A woman working on a laptop with spreadsheets in a modern office

Photo: Mikhail Nilov / Pexels

Sooner or later every QGIS project meets someone who does not have QGIS. They have Excel, and they want the table: the names, the numbers, the categories, in rows they can sort and mail to a colleague. Exporting the attribute table sounds like the simplest job in the program, and the mechanics are simple, but the export dialog hides three decisions that determine whether the spreadsheet you send is the data you meant to send. This guide makes those decisions explicit: the format, the fields, and the geometry, then covers the two alternate routes, selected features only and copy-paste, and the traps that wait in each.

Interactive tool

Export It Clean: The Spreadsheet Checklist

Check off each step as you finish it. Your progress stays on this page.

0 of 7 complete

0% done

The Main Route: Export, Save Features As

The full-control route runs through the layer, not the table window:

  1. In the Layers panel, right-click the layer and choose Export, then Save Features As.
  2. In the Format list, choose MS Office Open XML spreadsheet (XLSX) for a real Excel file, or Comma Separated Value (CSV) if the file will feed another program rather than a person.
  3. Set the file name and location. Leave the CRS alone; it does not affect the attribute columns, only the geometry encoding discussed below.
  4. Open the Field list and uncheck any field the spreadsheet does not need. Internal IDs, edit-tracking columns, and half-finished working fields are the usual passengers to leave behind.
  5. Decide the geometry (next section) and whether to export only selected features (the checkbox appears when a selection exists).
  6. Click OK, then open the result in Excel and check it before you send it. The check is part of the export, not a courtesy.

That is the whole mechanism. Everything else in this article is judgment about the three decisions the dialog asks you to make.

Decision One: Real XLSX Against CSV

Choose XLSX when a person will read the file. A real Excel workbook preserves column types: numbers stay numbers, dates stay dates, and the person receiving it can sort and filter without first persuading Excel that the third column is not text. Choose CSV when a program will read the file, because CSV is the format every tool on Earth can open, and its simplicity is its virtue. But CSV carries two traps the XLSX route avoids. The first is encoding: names with accented characters can arrive mangled if the reading program assumes a different character set than the one QGIS wrote; if your data has non-English names, open the CSV once and look at them before sending. The second is delimiters and decimals: a comma inside a text field, or a locale that uses commas as decimal separators, can shift columns silently. XLSX has neither problem, which is why the rule of thumb is simple: people get XLSX, pipelines get CSV, and anyone who asks for "an Excel file" means the workbook.

Decision Two: Which Fields Travel

The export dialog lists every field in the layer, and the default is all of them. Resist the default. A spreadsheet with twenty columns where six matter is a spreadsheet nobody reads carefully, and it leaks working data (internal codes, draft classifications, personal notes fields) that was never meant to leave the project. Check the field list against the question the recipient actually asked. If they want site names, areas, and status, those three plus a stable ID are the export; the rest stays home. The ID matters more than it looks: if the recipient writes back about row 412, the ID is how you find the same feature in QGIS in seconds. Exporting a subset of fields changes nothing in the source layer; it is a publishing decision, reversible and safe.

A man at a desk looking at data on laptop screens
A man at a desk looking at data on laptop screens

Decision Three: The Geometry, Coordinates, WKT, or Nothing

A spreadsheet has no shapes, so the export must decide what a polygon becomes in a grid of cells. The dialog's Geometry type choices give you the answer set:

ChoiceWhat lands in the spreadsheetRight when
No GeometryAttributes only, one row per featureThe recipient needs the table, full stop
AS_XYTwo extra columns, X and Y of each pointPoint layers whose location matters in the sheet
AS_WKTOne column holding the full Well-Known Text geometryThe data must round-trip back into a GIS later

No Geometry is the right answer for most attribute exports and the one most tutorials skip past: the recipient asked for the table, and a column of thousand-character WKT strings helps nobody read it. AS_XY suits point data, site lists, sampling locations, anywhere the coordinates are themselves information the recipient will use, and it only makes sense for points; a polygon has no single X and Y to give. AS_WKT is the preservation option: it writes the complete geometry as text, so the spreadsheet can be brought back into QGIS or another GIS and rebuilt into shapes. Choose it when the file is an exchange format, not a reading format, and warn the recipient not to edit those cells, because a single stray keystroke in a WKT string quietly breaks one feature's geometry.

Exporting Only the Selected Features

Half of real exports are subsets: the sites in one district, the parcels flagged in review, the rows a filter isolated. Make the selection first, in the table or on the map, using a filter, a spatial selection, or plain clicking, then run the same Export route and check Save only selected features. The dialog reports how many features it will write; compare that number against your selection count before clicking OK, because exporting the full layer when you meant the subset is the classic silent error of this whole workflow, and the recipient cannot tell from the file that it happened. The alternative route, Export, Save Selected Features As, lands in the same dialog with the subset already chosen. Either way, verify the row count in the spreadsheet against the selection count in QGIS. Two numbers agreeing is the whole quality system.

The Copy-Paste Route, and Its Limits

For a handful of rows there is a faster path: select the features, open the attribute table, and use Copy selected rows to clipboard, then paste into Excel. The rows arrive with their attributes, ready to read. Know its limits before you lean on it. The paste carries the fields in table order with no chance to drop columns, the geometry handling is whatever the clipboard format does rather than a decision you made, and the route scales badly: fine for nine rows, miserable and error-prone for nine thousand. Treat copy-paste as the sticky-note version of exporting, perfect for a quick look, wrong for anything that will be filed, mailed, or built upon. The MMQGIS plugin offers its own attribute export among its utilities for users who live in that toolbox, but it answers the same three decisions, so the judgment in this guide applies whichever door you walk through.

After the Export: The Two-Minute Audit

Open the file you made, every time, and check four things. Row count against the layer or selection count. Column count and names against the field list you intended. One accented or long text value, read in full, to catch encoding and truncation problems. And one number you know by heart, a total, a maximum, a specific site's area, found in the sheet and matched against QGIS. Exports fail quietly and spreadsheets fail politely, opening without complaint on corrupted data. The audit is what separates an export you sent from an export you vouched for, and it costs less time than one round of apology email. If the table itself is unfamiliar territory, our guide to the QGIS attribute table covers reading, sorting, filtering, and editing it in place; this article begins where that one ends, at the moment the data leaves the program.

Field Types in Transit: What Changes on the Way

A spreadsheet is not a database, and some of your fields will change character on arrival whether you plan for it or not. Long integer IDs are the classic casualty: Excel stores numbers with limited precision, and a sixteen-digit identifier can come back rounded, its last digits replaced by zeros, which breaks any later join beyond repair. If a field is an identifier rather than a quantity, it is safer as text, and the XLSX route with the field's type preserved is safer than CSV, where the receiving program guesses. Dates are the second casualty: a date column that QGIS holds properly can be reinterpreted by a spreadsheet in another locale as a different day and month order, silently swapping the two. The defense is the audit from the previous section, applied with suspicion to exactly these fields: check one long ID digit by digit, check one date whose day number is above twelve (so a swap would be visible), and check one decimal value for its separator. Data that survives those three checks usually survives the trip. Data that does not has told you, cheaply, that this export wants a different format or a different route, and it is far better to learn that from your own audit than from the recipient's confusion.

Sending It Well: File Names and a Cover Note

The last step is clerical and saves more confusion than any other. Name the exported file for its contents and its moment: the layer, the subset if there is one, and the date (sites_north_district_2026-11.xlsx teaches; export1.xlsx accuses). If the export answers a request, say in the covering message what decisions you made on the recipient's behalf: which fields you included, whether geometry traveled and in what form, and whether the rows are the full layer or a selection, with the count. Every one of those facts is invisible inside the file itself, and every one will otherwise be reverse-engineered by the recipient at the cost of an email round trip, or worse, not reverse-engineered at all and silently assumed. An export is a publication in miniature: it has an audience, a purpose, and a responsibility to be understood. The dialog takes a minute; the audit takes two; the naming and the note take one more, and together they are the difference between sending data and throwing it.

Related Guides

If this page answered part of the question, these GIS guides cover the rest of the same ground:

Frequently Asked Questions

How do I export a QGIS attribute table to Excel?

Right-click the layer, choose Export, then Save Features As, and set the format to MS Office Open XML spreadsheet (XLSX). Choose which fields to include, decide the geometry handling, and click OK. Open the result and check the row count before sending it.

Should I export as XLSX or CSV?

Send XLSX when a person will read the file: it preserves numbers and dates as real types. Send CSV when a program will read it, and check the encoding if your data contains accented characters, since CSV can mangle them when the reading program assumes a different character set.

How do I export only some rows to Excel?

Select the features first, on the map or in the attribute table, then run Export, Save Features As and check Save only selected features. Compare the feature count the dialog reports with your selection count before confirming.

How do I include coordinates in the Excel export?

In the Save Features As dialog, set the geometry type to AS_XY to add X and Y columns for point layers, or AS_WKT to write the full geometry as text. Choose No Geometry when the recipient needs only the attributes, which is most of the time.

Can I just copy and paste the attribute table into Excel?

Yes, for small selections: copy the selected rows from the attribute table and paste them into a sheet. It is quick but gives you no control over columns or geometry handling, and it scales badly, so use the Save Features As route for anything large or official.

Photo credits: Mikhail Nilov (Pexels); Yan Krukau (Pexels). Photos are served from this site; follow the credit to the library page for the original.