How to Create Barcodes in Excel — Step-by-Step Guide

Method 1: Generate barcodes directly from your Excel workbook

This is the most direct option when the spreadsheet is already your source of truth. Keep the product name in one column and the value you want to encode in another. BarcodeBatch reads the workbook in the browser, detects the likely barcode and optional name columns, and asks you to choose EAN-13 or Code 128 before generation.

The source cells are not rewritten to make invalid data look valid. If a row does not satisfy the structural rules of the selected format, that row stays visible as a problem instead of being silently changed.

• Prepare an .xlsx workbook with one row per item.
• Use a clear heading such as Barcode Value; Product Name is optional.
• Open the Excel Barcode Generator and choose the workbook.
• Select EAN-13 for a 13-digit retail value or Code 128 for a flexible internal value.
• Generate once, review the result, then download the XLSX and PNG ZIP.
• Keep the original barcode values as text when leading zeros matter.

Method 2: Use a barcode font inside Excel

A barcode font can work for a small, controlled workflow, especially when a system already expects a specific font-based setup. A common Code 39 pattern is to wrap the value with start/stop characters and display the result using a compatible Code 39 font.

The important limitation is that changing a font does not turn arbitrary data into a valid retail identifier. Different barcode symbologies have different encoding rules, and some font workflows need encoder logic rather than a simple font change. Font availability, licensing and compatibility also become part of the workbook setup.

Important: Use font-based barcodes only when you understand the exact symbology and the font or encoder license. A font does not assign a GTIN and does not prove that a retail identifier belongs to your product.

Method 3: Use Excel’s IMAGE() function with hosted barcode images

Modern Excel versions include IMAGE(), which can place an image from an HTTPS source into a cell. That makes it possible to point a cell at a remotely rendered barcode image and keep the visual result inside a spreadsheet layout.

Microsoft documents that IMAGE() uses a source URL and that external-image access can be blocked by security settings. That makes the method useful for some connected workbooks, but it also means the image depends on an external source instead of being generated entirely from the workbook itself.

If privacy, repeatability or offline-style processing matters, a browser-side generator that embeds the finished PNG into the returned XLSX avoids a permanent dependency on a remote image URL.

Which barcode type should you use for Excel data?

The spreadsheet is only the data source. The barcode type should be chosen by the system that will scan the finished code. BarcodeBatch intentionally keeps the first Excel flow simple with EAN-13 and Code 128.

Protect barcode values before you generate

Spreadsheet formatting can damage identifiers before the barcode generator ever sees them. Leading zeros may disappear if a cell is treated as a number, and long numeric strings can be displayed in scientific notation. For identifiers where every digit matters, store the value as text and inspect the actual cell value rather than only the visual formatting.

Do not trim, pad or rewrite values just to make a barcode render. For a retail identifier, fix the source data or confirm the assigned number. For internal Code 128 data, preserve the exact characters your receiving system expects.

• Use text cells when leading zeros are significant.
• Keep one item per row and one barcode value per cell.
• Avoid merged cells in the value column.
• Use clear headers so automatic column detection is unambiguous.
• Scan-test a sample of the generated labels before a large print run.

What a useful Excel barcode workflow should give you

A finished bulk workflow should leave you with files you can actually use, not only bars displayed through a local font. For that reason BarcodeBatch produces an XLSX with embedded Barcode Image PNGs and a ZIP with one PNG per valid row. Product Name is optional, while Barcode Value is required.

The processing stays in the browser. The workbook is not uploaded to BarcodeBatch, and the current security limits are intentionally conservative: .xlsx only, up to 10 MiB input and up to 1,000 data rows per worksheet.