ExcelDataReader Write Excel Files: Why It Can't and How IronXL Solves This

Can ExcelDataReader Write Excel Workbook Data?

No. ExcelDataReader is a read-only library by design, and that limitation is intentional. The official ExcelDataReader GitHub repository describes the project explicitly as "a library for reading Microsoft Excel files" -- there is no writing API, no save method, and no cell-value setter anywhere in the public surface. You can verify this for yourself by browsing the ExcelDataReader NuGet package page, where the package description reinforces the read-only scope.

ExcelDataReader supports XLS, XLSX, and CSV formats for reading, and it does that job efficiently. The library exposes a streaming, forward-only reader pattern similar to IDataReader in ADO.NET. That architecture is well suited for extracting large datasets quickly, but it is fundamentally incompatible with the random-access, mutable model that Excel writing requires.

The code below illustrates the ceiling you hit with ExcelDataReader:

using ExcelDataReader;
using System.Text;

// Register the encoding provider required for .NET 5+
Encoding.RegisterProvider(CodePagesEncodingProvider.Instance);

using var stream = File.Open("source.xlsx", FileMode.Open, FileAccess.Read);
using var reader = ExcelReaderFactory.CreateReader(stream);

while (reader.Read())
{
    string cellValue = reader.GetString(0); // Read a cell value
    Console.WriteLine(cellValue);
    // There is no Write(), Save(), or SetCellValue() method here
}

using ExcelDataReader;
using System.Text;

// Register the encoding provider required for .NET 5+
Encoding.RegisterProvider(CodePagesEncodingProvider.Instance);

using var stream = File.Open("source.xlsx", FileMode.Open, FileAccess.Read);
using var reader = ExcelReaderFactory.CreateReader(stream);

while (reader.Read())
{
    string cellValue = reader.GetString(0); // Read a cell value
    Console.WriteLine(cellValue);
    // There is no Write(), Save(), or SetCellValue() method here
}

After calling Read(), there is simply no equivalent Write() or Save() counterpart. When your application needs to produce reports, update spreadsheet cells, export data to XLSX, apply formulas, or process templates, ExcelDataReader leaves you with an empty toolbox.

This is not a bug. It is a deliberate scope decision. ExcelDataReader does one thing well and stops there. Any workflow that involves writing data back to Excel requires a different library entirely.

How Does IronXL Solve the Writing Problem?

IronXL provides a unified API for reading, creating, modifying, and saving Excel files without any Microsoft Office installation. The library treats an Excel workbook as a fully mutable, in-memory object graph. You load or create a workbook, navigate to any cell by reference, set values or formulas, apply styles, then call SaveAs() -- a workflow that mirrors how a human would work in Excel itself.

IronXL supports XLSX, XLS, CSV, TSV, and JSON formats for both input and output. It runs on .NET 10, .NET Standard, and .NET Framework, making it suitable for console applications, ASP.NET Core web APIs, desktop tools, and background processing services alike.

Install-Package IronXL

Install-Package IronXL

dotnet add package IronXL

dotnet add package IronXL

using IronXL;

WorkBook workBook = WorkBook.Create(ExcelFileFormat.XLSX);
WorkSheet sheet = workBook.CreateWorkSheet("Report");

// Write header row
sheet["A1"].Value = "Product";
sheet["B1"].Value = "Quantity";
sheet["C1"].Value = "Unit Price";

// Write a data row
sheet["A2"].Value = "Widget";
sheet["B2"].Value = 150;
sheet["C2"].Value = 9.99;

workBook.SaveAs("report.xlsx");
Console.WriteLine("Workbook saved.");

using IronXL;

WorkBook workBook = WorkBook.Create(ExcelFileFormat.XLSX);
WorkSheet sheet = workBook.CreateWorkSheet("Report");

// Write header row
sheet["A1"].Value = "Product";
sheet["B1"].Value = "Quantity";
sheet["C1"].Value = "Unit Price";

// Write a data row
sheet["A2"].Value = "Widget";
sheet["B2"].Value = 150;
sheet["C2"].Value = 9.99;

workBook.SaveAs("report.xlsx");
Console.WriteLine("Workbook saved.");

