Encode

Barcode Generator

Generate downloadable 1D and 2D barcodes in your browser for retail products, logistics cartons, asset labels, tickets, ISBN publishing, and manufacturing traceability. Choose Code128, EAN, UPC, ITF-14, Interleaved 2 of 5, PDF417, or Data Matrix, tune scale, quiet zone, text, and colors, then export PNG, SVG, or JPG.

  • Covers Code128, Code39, EAN-13, EAN-8, UPC-A, UPC-E, ITF-14, Interleaved 2 of 5, PDF417, and Data Matrix
  • Built-in length and check-digit hints for EAN, UPC, and ITF-14 to catch invalid input early
  • Scene presets switch export settings in one click, useful for teams producing consistent labels
  • Runs entirely in the browser so your input is never uploaded to a server
tools/Barcode Generator
Code 128

General-purpose 1D barcode for IDs and internal numbers.

Switch between standard, small label, HD print, and no-text export profiles in one click.

A narrow quiet zone is a common cause of scan failures. Keep at least the default value.

Higher values push the readable text further from the bars.

Use transparent only when the final surface is clean. Otherwise prefer white for scanner reliability.

Overview

The workflow is built around three checkpoints: valid input, a readable image, and an export-ready file, so generated codes are less likely to fail in print or scanner tests.

  1. 01

    Many symbologies in one place

    Common retail, logistics, asset, ticket, and traceability standards on the same page, with no need to switch tools.

  2. 02

    Input validation

    EAN, UPC, and ITF-14 length and check-digit checks point directly to the correct code instead of just rejecting input.

  3. 03

    Tunable export settings

    Adjust scale, height, quiet zone, text, color, and background to balance scan reliability with visual rules.

  4. 04

    Local processing

    Everything runs in the browser. Input is not sent to a server, which suits internal and privacy-sensitive workflows.

  5. 05

    Scene presets

    Standard, small label, HD print, and no-text profiles help a team produce consistent batches without re-tuning every time.

  6. 06

    1D and 2D side by side

    Switch from Code128 to PDF417 or Data Matrix in the same workspace when different stages of the same workflow need different formats.

How to use

Follow a linear flow from input to export so the result is both visually correct and scanner-ready, whether for one quick code or a regular batch.

  1. 01

    Identify the scenario first, whether retail, logistics, internal ID, or high-capacity text, so you do not pick the wrong symbology to begin with.

  2. 02

    Choose the format: EAN or UPC for retail, ITF-14 for cartons, Code128 for internal IDs, and PDF417 or Data Matrix for longer or structured content.

  3. 03

    Enter the value and resolve validation hints first, especially length and check-digit issues for EAN, UPC, and ITF-14.

  4. 04

    Tune export settings to match the medium: scale, height, quiet zone, text display, and background. Prefer SVG for print and keep enough quiet zone.

  5. 05

    Export PNG, SVG, or JPG, then verify the result with at least one phone scanner and one handheld scanner before production.

Details

More than drawing bars from text. The tool is shaped around scan reliability, print handoff, and repeatable team output.

  • Format-specific length and character rules catch invalid input before it leaves the browser
  • Check-digit hints for EAN, UPC, and ITF-14 show whether the issue is length or the check digit itself
  • 1D and 2D symbologies share the same page so a single workflow can use both as needed
  • Scale, height, quiet zone, text, and background can be tuned independently to balance scan rate and visual rules
  • Scene presets help new team members produce on-brand output without reading the spec sheet
  • Live preview shows the rendered code and output dimensions so issues surface before export
  • Everything runs in the browser, suitable for offline use, internal networks, and sensitive content

Use cases

From retail and warehousing to manufacturing and publishing, the workflow covers situations where a barcode must both generate and scan reliably downstream.

  1. Retail product listing

    EAN and UPC drive shelf, POS, and distribution workflows. Length and check digit must match the official standard.

  2. Logistics cartons

    ITF-14 and Interleaved 2 of 5 are common for carton-level handling and routing. Contrast, quiet zone, and read distance matter.

  3. Assets and equipment

    Code128 and Code39 fit asset IDs, workstation tags, server room hardware, and inventory counts.

  4. Documents and tickets

    PDF417 and Data Matrix carry more structured fields, suitable for tickets, ID cards, gate passes, and batch information.

  5. Book publishing

    ISBN values ride on EAN-13 across distribution, inventory, and point-of-sale systems.

  6. Manufacturing traceability

    Data Matrix encodes part lots, process steps, and quality checks, common in electronics and automotive lines.

  7. Warehouse pick labels

    Locked parameters produce stable batches of location and item labels, improving pick speed and reducing mis-scans.

  8. Integration testing

    Quickly create sample codes across formats to validate scanners, PDAs, WMS, and POS handling during development.

