Metal Card RFID Technology Types

RFID UID Converter & Wiegand 26-bit Calculator

This free tool converts an RFID card UID between hexadecimal and decimal, reverses the byte order, and decodes Wiegand 26-bit data into facility code and card number, entirely in the browser, with nothing uploaded. It resolves the question behind most failed enrollments: the credential and the platform describe the same identifier differently.

Access teams whose imported card numbers do not match what the door controller logsIntegrators converting UID exports between hexadecimal and decimal representationsPrograms planning replacement credentials that must match a Wiegand 26-bit format
RFID UID Converter & Wiegand 26-bit Calculator
(00) — Interactive tool

UID converter

Paste a card UID as hexadecimal or decimal. Separators and prefixes are accepted.

Normalized hexadecimal
04 A1 B2 C3 D4 E5 F6
Reversed byte order
F6 E5 D4 C3 B2 A1 04
Decimal value
1303689068602870

Byte map

B0 04B1 A1B2 B2B3 C3B4 D4B5 E5B6 F6

Wiegand 26-bit calculator

Build a 26-bit value out of facility code and card number, or decode a raw value.

Binary (26-bit)
00001001010011101000110011
Hexadecimal
0x0253A33
Decimal
2439731
Facility code
18
Card number
40217
Parity
Parity valid

Need cards in this format?

Request a sample or quote

Runs locally in this browser. Identifiers are not uploaded or stored.

(03) — Metal Card RFID Technology Types

Why the same credential shows two different numbers.

Many access panels log the UID least-significant byte first, while the personalization file lists it most-significant byte first, so the identical chip appears as two different values. Other platforms store the decimal form of the hexadecimal identifier, or trim leading zeros. The converter shows every representation at 4, 7 or 10 bytes, so the mismatch is identified in seconds instead of being debugged at the door.

(04) — Metal Card RFID Technology Types

Wiegand 26-bit: facility code and card number, checked by parity.

The classic 26-bit format carries an 8-bit facility code, a 16-bit card number and 2 parity bits. The calculator builds the full binary and hexadecimal value out of a facility code and card number, or decodes a raw value back into its components and verifies both parity bits. This is useful when enrolling replacement credentials into a 125 kHz system.

(05) — Metal Card RFID Technology Types

Check the data before cards are produced.

A metal credential is engineered around the exact chip and encoding the installed system expects. Confirming identifier length, byte order and format on real examples first, then approving an encoded metal card on the actual door controller, prevents the most expensive failure: a finished batch the platform cannot enroll.

(06) — Applications

Best uses for UID converter.

The practical route is selected from the system, audience, and handling context before the final metal finish and mark treatment are approved.

Best for

  • Access teams whose imported card numbers do not match what the door controller logs
  • Integrators converting UID exports between hexadecimal and decimal representations
  • Programs planning replacement credentials that must match a Wiegand 26-bit format

Quote details

  • Target reader, lock, phone, scanner, or platform
  • Metal finish, quantity, and packaging need
  • Artwork files, data file, and encoding requirements
  • Sample approval and delivery deadline
(07) — Specification

Production details to confirm before sample or batch.

Metal card production should confirm body construction, finish, chip route, data handling, marking layers, and approval samples in one brief.

Tool functions UID hex to decimal, byte-order reversal, byte map, Wiegand 26-bit encode and decode
Identifier lengths 4-byte, 7-byte and 10-byte UIDs
Wiegand format 26-bit: 8-bit facility code, 16-bit card number, 2 parity bits
Frequencies covered 125 kHz LF formats and 13.56 MHz HF identifiers
Privacy Runs in the browser; identifiers are not uploaded or stored
Next step Test an encoded metal card on the installed system before a batch is approved
(FAQ) — Common questions

Questions buyers ask about UID converter.

01Why is the card number in my access system different from the printed UID?

Panels and platforms disagree on representation: one logs hexadecimal, another the decimal form, and many controllers reverse the byte order. Convert the printed UID with this tool and compare each representation against the platform log to see which transformation the installed chain applies.

02How do I calculate a Wiegand 26-bit value out of a facility code and card number?

Enter the facility code and the card number; the calculator places the 8-bit facility code and 16-bit card number into the 24 data bits and computes both parity bits, producing the binary and hexadecimal value the controller expects.

03Which UID lengths does the converter support?

Identifiers of 4, 7 and 10 bytes, entered as hexadecimal or decimal, with spaces, colons or hyphens accepted. The output shows the normalized value, the reversed byte order, the decimal form and each byte separately.

04Is credential data uploaded when I use these tools?

No. Conversion and decoding run locally in the browser; identifiers are never transmitted or stored. For a full batch, the encoded metal card tested on the installed system remains the decisive check.

(10) — Quote UID converter

Send quantity, chip, material, print and encoding requirements.

Engineered antenna pathFerrite or hybrid RF structureLaser and deep engravingBrushed, plated, coated finishesUID, NDEF, and access encodingSample kits and production approval