What is a Hamming code and what can it actually do?

A Hamming code is a single-error-correcting (SEC) block code: it adds a handful of parity bits to your data so a receiver can fix any one flipped bit on its own, with no retransmission. For example, encode the 4 data bits 1011 and you get the 7-bit codeword 0110011. If one bit arrives wrong, the decoder finds which one and flips it back. It cannot fix two errors in the same word unless you add SECDED.

Why do parity bits sit at positions 1, 2, 4, 8?

Those are the powers of two, and each one owns a different bit of the position number. Parity bit P1 checks every position whose index has the 1s bit set (1, 3, 5, 7…), P2 checks the 2s bit group (2, 3, 6, 7…), P4 the 4s group, and so on. Because each data position is covered by a unique combination of parity bits, the failing checks add up to the exact position of the error. This tool prints the coverage list for every parity bit.

How does the syndrome locate an error?

After receiving a code, you recompute each parity check. Each check that fails contributes its parity position to a running sum; that sum is the syndrome. A syndrome of 0 means every check passed and no single-bit error is present. A syndrome of 5 means position 5 is wrong, so flipping bit 5 corrects it. The number is literally the 1-based index of the bad bit, which is the whole elegance of Hamming's scheme.

What is the (7,4) Hamming code?

It is the smallest practical Hamming code: 4 data bits plus 3 parity bits make a 7-bit codeword, written (7,4). It corrects any single-bit error and is the textbook example. Feeding 1011 into this tool gives 0110011, with parity bits at positions 1, 2 and 4. The next common sizes are (15,11) and (31,26), all built by the same rule of adding r parity bits where 2^r is at least m + r + 1.

What does SECDED add over a plain Hamming code?

SECDED means single-error-correct, double-error-detect. It prepends one overall parity bit covering the whole codeword. With both the syndrome and that extra bit you can tell three cases apart: no error, one error (corrected), and two errors (detected but not correctable). Without SECDED, a double error would either look clean or get miscorrected into a third wrong bit. Memory ECC in servers uses exactly this idea, which is why a stray double-bit flip is logged instead of corrupting data.

How do I correct an error by hand with this tool?

Paste the received code into decode mode. Read the syndrome: 0 means clean, any other number is the 1-based position to flip. The tool flips it for you and shows the corrected codeword plus the extracted data. To see why, check the coverage panel: the failing parity checks are exactly the ones whose positions sum to the syndrome. Walk those rows and you will see the bad position is the only one covered by that precise set of checks.

Check your computer-networks homework

A course problem hands you 4 data bits and asks for the (7,4) Hamming codeword, or gives you a received code and asks where the error is. Type the bits, read the codeword or the syndrome, and the coverage panel shows exactly which parity bit checks which positions so you can reproduce the steps in your write-up instead of copying a number you cannot defend.

Build and verify an FEC encoder in firmware

You are writing a Hamming encoder for a low-bandwidth radio link and need a reference oracle. Encode the same test vectors here, compare bit for bit, then flip a bit in your captured frames and confirm your decoder lands on the same error position this tool reports. It turns an off-by-one parity placement bug from a guessing game into a diff.

Explain ECC memory to a teammate

Someone asks why server RAM can shrug off a cosmic-ray bit flip. Turn on SECDED, flip one bit to show it gets corrected, then flip two to show the double-error is detected and refused rather than miscorrected. The live status line makes the single-correct / double-detect promise concrete instead of a slide bullet.

Prep a lecture or tutorial on error-correcting codes

Building slides on Hamming codes? Generate clean worked examples with the bit layout and per-parity coverage already laid out, screenshot them, and hand students a shareable link with the exact bits so they can poke at encode and decode themselves between classes.

Hamming Code Calculator — Encoder, Decoder + Error Correction

Encode, decode and error-correct Hamming (SEC / SECDED) codes — syndrome, parity coverage, one-click copy — browser-only

Runs locally
Category Developer & DevOps
Best for Formatting, validating, shrinking, or inspecting code-adjacent text.

Mode

SECDED (add overall parity bit)Data bitsAny length of 0 and 1 — spaces ignored

Result

Hamming code0110011

Bit layout

Pos1234567

Bit0110011

RolePPDPDDD

Coverage

P1covers positions: 1, 3, 5, 7

P2covers positions: 2, 3, 6, 7

P4covers positions: 4, 5, 6, 7

Hamming code lets a receiver fix one flipped bit on its own. Everything runs in your browser.

What this tool does

Free Hamming code calculator that encodes binary data into a single-error-correcting Hamming code, then decodes a received codeword to locate and fix one flipped bit. Type any length of data bits; the tool inserts parity bits at the power-of-two positions (1, 2, 4, 8…), computes each one as even parity over the positions it covers, and shows the full codeword with a labeled bit layout. Switch to decode mode, paste a received code, and it computes the syndrome, points to the exact bit in error, flips it back, and extracts the original data. Turn on SECDED to add an overall parity bit so a double-bit error is detected instead of silently miscorrected. The classic (7,4) code, the (15,11) code and any width in between all work. Every parity position and its coverage list are spelled out so you can follow the math by hand. Runs entirely in your browser; share a link that reopens the exact bits. 100% client-side.

