Spire.Barcode vs IronBarcode: C# Barcode Library Comparison

The Type Specification Requirement

Spire.Barcode's BarcodeScanner.Scan() has no overload that accepts only a file path. Every read operation demands that the calling code declare the barcode format in advance. For single-format workflows this is workable, but for mixed-format document processing it produces a candidate iteration loop:

// Spire.Barcode: multi-format detection requires a guessing loop
BarcodeScanner scanner = new BarcodeScanner();
var candidates = new[] { BarCodeType.Code128, BarCodeType.QRCode, BarCodeType.DataMatrix, BarCodeType.EAN13, BarCodeType.PDF417 };

string foundValue = null;
foreach (var type in candidates)
{
    string[] found = scanner.Scan("barcode.png", type);
    if (found.Length > 0)
    {
        foundValue = found[0];
        break;
    }
}

// Spire.Barcode: multi-format detection requires a guessing loop
BarcodeScanner scanner = new BarcodeScanner();
var candidates = new[] { BarCodeType.Code128, BarCodeType.QRCode, BarCodeType.DataMatrix, BarCodeType.EAN13, BarCodeType.PDF417 };

string foundValue = null;
foreach (var type in candidates)
{
    string[] found = scanner.Scan("barcode.png", type);
    if (found.Length > 0)
    {
        foundValue = found[0];
        break;
    }
}

Imports Spire.Barcode

Dim scanner As New BarcodeScanner()
Dim candidates = {BarCodeType.Code128, BarCodeType.QRCode, BarCodeType.DataMatrix, BarCodeType.EAN13, BarCodeType.PDF417}

Dim foundValue As String = Nothing
For Each type In candidates
    Dim found As String() = scanner.Scan("barcode.png", type)
    If found.Length > 0 Then
        foundValue = found(0)
        Exit For
    End If
Next

Every type added to the candidate array is an additional scan pass. Any format absent from the list is silently missed. The developer is responsible for maintaining an exhaustive type inventory and re-testing whenever a new format enters the workflow.

Detailed Feature Comparison

Spire.Barcode Approach

Spire.Barcode's BarcodeScanner.Scan() requires a BarCodeType parameter on every call. The single-type call is appropriate when the format is known and guaranteed:

// Spire.Barcode — type is mandatory
BarcodeScanner scanner = new BarcodeScanner();
string[] results = scanner.Scan("barcode.png", BarCodeType.Code128);

foreach (string value in results)
{
    Console.WriteLine(value);
}

// Spire.Barcode — type is mandatory
BarcodeScanner scanner = new BarcodeScanner();
string[] results = scanner.Scan("barcode.png", BarCodeType.Code128);

foreach (string value in results)
{
    Console.WriteLine(value);
}

Imports Spire.Barcode

Dim scanner As New BarcodeScanner()
Dim results As String() = scanner.Scan("barcode.png", BarCodeType.Code128)

For Each value As String In results
    Console.WriteLine(value)
Next

When the format is not known in advance, the only available approach is to iterate through candidate types. Each iteration is a full scan pass, and any format absent from the list is silently missed. The result is a string[] that carries no type information, so downstream routing based on format requires additional state management by the caller.

IronBarcode Approach

IronBarcode's BarcodeReader.Read() requires no type parameter. The library detects the format automatically across all supported symbologies in a single pass. Reading barcodes from images is a single method call regardless of how many different formats the source may contain:

// IronBarcode — auto-detection built in
var results = BarcodeReader.Read("barcode.png");

foreach (var result in results)
{
    Console.WriteLine($"{result.BarcodeType}: {result.Value}");
}

// IronBarcode — auto-detection built in
var results = BarcodeReader.Read("barcode.png");

foreach (var result in results)
{
    Console.WriteLine($"{result.BarcodeType}: {result.Value}");
}

Imports IronBarCode

' IronBarcode — auto-detection built in
Dim results = BarcodeReader.Read("barcode.png")

For Each result In results
    Console.WriteLine($"{result.BarcodeType}: {result.Value}")
Next

Each result object includes BarcodeType, Value, and positional metadata. Downstream routing based on format requires no additional state — the type is present in the result itself.

Spire.Barcode Free Tier

FreeSpire.Barcode applies a large evaluation watermark to generated barcode images. The watermark covers the barcode in a way that renders it unsuitable for production use and obscures meaningful evaluation of generation quality. Scan performance is intentionally degraded in the free version, which means throughput measurements made during evaluation do not represent commercial Spire.Barcode performance. The free package also requires a registration key obtained from E-iceblue before warning dialogs are suppressed during execution. The available symbology set in the free tier is a subset of the commercial offering. These restrictions collectively mean that an evaluation built on FreeSpire.Barcode does not accurately represent what the commercial product delivers.

IronBarcode Trial Mode

IronBarcode's trial is the licensed package used without a license key. Reading operates at full speed with full symbology support and no behavioral restrictions. Reading speed and accuracy options behave identically in trial and licensed mode. Generated barcode output in trial mode carries a small watermark at the edge of the image; it does not obscure the barcode itself. The behavior measured during an IronBarcode evaluation is the behavior that ships to production.

