Check your .proto files against the Google Protocol Buffer style guide. Catch naming issues, structural problems, and style violations instantly.
Drag & drop a .proto file or paste content above
Files must declare syntax version
Package should be declared
Messages and enums use PascalCase
Field names use snake_case
Enum values use UPPER_SNAKE_CASE
First enum value should be UNSPECIFIED = 0
Public imports come first
Services and RPCs should have comments
Lines should not exceed 80 characters
Files should end with a newline
Integrate protolint into your CI/CD pipeline or tooling.
# JSON body
curl -X POST https://protolint.com/api/validate \
-H "Content-Type: application/json" \
-d '{"content": "syntax = \"proto3\";\npackage example;"}'
# File upload
curl -X POST https://protolint.com/api/validate \
-F "file=@path/to/your.proto"{
"valid": true,
"errors": [],
"warnings": [
{
"line": 5,
"column": 81,
"rule": "max-line-length",
"message": "Line exceeds 80 characters (92).",
"severity": "warning"
}
],
"info": []
}