Skip to content

Formatters & Code

gRPC .proto ⇄ JSON Schema

Bridge protobuf and JSON Schema definitions.

Runs in your browser
.proto · source
lines: 9chars: 138size: 138 B
JSON Schema · result
lines: 25chars: 375size: 375 B
live

Redactionele opmerking

Understanding · Two schema languages — one for wire, one for validation.

Dit uitgebreide hoofdstuk is momenteel alleen in het Engels beschikbaar. De conversietool hierboven werkt in jouw taal; de lange uitleg is nog niet vertaald.

Veelgestelde vragen

Quick answers.

How are protobuf types mapped to JSON Schema?

The converter follows standard proto3 mapping conventions. For example, `string` and `bytes` become `string` types in JSON Schema, while numeric types like `int32` are mapped to `number` or `integer` with range constraints.

Is my API schema sent to a server?

No. The parsing and transformation logic is executed locally using JavaScript in your browser, keeping your protobuf definitions confidential.

Can I convert from JSON Schema back to .proto?

Yes, the tool is bidirectional. You can paste a JSON Schema to generate equivalent protobuf message definitions, though documentation tags and specific gRPC service options may require manual adjustment.

Does it support nested messages and enums?

Yes. The tool recursively processes nested messages, enums, and `oneof` fields into their corresponding `definitions` or `anyOf` representations in JSON Schema.

Mensen zoeken ook naar

Gerelateerde tools

More in this room.

Bekijk alles in Formatters & Code