What is SplitForge Excel Sheet Merger Performance?

SplitForge Excel Sheet Merger processes up to 2 million rows across multiple Excel workbooks in 35 seconds at 57,092 rows/sec — entirely in your browser. No file is uploaded to a server. Five intelligent merge modes handle stack rows, column alignment, sheet combining, numeric consolidation, and VLOOKUP-style joins. All benchmarks below were produced on Chrome 132, Windows 11, Intel i5-12600KF, 64GB RAM, February 2026.

Last verified: February 2026. Full methodology · Benchmark protocol

Verified Benchmark · Feb 2026 · i5-12600KF · Chrome 132

Merge 2M Excel Rows in 35 Seconds — In Your Browser

Five intelligent merge modes. Zero uploads. 57K rows/sec throughput verified on Chrome 132. Works on files that crash Excel's Power Query.

57K/sec

Throughput

rows/sec (Stack Rows, 2M rows, Feb 2026)

2M+

Max Tested

rows processed in 35 seconds

Merge Modes

Stack, Align, Combine, Consolidate, VLOOKUP

None

Data Uploaded

100% client-side processing

Performance by Row Count

All times measured from file drop to download-ready. No upload delay included — there is no upload. Excel Power Query benchmarks omitted above 1M rows due to consistent OOM crashes on 16GB test hardware.

Full Scalability Data

Chrome 132, Windows 11, i5-12600KF, 64GB RAM, February 2026

Dataset Size	Stack Rows	Align Columns	Combine Sheets	Consolidate	VLOOKUP
10K rows	0.14s	0.17s	0.12s	0.20s	~0.3s*
100K rows	1.4s	1.7s	1.2s	2.0s	1.4s
500K rows	8.7s	10.5s	7.3s	12.0s	~8s
1M rows	17.5s	21.0s	14.7s	24.5s	~17s
2M rows	35.0s	42.0s	29.5s	49.0s	~35s

* VLOOKUP at 10K rows includes hash map build time (~0.1s) + lookup (~0.2s). Results vary ±15–20% by hardware, browser, and file complexity. Times shown are averages of 8 runs (10 total, drop highest and lowest).

Ready to merge your Excel files?

Drop files, configure merge settings, download result. Zero uploads.

Merge Mode Overhead Breakdown

Stack Rows

Baseline

71K rows/sec

Pure row concatenation. No column inspection beyond header detection. Fastest mode — identical schema files only. Output row count = sum of all input row counts.

Align Columns

+20% overhead

~59K rows/sec

Builds a unified column map across all files. Normalizes header names (case-insensitive, trims whitespace). Missing columns filled with empty string. Handles files with different column orderings. Overhead from column map construction and per-row column index lookup.

Combine Sheets

-15% (fastest at output)

~83K rows/sec

Each sheet processed independently, output sheet-by-sheet. No cross-sheet column alignment needed. Faster than Stack Rows in practice because no unified schema pass is required — each sheet keeps its own headers.

Consolidate (SUM/AVG/COUNT)

+33% overhead

~47K rows/sec

Maintains an aggregation Map per numeric column, keyed by the group-by column(s). Two passes: streaming accumulation + finalization (mean computation, output serialization). Memory grows with unique group count. Slowest mode due to double-pass architecture.

VLOOKUP Join

+20% overhead

~59K rows/sec

Builds a hash map from the lookup file (O(m)). Main file streaming pass does O(1) Map.get() per row. Total complexity: O(n+m) vs Excel's O(n×m) for formula-based VLOOKUP. Hash map build adds a one-time overhead proportional to lookup file size.

Dedup + Source Tracking

+15–25% overhead

~60K rows/sec

Hash-based duplicate detection using a Set of row fingerprints. _Source_File and _Source_Sheet columns appended per row. Overhead from string hashing (fingerprint per row) and Set.has() check. Memory grows with unique row count if dedup is enabled.

Mode overhead is additive: Align Columns + Dedup + Source Tracking combined adds approximately 40–50% vs Stack Rows baseline. For maximum throughput on large files, use Stack Rows mode when your files have identical schemas.

Time Savings Calculator

Manual baseline: ~15 min per merge session (open files, copy sheets, fix column mismatches, verify output, save). SplitForge: ~30 seconds from file drop to download.

Example: Monthly department report consolidation

12 department files × 52 weeks × 15 min manual = 156 hours/year. At $60/hr analyst rate, that's $9,360 in labor. SplitForge reduces that to ~52 minutes/year.

Workbooks merged per session

Typical: 3–15 department or regional files

Sessions per year

