How to Merge Multiple Excel Files at Once (10, 50 or 200 Files)

Merging two Excel files is easy. Merging fifty is a different job. The files arrive from different people, with different headers, different column orders, and different ideas about how a date should be written. The merge itself is the easy part. The hard part is getting fifty files into a state where one merge produces one correct table.

This guide is about that job: merging multiple Excel files at once, in batches, without losing rows and without spending a day on it. It covers how many files you can merge in one run, how to split a big job into batches, how to prepare a folder of files so the merge works first time, and how to check a result that is too big to read by eye.

How many files can you merge at once?

The honest answer is: it depends on the plan, and on the files. MergeExcel merges up to 10 files per run on the free plan, 50 on Starter ($9 a month) and 200 on Pro ($19 a month). Those are per-merge limits. There is also a monthly limit: 10 merges a month free, 100 on Starter, unlimited on Pro. And a per-file size limit: 20 MB free, 100 MB Starter, 200 MB Pro.

Those numbers are not arbitrary. They reflect what the server can do reliably in one run, and what keeps the result checkable. A merge of 200 files is a big job, and the audit report for 200 files is a long document — but it is still one report, and it still tells you what happened to every file.

If you have more files than the plan allows in one merge, do not try to force them in. Split the job into batches and merge the batches. That is a normal workflow, and this guide shows how to do it without double-counting anything.

Other tools have their own limits, and they are worth knowing because they shape the comparison. GroupDocs allows 10 files per merge and 5 merges a day on its free tier. Aspose allows 5 files without an account and 10 with one. CompressExcel allows 10 files per merge. ToolTiny allows 10 files and 20 MB in total per task. AnyTool, which runs in the browser, allows 50 files but is limited by your computer's memory. Power Query, inside Excel, has no file limit at all — but it needs Excel, and it needs you to build a query. The point is not that one limit is better than another. The point is to pick the tool whose limits fit your job, and to have a batch plan for the jobs that do not fit.

The batch plan: merging 200 files in four runs

Suppose you have 120 branch reports and a Starter plan, which allows 50 files per merge. You cannot merge all 120 at once. Here is the plan.

Step 1: Sort the files into batches of 50. Name the batches clearly: batch-01, batch-02, batch-03. Keep the original files untouched in a "source" folder, and put each batch's result in an "output" folder. Never mix sources and results in one folder — merging a result together with its own sources is the easiest way to double every row.

Step 2: Merge each batch with Append rows. Use the same mode and the same options for every batch: same "Source File" column setting, same deduplication setting. Consistency matters, because the batch results have to merge cleanly in the next step.

Step 3: Check each batch. Read the audit report for each batch before you go on. A header mismatch in batch 2 will still be there in the final merge, and it is easier to fix when the batch is small. Check the row counts: each batch's "rows out" should equal its "rows in" minus duplicates and skips.

Step 4: Merge the batch results. Now merge the three batch result files into one final workbook, again with Append rows. Because the batch results all have the same headers — they were built by the same tool with the same settings — this merge is clean. Check the final row count: it should equal the sum of the batch row counts.

Step 5: Verify the final file. Sum one numeric column in the final file and compare it with the sum across all 120 source files. If you cannot sum the sources by hand, sum them in batches: the batch reports already give you per-batch totals, and the final total should equal the sum of the batch totals.

This works because merging is associative: merging A and B, then merging the result with C, gives the same table as merging A, B and C together — as long as the mode and options are the same each time, and as long as you do not deduplicate in the middle of the chain in a way that hides a real duplicate. One caution: if you deduplicate at the batch stage and again at the final stage, that is fine — a row removed twice is still removed once. But if you use Merge by ID at the batch stage and Append rows at the final stage, the final file will have one row per ID per batch, not one row per ID overall. Keep the mode consistent, or do the ID merge only at the final step.

Preparing a folder of many files

With two files, you can check each one by hand. With fifty, you cannot. Preparation has to be systematic, and it has to be done before the merge, not after.

Standardise the file names. A file called "report (3).xlsx" tells you nothing. Rename files with the branch, the month or the batch: "sales-north-2026-10.xlsx". A good name does three jobs: it tells you which file it is, it sorts correctly in a folder listing, and it shows up in the "Source File" column so a strange row can be traced back. If you have many files, rename them with a script or a bulk rename tool rather than by hand — hand renaming fifty files is where typos come from.

Check that every file has the same headers. This is the single most valuable check. Open a few files at random — five out of fifty is a fair sample — and compare their header rows. If the sample is consistent, the rest probably is. If the sample shows two spellings of the same column, assume the whole folder has the problem, and fix the headers in every file before you merge. A spreadsheet program can help: open the files one at a time and use Find and Replace on the header row.

Look for the odd file out. In a folder of fifty, one file is usually different: a different template, an extra column, a second sheet, a password, a file that is actually a CSV with an .xlsx extension. The merge will fail on that file, or the audit report will flag it. Find it before you merge by checking file sizes — a file that is much bigger or much smaller than the rest is worth opening — and by checking file types. A file that cannot be read fails the whole job with a clear error code, and the run is not charged, so a bad file costs you a minute, not a run. But finding it first costs you less.

Decide what to do with empty files. A folder of monthly reports often contains an empty file: a branch that had no sales, a class with no students. An empty file contributes nothing to the merge, and the audit report lists it as an empty sheet. That is fine. What is not fine is an empty file that you expected to have rows — that means the export failed, and you need a fresh copy from the source.

