Redshift to Excel: Export Query Results as .xlsx
Last updated October 3, 2026 · By the SaturnSQL team
Amazon Redshift has three built-in ways out: the Query Editor v2 download, UNLOAD to S3, and an ODBC driver Excel can talk to. None of them hands you a .xlsx file. Here is what each one does, where it stops, and the shortest path to a real workbook.
The short version
For a quick one-off, Query Editor v2 gives you a CSV. For a very large extract, UNLOAD to S3. For a workbook on your own Windows machine that refreshes itself, use ODBC. For a genuine .xlsx in one click, or a report other people need every week, use a client that writes the file and schedules the query. The general tradeoffs across all engines are in the export SQL to Excel guide.
Method 1: the Query Editor v2 download
The AWS console’s query editor is the free route everyone tries first. Run the query, choose Export in the results area, and pick CSV or JSON. There is no Excel option, so the file Excel opens is a CSV, and Excel type-guesses every column on the way in: leading zeros, long IDs and date-shaped strings are all at risk, as catalogued in the general guide.
Check the Limit toggle first. Query Editor v2 runs every query with Limit 100 switched on by default, and the export only contains the rows the query returned. If your spreadsheet has exactly 100 rows, this is why. AWS also caps the data the editor fetches per query at 100 MB, so wide or very long results need another route.
Method 2: UNLOAD to S3 for big extracts
UNLOAD writes a query result straight from the cluster to files in an S3 bucket, as delimited text, CSV, JSON or Parquet. It is the right tool when the result is too big for any editor download:
UNLOAD ('SELECT id, name, created_at FROM customers ORDER BY id')
TO 's3://my-bucket/exports/customers_'
IAM_ROLE default
FORMAT CSV
HEADER
PARALLEL OFF
EXTENSION 'csv';A few details decide whether the output is usable in Excel. By default UNLOAD writes in parallel, one or more files per slice, so you get a folder of part files rather than one spreadsheet; PARALLEL OFF writes serially in ORDER BY order, still splitting at 6.2 GB per file. HEADER adds the column names, and without EXTENSION the files have no .csv suffix. The outer SELECT cannot use LIMIT, and the cluster needs an IAM role allowed to write to the bucket. You then download the files from S3, and Excel still type-guesses the CSV on open.
Method 3: connect Excel to Redshift with ODBC
The other direction: let Excel pull. Install the Amazon Redshift ODBC driver, create a data source (DSN) for your cluster in the Windows ODBC Data Source Administrator, then in Excel go to Data → Get Data → From Other Sources → From ODBC and pick the DSN. Under Advanced options you can paste a SQL statement instead of picking a table, and Data → Refresh All re-runs it later. Power Query also has a dedicated Amazon Redshift connector, but Microsoft lists it for Power BI and Fabric rather than Excel, so in Excel ODBC is the route.
This works well on one analyst’s machine and badly for sharing. Every computer that refreshes the workbook needs the driver installed, database credentials, and a network path to the cluster, and a Redshift cluster sits inside a VPC that the internet cannot reach until someone opens a route. The Redshift connection guide explains those network options; a copy of the workbook mailed around goes stale the moment it is sent.
Method 4: a one-click .xlsx download
SaturnSQL is a browser-based Redshift SQL editor. Connect a provisioned cluster or Redshift Serverless with a read-only user, through an SSH bastion, or over the Redshift Data API with IAM keys and no network changes at all. Run the query, open the export menu above the results grid, and choose Excel. You get a genuine .xlsx workbook with a header row, so there is no CSV import step and text columns such as zip codes keep their leading zeros.
The export re-runs your query rather than saving what is on screen, so it is not limited to the 1,000 rows the results grid shows by default. Plan on up to 100,000 rows per export; if a file hits its cap, SaturnSQL says so instead of handing you a silently short spreadsheet. The details are on the row limits page. Past that size, UNLOAD is the honest answer.
Method 5: stop exporting, schedule it
Most people who export a Redshift query to Excel once end up exporting the same query every Monday. In SaturnSQL you save the query, attach a schedule with a cron cadence and an IANA timezone, and each run writes the fresh rows to the destination. Excel export, Google Sheets delivery and scheduling are all in the Starter plan at €19/user/month, with a 14-day free trial and no credit card.
Where scheduled runs deliver
Scheduled runs deliver to a Google Sheet or to Slack. SaturnSQL does not email an .xlsx attachment on a timer. For Excel users a Sheet is one click away (File → Download → Microsoft Excel (.xlsx)), and the URL stays stable, so anyone with the link sees this morning’s numbers without a driver, a VPN or database credentials. The full setup is in the Redshift to Google Sheets guide, and if a few headline numbers are enough, see Redshift to Slack.
Writing the query is half the job. If you are coming to Redshift from PostgreSQL, the Redshift SQL reference marks the syntax that differs, including the UNLOAD and COPY paths.
Frequently asked questions
How do I export Redshift query results to Excel?
Amazon's own tools stop at CSV: Query Editor v2 exports CSV or JSON, and UNLOAD writes CSV, JSON or Parquet files to Amazon S3. For a genuine .xlsx workbook, run the query in a client that writes one. In SaturnSQL you run the query, open the export menu above the results and choose Excel.
Can Redshift Query Editor v2 export to Excel?
Not as .xlsx. The Export option in the results area offers JSON and CSV. The Limit 100 option is on by default, so turn it off before exporting or the file holds 100 rows, and AWS caps the data the editor fetches per query at 100 MB.
How do I connect Excel to Amazon Redshift directly?
Install the Amazon Redshift ODBC driver, create a data source (DSN) in the Windows ODBC Data Source Administrator, then in Excel choose Data, Get Data, From Other Sources, From ODBC. The workbook can be refreshed, but every machine that refreshes it needs the driver, database credentials and a network path to the cluster.
How do I export Redshift to Excel automatically on a schedule?
Schedule the saved query in a tool that owns both the Redshift connection and the destination. SaturnSQL runs a saved query on a cron cadence and writes the rows to a Google Sheet or posts them to Slack. A Google Sheet is one click from Excel (File, then Download, then Microsoft Excel) and the link stays stable. SaturnSQL does not email an .xlsx attachment on a schedule.
How many rows can I export from Redshift to Excel?
Excel stops at 1,048,576 rows per worksheet. Plan on up to 100,000 rows per SaturnSQL export, and SaturnSQL tells you when a file hits its cap. For anything bigger, UNLOAD the result to S3 as CSV files and work from those.
Export a real .xlsx from Redshift in one click, or put the query on a schedule and stop exporting it at all.
