Protobuf support installs statistics
By peterj · VS Code Marketplace · Programming Languages
Protobuf support (.proto file syntax highlighting)
Protobuf support has 333,893 recorded installs on VS Code Marketplace.
It ranks #1078 of 2,500 tracked VS Code Marketplace listings by installs.
It is rated 3.0 out of 5 from 5 ratings.
PluginStats has 3 daily observations since Oct 16, 2026; the latest is from Oct 18, 2026.
Rating: 3.00 / 5 from 5 ratings
About Protobuf support
Protobuf support for Visual Studio Code
Functionality
This extensions adds syntax highlighting and bracket matching for .proto files (protobuf) in VS code. This extension is using this tmbundle: https://github.com/kevinweil/protobuf.tmbundle.
Installation
Launch Visual Studio code, press F1 and type ext install to bring up the list of extensions. Pick Protobuf support from the list to install the extension. Restart Visual Studio Code and you should be ready to go. Alternatively, you can copy the contents of the repo under ~/.vscode/extensions/vscode-protobuf.
Description from the VS Code Marketplace listing.
- proto
- Protocol Buffers
Where Protobuf support sits in the listing
Each band is one page of 20. Installs on a log scale. Placement is projected from installs, so it can differ from the marketplace's own sort order. Hover a dot to see the listing.
Charts
Images: 30d · 1y · all time · 1600×900 dark
Adoption over time
7/30/90-day growth
Ranking history
Filled points are observed values; hollow points come from Internet Archive snapshots of the listing page. Dashed segments span periods with no observations — values between points are not interpolated.
Recent observations
Full history (3)Similar VS Code Marketplace Programming Languages plugins
Data source
Install counts, average rating, and rating counts come from the public Visual Studio Marketplace gallery API. Installs are cumulative and exclude updates.
Listing: https://marketplace.visualstudio.com/items?itemName=peterj.proto. First seen Oct 16, 2026; last successful collection Oct 18, 2026. See the methodology.