Why ZXing Became the Global Standard for QR Code Processing

Introduction

Payment systems typically use two scanning modes: user scans merchant's static code ("primary scan") or merchant scans user's payment code ("passive scan"). Nearly every scanning app — WeChat, Alipay, Taobao, Meituan — relies on ZXing for barcode recognition. Android's built-in scanner also uses ZXing. The library has 34,000 GitHub stars, Apache 2.0 license, and has been maintained since 2007.

What Is ZXing?

ZXing (pronounced "zebra crossing") is an open-source, multi-format 1D/2D barcode image processing library written in Java and ported to other languages. It generates and recognizes virtually all mainstream barcode formats:

2D codes: QR Code, Data Matrix, Aztec, MaxiCode, PDF417

1D barcodes: UPC-A, UPC-E, EAN-8, EAN-13, Code 39, Code 93, Code 128, ITF, Codabar, RSS-14, RSS Expanded

This means ZXing handles WeChat payment codes, product barcodes, and airline PDF417 tickets alike.

Origin: A Google 20% Project

ZXing began as a Google employee's "20% time" side project. The 2007 announcement called it experimental and incomplete, yet it became the industry standard. This demonstrates how a focused, open solution can outpace proprietary alternatives.

Encoding and Decoding Flow

Generation (encoding + error correction): Text → binary → add error correction codewords → place modules in matrix per QR standard → render image.

Recognition (locate + decode): Find finder patterns (three corner squares), correct perspective, then decode bit by bit.

Code Examples

Dependencies (Maven)

<dependency>
  <groupId>com.google.zxing</groupId>
  <artifactId>core</artifactId>
  <version>3.5.3</version>
</dependency>
<dependency>
  <groupId>com.google.zxing</groupId>
  <artifactId>javase</artifactId>
  <version>3.5.3</version>
</dependency>

Generate QR Code (Core Two Lines)

import com.google.zxing.BarcodeFormat;
import com.google.zxing.MultiFormatWriter;
import com.google.zxing.client.j2se.MatrixToImageWriter;
import com.google.zxing.common.BitMatrix;
import java.nio.file.Path;
import java.nio.file.Paths;

public class QRCodeGenerator {
  public static void main(String[] args) throws Exception {
    String data = "https://www.example.com";
    String path = "QRCode.png";
    // Core two lines: encode + write file
    BitMatrix bitMatrix = new MultiFormatWriter()
      .encode(data, BarcodeFormat.QR_CODE, 200, 200);
    MatrixToImageWriter.writeToPath(bitMatrix, "PNG", Paths.get(path));
    System.out.println("QR code generated");
  }
}

MultiFormatWriter.encode()

handles data encoding, error correction calculation, matrix filling, and finder pattern insertion. You only specify content, format, and size.

Read QR Code

import com.google.zxing.BinaryBitmap;
import com.google.zxing.MultiFormatReader;
import com.google.zxing.Result;
import com.google.zxing.client.j2se.BufferedImageLuminanceSource;
import com.google.zxing.common.HybridBinarizer;
import javax.imageio.ImageIO;
import java.io.File;

public class QRCodeReader {
  public static void main(String[] args) throws Exception {
    // Read image
    var image = ImageIO.read(new File("QRCode.png"));
    // Build binary bitmap
    var source = new BufferedImageLuminanceSource(image);
    var bitmap = new BinaryBitmap(new HybridBinarizer(source));
    // Decode
    Result result = new MultiFormatReader().decode(bitmap);
    System.out.println("Result: " + result.getText());
  }
}

MultiFormatReader.decode()

is the core entry: it auto-locates the code, corrects the image, decodes, and applies error correction.

Generation with Error Correction Level (Production Recommended)

import com.google.zxing.EncodeHintType;
import com.google.zxing.qrcode.decoder.ErrorCorrectionLevel;
import java.util.HashMap;
import java.util.Map;

Map<EncodeHintType, Object> hints = new HashMap<>();
// H level: corrects 30% errors, suitable for wear-prone surfaces
hints.put(EncodeHintType.ERROR_CORRECTION, ErrorCorrectionLevel.H);
// Set charset to avoid Chinese garbling
hints.put(EncodeHintType.CHARACTER_SET, "UTF-8");

BitMatrix bitMatrix = new MultiFormatWriter()
  .encode(data, BarcodeFormat.QR_CODE, 300, 300, hints);

Error correction levels: L (7%), M (15%), Q (25%), H (30%). Higher levels increase resilience but also code size.

ZXing in Android Architecture

Android is a primary battlefield for ZXing. WeChat and Alipay scanning features are built on it. ZXing provides a dedicated Android client module with camera preview, scanning frame, and decoding thread.

Key design: Decoding runs on a separate thread, communicating via Handler to avoid ANR (Application Not Responding) on the main thread.

Comparison: ZXing vs ZBar vs OpenCV

The article benchmarks three libraries across several dimensions:

Language: ZXing (Java), ZBar (C), OpenCV (C++)

Detection speed: ZXing fastest, OpenCV slowest

Small QR codes: OpenCV best, ZXing average

Blurry/distorted tolerance: ZXing and ZBar good, OpenCV average

Integration difficulty: ZXing extremely low, ZBar low, OpenCV high

Ecosystem maturity: ZXing most mature, OpenCV good, ZBar average

Measured data confirms ZXing leads in detection speed. For standard clear codes, ZXing and ZBar have similar accuracy; for small or low-resolution codes, OpenCV performs better. ZXing's core advantage is not highest accuracy but best overall experience: pure Java, zero dependencies, concise API, native Android support, Apache 2.0 license.

Pros and Cons

Pros

Zero dependencies, pure Java: No native libraries, no JNI; just add core and javase JARs.

Minimal API: Two lines to generate, one core line to decode.

Multi-format support: Covers nearly all mainstream 1D and 2D formats.

Native Android support: Complete client module with camera, UI, and decoding thread.

Mature ecosystem: 19 years, 34k stars, Apache 2.0.

Fastest detection speed among open-source libraries.

Cons

Poor small-code recognition: Module size <3 pixels drops accuracy; OpenCV is better.

Cannot read inverted (light-on-dark) QR codes: Default logic expects dark modules on light background. This is a widely reported limitation.

Weaker on severe distortion/occlusion: ZBar's error correction is stronger.

Recommended Use Cases

Payment system QR generation: Strongly recommended — few lines, stable.

Android scanning feature: Strongly recommended — native support, same as WeChat/Alipay.

Product barcode generation: Strongly recommended — supports EAN, UPC, Code 128.

E-tickets/coupons: Strongly recommended — generate QR as credential.

Inverted QR codes: Requires preprocessing (manual color inversion).

Tiny QR codes: Evaluate; OpenCV may be better.

Heavily distorted/occluded codes: Evaluate; ZBar may be better.

Conclusion

ZXing succeeds because it turns a complex problem — data encoding, error correction, image processing, localization — into two method calls: encode() and decode(). Its speed comes from early, mature optimization of localization algorithms and floating-point operations, not superior "intelligence." For standard clear codes, ZXing is the fastest. Its stability stems from 19 years of validation at billions of daily scans (WeChat, Alipay, Taobao). Shortcomings like inverted codes and tiny codes can be mitigated with preprocessing, while ZXing's simplicity and ecosystem remain hard to replace.

Open source:

https://github.com/zxing/zxing