Remove files you do not need. A folder accumulates drafts, old months and test files. Merge only the files that belong in the result. Every extra file is a chance for a wrong row to slip in, and it makes the audit report longer for no reason.

Why multiple files go wrong more often than two

The failure modes of a big merge are the same as a small merge, but they are harder to see. With two files, you can read the audit report in full. With fifty, the report has fifty lines, and you will skim it. That is why the checks in this guide are arithmetic, not visual: row counts that add up, column sums that match, and a sample of rows you know.

There are three specific risks that grow with the number of files.

Header drift. The more people who make the files, the more spellings you get. One person writes "Customer ID", another writes "Cust ID", a third writes "CustomerID". With two files you notice. With fifty you do not, until the merged table has three half-empty columns and the totals are wrong. The fix is the same as always — standardise headers first — but the cost of skipping it grows with the file count.

Duplicate rows across files. Two branches can report the same order, or two survey batches can contain the same respondent. With two files, a duplicate is easy to spot. With fifty, duplicates hide. Turn on deduplication in Append rows mode, and choose the key carefully: "all" removes rows that are identical in every column, which is safe; a key like "Customer ID, Order Date" removes rows that repeat the same key even if other values differ, which is stronger but needs a key you trust. Our guide on merging duplicate rows explains the difference in detail.

One bad file spoiling the batch. A file that cannot be read fails the whole job. That is honest, and it is better than silently skipping the file — but it means a folder of fifty files needs one clean pass before the merge works. Check the files first, or merge in smaller batches so a bad file only blocks its own batch.

Checking a result too big to read

You cannot read 200,000 rows by eye. You check a big merged file with arithmetic and samples.

Row count identity. Add up the data rows in the source files — or, if you merged in batches, add up the batch row counts. The final row count should equal that total, minus duplicates removed, minus rows folded by ID, minus rows skipped. The audit report gives you all four numbers. If they do not balance, something is wrong, and the audit notes will say what.

Column sums. Pick one numeric column, sum it in the merged file, and compare it with the sum across the sources. Do the same for a second column if the first one is clean. A mismatch means a column was misaligned or a value was stored as text. The U.S. Bureau of Labor Statistics publishes its datasets with numeric fields typed as numbers for the same reason: a total is only meaningful if every value in the column is actually a number.

Sample checks. Pick ten rows at random from the merged file and check each one against its source file. Pick the rows by their ID, not by their position — the first rows are the easiest to get right, and the errors hide in the middle. Also check the last rows of the file, where a truncated file would show up.

Filter for blanks. Filter the merged table on a column that should never be blank, such as the ID. If blank rows appear, a file was missing that column, or a header did not match. The audit report will name the file.

Check the sheet count. In Separate sheets mode, the merged workbook should have one sheet per input sheet. Count them. A missing sheet means a file was not read, or a sheet was hidden.

Speed: how long does a big merge take?

Merging is fast compared with doing it by hand, but it is not instant, and the time grows with the number of rows. Our own measurements on the server, using generated workbooks, put a 200,000-row merge at a few seconds of engine time — the exact number is in the local acceptance report for this build, and it is re-measured on every release. What matters for planning is the shape of the curve: doubling the rows roughly doubles the time, and the upload time depends on your connection, not the tool. A 200 MB file takes a while to upload on a slow connection, so for very large files, upload once and merge once, rather than uploading the same files several times while you experiment.

If a merge feels slow, check the file sizes first. A workbook with 200,000 rows and fifty columns is a big file, and most of the time goes to reading it, not merging it. Splitting it into smaller files does not help — the total work is the same. What helps is removing columns you do not need before you upload, and removing formatting-heavy sheets that add size without adding data.

Frequently asked questions

How many Excel files can I merge at once? On MergeExcel, 10 files per merge on the free plan, 50 on Starter, 200 on Pro. If you have more files than that, merge in batches and then merge the batch results. See the pricing page for the full limits.

Can I merge 100 Excel files into one? Yes, in batches. Merge them 50 at a time on Starter, or 200 at a time on Pro, then merge the batch results. Keep the mode and options the same at every step, and check the row counts after each batch.

What is the fastest way to merge many files? Prepare the headers first, then merge in the largest batches your plan allows, with Append rows and a "Source File" column. The preparation is what makes it fast: a clean folder merges first time, and a messy folder costs you a second and third attempt.

Do I need Power Query to merge many files? No. Power Query is one way to do it inside Excel, and it has no file limit. But an online tool does the same job without Excel and without building a query. Our guide on merging without Power Query compares the two. For a folder of files you merge once, the online tool is faster. For a folder you merge every week with the same structure, Power Query's saved query is worth learning.

What happens if one file in a big batch is corrupt? The merge fails with a clear error code — UNREADABLE_FILE — and the run is not charged. Fix or remove the bad file and merge again. To find the bad file quickly, merge in smaller batches: the batch that fails contains it.

Can I merge files from different folders? Yes. The tool does not care where the files came from. Upload them all in one run, or in batches. The "Source File" column records the file name, not the folder, so give files distinct names if two folders have files with the same name.

References

• U.S. Bureau of Labor Statistics, published datasets and data types: https://www.bls.gov/
• U.S. Census Bureau, data documentation: https://www.census.gov/
• National Center for Education Statistics, data files and documentation: https://nces.ed.gov/
• Microsoft Support, Excel help and how-to articles: https://support.microsoft.com/