JSON Schema VS Protocol Buffers
As of 30 October 2026, Protocol Buffers is named by 431 companies and JSON Schema by 127; JSON Schema skews to companies under 200 people (34% vs 46%), Protocol Buffers to companies over 1,000 (26% vs 35%).
As of 30 October 2026 · refreshed daily · counts move as websites, DNS and career sites are re-read.
The website-and-DNS footprint is not comparable between a marketing suite and a CRM: JSON Schema's script and mail records show on hundreds of thousands of small sites, Protocol Buffers rarely leaves a trace outside its own apps. Compare on the job-posting numbers; use the footprint for reach.
- JSON Schema: 2–200 employees
- 34%
- Protocol Buffers: 2–200 employees
- 46%
- JSON Schema: 1,000+ employees
- 35%
- Protocol Buffers: 1,000+ employees
- 26%
- Postings per company, 90 days
- 1.9 · 2.1
- Website or DNS footprint
- 0 · 0
Who chooses which
Share of each tool's companies in every segment. "Leans" marks a gap of more than two points.
| Segment | JSON Schema | share | Protocol Buffers | share | Leans |
|---|---|---|---|---|---|
| Self-employed | 5 | 4% | 6 | 1% | JSON Schema |
| 2-10 employees | 6 | 5% | 37 | 9% | Protocol Buffers |
| 11-50 employees | 19 | 15% | 61 | 14% | even |
| 51-200 employees | 18 | 14% | 99 | 23% | Protocol Buffers |
| 201-500 employees | 20 | 16% | 73 | 17% | even |
| 501-1000 employees | 15 | 12% | 41 | 10% | JSON Schema |
| 1001-5000 employees | 15 | 12% | 65 | 15% | Protocol Buffers |
| 5001-10000 employees | 8 | 6% | 13 | 3% | JSON Schema |
| 10,001+ employees | 21 | 17% | 36 | 8% | JSON Schema |
| Segment | JSON Schema | share | Protocol Buffers | share | Leans |
|---|---|---|---|---|---|
| Technology & software | 68 | 54% | 205 | 48% | JSON Schema |
| Business & finance services | 23 | 18% | 79 | 18% | even |
| Manufacturing & industry | 12 | 9% | 77 | 18% | Protocol Buffers |
| Public, community & associations | 5 | 4% | 6 | 1% | JSON Schema |
| Media & content | 5 | 4% | 18 | 4% | even |
| Health care | 3 | 2% | 3 | 1% | even |
| Utilities & infrastructure | 3 | 2% | 8 | 2% | even |
| Automotive | 2 | 2% | 4 | 1% | even |
| Consumer services & leisure | 2 | 2% | 6 | 1% | even |
| Transport, logistics & rental | 2 | 2% | 12 | 3% | even |
| Commerce & trade | 1 | 1% | 9 | 2% | even |
| Hospitality & travel | 1 | 1% | 2 | 0% | even |
| Segment | JSON Schema | share | Protocol Buffers | share | Leans |
|---|---|---|---|---|---|
| United States | 90 | 71% | 288 | 67% | JSON Schema |
| United Kingdom | 12 | 9% | 32 | 7% | JSON Schema |
| Australia | 4 | 3% | – | – | outside top 12 |
| Canada | 4 | 3% | 6 | 1% | even |
| Brazil | 3 | 2% | 4 | 1% | even |
| India | 2 | 2% | 7 | 2% | even |
| Mexico | 2 | 2% | – | – | outside top 12 |
| Singapore | 2 | 2% | – | – | outside top 12 |
| Austria | 1 | 1% | – | – | outside top 12 |
| Germany | 1 | 1% | 25 | 6% | Protocol Buffers |
| Denmark | 1 | 1% | – | – | outside top 12 |
| France | 1 | 1% | 9 | 2% | even |
| Japan | – | – | 5 | 1% | outside top 12 |
| Poland | – | – | 5 | 1% | outside top 12 |
| Sweden | – | – | 5 | 1% | outside top 12 |
| Switzerland | – | – | 4 | 1% | outside top 12 |
| Netherlands | – | – | 4 | 1% | outside top 12 |
| Segment | JSON Schema | share | Protocol Buffers | share | Leans |
|---|---|---|---|---|---|
| Software engineering | 129 | 42% | 940 | 75% | Protocol Buffers |
| Data & AI | 88 | 28% | 107 | 9% | JSON Schema |
| IT operations & business systems | 20 | 6% | 30 | 2% | JSON Schema |
| Legal, compliance & risk | 4 | 1% | – | – | outside top 12 |
| Engineering (non-software) | 3 | 1% | 34 | 3% | even |
| Product, program & project management | 3 | 1% | 5 | 0% | even |
| Design & UX | 2 | 1% | – | – | outside top 12 |
| Sales | 2 | 1% | 2 | 0% | even |
| Administration & office | 1 | 0% | – | – | outside top 12 |
| Arts media and entertainment | 1 | 0% | 1 | 0% | even |
| Marketing & communications | 1 | 0% | 4 | 0% | even |
| Real estate and property | 1 | 0% | – | – | outside top 12 |
| Customer service & success | – | – | 4 | 0% | outside top 12 |
| Finance & accounting | – | – | 2 | 0% | outside top 12 |
| Construction and civil | – | – | 1 | 0% | outside top 12 |
| Unclassified | – | – | 1 | 0% | outside top 12 |
The companies behind each column
Companies using JSON Schema →
Companies using Protocol Buffers →
api specs data formats ranked →
Quote the sentence with the date and the link. The numbers change daily; the link always shows the current ones.
Protocol Buffers is named by 431 companies in job postings and JSON Schema by 127; 25 name both. (Breaknorm, 30 October 2026, https://breaknorm.co/compare/json-schema-vs-protocol-buffers)
Read from the source, not self-reported
Every number on this page can be traced to a page we crawled or a posting we read. Full methodology →
- Job postingsRead hourly from career sites. A tool counts when the employer's own text names it as the team's system; both tools can count for one company.
- Website and DNSScripts and embeds on the company's pages, plus SPF, DKIM, MX and CNAME records of its domain that point at the vendor.
- SegmentsCountry, size and industry from the company profile built from its website.
- Not a reviewNo ratings, prices or feature claims. For those, read the vendors.
JSON Schema vs Protocol Buffers: questions
Which is more used, JSON Schema or Protocol Buffers?
By companies naming it in their own job postings, Protocol Buffers (431) over JSON Schema (127). By website-and-DNS footprint, Protocol Buffers (0 vs 0), because its scripts and mail records sit on many small company sites.
Who chooses JSON Schema?
34% of JSON Schema companies have 2 to 200 employees, against 46% for Protocol Buffers. 35% of JSON Schema companies have over 1,000 employees, against 26% for Protocol Buffers.
Do companies run both?
25 companies name both in their postings, usually JSON Schema in marketing and Protocol Buffers in sales, or during a migration.
Where do these numbers come from?
From the employer's own text in job postings read hourly from career sites, and from scripts found on company websites in our crawl. No vendor data, no surveys.
Get either list your way
The same data as a search, over MCP and the API, as bulk files, or pushed to you as it changes.
Every company on either tool,
with the person who owns it
Filter on JSON Schema or Protocol Buffers. Start free, no card.