Calculate CRC32 Hash

What the CRC-32 tool does

This calculates the CRC-32 of your text, an 8-character hex value. Type or paste your text, press Generate Hash, and copy or download the result. It is often called a hash, but a CRC is really a different kind of thing from MD5 or SHA-256, a checksum, and understanding that difference is the most useful thing on this page.

It runs in your browser, so nothing you enter is uploaded.

How to use it

1. Enter your text. Type or paste it, or upload a plain text file.
2. Press Generate Hash. The 8-character CRC-32 value appears, ready to Copy or Download.

What a CRC actually is

CRC stands for Cyclic Redundancy Check, and its one job is to catch accidental errors. The idea is neat: your data is treated as one enormous number, divided by a fixed, agreed-upon number, and the remainder of that division is the CRC. Send the data along with its CRC, and the receiver can divide again and check that the remainder still matches. If even a single bit got flipped in transit, or a byte dropped, or a run of bits scrambled, the remainder almost certainly comes out different, and the error is caught. It is fast, it is simple, and it is brilliant at spotting the kind of random corruption that creeps into data moving across a wire or sitting on a disk.

It is not for security, and that matters

Here is the line that has to be drawn clearly. A CRC is not a cryptographic hash, and it is not built to stop anyone tampering with data on purpose. It is designed against accident, not against an attacker, and the two are worlds apart. Because a CRC is simple and predictable, it is trivially easy for someone to change your data and then tweak it further so the CRC comes out to whatever they want, leaving the check passing on data they altered. So a CRC can tell you "this probably was not corrupted by chance," but it can never tell you "this was not changed by someone." For that second question, you need a real cryptographic hash like SHA-256, which is built to resist exactly that kind of deliberate tampering. Use a CRC to catch glitches, and a cryptographic hash when security is the point.

You have used CRC-32 a thousand times

CRC-32, the 32-bit version that gives an 8-character result, is woven invisibly through everyday computing. Every Ethernet frame your network card sends and receives carries a CRC-32 on the end to catch transmission errors. Every file inside a ZIP archive has a CRC-32 stored with it, which is why, when an unzip program says an archive is corrupt and refuses to extract it, what really happened is a CRC-32 that did not match. The same check guards the data in PNG images and gzip files. The version used in all of these is one specific, standard CRC-32, so the value this tool produces lines up with that long-established standard rather than being one of many competing flavours, which is a real convenience.

The library doing the work

The calculation is handled by js-crc, a small JavaScript library for CRC values. Your text is read as bytes and run through the standard CRC-32 in your browser, with the 8-character hex result handed back.

Questions people ask

Is a CRC the same as a hash like MD5 or SHA-256?

Not in the way that matters. A CRC is a checksum built to catch accidental errors. It is not cryptographic and cannot resist deliberate tampering, which is what hashes like SHA-256 are designed for.

Can I use CRC-32 to verify a file has not been tampered with?

No. A CRC is easy to forge on purpose, so it cannot prove nobody changed the data. Use it for accidental corruption, and a cryptographic hash like SHA-256 when security matters.

Is this the same CRC-32 that ZIP files use?

Yes. ZIP archives, PNG images, gzip, and Ethernet all use the same standard CRC-32 that this tool produces.

Can I get my text back from a CRC-32?

No. A CRC is a short check value, and countless different inputs share the same one, so the original cannot be recovered from it.

References

1. Deutsch, P. (1996). RFC 1952: GZIP file format specification version 4.3 (which uses CRC-32 for integrity). Internet Engineering Task Force (IETF). https://www.rfc-editor.org/rfc/rfc1952
2. js-crc, a CRC implementation for JavaScript (npm package). https://www.npmjs.com/package/js-crc