How Do You Read and Write in a Single IronXL Workflow?

A common requirement is to read an existing Excel file, transform its data, and write the results back. ExcelDataReader handles only the first step, which means you need to introduce a second library -- an unnecessary complication that adds dependency management overhead and potential version conflicts.

IronXL covers the entire pipeline. The example below loads a source file, reads values from column A, transforms them, and saves the modified workbook as a new file:

using IronXL;

WorkBook workBook = WorkBook.Load("source.xlsx");
WorkSheet sheet = workBook.DefaultWorkSheet;

// Read existing data
string originalValue = sheet["A1"].StringValue;
Console.WriteLine($"Original: {originalValue}");

// Modify existing data
sheet["A1"].Value = originalValue.ToUpper();

// Add new data alongside existing content
sheet["B1"].Value = DateTime.Now.ToString("yyyy-MM-dd");
sheet["C1"].Formula = "=LEN(A1)";

workBook.SaveAs("modified.xlsx");
Console.WriteLine("Modified workbook saved.");

using IronXL;

WorkBook workBook = WorkBook.Load("source.xlsx");
WorkSheet sheet = workBook.DefaultWorkSheet;

// Read existing data
string originalValue = sheet["A1"].StringValue;
Console.WriteLine($"Original: {originalValue}");

// Modify existing data
sheet["A1"].Value = originalValue.ToUpper();

// Add new data alongside existing content
sheet["B1"].Value = DateTime.Now.ToString("yyyy-MM-dd");
sheet["C1"].Formula = "=LEN(A1)";

workBook.SaveAs("modified.xlsx");
Console.WriteLine("Modified workbook saved.");

The WorkBook.Load() call reads the file into memory as a mutable object. You then navigate cells using Excel-style references, update values, set formulas, and save -- all within a single library and a single API pattern.

What Advanced Writing Features Does IronXL Support?

Beyond simple cell assignment, IronXL exposes the full range of Excel capabilities that business applications typically require.

using IronXL;
using IronXL.Styles;

WorkBook workBook = WorkBook.Create(ExcelFileFormat.XLSX);
WorkSheet sheet = workBook.CreateWorkSheet("Analytics");

// Write labels
sheet["A1"].Value = "Revenue";
sheet["B1"].Value = "Cost";
sheet["C1"].Value = "Margin";

// Write data
sheet["A2"].Value = 50000;
sheet["B2"].Value = 32000;

// Write a calculated formula
sheet["C2"].Formula = "=A2-B2";

// Apply bold formatting to the header row
sheet["A1:C1"].Style.Font.Bold = true;

// Highlight the margin cell
sheet["C2"].Style.BackgroundColor = "#D4EDDA";
sheet["C2"].Style.Font.Bold = true;

workBook.SaveAs("analytics.xlsx");

using IronXL;
using IronXL.Styles;

WorkBook workBook = WorkBook.Create(ExcelFileFormat.XLSX);
WorkSheet sheet = workBook.CreateWorkSheet("Analytics");

// Write labels
sheet["A1"].Value = "Revenue";
sheet["B1"].Value = "Cost";
sheet["C1"].Value = "Margin";

// Write data
sheet["A2"].Value = 50000;
sheet["B2"].Value = 32000;

// Write a calculated formula
sheet["C2"].Formula = "=A2-B2";

// Apply bold formatting to the header row
sheet["A1:C1"].Style.Font.Bold = true;

// Highlight the margin cell
sheet["C2"].Style.BackgroundColor = "#D4EDDA";
sheet["C2"].Style.Font.Bold = true;

workBook.SaveAs("analytics.xlsx");

using IronXL;

// Load a CSV file as if it were a workbook
WorkBook csvWorkBook = WorkBook.LoadCSV("data.csv", fileFormat: ExcelFileFormat.CSV);
WorkSheet csvSheet = csvWorkBook.DefaultWorkSheet;

// Apply a bold header style to the first row
csvSheet["A1:Z1"].Style.Font.Bold = true;

// Save as XLSX
csvWorkBook.SaveAs("converted.xlsx");
Console.WriteLine("CSV converted to XLSX.");

using IronXL;