Spire.Barcode Approach

Spire.Barcode has no native PDF reading capability. To extract barcodes from a PDF file, a developer must install the separate Spire.PDF package, purchase a separate Spire.PDF license, and write manual page iteration and image extraction code before barcode scanning can begin:

// Spire.Barcode + Spire.PDF: two libraries, two licenses
using Spire.Pdf;

var pdf = new PdfDocument();
pdf.LoadFromFile("document.pdf");

var scanner = new BarcodeScanner();
foreach (PdfPageBase page in pdf.Pages)
{
    var images = page.ExtractImages();
    foreach (var image in images)
    {
        // BarCodeType is still required even here
        string[] results = scanner.Scan(image, BarCodeType.QRCode);
    }
}

// Spire.Barcode + Spire.PDF: two libraries, two licenses
using Spire.Pdf;

var pdf = new PdfDocument();
pdf.LoadFromFile("document.pdf");

var scanner = new BarcodeScanner();
foreach (PdfPageBase page in pdf.Pages)
{
    var images = page.ExtractImages();
    foreach (var image in images)
    {
        // BarCodeType is still required even here
        string[] results = scanner.Scan(image, BarCodeType.QRCode);
    }
}

Imports Spire.Pdf

Dim pdf As New PdfDocument()
pdf.LoadFromFile("document.pdf")

Dim scanner As New BarcodeScanner()
For Each page As PdfPageBase In pdf.Pages
    Dim images = page.ExtractImages()
    For Each image In images
        ' BarCodeType is still required even here
        Dim results As String() = scanner.Scan(image, BarCodeType.QRCode)
    Next
Next

This pattern requires two NuGet packages, two license agreements, and developer-written page management code. If barcodes are embedded in vector content rather than raster images within the PDF, the image extraction approach may miss them entirely.

IronBarcode Approach

IronBarcode handles PDF files natively without any additional dependency. Reading barcodes from PDF documents is a single method call using the same BarcodeReader.Read() API used for image files. Page numbers are included in each result object:

// IronBarcode: native PDF support, no additional library
var results = BarcodeReader.Read("document.pdf");

foreach (var barcode in results)
{
    Console.WriteLine($"Page {barcode.PageNumber}: {barcode.BarcodeType} = {barcode.Value}");
}

// IronBarcode: native PDF support, no additional library
var results = BarcodeReader.Read("document.pdf");

foreach (var barcode in results)
{
    Console.WriteLine($"Page {barcode.PageNumber}: {barcode.BarcodeType} = {barcode.Value}");
}

Imports IronBarcode

Dim results = BarcodeReader.Read("document.pdf")

For Each barcode In results
    Console.WriteLine($"Page {barcode.PageNumber}: {barcode.BarcodeType} = {barcode.Value}")
Next

No manual page extraction, no secondary package, and no additional license purchase are required.

Spire.Barcode Approach

Spire.Barcode's generation model centers on a mutable BarcodeSettings configuration object. A developer instantiates the settings, assigns properties individually, passes the settings object to a BarCodeGenerator, and then calls GenerateImage():

// Spire.Barcode generation
using Spire.Barcode;

BarcodeSettings settings = new BarcodeSettings();
settings.Type = BarCodeType.Code128;
settings.Data = "12345678";
settings.ShowText = true;
settings.TextMargin = 5;
settings.BarHeight = 60;
settings.Unit = GraphicsUnit.Pixel;

BarCodeGenerator generator = new BarCodeGenerator(settings);
Image barcodeImage = generator.GenerateImage();
barcodeImage.Save("barcode.png", ImageFormat.Png);

// Spire.Barcode generation
using Spire.Barcode;

BarcodeSettings settings = new BarcodeSettings();
settings.Type = BarCodeType.Code128;
settings.Data = "12345678";
settings.ShowText = true;
settings.TextMargin = 5;
settings.BarHeight = 60;
settings.Unit = GraphicsUnit.Pixel;

BarCodeGenerator generator = new BarCodeGenerator(settings);
Image barcodeImage = generator.GenerateImage();
barcodeImage.Save("barcode.png", ImageFormat.Png);

Imports Spire.Barcode
Imports System.Drawing
Imports System.Drawing.Imaging

Dim settings As New BarcodeSettings()
settings.Type = BarCodeType.Code128
settings.Data = "12345678"
settings.ShowText = True
settings.TextMargin = 5
settings.BarHeight = 60
settings.Unit = GraphicsUnit.Pixel

Dim generator As New BarCodeGenerator(settings)
Dim barcodeImage As Image = generator.GenerateImage()
barcodeImage.Save("barcode.png", ImageFormat.Png)

The mutable settings object means configurations can be accidentally shared across calls when a single instance is reused across multiple generation operations. The generator class adds an additional instantiation step that carries no configuration logic of its own.

IronBarcode Approach

IronBarcode uses a static factory method with optional fluent chaining. There is no settings object and no generator instance to manage:

// IronBarcode generation
using IronBarCode;

