Patagames Tesseract.Net SDK vs IronOCR: .NET OCR

Basic OCR with Patagames

The Patagames API initializes an OcrApi instance per operation, specifies a tessdata folder path explicitly, and accepts a System.Drawing.Bitmap:

// NuGet: Install-Package Tesseract.Net.SDK
using Patagames.Ocr;
using Patagames.Ocr.Enums;
using System.Drawing;

public class PatagamesOcrService
{
    private const string TessDataPath = @"./tessdata"; // must exist and be populated

    public string ExtractText(string imagePath)
    {
        using var api = OcrApi.Create();
        api.Init(TessDataPath, "eng"); // tessdata path — breaks on deployment if path is wrong

        using var bitmap = new Bitmap(imagePath);
        return api.GetTextFromImage(bitmap);
    }

    public string MultiLanguageOcr(string imagePath)
    {
        using var api = OcrApi.Create();
        api.Init(TessDataPath, "eng+fra+deu"); // language string must match tessdata files present

        using var bitmap = new Bitmap(imagePath);
        return api.GetTextFromImage(bitmap);
    }

    public string OcrWithSegmentation(string imagePath, PageSegmentationMode mode)
    {
        using var api = OcrApi.Create();
        api.Init(TessDataPath, "eng");
        api.SetVariable("tessedit_pageseg_mode", ((int)mode).ToString()); // raw Tesseract variable

        using var bitmap = new Bitmap(imagePath);
        return api.GetTextFromImage(bitmap);
    }
}

// NuGet: Install-Package Tesseract.Net.SDK
using Patagames.Ocr;
using Patagames.Ocr.Enums;
using System.Drawing;

public class PatagamesOcrService
{
    private const string TessDataPath = @"./tessdata"; // must exist and be populated

    public string ExtractText(string imagePath)
    {
        using var api = OcrApi.Create();
        api.Init(TessDataPath, "eng"); // tessdata path — breaks on deployment if path is wrong

        using var bitmap = new Bitmap(imagePath);
        return api.GetTextFromImage(bitmap);
    }

    public string MultiLanguageOcr(string imagePath)
    {
        using var api = OcrApi.Create();
        api.Init(TessDataPath, "eng+fra+deu"); // language string must match tessdata files present

        using var bitmap = new Bitmap(imagePath);
        return api.GetTextFromImage(bitmap);
    }

    public string OcrWithSegmentation(string imagePath, PageSegmentationMode mode)
    {
        using var api = OcrApi.Create();
        api.Init(TessDataPath, "eng");
        api.SetVariable("tessedit_pageseg_mode", ((int)mode).ToString()); // raw Tesseract variable

        using var bitmap = new Bitmap(imagePath);
        return api.GetTextFromImage(bitmap);
    }
}

Imports Patagames.Ocr
Imports Patagames.Ocr.Enums
Imports System.Drawing

Public Class PatagamesOcrService
    Private Const TessDataPath As String = "./tessdata" ' must exist and be populated

    Public Function ExtractText(imagePath As String) As String
        Using api = OcrApi.Create()
            api.Init(TessDataPath, "eng") ' tessdata path — breaks on deployment if path is wrong

            Using bitmap = New Bitmap(imagePath)
                Return api.GetTextFromImage(bitmap)
            End Using
        End Using
    End Function

    Public Function MultiLanguageOcr(imagePath As String) As String
        Using api = OcrApi.Create()
            api.Init(TessDataPath, "eng+fra+deu") ' language string must match tessdata files present

            Using bitmap = New Bitmap(imagePath)
                Return api.GetTextFromImage(bitmap)
            End Using
        End Using
    End Function

    Public Function OcrWithSegmentation(imagePath As String, mode As PageSegmentationMode) As String
        Using api = OcrApi.Create()
            api.Init(TessDataPath, "eng")
            api.SetVariable("tessedit_pageseg_mode", CInt(mode).ToString()) ' raw Tesseract variable

            Using bitmap = New Bitmap(imagePath)
                Return api.GetTextFromImage(bitmap)
            End Using
        End Using
    End Function
End Class

The tessdata path string is the first deployment problem teams hit. On a developer machine it works. In a Docker container or a Linux CI runner, the path either fails or the runtime does not exist at all. On macOS, the native Windows binary simply does not load. The segmentation mode is set by writing a raw Tesseract variable string — there is no strongly typed enum wrapping that call. These are the seams where Tesseract's raw nature shows through despite the commercial wrapper.

Detailed Feature Comparison

Patagames Approach

