JSON to Protobuf Schema Generator

About This Tool

Convert JSON to Protocol Buffer schema definitions for gRPC systems. This tool runs entirely in your browser — no data is ever sent to a server. Free to use, no account required.

What Protocol Buffers (Protobuf) Are

Protobuf is Google's binary serialization format — faster and more compact than JSON, but requiring a schema to encode and decode data.

Protobuf Schema (.proto files)

A .proto file defines messages with named, typed, numbered fields. Each field has a type (string, int32, bool, bytes, or another message type) and a unique field number. The schema is compiled by protoc to generate serialization code in your language of choice.

Protobuf vs JSON

Protobuf is 3–10x smaller than equivalent JSON because field names are replaced by field numbers in the binary encoding, and data types are encoded more efficiently. Parse speed is also 5–10x faster, making Protobuf standard for high-performance internal microservice APIs.

Converting JSON to Protobuf Schema

The tool generates a .proto file from your JSON sample, mapping JSON types to appropriate Protobuf field types.

Field Type Mapping

JSON string → string, integer → int32 or int64, float → float or double, boolean → bool, nested object → message, array → repeated field. The tool chooses int32 vs int64 and float vs double based on the magnitude of values in your sample.

Field Numbers

Protobuf requires a unique integer field number per field, used in the binary encoding. The tool assigns numbers sequentially starting from 1. Field numbers 1–15 are most efficient and should be used for the most frequent fields.

JSON to Protobuf Conversion Guide

Protocol Buffers (Protobuf) is Google's binary serialization format — 3-10x smaller and 5-10x faster than JSON. It's the standard format for gRPC APIs and high-performance microservices.

JSON Input → Proto3 Definition

// JSON
{"userId": 1, "name": "Alice", "email": "alice@example.com", "active": true, "score": 98.5}

// Proto3 Definition
syntax = "proto3";

package example;

message User {
  int32  user_id = 1;
  string name    = 2;
  string email   = 3;
  bool   active  = 4;
  double score   = 5;
}

JSON vs Protobuf Size Comparison

JSON to Protobuf Type Mappings

JSON to Protobuf Type Mapping

Every JSON value type maps to one or more Protobuf scalar or composite types. Choosing the right type matters: using int32 for a Unix timestamp that exceeds 2,147,483,647 will silently truncate data. Always use int64 for epoch milliseconds, IDs, and any number that may grow large.

Generated .proto Example

Given the JSON input {"name":"Alice","age":30,"email":"alice@example.com","active":true}, the converter produces:

syntax = "proto3";
package example;

message User {
  string name   = 1;
  int32  age    = 2;
  string email  = 3;
  bool   active = 4;
}

Protobuf vs JSON: Performance Comparison

Protobuf is a binary encoding format designed for high-throughput, low-latency scenarios such as gRPC services, Kafka message queues, and mobile apps with limited bandwidth. JSON prioritizes human readability and universal tooling support. Use JSON for public APIs and configuration files; use Protobuf when performance or payload size is the bottleneck.