# CAN Bus Packet Decoder

> Decode CAN bus frames, identifiers and payload bytes.

- Page: https://decoder.tools/can-bus-decoder
- Category: Hardware, Radio & Telecom
- Status: live, runs in the browser
- Last reviewed: 2026-10-23

A CAN bus decoder parses a Controller Area Network frame into its arbitration identifier, control field and data bytes, revealing which node sent the message and at what priority it contended for the bus.

## Example

```text Input
can0 7E8#04410C1AF8000000
can0 7E8#03410D3C
can0 0CF00400#F87D7D401F00FF7D
```

```text Output
ID 0x7E8 (11-bit standard), DLC 8
  Data: 04 41 0C 1A F8 00 00 00
  OBD-II response, mode 01 PID 0x0c: Engine RPM = 1726 rpm
ID 0x7E8 (11-bit standard), DLC 4
  Data: 03 41 0D 3C
  OBD-II response, mode 01 PID 0x0d: Vehicle speed = 60 km/h
ID 0x0CF00400 (29-bit extended), DLC 8
  Data: F8 7D 7D 40 1F 00 FF 7D
  J1939: priority 3, PGN 61444 (0xF004) EEC1 Electronic Engine Controller 1, source 0x00
Frames: 3
```

## What is the CAN Bus Packet Decoder?

CAN is a broadcast, message-oriented bus: frames carry an identifier describing the content, not an address describing a recipient. Every node hears every frame and decides for itself what to act on. Arbitration is bitwise and non-destructive — a lower numeric identifier wins the bus, and the loser simply retries, so the highest-priority message is never delayed by a collision.

A standard frame has an 11-bit identifier (2 048 values), an extended frame 29 bits. The data length code gives 0 to 8 payload bytes for classic CAN; CAN FD raises that to 64 and allows a faster data phase. What those bytes mean is entirely manufacturer-defined and normally documented in a DBC file — without one, decoding payload semantics is reverse engineering.

This is also why automotive security research starts here: CAN has no authentication, so any node with bus access can inject a valid-looking frame.

## How to use the CAN Bus Packet Decoder

1. Paste the frame, typically as an identifier plus the data bytes in hex.
2. Read the decoded identifier, frame format and data length.
3. Interpret the payload against the vehicle's DBC file if you have one.

## When to use it

- Reverse-engineering an unknown message on a vehicle bus.
- Debugging an embedded CAN node that isn't being heard.
- Learning the CAN frame layout for an automotive or industrial project.

## CAN Bus Packet Decoder at a glance

| | |
|---|---|
| Identifier | 11-bit standard or 29-bit extended |
| Payload | 0–8 bytes classic CAN · up to 64 with CAN FD |
| Arbitration | Lower identifier wins, non-destructively |
| Security | No authentication — any node can inject frames |

## FAQ

### What does the CAN identifier mean?

It labels the message content and sets its priority — it is not a device address. Lower identifiers win arbitration, so safety-critical messages are assigned low IDs.

### How do I know what the data bytes mean?

You need the manufacturer's DBC (database) file mapping signals to bit positions and scaling. Without it, meaning has to be inferred by correlating frames with observed vehicle behaviour.

### What is CAN FD?

CAN with Flexible Data-rate: up to 64 payload bytes and a faster bit rate during the data phase, while keeping the same arbitration scheme. It is standard on newer vehicles.
