ToolNestHow to Convert Hexadecimal to Decimal Manually
Multiply each hex digit by 16 raised to its position power (counting from 0 on the right), then add the results. For 2F: (2 × 16) + (15 × 1) = 47, since F stands for 15. ToolNest's free number base converter checks your hand calculation instantly.
The 3-step method, worked twice
Hexadecimal is base 16: digits 0–9 plus A–F standing for 10–15. To convert by hand, work right to left. Step 1: number the positions from the right starting at 0. Step 2: multiply each digit's value by 16 raised to its position power. Step 3: add everything up. Example 1 — convert 2F. Positions: F is position 0, 2 is position 1. F = 15, so (2 × 16¹) + (15 × 16⁰) = 32 + 15 = 47. Example 2 — convert 1A3. Positions from the right: 3 at 0, A at 1, 1 at 2. (1 × 16²) + (10 × 16¹) + (3 × 16⁰) = 256 + 160 + 3 = 419. That's the whole method — positional notation, the same idea as decimal, with 16 as the base instead of 10. Once you've done two or three by hand, verify with a base converter until the pattern is automatic.
Hexadecimal to decimal conversion table
Keep this reference until the digit values are muscle memory. Digit values: 0=0, 1=1, 2=2, 3=3, 4=4, 5=5, 6=6, 7=7, 8=8, 9=9, A=10, B=11, C=12, D=13, E=14, F=15. Powers of 16 (the position multipliers): 16⁰=1, 16¹=16, 16²=256, 16³=4,096, 16⁴=65,536, 16⁵=1,048,576. Common conversions worth memorizing: FF = 255 (the max of one byte), 100 (hex) = 256, 1000 (hex) = 4,096, FFFF = 65,535 (max of two bytes). Notice the pattern: each extra hex digit multiplies the range by 16, which is why programmers love hex — one digit always equals exactly 4 bits (a nibble), so a byte is always two hex digits. That clean mapping is also why UUIDs are written in hex: 32 hex digits encode 128 bits with zero ambiguity.
Why is hex used in computing?
Three reasons, all practical. Compactness: binary is precise but unreadable — the byte 11111111 is 'FF' in hex, two characters instead of eight. Every hex digit packs exactly 4 bits, so conversion between binary and hex is mechanical: group bits in fours, read off the digits. Memory addresses and debugging: addresses like 0x7FFF5FBFF8A0 are hex because the underlying values are bit patterns, and hex shows the bit structure that decimal hides. Colors: web colors are three bytes — red, green, blue — written as six hex digits: #FF5733 means red=FF (255), green=57 (87), blue=33 (51). Our hex-to-RGB guide walks through reading color codes. The 0x prefix you'll see in code (0xFF) is just a label meaning 'what follows is hexadecimal' — strip it before converting. Hex isn't a separate kind of number; it's the same values written in a base that matches how computers actually store them.
The reverse: decimal to hexadecimal
Going backward uses division instead of multiplication. Step 1: divide the decimal number by 16, note the remainder. Step 2: divide the quotient by 16 again, note the remainder. Step 3: repeat until the quotient is 0, then read the remainders bottom-to-top as hex digits (10–15 become A–F). Example — convert 47 to hex. 47 ÷ 16 = 2 remainder 15. 2 ÷ 16 = 0 remainder 2. Read bottom-to-top: 2, then 15 = F → 2F. Check against the earlier example: 2F was 47. Round trip confirmed. Example 2 — convert 419: 419 ÷ 16 = 26 r 3; 26 ÷ 16 = 1 r 10 (A); 1 ÷ 16 = 0 r 1 → read up: 1A3. Matches again. The division method is also how you sanity-check a hex-to-decimal conversion: convert your answer back and confirm you land where you started.
Five mistakes beginners make
1. Reading hex digits as decimal: in 1A3, the 'A' is ten, not one — treating letters as their lookalike digits is the #1 error. 2. Forgetting position powers: in 2F, the 2 means two sixteens, not two — every digit's value depends on its position. 3. Counting positions from the left: powers start at 0 on the right; starting from the left scrambles every digit's weight. 4. Dropping the 0x prefix incorrectly: 0xFF means hex FF (= 255); '0x' is a label, not part of the number — but forgetting the label exists leads to converting the 'x' as a digit. 5. Case confusion: hex is case-insensitive (ff = FF = 255), but in some contexts a trailing 'h' (FFh) or leading '$' ($FF) marks hex instead — know your notation. When a hand calculation looks wrong, the culprit is almost always #1 or #2: recheck each letter's value (A=10…F=15) and each position's power of 16, or just run it through the converter to find which digit went astray.