Patagames ships Windows native binaries for the Tesseract engine. The OcrApi class loads a Windows DLL. On Linux or macOS, there is nothing to load. The System.Drawing.Bitmap dependency compounds the issue: System.Drawing on .NET Core and .NET 5+ requires libgdiplus on Linux and is unsupported on macOS without Mono, which adds its own complexity.

A team building an ASP.NET Core application on .NET 8 and deploying to a Linux container hits two separate walls with Patagames: the native Tesseract binary does not exist for that platform, and the System.Drawing dependency requires an additional native package even if it did. The application simply does not run. There is no fallback and no migration path short of replacing the library.

Consider what this means for a typical modern .NET shop. Development happens on Windows or macOS. CI runs on Linux. Production is a Docker container on Kubernetes. Patagames fails at step two of that pipeline.

// Patagames: Windows runtime only
// This code path does not execute on Linux or macOS
using var api = OcrApi.Create();
api.Init(@"./tessdata", "eng"); // Windows DLL load — fails silently or throws on Linux

using var bitmap = new Bitmap(imagePath); // System.Drawing — requires libgdiplus on Linux
return api.GetTextFromImage(bitmap);

// Patagames: Windows runtime only
// This code path does not execute on Linux or macOS
using var api = OcrApi.Create();
api.Init(@"./tessdata", "eng"); // Windows DLL load — fails silently or throws on Linux

using var bitmap = new Bitmap(imagePath); // System.Drawing — requires libgdiplus on Linux
return api.GetTextFromImage(bitmap);

Imports System.Drawing

' Patagames: Windows runtime only
' This code path does not execute on Linux or macOS
Using api = OcrApi.Create()
    api.Init("./tessdata", "eng") ' Windows DLL load — fails silently or throws on Linux

    Using bitmap As New Bitmap(imagePath) ' System.Drawing — requires libgdiplus on Linux
        Return api.GetTextFromImage(bitmap)
    End Using
End Using

The tessdata path also creates a separate deployment problem. In a container, the tessdata directory must be explicitly copied into the image. If the path is wrong, the Init call fails at runtime. Nothing in the build pipeline catches this; it surfaces in production.

IronOCR Approach

IronOCR publishes platform-specific runtime packages as part of its NuGet dependency graph. Adding IronOcr to a project resolves the correct native binary for Windows x64, Windows x86, Linux x64, or macOS automatically. No RuntimeIdentifier gymnastics, no manual binary copying.

// IronOCR: same code on Windows, Linux, macOS, Docker
using IronOcr;

var text = new IronTesseract().Read("document.jpg").Text;

// IronOCR: same code on Windows, Linux, macOS, Docker
using IronOcr;

var text = new IronTesseract().Read("document.jpg").Text;

Imports IronOcr

Dim text As String = New IronTesseract().Read("document.jpg").Text

A Linux Docker deployment is documented and supported out of the box. See the IronOCR Docker deployment guide for the exact Dockerfile configuration. The Linux deployment guide covers both Debian and Alpine. No platform-specific code branching is required anywhere in the application.

Language data arrives through NuGet. dotnet add package IronOcr.Languages.French adds the French tessdata. The package is resolved at build time, copied to output automatically, and available in every deployment environment without any path configuration. See how IronOCR handles multiple languages for the full language management workflow.

What Patagames Adds Over Free Wrappers

Patagames markets four benefits over free Tesseract wrappers: commercial support, a simplified API, pre-built native binaries, and managed tessdata handling. Each deserves examination.

Commercial support is real but difficult to price. You are paying for a support contract for problems that trace back to Tesseract, a third-party open-source engine Patagames does not control. If Tesseract produces incorrect output on a particular image type, Patagames support cannot improve the engine.

Simplified API is marginal. OcrApi.Create() followed by api.Init(path, "eng") is slightly cleaner than the raw Tesseract interop layer in charlesw/tesseract, but both still require the same manual tessdata management and the same absence of preprocessing.

Pre-built native binaries save the hour or two required to compile Tesseract from source on Windows. This was meaningful in 2015. Today, the free tesseractocr NuGet package (Tesseract on NuGet.org) also ships pre-built native binaries at zero cost.

Managed tessdata handling is the claim most undermined by the actual API. The api.Init(TessDataPath, "eng") call still takes a path string. You still populate that directory. The management is only slightly cleaner than pointing a config file at a folder.

The result: Patagames charges commercial prices for a convenience layer that free alternatives also provide, does not solve Tesseract's fundamental preprocessing and PDF gaps, and removes cross-platform support that free alternatives retain.

IronOCR's Commercial Justification