Weekly = 52, monthly = 12, daily = 250

Hourly rate ($)

Analyst avg: $45–75/hr

Annual Time Saved

64.6

hours per year

Annual Savings

$3,228

vs. manual Excel workflow

What you eliminate:

Opening each workbook individually
Manual copy-paste across sheets
Fixing column order mismatches by hand
Waiting for Power Query to refresh
Re-running VLOOKUP formulas after each merge

Test Methodology

Full transparency on how every number on this page was produced.

Click to expand full test configuration and protocol.

Expand

Honest Limitations: Where SplitForge Falls Short

No tool is perfect for every use case. Here's where Excel Power Query might be a better choice, and the real limitations of our browser-based architecture.

Browser-Based Processing

Performance depends on your device's RAM and CPU. Modern laptops (2022+) handle 10M+ rows easily, but older devices may struggle with very large files.

Workaround:

Close unnecessary browser tabs to free up memory. For files over 50M rows, consider database solutions.

No Offline Mode (Initial Load)

Requires internet connection to load the tool initially. Processing happens offline in your browser after loading.

Workaround:

Once loaded, you can disconnect and continue processing. For true offline environments, desktop tools may be better.

Browser Tab Memory Limits

Most browsers limit individual tabs to 2-4GB RAM. This is the practical ceiling for file size.

Workaround:

Use 64-bit browsers with sufficient RAM. Chrome and Firefox handle large files best.

Browser memory ceiling (~2M rows for typical XLSX)

XLSX files consume more memory than CSV due to SheetJS parsing overhead. The practical ceiling is approximately 2M rows for typical 8–12 column business XLSX files. Above this, Chrome may crash.

Workaround:

Export source files as CSV before merging to reduce memory footprint by 3–5×.

No formula preservation

Excel formulas are evaluated to their computed values during XLSX parsing. The merged output contains values only — no formulas are carried forward.

Workaround:

If formulas must be preserved, use Excel Power Query or VBA. SplitForge is designed for value-level data merging.

No chart or image merging

Charts, images, conditional formatting, and pivot tables embedded in source workbooks are not carried into the merged output. Data cells only.

Workaround:

Merge the data layer with SplitForge, then add charts/formatting in Excel on the merged output.

No password-protected files

Password-protected XLSX files cannot be parsed. SheetJS requires unprotected workbooks.

Workaround:

Remove workbook protection in Excel (Review → Protect Workbook → uncheck) before merging.

No API or automation support

SplitForge is browser-only. It cannot be called from Python scripts, cron jobs, or ETL pipelines.

Workaround:

For scheduled/automated merges, use openpyxl (Python), SheetJS (Node.js), or AWS Glue.

When to Use Excel Power Query Instead

You need to preserve Excel formulas in the merged output

SplitForge evaluates formulas to values. If downstream processes depend on live formula references, the output will break.

💡 Use Excel Power Query or VBA to merge formula-bearing sheets.

Your workflow requires automated, scheduled merges

SplitForge is browser-only — no CLI, no API, no cron support.

💡 Use openpyxl, xlrd, or a cloud ETL tool for automated pipelines.

You need to merge charts, pivot tables, or images

SplitForge merges data cells only. Visual elements are not transferred.

💡 Use Excel directly or a macro to copy chart objects across workbooks.

Your files exceed 2M rows or 500MB

Above the browser memory ceiling, Chrome will crash or produce incomplete output.

💡 Convert to CSV first (reduces memory 3–5×), or use Python pandas for very large datasets.

Questions about limitations? Check our FAQ section below or contact us via the feedback button.

Frequently Asked Questions

How were the benchmark numbers produced?

Why is Consolidate mode slower than Stack Rows?

Why is VLOOKUP mode faster than Excel's VLOOKUP formula?

Can I merge files with different column structures?

What is the largest file I can merge?

Does it handle duplicate rows?

Does my data get uploaded anywhere?

How does this compare to Python pandas for Excel merging?

Benchmarks last verified February 2026. Re-tested quarterly.

Ready to Merge Your Workbooks?

Drop your Excel files. Configure in 30 seconds. Download the merged result. File contents never leave your browser.

57K rows/sec (Stack Rows, Chrome 132, i5-12600KF, Feb 2026)

5 merge modes including VLOOKUP and Consolidate

100% client-side — zero uploads, works offline

Results vary by hardware and file complexity (±15–20%)

Also try: Excel Sheet Extractor · Excel Splitter · CSV Merger · VLOOKUP Join
Read: Excel Sheet Merger vs Excel Copy-Paste