BarcodeWriter.CreateBarcode("12345678", BarcodeEncoding.Code128)
    .SaveAsPng("barcode.png");

// With sizing:
BarcodeWriter.CreateBarcode("12345678", BarcodeEncoding.Code128)
    .ResizeTo(400, 100)
    .SaveAsPng("barcode.png");

// IronBarcode generation
using IronBarCode;

BarcodeWriter.CreateBarcode("12345678", BarcodeEncoding.Code128)
    .SaveAsPng("barcode.png");

// With sizing:
BarcodeWriter.CreateBarcode("12345678", BarcodeEncoding.Code128)
    .ResizeTo(400, 100)
    .SaveAsPng("barcode.png");

Imports IronBarCode

BarcodeWriter.CreateBarcode("12345678", BarcodeEncoding.Code128) _
    .SaveAsPng("barcode.png")

' With sizing:
BarcodeWriter.CreateBarcode("12345678", BarcodeEncoding.Code128) _
    .ResizeTo(400, 100) _
    .SaveAsPng("barcode.png")

QR codes with custom logos are available across all IronBarcode license tiers:

var qr = QRCodeWriter.CreateQrCode("https://example.com", 500, QRCodeWriter.QrErrorCorrectionLevel.Highest);
qr.AddBrandLogo("logo.png");
qr.SaveAsPng("qr-with-logo.png");

var qr = QRCodeWriter.CreateQrCode("https://example.com", 500, QRCodeWriter.QrErrorCorrectionLevel.Highest);
qr.AddBrandLogo("logo.png");
qr.SaveAsPng("qr-with-logo.png");

Dim qr = QRCodeWriter.CreateQrCode("https://example.com", 500, QRCodeWriter.QrErrorCorrectionLevel.Highest)
qr.AddBrandLogo("logo.png")
qr.SaveAsPng("qr-with-logo.png")

Mixed-Format Document Processing

Teams that begin with a single known barcode format often find their format diversity grows over time. A warehousing application that started with Code128 labels may receive shipments from suppliers using DataMatrix, GS1-128, or QR codes. Each new format that enters the workflow requires updating the candidate array in the type-guessing loop, re-testing the detection logic, and confirming that no existing format is displaced by the iteration order. When format diversity reaches a point where the maintenance overhead of that loop becomes a recurring development cost, teams evaluate whether auto-detection would eliminate that burden entirely.

PDF Integration

Document-heavy applications often encounter a moment where barcodes must be extracted from PDF files rather than standalone images. In a Spire.Barcode workflow, this transition requires acquiring a Spire.PDF license, integrating a second package, and writing page iteration and image extraction infrastructure before any barcode reading can occur. Teams that did not anticipate this requirement at initial purchase find themselves managing two product licenses and two API surfaces for a task that conceptually belongs to barcode reading. The discovery that PDF support requires a separate purchase is a common trigger for re-evaluating the product selection.

Free Tier Evaluation Limitations

Teams that evaluated FreeSpire.Barcode and then purchased the commercial license sometimes report that the commercial product behaves differently than their evaluation suggested. This is by design: the free tier intentionally degrades reading performance and restricts the symbology set, which means benchmarks and format coverage tests conducted during evaluation do not transfer to the commercial deployment. When a team discovers this discrepancy post-purchase, they often look for alternatives whose trial behavior is representative of production behavior.

Reducing Product Count

Organizations that standardize their technology stack sometimes identify Spire.Barcode as one component in a growing inventory of E-iceblue products, each carrying its own license cost and renewal cycle. If the primary driver for Spire.Barcode is barcode reading within a document processing pipeline — rather than deep integration with Spire.Doc or Spire.XLS — teams evaluate whether a single self-contained barcode library would reduce both licensing complexity and support surface area.

Removing the BarCodeType Parameter

Every scanner.Scan() call in a Spire.Barcode codebase carries a BarCodeType argument. Replacing these calls with BarcodeReader.Read() removes the type parameter entirely. Type-guessing loops — foreach blocks that iterate through candidate BarCodeType values — can be deleted in full; a single BarcodeReader.Read() call replaces the entire loop.

Updating the Return Type

Spire.Barcode's Scan() returns string[]. IronBarcode returns a BarcodeResults collection. Call sites that assign to string[] or pass results to methods expecting that type require updating. Extracting values as an array uses .Select(r => r.Value).ToArray(); accessing the first result uses .First()?.Value.

Removing the Spire.PDF Package

If Spire.PDF was installed solely to support barcode extraction from PDF files, it can be removed after migrating to IronBarcode. All using Spire.Pdf; imports and manual page iteration blocks are replaced by a single BarcodeReader.Read("file.pdf") call. If Spire.PDF is used for other document operations beyond barcode extraction, it should be retained and only the barcode-related code paths replaced.

Namespace Changes

Replace using Spire.Barcode; with using IronBarCode;. The BarCodeType enum is replaced by BarcodeEncoding for generation and requires no equivalent for reading. License initialization changes from BarcodeSettings.ApplyKey() or Spire.License.LicenseProvider.SetLicenseKey() to a single IronBarCode.License.LicenseKey property assignment at application startup.