When evaluating whether a commercial OCR library earns its license cost, the question is what the library solves that free alternatives cannot. IronOCR's pricing starts at $999 for a perpetual Lite license. That price buys capabilities Tesseract wrappers — free or commercial — simply do not provide.

// PDF OCR: Patagames has no PDF support at all
// Free wrappers have no PDF support at all
// IronOCR: one line
using IronOcr;

var text = new IronTesseract().Read("scanned-invoice.pdf").Text;

// PDF OCR: Patagames has no PDF support at all
// Free wrappers have no PDF support at all
// IronOCR: one line
using IronOcr;

var text = new IronTesseract().Read("scanned-invoice.pdf").Text;

Imports IronOcr

' PDF OCR: Patagames has no PDF support at all
' Free wrappers have no PDF support at all
' IronOCR: one line
Dim text As String = New IronTesseract().Read("scanned-invoice.pdf").Text

For the PDF OCR workflow, Patagames requires an external PDF renderer (PdfiumViewer, iText, or similar), a loop to render each page to a Bitmap, passing each bitmap to GetTextFromImage, and concatenating results. That is 30-50 additional lines of code, an additional NuGet dependency, and another failure point. IronOCR handles it in one call.

// Searchable PDF output: not available in Patagames, not available in free wrappers
// IronOCR: two lines
var result = new IronTesseract().Read("scanned-document.pdf");
result.SaveAsSearchablePdf("searchable-output.pdf");

// Searchable PDF output: not available in Patagames, not available in free wrappers
// IronOCR: two lines
var result = new IronTesseract().Read("scanned-document.pdf");
result.SaveAsSearchablePdf("searchable-output.pdf");

' Searchable PDF output: not available in Patagames, not available in free wrappers
' IronOCR: two lines
Dim result = New IronTesseract().Read("scanned-document.pdf")
result.SaveAsSearchablePdf("searchable-output.pdf")

The searchable PDF output capability — producing a PDF with an invisible text layer that makes the original document Ctrl+F searchable — requires either IronOCR or a complex hOCR-to-PDF pipeline using external tools. There is no Tesseract wrapper, free or commercial, that provides this in a single method call.

Preprocessing tells the same story. Low-quality scans — rotated, noisy, low-contrast — produce poor Tesseract output without preprocessing. Patagames has no preprocessing. You write the preprocessing code yourself using System.Drawing or ImageSharp or similar.

// IronOCR: built-in preprocessing pipeline for poor quality images
using IronOcr;

using var input = new OcrInput();
input.LoadImage("rotated-noisy-scan.jpg");
input.Deskew();          // correct rotation
input.DeNoise();         // remove scan noise
input.Contrast();        // improve contrast
input.Binarize();        // convert to black/white optimal for OCR
input.EnhanceResolution(300); // normalize DPI

var result = new IronTesseract().Read(input);
Console.WriteLine($"Confidence: {result.Confidence}%");

// IronOCR: built-in preprocessing pipeline for poor quality images
using IronOcr;

using var input = new OcrInput();
input.LoadImage("rotated-noisy-scan.jpg");
input.Deskew();          // correct rotation
input.DeNoise();         // remove scan noise
input.Contrast();        // improve contrast
input.Binarize();        // convert to black/white optimal for OCR
input.EnhanceResolution(300); // normalize DPI

var result = new IronTesseract().Read(input);
Console.WriteLine($"Confidence: {result.Confidence}%");

Imports IronOcr

Dim input As New OcrInput()
Using input
    input.LoadImage("rotated-noisy-scan.jpg")
    input.Deskew()          ' correct rotation
    input.DeNoise()         ' remove scan noise
    input.Contrast()        ' improve contrast
    input.Binarize()        ' convert to black/white optimal for OCR
    input.EnhanceResolution(300) ' normalize DPI

    Dim result = New IronTesseract().Read(input)
    Console.WriteLine($"Confidence: {result.Confidence}%")
End Using

The image quality correction guide covers the full range of available filters and when to apply each one. For color-specific preprocessing, the image color correction guide provides additional options. None of this is available in Patagames regardless of the license tier purchased.

Patagames Approach to Language Configuration

Patagames uses a path string and a language concatenation string for multi-language OCR:

// Patagames multi-language: manual tessdata, string concatenation
using Patagames.Ocr;

using var api = OcrApi.Create();
api.Init(@"./tessdata", "eng+fra+deu"); // tessdata folder must contain eng.traineddata, fra.traineddata, deu.traineddata

using var bitmap = new Bitmap(imagePath);
return api.GetTextFromImage(bitmap);