Tool details

Input: Form fields; The page exposes text boxes, numeric controls, file pickers, or structured inputs depending on the tool.
Output: Live result + Copy; The result area focuses on usable output, with copy, download, or preview actions when supported.
Privacy: Browser-side processing; The main tool logic does not call an external API, so inputs normally stay in the current tab.
Save / share: Shareable URL state; Key settings are encoded in the URL so another person can reopen the same setup.
Performance budget: Initial JS <= 10 KB; No WASM budget is declared, keeping the tool quick to open on mobile.
Best fit: Developer & DevOps · Developer; Category and role tags drive related tools, internal links, and quick fit checks.

How to use

1. Input

Paste or drop your content into the tool panel.
2. Process

Click the button. All processing is local in your browser.
3. Copy / Download

Copy the result or download to disk in one click.

How Hamming Code Calculator fits into your work

Use it in the small gaps between coding, reviewing, debugging, and shipping.

Developer jobs

Formatting, validating, shrinking, or inspecting code-adjacent text.
Preparing snippets for documentation, tickets, commits, or handoff.
Checking a small payload quickly without switching tools.

Developer checks

Run irreversible transforms like minify or obfuscate on a copy.
Keep secrets out of pasted snippets unless the tool explicitly stays local.
Use your normal tests or linter before shipping transformed code.

Good next steps

These links move the current task into a more complete workflow.

Real-world use cases

Check your computer-networks homework
A course problem hands you 4 data bits and asks for the (7,4) Hamming codeword, or gives you a received code and asks where the error is. Type the bits, read the codeword or the syndrome, and the coverage panel shows exactly which parity bit checks which positions so you can reproduce the steps in your write-up instead of copying a number you cannot defend.
Build and verify an FEC encoder in firmware
You are writing a Hamming encoder for a low-bandwidth radio link and need a reference oracle. Encode the same test vectors here, compare bit for bit, then flip a bit in your captured frames and confirm your decoder lands on the same error position this tool reports. It turns an off-by-one parity placement bug from a guessing game into a diff.
Explain ECC memory to a teammate
Someone asks why server RAM can shrug off a cosmic-ray bit flip. Turn on SECDED, flip one bit to show it gets corrected, then flip two to show the double-error is detected and refused rather than miscorrected. The live status line makes the single-correct / double-detect promise concrete instead of a slide bullet.
Prep a lecture or tutorial on error-correcting codes
Building slides on Hamming codes? Generate clean worked examples with the bit layout and per-parity coverage already laid out, screenshot them, and hand students a shareable link with the exact bits so they can poke at encode and decode themselves between classes.

Common pitfalls

Counting bit positions from 0 or from the right. This tool numbers positions from 1 starting at the leftmost bit, which is the convention that puts parity at 1, 2, 4. If you index the other way the syndrome will point at the mirror position and look wrong.
Expecting a plain Hamming code to fix two errors. A single (7,4) or (15,11) code corrects exactly one flipped bit. Two flips in one word will be miscorrected into a third wrong bit. Turn on SECDED so a double error is at least detected.
Feeding the data bits and parity bits as one blob into encode mode. Encode takes only the raw data bits and computes the parity for you. If you paste a full codeword into the data field you double-encode it. Use decode mode for codewords that already carry parity.

Privacy

The whole pipeline — parity placement, the syndrome computation, the bit-flip correction and the data extraction — is plain JavaScript running in your browser tab. No bits you type are uploaded or logged anywhere. The one thing to know: the shareable link encodes your data or codeword in the query string, so a link pasted into chat records those bits in the recipient server's access log. For anything sensitive, use the copy button and paste the text rather than the URL.

FAQ

Tool combos

Folks in your role tend to reach for these alongside this tool.

Browse all tools for this role

Hamming Code Calculator — Encoder, Decoder + Error Correction

Result

What this tool does

Tool details

How to use

1. Input

2. Process

3. Copy / Download

How Hamming Code Calculator fits into your work

Developer jobs

Developer checks

Good next steps

Real-world use cases

Check your computer-networks homework

Build and verify an FEC encoder in firmware

Explain ECC memory to a teammate

Prep a lecture or tutorial on error-correcting codes

Common pitfalls

Privacy

FAQ

Unit Converter

Number Base Converter

Bitwise Calculator

CRC32 Checksum Calculator

Scientific Calculator

AI Eval Planner

API Key Generator

ASCII Table Generator

ASCII Table Reference

awk + sed Cheatsheet

AWS CLI Cheatsheet

Backup Codes Generator