Making a QR code in .NET is a three-line job, and the same snippet shows exactly where the library stops.
// QRCoder, a QR code in three lines
var generator = new QRCodeGenerator();
var data = generator.CreateQrCode("ORDER-1042", QRCodeGenerator.ECCLevel.Q);
byte[] png = new PngByteQRCode(data).GetGraphic(20);
// Read one back? There is no QRCoder call for that.
Three lines to write a QR code, and no call at all to read one, because decoding is not in the library. Every workflow that scans, validates, or verifies a code needs a second library, and IronQR is where both directions live in one place.
Full disclosure. We build IronQR at Iron Software, and this read looks at where QRCoder's generate-only boundary costs a team and where IronQR covers both directions.
What's the One Line That Decides It?
Everything else about QRCoder is a detail next to this. It writes a QR code and it cannot read one back, so the question is not how the generation looks, it is whether reading is ever part of the feature. If the answer is yes to decoding a barcode, then the generate-only library is half of what the feature needs, and the other half is a separate dependency. IronQR generates and decodes from the same package, so the answer to that question never changes the shape of the project.
The Whole Decision, in One Table
Set the two side by side and the read row at the top is the one that decides it.
| Aspect | QRCoder | IronQR |
|---|---|---|
| Read or decode a QR | Not supported at all | Supported, QrReader.Read
|
| Read a QR from a PDF | Not supported | Supported |
| Damaged, rotated, or skewed codes | Not handled | ML-based detection |
| Micro QR and rMQR formats | Not supported | Supported |
| Cross-platform renderers | Some need Windows or extra packages | Runs anywhere from one package |
| Generate a QR | Yes | Yes, QrWriter.Write
|
Table 1. QRCoder and IronQR across the generate-and-read questions, from each project's own README and documentation.
What Does the Boundary Cost a Real Feature?
The boundary is abstract until it meets a real feature. Generate a ticket and scan it at the door, print a label and verify it before shipping, read a code a user uploaded, and QRCoder covers exactly the first half of each, leaving you to integrate a reader for the second. Even its PDF output only writes a code into a document and cannot find one inside a PDF that arrives, which is a separate job it does not do at all. That is two libraries, two object models, and two sets of platform constraints for what a product owner described as one feature.
A quieter cost sits further down. QRCoder ships many renderers and they do not all run everywhere, since the System.Drawing-backed ones are restricted to Windows from .NET 6 on while the pure-managed PNG and SVG renderers run anywhere, so code copied from an older tutorial builds on a Windows machine and fails in a Linux container. Under the project itself, QRCoder dates to 2013 and passed to a new maintainer in 2025, so a shipped feature built on it is also betting on a single-maintainer handover holding.
IronQR reads the code it just wrote, renders through one cross-platform imaging layer that runs the same on Windows, Linux, and containers, and is maintained by Iron Software directly on a monthly cadence, so none of those costs lands on the team.
One Library That Reads and Writes
IronQR writes a code and reads one back from the same package, and the read side is built for real captures rather than clean inputs.
using IronQr;
using IronSoftware.Drawing;
// Generate
QrCode myQr = QrWriter.Write("https://example.com/order/1042");
myQr.Save().SaveAs("order-qr.png");
// Read the same code back, including photographs and rotated codes
var input = new QrImageInput(AnyBitmap.FromFile("scanned-ticket.jpg"));
var reader = new QrReader();
foreach (QrResult result in reader.Read(input))
{
Console.WriteLine(result.Value);
}
One library covers both directions, machine-learning detection handles rotated, skewed, and partially damaged codes rather than requiring a clean scan, it reads directly from PDFs, and it supports Micro QR and rMQR. You can pull IronQR from NuGet and run this generate-and-read path in a couple of minutes, and the QR scanning guide walks the read side end to end.
Which is it for you, generation only, or are you already looking for something to read them back? Tell us in the comments, we read every one.
IronQR has a free trial if you want to run the generate-and-read path on your own codes before deciding.
QRCoder is an open-source project distributed under the MIT licence, and is not affiliated with Iron Software. The details above are drawn from the project's own README and NuGet listing. If something has changed since, correct us in the comments.
Top comments (0)