What this tool gives you
Type your asset value and you get three things: the EPC (96- or 128-bit hex string), a copy-ready ZPL ^RFW command to send to an RFID printer, and a preview of the smart label itself: antenna, chip and a printed Code 128 of the value. Switch to Batch to encode a whole serial range at once and export every value, EPC and ZPL command to CSV, or download the raw ZPL file and send it straight to the printer.
SGTIN-96: the GS1 standard EPC
The default mode encodes a true SGTIN-96 EPC per the GS1 Tag Data Standard: your GS1 Company Prefix + indicator & item reference + serial are packed into the exact 96-bit structure (header, filter, partition table) that Gen2 UHF readers expect. You also get the GTIN-14 (with check digit) and the urn:epc:tag:sgtin-96: URI for your records. Batch mode serialises cleanly; every tag gets a unique EPC.
ASCII or hex?
Internal asset tracking can instead encode plain text (ASCII) (e.g. the asset tag FA-000123) or raw hexadecimal you already have. ASCII keeps the chip and the printed label in perfect agreement. A 96-bit tag holds up to 12 ASCII characters (24 hex); 128-bit holds more. Learn the fundamentals in our plain-English RFID encoding guide.
Will any RFID reader be able to read it?
Yes, provided the tag is encoded. Print your labels on RFID inlay stock through an RFID printer using the ZPL this tool generates: your EPC is written to the tag's memory openly (no locks or passwords) in the universal GS1 SGTIN-96 format. That means any UHF EPC Gen2 (RAIN) reader (Zebra, Impinj, Honeywell; handheld, fixed portal or drone, anywhere in the world) reads the same value and decodes it back to your company prefix, item reference and serial. No vendor lock-in, no proprietary format. And the printed Code 128 stays as the everyday fallback: any regular barcode scanner reads it too.
Two boundaries worth knowing: UHF is a different radio to NFC (phone-tap) and LF readers: those technologies cannot read a UHF tag (if you ever need phone readability, hybrid UHF+NFC inlays exist). And a paper printout alone carries no chip: encoding needs RFID label stock and an RFID printer such as the ZD621R or ZT411 RFID.
Why can't the browser write the chip?
Writing a tag needs radio hardware: an RFID printer such as the Zebra ZD621R or ZT411 RFID. A web page can't power a chip, so instead it prepares the exact EPC and ZPL for you. Find Asset's Label Studio then prints the label and encodes the chip in a single pass; see the RFID hardware guide for recommended printers and readers.
RFID vs barcode
RFID reads without line of sight and can scan hundreds of tags at once, ideal for fast audits and hands-free tracking. Barcodes and QR are cheaper and need no chip. Many teams use both. Compare in RFID vs barcode, or make printed codes with our barcode and QR generators.
Print & encode RFID in one pass
Find Asset's Label Studio designs the label, encodes the chip and tracks every tagged asset, with no separate software.
Start a free 14-day trialFAQ
Can a browser write an RFID tag? No. Encoding a chip needs an RFID printer. This tool gives you the EPC value and the ZPL command; Label Studio does the print-and-encode.
What is an EPC? The Electronic Product Code: the value stored in a UHF RFID chip's memory. It's the digital equivalent of the number printed on the label.
Is it free? Yes. Encode as many tags as you like, single or batch, and export the EPC/ZPL to CSV, no signup.