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
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.
Paste a card UID as hexadecimal or decimal. Separators and prefixes are accepted.
04 A1 B2 C3 D4 E5 F6F6 E5 D4 C3 B2 A1 041303689068602870Byte map
Build a 26-bit value out of facility code and card number, or decode a raw value.
000010010100111010001100110x0253A3324397311840217Parity validRuns locally in this browser. Identifiers are not uploaded or stored.
Use this board to read the essentials at a glance: metal finish, marking contrast, edge quality, reader fit, and presentation style.
A brushed stainless route for phone-readable NFC, NDEF URLs, profiles, menus, loyalty, and public tap experiences.
A warm premium finish can still support a reader-tested phone-tap route when the RF stack is approved first.
For standard HF, high-security AES HF, and access builds, validate a finished card on the real reader before batch approval.
A copper finish direction that preserves the same reader-first approach: shield, antenna, chip, and final surface are tested together.
Use a purpose-built test bench for 125 kHz compatibility, legacy reader behavior, and final encoded-card validation.
Long-range UHF work needs range, orientation, reader power, nearby materials, and final metal body testing.
The front face, ferrite layer, antenna, chip, core, and rear face are a single engineered construction, not separate finish choices.
Use this to judge how the wood body, tap area, chip route, and reader test fit together.
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.
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.
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.
The practical route is selected from the system, audience, and handling context before the final metal finish and mark treatment are approved.
Metal card production should confirm body construction, finish, chip route, data handling, marking layers, and approval samples in one brief.
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.
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.
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.
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.