See also

For longer URLs, contact details, or Wi-Fi credentials, reach for the QR Code Generator instead. When the content contains query parameters or non-ASCII characters, clean it up first with URL Encoder and Decoder and pair the workflow with Base64 Encoder and Decoder when text moves between API fields, embeds, or encoded content.

Best practices

Treat these as a pre-release checklist for scanner reliability and print stability.

  • Prefer SVG for print so bars stay sharp at any size
  • Dark bars on a light background is the safe default. Avoid low contrast or gradients over the bars
  • Never set the quiet zone to zero. Insufficient white space is a leading cause of scan failure
  • Enter EAN, UPC, and ITF-14 at their standard length. Manual padding tends to break the check digit
  • Lock scale, height, and quiet zone for each label batch to keep scan rates consistent
  • For long or structured content, choose PDF417 or Data Matrix rather than packing a dense 1D code
  • Use transparent backgrounds only when the final surface is clean. Otherwise stay on white
  • Verify with at least a phone camera and a handheld scanner before any production run

Limitations

Knowing these limits helps avoid output that looks generated but is not operationally usable.

  • Scanner implementations vary across devices and systems, so the target environment must be tested
  • A syntactically valid barcode is not the same as a business-compliant one for retail and logistics
  • Manual edits, duplicate codes, or padding can break check digits and cause downstream rejection
  • Even a valid symbology can fail on low contrast, reflective material, lamination, or heavy scaling
  • Very small print sizes can look jagged in PNG. Prefer SVG and avoid further compression
  • 1D and 2D codes optimize for different goals such as density, error correction, and label size. Tune them separately
  • Stuffing very long content into a 1D format hurts scan speed and reliability. Use 2D instead
  • A barcode is not encryption. Mask or hash sensitive values before encoding them

FAQ

Answers to the questions teams ask most often about format choice, validation, printing, and scanner behavior.

Why does my barcode fail to scan?

The usual suspects are wrong format, invalid check digit, low contrast, or insufficient quiet zone. Check them in that order.

Should I export PNG or SVG?

PNG is fine for web and admin displays. Prefer SVG for print and design files so the bars stay sharp.

Is my data uploaded anywhere?

No. Barcode generation runs entirely in your browser.

Why does numeric EAN or UPC input still fail?

These formats require both the correct length and a valid check digit, not just numeric content.

Why must Interleaved 2 of 5 use an even number of digits?

It encodes digits in pairs. An odd-length input leaves the last digit without a partner and cannot be represented.

Does a transparent background hurt scanning?

Transparency itself is fine, but the final surface behind the code must still provide enough contrast.

Should I show the human-readable text under the bars?

Show it when manual entry or visual verification is possible. Hide it only when space is tight and scanning is fully automated.

Preview looks fine, but printed labels fail. Why?

Check printer resolution, material reflectivity, scale distortion, and quiet zone width. Re-exporting from SVG often helps.

How do teams keep barcode output consistent?

Lock the format and parameters, share the same scene preset, and agree on a file naming rule.

How do I choose between Code128 and Code39?

Code128 is the default for modern systems thanks to higher density and broader character support. Use Code39 for legacy compatibility.

Why should I test with more than one scanner?

Different scanners handle glare, low contrast, angle, and distance differently. A single passing device is not enough for production.

How do QR, PDF417, and Data Matrix compare?

All are 2D codes but differ in density and where they are common. Data Matrix suits small labels, PDF417 fits documents and tickets, QR is the general-purpose choice.

Can I use generated barcodes directly in production?

Run a small pilot first to confirm the print chain, material, and scanners agree before scaling up.

Related tools

Barcodes fit identifiers, products, cartons, and labels. For links, long text, URL parameters, or embedded encoded content, other encoding tools may be a better match.