How to Merge CSV Files into One Excel Workbook

CSV files are everywhere. Survey tools export them. Online shops export them. Banks export them. Government open-data portals publish them by the thousand. A CSV file is just text — one row per line, values separated by commas — which makes it the easiest format to produce and the easiest to get subtly wrong. This guide explains how to merge CSV files into one Excel workbook, what goes wrong with CSV specifically, and how to check a result that came from text files.

The short version: upload the CSV files to MergeExcel, pick Append rows, and download a .xlsx workbook. The tool reads CSV the same way it reads Excel files, and the result is always a proper workbook with typed values. The rest of this guide is about the quirks that make CSV merging different from Excel merging — commas inside values, encoding, dates as text, and headers that drift between exports.

What a CSV file actually is

A CSV file is a text file. Each line is a row. Commas separate the values. The first line is usually the header row. There is no formatting, no formulas, no sheets, and no type information: a number and a piece of text look exactly the same in a CSV file, because both are just characters.

That simplicity is why CSV is the export format of choice for almost every system. It is also why CSV files cause problems that Excel files do not. A value that contains a comma — an address like "12 Main St, Springfield" — has to be wrapped in quotes, or the comma will split the value into two columns. A value that contains a quote has to be escaped. A file saved in the wrong encoding will turn "José" into "José". A date written as "10/03/2026" could be 10 March or 3 October, depending on who wrote it. None of these problems exists in a .xlsx file, because the format stores types and structure explicitly.

The merge tool handles the standard cases: quoted fields with commas inside them are read as one value, and the usual encodings are detected. But it cannot know what a date means, or whether "00123" is a number or a code that must keep its leading zeros. Those are decisions you make, by preparing the files and checking the result.

How to merge CSV files step by step

Step 1: Collect the CSV files. Put them in one folder. Check that they really are CSV files: a file with a .csv extension that is actually an Excel file, or a semicolon-separated file saved with a .csv extension, will not read correctly. Open one in a text editor — Notepad, or any plain-text editor — and look at the first lines. You should see commas between values, and the first line should be the headers. If you see semicolons instead of commas, the file uses a different separator, and you should convert it first: open it in Excel, save it as a proper CSV, and use the saved copy.

Step 2: Check the headers. Open each file's first line and compare. The headers must match — same words, same spelling — for Append rows to line the columns up correctly. Survey tools are a common source of drift: a question renamed in the survey produces a new column name in the export, and the old and new names become two columns in the merged file. Fix the headers so they match, or accept the two columns and know why they are there.

Step 3: Check the encoding. If a file contains names or addresses with accents, open it and check that the characters look right. If "José" shows as "José", the file was saved in the wrong encoding. Re-save it as UTF-8 — in Excel, use Save As and pick "CSV UTF-8" — and merge the re-saved copy. The U.S. Census Bureau publishes its public CSV files in UTF-8 for exactly this reason: it is the encoding that survives moving between systems.

Step 4: Upload to MergeExcel. Drag the CSV files onto the upload area, or click to choose them. You can mix CSV files with .xlsx and .xls files in the same merge — the result is always a .xlsx workbook. The free plan merges up to 10 files at a time, with files up to 20 MB each.

Step 5: Pick Append rows. CSV files are almost always the same kind of table — rows of the same shape, from the same system — so Append rows is the usual mode. Turn on the "Source File" column so you can trace each row back to its file. Turn on deduplication if the exports overlap. If the files are different kinds of tables, use Separate sheets instead; each CSV becomes one sheet.

Step 6: Read the audit report, then download. The report tells you how many rows went in and out, how many duplicates were removed, and which columns were missing from which files. Check the row count against what you expected, then download the .xlsx workbook and verify it: count the rows, check the first and last rows, and sum one numeric column against the source files.

CSV quirks and how to handle them

Commas inside values. An address, a company name, or a free-text answer often contains a comma. In a well-formed CSV, that value is wrapped in double quotes: "12 Main St, Springfield". The tool reads quoted fields correctly, and the comma inside the quotes does not split the value. If a file was produced by a system that does not quote its values, the row will have too many columns, and the values after the stray comma will land under the wrong headers. There is no way to fix that automatically — the file itself is ambiguous. Open it in a text editor, find the broken rows, and fix the quoting, or ask the source system for a clean export.

Quotes inside values. A value that contains a double quote is written with the quote doubled: "She said ""hello""". The tool handles that. A value with a single, unescaped quote will break the row. Again, the fix is in the source file.