// Patagames multi-language: manual tessdata, string concatenation
using Patagames.Ocr;

using var api = OcrApi.Create();
api.Init(@"./tessdata", "eng+fra+deu"); // tessdata folder must contain eng.traineddata, fra.traineddata, deu.traineddata

using var bitmap = new Bitmap(imagePath);
return api.GetTextFromImage(bitmap);

Imports Patagames.Ocr

Using api = OcrApi.Create()
    api.Init("./tessdata", "eng+fra+deu") ' tessdata folder must contain eng.traineddata, fra.traineddata, deu.traineddata

    Using bitmap As New Bitmap(imagePath)
        Return api.GetTextFromImage(bitmap)
    End Using
End Using

This is functionally identical to the free charlesw/tesseract wrapper's multi-language syntax. You still download tessdata files manually, copy them to the correct directory, and reference them by code string. The commercial license provides no automation for that workflow.

IronOCR Approach to Language Configuration

IronOCR manages language data as NuGet packages with a strongly typed API:

// IronOCR multi-language: NuGet packages, strongly typed
// dotnet add package IronOcr.Languages.French
// dotnet add package IronOcr.Languages.German
using IronOcr;

var ocr = new IronTesseract();
ocr.Language = OcrLanguage.English;
ocr.AddSecondaryLanguage(OcrLanguage.French);
ocr.AddSecondaryLanguage(OcrLanguage.German);

var result = ocr.Read(imagePath);

// IronOCR multi-language: NuGet packages, strongly typed
// dotnet add package IronOcr.Languages.French
// dotnet add package IronOcr.Languages.German
using IronOcr;

var ocr = new IronTesseract();
ocr.Language = OcrLanguage.English;
ocr.AddSecondaryLanguage(OcrLanguage.French);
ocr.AddSecondaryLanguage(OcrLanguage.German);

var result = ocr.Read(imagePath);

Imports IronOcr

Dim ocr As New IronTesseract()
ocr.Language = OcrLanguage.English
ocr.AddSecondaryLanguage(OcrLanguage.French)
ocr.AddSecondaryLanguage(OcrLanguage.German)

Dim result = ocr.Read(imagePath)

Language management through NuGet means the CI pipeline resolves language data the same way it resolves any other dependency. There is no tessdata directory to copy into Docker images, no deployment checklist item for "make sure tessdata is present," and no typo risk from hand-typing language code strings. The 125+ available language packs all install the same way.

The gap between Patagames and free wrappers is narrow — the commercial price buys primarily Windows binary convenience. The gap between Patagames and IronOCR is wide — the commercial price buys native PDF support, automatic preprocessing, searchable PDF output, cross-platform deployment, and structured result data.

The Linux Container Deployment

The most common forcing function is a migration from Windows Server to Linux containers. A team that built an internal document processing tool on Windows, using Patagames for OCR, discovers during a cloud migration project that the library simply does not run in a Docker container on Amazon ECS or Azure Container Instances. The Windows-only native binary has no Linux equivalent. The migration options are either maintain a separate Windows compute instance just for OCR (expensive and architecturally awkward) or replace the OCR library. IronOCR is a drop-in replacement from an API standpoint — the multi-step Patagames initialization sequence collapses to a single read call — and the application runs on Linux without any other changes. The IronOCR Docker guide covers the exact Dockerfile configuration for production container deployments.

The PDF Processing Requirement

Document management applications frequently start with image OCR and then add PDF processing requirements as the product evolves. With Patagames, PDF support requires integrating an external PDF rendering library, writing a rendering loop, and managing per-page image buffers. Teams that have built this wrapper code find it brittle — PDF rendering quality varies, page rotation handling requires additional logic, and adding password-protected PDF support requires another external dependency. IronOCR handles all of it natively. The PDF input guide covers single-page, multi-page, and password-protected PDFs. The transition eliminates the external PDF renderer dependency and all the code written to bridge it to Patagames.

The Pricing Transparency Problem

Patagames does not publish its license prices. Teams evaluating OCR libraries for a new project cannot budget for Patagames without engaging a sales process. IronOCR's pricing starts at $999 for a single-developer perpetual Lite license with no per-transaction cost. A small team can make an informed build-vs-buy decision without a sales call. For teams that previously chose Patagames on the assumption that commercial meant better-than-free, finding that IronOCR starts at $999 perpetual with public pricing — versus Patagames at an undisclosed commercial rate — often reframes the evaluation entirely. See the IronOCR licensing page for full tier details.

The Scan Quality Problem

