批量条形码生成器

上传 CSV 文件一次最多生成 100 个条形码，所有处理均在浏览器中完成，数据不离开您的设备。

第一步：上传 CSV

CSV 格式

两列：数据列和码制列（可选）。如缺少码制列，则使用所选默认码制。

data,symbology
5901234123457,EAN13
012345678905,UPC
Hello-World,CODE128
CODE39-DEMO,CODE39

将 CSV 文件拖放至此，或

或直接粘贴数据（每行一条）：

第二步：预览 ( 个条形码)

# 数据 码制 状态

Related on QRCodeFYI

QR Code Batch Generator

Generate multiple QR codes at once from a list.

How to Use

  1. 1
    Prepare your CSV data file

    Create a CSV file with one barcode value per row, optionally including a label or description column. The generator accepts plain numeric values for EAN/UPC/ISBN, or alphanumeric strings for Code 128 and Code 39. Remove any existing check digits if you want the generator to calculate them automatically.

  2. 2
    Upload the CSV and configure settings

    Upload the CSV and select the target symbology, output format (PNG, SVG, PDF), resolution (for raster outputs), and whether to include human-readable text beneath each symbol. Check digit generation and format validation are applied to every row before generation.

  3. 3
    Download the generated batch

    The generator produces a ZIP archive containing one barcode image per row, named by the source value or the label column. A validation report is included listing any rows that failed due to invalid data, wrong character set, or check digit errors.

About

Batch barcode generation addresses the real-world requirement of printing unique, standards-compliant barcodes for an entire product catalog, warehouse location set, or inventory migration in a single workflow. The fundamental challenge in batch generation is data quality: each row of source data must encode a valid value for the target symbology before any image is produced. A batch of 10,000 EAN-13 labels generated from a CSV containing even a small percentage of malformed values will produce an unusable output if errors are not caught and reported per-row before generation.

For GS1 applications, batch generation must also respect the Application Identifier framework when producing GS1-128 or GS1 DataMatrix symbols. Application Identifiers are two- to four-digit codes defined in GS1 General Specifications that prefix each data field in a multi-field barcode, telling the scanner how to interpret each segment. AI (01) precedes a 14-digit GTIN, AI (17) precedes a six-digit expiry date, AI (10) precedes a variable-length batch/lot number, and AI (21) precedes a serial number. Correctly sequencing and delimiting these fields — including the use of FNC1 group separators between variable-length AIs — is essential for interoperability with GS1 verification systems in pharmaceuticals, food safety, and logistics.

SVG output is the recommended format for batch barcode generation because SVG files are text-based, compact, and can be imported directly into professional label design applications such as Adobe Illustrator, Label Matrix, BarTender, and NiceLabel without quality loss at any print size. For integration into ERP or WMS systems, barcode generation APIs that accept a data payload and return an SVG or PDF stream are commonly used, with the BarcodeFYI REST API providing a standards-compliant endpoint for programmatic generation without requiring local installation of a barcode library.

FAQ

What output formats are best for printing barcodes in bulk?
For professional label printing, SVG (Scalable Vector Graphics) is the preferred output because it is resolution-independent and can be scaled to any size without pixelation. PDF is similarly resolution-independent and integrates directly with most label printing software and print production workflows. PNG and other raster formats are acceptable for office label printing but must be generated at sufficient resolution — GS1 recommends a minimum of 300 DPI for barcode raster images, with 600 DPI preferred for symbols at or below 100% magnification to ensure sharp bar edges after rasterization.
How many barcodes can I generate in a single batch?
Practical batch size limits depend on the hosting environment and output format. SVG batches are compact — a typical EAN-13 SVG is under 5 KB — so batches of thousands of symbols are feasible. High-resolution PNG or PDF output for large batches can generate hundreds of megabytes. For production-scale batch generation (tens of thousands of barcodes for a product launch or inventory migration), server-side tools or barcode generation libraries such as python-barcode, bwip-js, or Zint running in a local environment are more appropriate than browser-based tools, which are limited by client-side memory and processing constraints.
Should I include check digits in my CSV data?
Best practice is to store your barcode data without check digits and let the generation tool compute and append them at render time. This prevents errors introduced by manually calculated or copied check digits and ensures the output always contains a mathematically correct check character. If your source data already includes check digits — for example, GTINs retrieved from a GS1 registry — the generator should validate those digits rather than recalculate them, as recalculation may strip a deliberate trailing digit from an already-complete value. The BarcodeFYI batch generator provides an option to select which mode applies.
Can I batch generate barcodes with variable data such as serial numbers or expiry dates?
Yes. Batch generation with variable data is common in pharmaceutical labeling, logistics, and manufacturing. For GS1-128 or GS1 DataMatrix symbols encoding GTIN plus serial number, lot number, and expiry date, the CSV should contain columns for each Application Identifier field. The generator assembles the GS1 data string using the correct AI format codes (01 for GTIN, 17 for expiry date in YYMMDD, 10 for batch/lot, 21 for serial number) and encodes the result as a single GS1-128 or DataMatrix symbol. Correct AI formatting is essential for downstream GS1 verification systems used by retailers and healthcare supply chains.
What are common errors in batch barcode generation from CSV files?
The most frequent errors in batch generation are: incorrect digit count (a 12-digit value submitted for EAN-13 which expects 12 data digits before the check digit, or a 13-digit complete EAN-13 treated as data without check digit removal); invalid characters for the target symbology (alphanumeric text submitted to a numeric-only symbology like EAN or ITF); encoding conflicts in the CSV file (BOM characters, Windows line endings, or UTF-8 characters in what should be ASCII data); and leading-zero loss when the CSV was opened in a spreadsheet application that silently converted barcode numbers to integers, truncating leading zeros in UPC or EAN values.