Dates as text. A CSV file has no date type, so a date is just text: "2026-10-03", "10/03/2026", "3 Oct 2026". The tool reads the value as text and writes it into the workbook as text, unless it recognises the format. If dates matter to your work — sorting by date, filtering by month — convert them to real dates in the merged workbook, or standardise the format in the source files before you merge. The ISO format, YYYY-MM-DD, is the least ambiguous: it sorts correctly as text and as a date, which is why public data publishers like the Bureau of Labor Statistics use it in their published files.

Leading zeros. A postcode "01234" or a product code "00123" is text, not a number — the zero matters. In a CSV file, the zero is preserved as a character. But if the value is read as a number, the zero is dropped, and "01234" becomes 1234. The tool preserves values as they are read, so a code that arrives as text stays as text. After merging, check a column of codes: if the leading zeros are gone, the column was read as numbers, and you should re-export with the codes quoted, or format the column as text in the merged workbook and re-enter the zeros.

Blank lines. CSV exports often end with a blank line, or contain blank lines between sections. The tool ignores fully blank rows, so they do not appear in the merged table. A line that contains only commas, though, is a row of empty values — it will be merged as an empty row. Delete such lines from the source files if you can.

Different separators. Some systems export "CSV" files separated by semicolons, especially in countries where the comma is a decimal separator. A semicolon-separated file will read as a single column with semicolons in it. Convert it first: open it in Excel with the Text Import wizard, choose semicolon as the separator, and save it as a proper comma-separated CSV.

Merging CSV files with Excel files

You can merge CSV and Excel files together in one run. The result is a .xlsx workbook. The rules are the same as for any merge: the columns are lined up by header, and the merged table uses the union of all headers.

There is one asymmetry to know about. An Excel file carries types — numbers are numbers, dates are dates. A CSV file carries text. When the same column is a number in the Excel file and text in the CSV file, the merged column will contain both, and a sum will ignore the text cells. If that column matters, convert the CSV values to numbers before you merge, or convert the column in the merged workbook afterwards. The check is the same as always: sum the column in the merged file and compare it with the sum across the sources.

The other direction is easier: exporting a merged workbook back to CSV. Open the merged .xlsx file in Excel and use Save As, CSV UTF-8. The result is a single CSV file with the merged table — useful if the next system in your chain only accepts CSV.

Where to get CSV files, and what to watch for

Public CSV files are everywhere, and they are a good way to practise merging before you touch real work files. Government open-data portals publish CSV by the thousand: the U.S. Census Bureau for population and housing, the Bureau of Labor Statistics for employment and prices, and the National Center for Education Statistics for schools and colleges. These files are well-formed, documented, and free — and they have the same quirks as real work files, which is what makes them good practice.

When you download a public CSV, read its documentation first. A data dictionary tells you what each column means, what the codes stand for, and whether a value is a number or a code. Without it, you are guessing — and a guessed column is a wrong column. The same applies to your own files: if a column's meaning is not obvious from its header, write it down. Future you will be grateful.

Frequently asked questions

How do I merge CSV files into one Excel file? Upload the CSV files to an online merge tool, pick Append rows, and download the result as .xlsx. The tool reads the CSV text and writes a proper workbook. Our step-by-step combine guide walks through the same process for mixed file types.

Can I merge CSV files without Excel? Yes. You do not need Excel installed to merge CSV files online — the tool reads the text and builds the workbook on the server. You need Excel, LibreOffice or Google Sheets only to open the result.

Why do my merged CSV values end up in the wrong columns? Usually because a value contains an unquoted comma, so the row has too many values and everything after the comma shifts one column to the right. Open the source file in a text editor, find the row, and quote the value that contains the comma.

Why are my dates wrong after merging CSV files? Because CSV stores dates as text, and the format may differ between files — "10/03/2026" could be 10 March or 3 October. Standardise dates to YYYY-MM-DD in the source files before you merge, and check the merged date column afterwards.

Can I merge a CSV file with 200,000 rows? Yes, on the server. The free plan accepts files up to 20 MB, Starter up to 100 MB, Pro up to 200 MB. A 200,000-row CSV is usually well within those limits, and the merge takes a few seconds. See our guide to merging multiple files at once for batch sizes and timing.

Does merging CSV files keep the leading zeros in codes? Values are preserved as read, so a code that arrives as text keeps its zeros. If the zeros disappear, the column was read as numbers — re-export with the codes quoted, or format the merged column as text and restore the zeros.

References

• U.S. Census Bureau, public data and file formats: https://www.census.gov/
• U.S. Bureau of Labor Statistics, published datasets: https://www.bls.gov/
• National Center for Education Statistics, data files: https://nces.ed.gov/
• Library of Congress, CSV and data preservation guidance: https://www.loc.gov/