OpenAPI Validator
Check a local Swagger 2.0, OpenAPI 3.0 or OpenAPI 3.1 document for schema errors and broken internal references. Read the reported paths without querying your API.
Open toolDraft proto3 messages from a JSON sample. Review inferred scalar types, nested messages and numbered fields before adopting the schema in a protocol.
Enter the inputs, then select Generate Protobuf.
Result will appear here
Infer scalar, array and nested object fields with a bounded structural mapper and render proto3 messages.
Processing uses bundled libraries in this browser. The download contains the generated source or document, rather than a link to a conversion service.
Start with the supported input, then check the generated result.
Use JSON sample, Root type name. The form starts with an example you can replace.
Review a proto3 message schema inferred from JSON. Download the generated file and check it in the application where you plan to use it.
These workflows use the formats and behavior supported by this implementation.
Use a representative JSON object to sketch a new proto3 message. Mixed field types and empty or null-only examples cannot establish a usable type.

Objects become messages and arrays become repeated fields. Review inferred numbers and normalized names before integrating the schema.

Field numbers are assigned from the sample order. Once a protocol is in use, maintain stable numbers and review every subsequent schema change.

Keep the output format and conversion policy in view.
A proto3 message schema inferred from JSON. Infer scalar, array and nested object fields with a bounded structural mapper and render proto3 messages.
Compare the result with the original before replacing a source file. Conversion limits are listed below.

Check these conditions before relying on the result.
Mixed-type fields, null-only fields and nested arrays are rejected. Sample-derived field numbers are not a migration policy. Review integer ranges, optional values and stable numbering before using a schema in an existing protocol. No compiler is run.
Input and results are not stored after leaving or reloading. Keep the original and download any output you need.

Check a local Swagger 2.0, OpenAPI 3.0 or OpenAPI 3.1 document for schema errors and broken internal references. Read the reported paths without querying your API.
Open toolGenerate plain Java model classes from a JSON object or object array. Download a ZIP with separate class files, then review inferred types and add your serializer mapping.
Open toolConvert a supported WOFF font to a TrueType container while keeping its table content. Use a font you have permission to convert and review the downloaded TTF.
Open toolChoose another tool for your next calculation, conversion, or text task.
Inspect quoted CSV cells in a readable table without uploading your data.
Open toolCheck CSV quoting and consistent column counts, then review the record count and selected delimiter.
Open toolCompare two JSON values by structure. See changed paths without treating object key order as a difference.
Open toolValidate JSON against a draft-07 or 2020-12 schema. Review error paths without sending the documents to a server.
Open toolGenerate the supported output, review it, and save a copy for your next step.
Answers about using JSON to Protobuf Converter and understanding its results.
It produces a proto3 message schema inferred from JSON. Mixed-type fields, null-only fields and nested arrays are rejected. Sample-derived field numbers are not a migration policy. Review integer ranges, optional values and stable numbering before using a schema in an existing protocol. No compiler is run.
Processing runs in this browser with local bundled libraries. No input is sent to a conversion server. Download your result before leaving the page.