Hash & checksum · CRC-32

CRC-32 checksum

Calculate CRC-32 for a file when a transfer log, archive tool, or compatibility test asks for that checksum. The useful question is whether the exact bytes agree with a known reference, not whether the file has a reassuring-looking hexadecimal value.

Ready◎ This file never leaves your device⌁ text/plain · */*
Processing locallyThis file never leaves your device

Working with several files? Add the files you need, then keep this tab open until processing finishes. Large batches use more device memory.

Drag and drop files here

Supported files: text/plain, */*

1Choose your file→2Set the result→3Convert and download

Local workflow

How it works

01

Choose your file

Pick a supported file from your device or drop it into the tool.

02

Set the result

Choose the output, quality, or size options that matter for this job.

03

Convert and download

Your browser processes the file locally and prepares a fresh download.

Tool-specific guide · Reviewed October 18, 2026

01

Distinguish a file from its archive entry

Selecting a ZIP computes the CRC of the complete ZIP file. It does not automatically reproduce the CRC recorded for one item inside that archive. Extract the intended entry locally if that entry is what your reference describes. The filename in the result helps document what you selected but is not included in the checksum input.

02

Use the standard check string

Create a nine-byte file containing 123456789 with no newline. The CRC-32 routine used here gives cbf43926. Then add a newline and run it again to see how an apparently minor text change changes the bytes being checked. This small experiment is useful when diagnosing cross-platform text transfers.

03

Read the reference's algorithm name

CRC variants can differ even when all are described casually as a 32-bit CRC. Compare the precise variant and the representation expected by the other program. Do not reverse byte pairs or drop leading zeroes simply to make values look similar. CRCs detect many accidental errors, but they are not cryptographic protection against deliberate modifications.

Help

Frequently asked questions

Will renaming the selected file change its CRC?+

Renaming alone leaves the file bytes unchanged, so the checksum stays the same. The generated result record will show the new name, which is separate from the hexadecimal checksum.