# CRC-32 and Adler-32 checksum

Compute the CRC-32 and Adler-32 checksums of text or bytes, as decimal and hex.

- Endpoint: `POST https://setget.net/v1/tools/crc32` with JSON `{"input": {...}}`
- MCP: `run_tool` with `slug` = `crc32`
- Page: https://setget.net/tools/crc32

## Inputs

- `text` (required, string): The input to checksum.
- `input_encoding` (optional, string, one of `text`, `hex`, `base64`, default `"text"`): How the input is written: plain text (read as UTF-8), hex digits or base64.

## Example

```json
{"input":{"text":"123456789"}}
```

Result:

```json
{"crc32":{"decimal":3421780262,"hex":"cbf43926"},"adler32":{"decimal":152961502,"hex":"091e01de"},"bytes":9}
```

**Which CRC-32 is this?** The common one used by ZIP, gzip, PNG and Ethernet (polynomial 0x04C11DB7, reflected). It is not CRC-32C.

**Can I use a CRC for security?** No. Checksums catch accidental damage only. Anyone can craft different data with the same CRC. Use SHA-256 to detect tampering.
