W3C Trace Context

traceparent

The traceparent header is the standard way to propagate a distributed trace across services. It encodes a version, trace-id, parent-id, and trace-flags in a compact format that works across vendors and instrumentation.

What to look for

trace-id is 16 bytes (32 hex characters) and uniquely identifies the trace.
parent-id is 8 bytes (16 hex characters) and identifies the incoming span.
trace-flags communicates sampling decisions (01 = sampled, 00 = not sampled).

Minimal traceparent header

Version 00 with a 16-byte trace-id, 8-byte parent-id, and sampled flag.

traceparent: 00-4bf92f3577b34da6a3ce929d0e0e4736-00f067aa0ba902b7-01

traceparent + tracestate

tracestate carries vendor-specific data alongside traceparent.

traceparent: 00-4bf92f3577b34da6a3ce929d0e0e4736-00f067aa0ba902b7-01
tracestate: acme=vendor1,rojo=00f067aa0ba902b7

Privacy note

All parsing and conversion runs locally in your browser. Nothing is sent to a server.

Spec references: W3C Trace Context (traceparent, tracestate).

Decode a traceparent header

Paste trace headers

Supports W3C traceparent, B3 (single/multi), Jaeger uber-trace-id, and Datadog headers.

Normalize hex to lowercase

Detected format: Unknown / unsupported formatPaste headers to detect the trace format.

Decoded locally in your browser. No data leaves your machine.

Spec-accurate parsing with explicit validation for flags, sampling, and ID lengths.