Invoice processing, form OCR, and scanned document archival all produce images that require preprocessing. A Patagames-based pipeline for these workflows requires writing preprocessing code in System.Drawing or a third-party imaging library, tuning thresholds manually, and maintaining that code as input quality varies. Teams that have built this infrastructure know it takes 20-40 hours to get right. IronOCR's built-in preprocessing eliminates that investment — deskew, denoise, contrast, and binarization are single method calls that cover the cases causing most OCR accuracy problems on real-world scans. The low quality scan example demonstrates the accuracy difference preprocessing makes on degraded images.

The Searchable PDF Archive Requirement

Compliance, legal, and records management applications require searchable PDF output. A scanned document needs a text layer so users can search, copy, and highlight content in Acrobat or any PDF viewer. Patagames has no mechanism to produce searchable PDFs. Free Tesseract wrappers produce hOCR output that you can convert to a text layer using third-party tools, but that pipeline has multiple moving parts. IronOCR handles the full pipeline in a single method call — no external tools, no intermediate hOCR conversion step. Teams building archival systems discover this capability gap early and it is rarely a feature that can be added to Patagames through a workaround — it requires replacing the library.

Replacing the tessdata Directory with NuGet Packages

Patagames requires a tessdata directory populated with .traineddata files for each language. The IronOCR migration removes this entirely. Language data installs as a NuGet package:

dotnet add package IronOcr.Languages.English
dotnet add package IronOcr.Languages.French

dotnet add package IronOcr.Languages.English
dotnet add package IronOcr.Languages.French

The language is then referenced through the strongly typed OcrLanguage enum. No path configuration, no deployment checklist, no missing-tessdata production incidents.

Migrating the OcrApi Initialization Pattern

The Patagames OcrApi.Create() / api.Init() pattern has a direct IronOCR equivalent. The migration is mechanical:

// Patagames: before
using var api = OcrApi.Create();
api.Init(@"./tessdata", "eng");
using var bitmap = new Bitmap(imagePath);
var text = api.GetTextFromImage(bitmap);

// IronOCR: after
var text = new IronTesseract().Read(imagePath).Text;

// Patagames: before
using var api = OcrApi.Create();
api.Init(@"./tessdata", "eng");
using var bitmap = new Bitmap(imagePath);
var text = api.GetTextFromImage(bitmap);

// IronOCR: after
var text = new IronTesseract().Read(imagePath).Text;

Imports Patagames.Ocr
Imports System.Drawing

' Patagames: before
Using api = OcrApi.Create()
    api.Init("./tessdata", "eng")
    Using bitmap As New Bitmap(imagePath)
        Dim text = api.GetTextFromImage(bitmap)
    End Using
End Using

' IronOCR: after
Dim text = New IronTesseract().Read(imagePath).Text

For multi-language configurations, "eng+fra+deu" becomes individual AddSecondaryLanguage calls. The Patagames SetVariable("tessedit_pageseg_mode", ...) raw string call maps to ocr.Configuration.PageSegmentationMode, which is strongly typed and discoverable through IntelliSense.

System.Drawing Dependency Removal

Patagames depends on System.Drawing.Bitmap. IronOCR accepts file paths, byte arrays, streams, URLs, and System.Drawing.Bitmap objects, but the typical usage does not require System.Drawing at all. Teams migrating from Patagames can remove the System.Drawing dependency from classes that existed solely to construct Bitmap objects for passing to the OCR API. This cleans up nullable warnings on non-Windows platforms and removes a dependency that Microsoft has formally marked as not recommended for new development on non-Windows targets. The image input guide lists all supported input types.

Adding Preprocessing for Existing Workflows

If the existing Patagames implementation includes a preprocessing step written in System.Drawing or ImageSharp, that code can often be removed entirely when switching to IronOCR. Test the IronOCR output without preprocessing first. For images where automatic preprocessing is insufficient, apply explicit filters through OcrInput:

using var input = new OcrInput();
input.LoadImage(imagePath);
input.Deskew();
input.DeNoise();
var result = new IronTesseract().Read(input);

using var input = new OcrInput();
input.LoadImage(imagePath);
input.Deskew();
input.DeNoise();
var result = new IronTesseract().Read(input);

Imports IronOcr

Using input As New OcrInput()
    input.LoadImage(imagePath)
    input.Deskew()
    input.DeNoise()
    Dim result = New IronTesseract().Read(input)
End Using

The image orientation correction guide covers deskew and rotation detection in detail. In most cases, IronOCR's automatic preprocessing produces better output than a manually tuned System.Drawing preprocessing pipeline.