// Load a CSV file as if it were a workbook
WorkBook csvWorkBook = WorkBook.LoadCSV("data.csv", fileFormat: ExcelFileFormat.CSV);
WorkSheet csvSheet = csvWorkBook.DefaultWorkSheet;

// Apply a bold header style to the first row
csvSheet["A1:Z1"].Style.Font.Bold = true;

// Save as XLSX
csvWorkBook.SaveAs("converted.xlsx");
Console.WriteLine("CSV converted to XLSX.");

How Do You Compare ExcelDataReader and IronXL Side by Side?

The table below summarizes the capability difference between the two libraries across the most common Excel development scenarios:

ExcelDataReader remains a legitimate choice when reading is the only requirement and binary size matters. For any scenario involving output, IronXL is the appropriate tool.

When Should You Use IronXL?

IronXL becomes the right choice whenever your application needs to produce or modify Excel files. The following scenarios are representative of real business requirements that ExcelDataReader cannot address:

• Report generation: Produce Excel reports from database queries, API responses, or in-memory calculations. See the Excel report creation guide for a structured walkthrough.
• Data export: Convert application data -- collections, DataTables, or DataSets -- to XLSX for download or archiving. The DataTable to Excel tutorial shows the exact API.
• Template processing: Load an XLSX template with placeholder cells, fill them dynamically, then save the populated result.
• Batch file modification: Iterate over a directory of workbooks, apply changes programmatically, and save each file. IronXL handles multiple open workbooks independently.
• Invoice and financial document generation: Build structured documents with formulas, number formatting, merged cells, and styled headers.
• CSV-to-XLSX conversion: Accept comma-separated uploads, reformat them as structured workbooks, and return XLSX downloads to users.

Business applications that previously required a read library plus a write library -- or a dependency on Excel automation via COM -- can consolidate to IronXL alone.

For advanced output scenarios, the conditional formatting documentation and the chart creation guide cover the full range of formatting and visualization capabilities. The licensing page outlines production deployment options, and the full API reference documents every class and method.

How Do You Get Started with a Free Trial?

IronXL is available under a free development license. Install the NuGet package, run the examples above against your own files, and verify that the output meets your requirements before committing to a production license.

The IronXL getting started guide walks through installation, first-use patterns, and common scenarios with runnable code. The tutorials section covers reading workflows in detail, which is useful if your application needs both read and write operations.

Start the free trial to access the full feature set, including export formats, advanced formatting, formula evaluation, and multi-sheet workbook management. For teams evaluating the library at scale, the IronSuite bundle includes IronXL alongside IronPDF, IronOCR, and other productivity libraries at a reduced combined price.

Is ExcelDataReader Still Worth Using?

ExcelDataReader is a well-maintained, open-source library with a clear purpose. If your application only reads Excel files and never writes them -- for example, a data ingestion pipeline that imports XLSX uploads into a database -- ExcelDataReader is a reasonable, lightweight choice. Its streaming model is memory-efficient for very large files.

The problem arises when requirements expand. Applications that start as read-only importers often evolve to produce confirmation exports, error reports, or modified copies of the original files. At that point, ExcelDataReader's scope boundary becomes a blocker, and migrating to a read-write library mid-project is more disruptive than starting with one.

Choosing IronXL from the outset covers both scenarios. The IronXL reading tutorial demonstrates that reading with IronXL is equally straightforward -- cell references, range iteration, DataSet export, and type-safe value access all work through the same familiar API.

What Should You Do Next?

ExcelDataReader is a read-only library. That constraint is by design and will not change. If your project requires writing, modifying, or exporting Excel files in any form, you need a library built for bidirectional Excel access.

IronXL provides that capability without Office dependencies, without COM interop complexity, and without combining multiple packages into a fragile multi-library stack. Install it from NuGet, replace your existing read code with IronXL's equivalent methods, and add write operations where needed -- the API is consistent across both directions.

Explore the IronXL documentation to understand the full scope of the library. Review the how-to guides for specific tasks such as writing Excel files, creating spreadsheets, and reading existing workbooks. When you are ready to evaluate production licensing, the pricing and licensing page lists all available tiers.