# OTLP JSON validator

Paste an OTLP JSON payload to check it and see the spans, log records or metrics inside.

## How it works

OTLP JSON nests data under resources and scopes. Trace and span IDs are hex strings, and times are nanoseconds since 1970, written as strings.

## Questions

### Why hex IDs?

OTLP over JSON writes trace and span IDs as hex, not base64 as in protobuf JSON mappings.

### Is my payload sent anywhere?

No. It’s parsed in your browser only.

## Related tools

- [Traceparent parser & generator](https://powertraces.com/tools/traceparent)
- [OpenTelemetry setup generator](https://powertraces.com/tools/opentelemetry-setup)
- [Collector config builder](https://powertraces.com/tools/collector-config)
- [Semantic conventions lookup](https://powertraces.com/tools/semantic-conventions)

[All tools](https://powertraces.com/tools)