CSS Specificity Calculator
Score a selector and find out which of two rules actually wins.
Compute a CRC-32 checksum in hex, decimal and signed form.
The CRC32 Calculator computes the IEEE 802.3 checksum — the one zip, gzip and PNG use — and reports it as hexadecimal, unsigned decimal and the signed 32-bit integer that languages without an unsigned type produce.
CRC-32 is an error-detecting code, not a hash. It uses the IEEE 802.3 polynomial and produces a 32-bit value — the same one zip archives, gzip streams and PNG chunks carry to prove their contents arrived intact.
The result is shown three ways because different systems report it differently: hexadecimal, unsigned decimal, and the signed 32-bit integer that languages with no unsigned type produce. That last one is why a checksum can look negative in Java or older PHP while a command-line tool reports a large positive number — they are the same 32 bits read differently, which this makes obvious rather than mysterious.
Hexadecimal, unsigned decimal and signed 32-bit, which is why the same checksum can look negative in Java and positive on the command line.
Uses 0xEDB88320, the IEEE 802.3 variant, which is what zip, gzip, PNG and Ethernet mean by CRC-32.
Paste an expected value in any of the three forms and the tool tells you whether it matches.
CRC-32 catches accidental corruption and nothing else — a deliberate collision is trivial, and the page says so.
A table-driven implementation, so even a long document is checksummed as you type.
The checksum updates as you type.
Hexadecimal, unsigned decimal and signed 32-bit, so it matches whatever you are comparing against.
Paste an expected checksum and the tool tells you whether it matches, in any of the three forms.
Click any of the three representations to copy it.
Not a cryptographic one. It detects accidental corruption very well and is extremely fast, but it is trivial to construct a different input with the same checksum, so it proves nothing about intent.
Because the language has no unsigned 32-bit type and read the top bit as a sign. It is the same value — add 4,294,967,296 to a negative result to get the unsigned form.
The IEEE 802.3 one with polynomial 0xEDB88320, which is what zip, gzip, PNG and Ethernet use. CRC-32C, used by iSCSI and some databases, is a different polynomial and gives different values.
For accidental corruption, yes — that is exactly its job. For confirming nobody altered the file deliberately, use SHA-256.
What people who use the CRC32 Calculator think of it. Reviews come from visitors and are posted as written.
No ratings yet
Yours would be the first.
0 reviews
Newest first
No reviews yet
Be the first to rate the CRC32 Calculator. It takes half a minute and no account.
Write the first reviewScore a selector and find out which of two rules actually wins.
Generate cryptographically random strings over any alphabet you choose.
Convert file permissions between octal, symbolic and checkboxes.
Generate Luhn-valid test card numbers that no processor will ever charge.
Rebuild nested JSON from flat dot-notation or bracket-notation keys.
Convert tab-separated data — or a spreadsheet paste — straight into JSON.
Inspect any character: code point, block, category, UTF-8 bytes and escapes.
Produce SHA-1, SHA-256, SHA-384 and SHA-512 digests of any text.