No description
Find a file
Protobuf Team Bot 3645f08153 Automated Code Change
PiperOrigin-RevId: 868103806
2026-02-10 05:55:47 -08:00
.bazelci Drop Bazel 7 tests for bazel, python, partially java partially cpp. 2026-01-13 20:11:39 -08:00
.bcr Internal change 2026-02-04 13:39:14 -08:00
.github Update the path to prebuilt_tool_integrity.bzl after refactor. 2026-02-07 08:58:29 -08:00
bazel Internal change 2026-02-10 04:08:40 -08:00
benchmarks Removed the third_party/upb/upb/bazel directory. 2026-01-23 16:35:18 -08:00
build_defs Breaking change: remove deprecated flag for enabling MSVC support 2026-01-07 17:57:26 -08:00
ci Add metadata annotations for generated Python protobuf symbols. 2026-01-06 16:05:56 -08:00
cmake Auto-generate files after PR #25437 2026-01-29 04:25:27 +00:00
compatibility add refresh_gencode.sh script to Java smoke tests (#25671) 2026-02-03 19:06:19 -08:00
conformance Add conformance tests for parsing custom Any type URLs in text-protos. 2026-02-06 00:49:09 -08:00
csharp Auto-generate files after cl/864384082 2026-02-02 17:22:39 +00:00
docs Formatted all of our Markdown docs to standard formatting. 2026-01-20 21:46:12 -08:00
editions Automated Code Change 2026-02-10 01:55:09 -08:00
editors Update Vim syntax files to support edition keyword (which is weirdly already 2025-10-10 11:07:10 -07:00
examples Fix the prefer_prebuilt_protoc alias to use the correct originally announced location 2026-02-04 14:36:07 -08:00
go go_features: prepare Go-specific optimize_mode 2025-10-03 01:22:29 -07:00
hpb Removed the third_party/upb/upb/bazel directory. 2026-01-23 16:35:18 -08:00
hpb_generator Automated Code Change 2026-02-10 05:55:47 -08:00
java Automated Code Change 2026-02-10 01:55:09 -08:00
lua Removed the third_party/upb/upb/bazel directory. 2026-01-23 16:35:18 -08:00
objectivec Automated Code Change 2026-01-25 20:54:45 -08:00
patches Add java bazel 8 tests and make java builds compatible with bazel 8. 2025-04-07 09:32:55 -07:00
php Auto-generate files after PR #25363 2026-02-04 15:42:40 +00:00
pkg Breaking change: make generator headers private 2026-01-18 19:42:51 -08:00
python Protobuf Python UPB Free Threading support. 2026-02-03 09:04:20 -08:00
ruby Auto-generate files after PR #25363 2026-02-04 15:42:40 +00:00
rust Remove accidental map.rs change. 2026-02-09 16:31:39 -08:00
src Stop inlining ClassDataLite::type_name[] to make 2026-02-09 15:50:21 -08:00
third_party Internal changes 2026-01-29 10:19:36 -08:00
toolchain update min mac ver from 11 to 12 2025-12-16 10:18:38 -08:00
upb Fix an endian problem in upb that caused protoc plugins to crash on big endian platforms (#25363) 2026-02-04 07:32:29 -08:00
upb_generator Fix upb C generator to handle reserved name collisions. 2026-01-26 17:23:49 -08:00
.bazelignore Internal changes 2024-10-17 11:33:01 -07:00
.bazeliskrc Drop Bazel 7 tests for bazel, python, partially java partially cpp. 2026-01-13 20:11:39 -08:00
.bazelrc Delete repo_env=BAZEL_NO_APPLE_CPP_TOOLCHAIN=1 flag from .bazelrc since it is not needed and causing errors. 2025-02-21 11:08:17 -08:00
.clang-format Clean up a few stray files that ended up in the wrong place 2023-09-27 09:30:44 -07:00
.gitattributes feat: update bazel central registry publish workflow (#23465) 2025-10-09 09:55:13 -07:00
.gitignore Add a multi-platform Gemfile.lock (#19804) 2025-01-10 19:39:38 -08:00
.gitmodules Internal changes 2024-10-17 11:33:01 -07:00
.readthedocs.yml Automated rollback of commit 4dc164884c. 2024-06-10 16:32:18 -07:00
appveyor.bat CMake: Stop building tests by default (related to #20539) (#24373) 2025-11-13 12:30:47 -08:00
appveyor.yml Upgrade to MSVC 2017 (#10437) 2022-08-22 14:29:12 -07:00
BUILD.bazel Add missing timestamp_upb_reflection_proto alias 2026-01-29 15:12:32 -08:00
CMakeLists.txt Updating version.json and repo version numbers to: 35-dev 2026-01-22 07:25:02 -08:00
CODE_OF_CONDUCT.md Add a code of conduct based on https://www.contributor-covenant.org/ and https://github.com/carbon-language/carbon-lang/blob/trunk/CODE_OF_CONDUCT.md 2022-12-01 09:29:45 -08:00
CONTRIBUTING.md Add instructions for documentation changes to CONTRIBUTING.md. 2025-07-30 11:02:15 -07:00
CONTRIBUTORS.txt Match service argument names to abstract interface (#9418) 2022-02-03 09:14:44 -08:00
Disable_bundle_install.patch Switch rules_ruby to the supported version from bazel-contrib (#19808) 2025-03-06 13:42:11 -08:00
fix_permissions.sh Set execute bit on files if and only if they begin with (#!). (#7347) 2020-04-01 15:28:25 -07:00
generate_descriptor_proto.sh Release prototype of Protobuf Editions. 2023-06-30 20:18:49 -07:00
global.json Update .NET SDKs to LTS versions 2021-11-10 08:49:53 +13:00
google3_export_generated_files.sh Bump protobuf to latest upb version. 2023-01-14 00:11:12 -08:00
LICENSE Cleanup LICENSE file. 2018-03-26 15:03:41 -07:00
maven_dev_install.json Split maven dependencies into dev vs local (#20549) 2025-03-04 09:44:39 -08:00
maven_install.json Split maven dependencies into dev vs local (#20549) 2025-03-04 09:44:39 -08:00
MODULE.bazel Internal change 2026-02-04 10:55:35 -08:00
Neverlink_jruby_jars.patch Patch rules_ruby to apply neverlink = True to the jars rule (#21416) 2025-04-22 20:50:21 -07:00
PrivacyInfo.xcprivacy Add PrivacyInfo.xcprivacy (#15557) 2024-01-25 00:31:38 -08:00
protobuf.bzl Use the toolchain protoc by default in internal rules. 2026-01-28 10:21:18 -08:00
Protobuf.podspec Updating version.json and repo version numbers to: 35-dev 2026-01-22 07:25:02 -08:00
protobuf_deps.bzl Update rules_apple dependency to support rules_swift 3.x (#25437) 2026-01-28 20:15:35 -08:00
protobuf_release.bzl Internal change 2024-03-27 05:50:55 -07:00
protobuf_version.bzl Updating version.json and repo version numbers to: 35-dev 2026-01-22 07:25:02 -08:00
README.md internal change 2025-12-16 10:24:47 -08:00
regenerate_stale_files.sh Remove upb gencode from upb/cmake/ 2025-02-19 12:38:58 -08:00
SECURITY.md grammar nit 2021-08-13 14:50:07 -04:00
version.json Updating version.json and repo version numbers to: 35-dev 2026-01-22 07:25:02 -08:00
WORKSPACE Drop support for building Rust with the old Bazel WORKSPACE setup 2025-10-06 14:54:14 -07:00
WORKSPACE.bzlmod Move previous_release dependency out of WORKSPACE.bzlmod and into MODULE.bazel 2025-04-02 11:21:57 -07:00

Protocol Buffers - Google's data interchange format

OpenSSF Scorecard

Copyright 2008 Google LLC

Overview

Protocol Buffers (a.k.a., protobuf) are Google's language-neutral, platform-neutral, extensible mechanism for serializing structured data. You can learn more about it in protobuf's documentation.

This README file contains protobuf installation instructions. To install protobuf, you need to install the protocol compiler (used to compile .proto files) and the protobuf runtime for your chosen programming language.

Working With Protobuf Source Code

Most users will find working from supported releases to be the easiest path.

If you choose to work from the head revision of the main branch your build will occasionally be broken by source-incompatible changes and insufficiently-tested (and therefore broken) behavior.

If you are using C++ or otherwise need to build protobuf from source as a part of your project, you should pin to a release commit on a release branch.

This is because even release branches can experience some instability in between release commits.

Bazel with Bzlmod

Protobuf supports Bzlmod with Bazel 7 +. Users should specify a dependency on protobuf in their MODULE.bazel file as follows.

bazel_dep(name = "protobuf", version = <VERSION>)

Users can optionally override the repo name, such as for compatibility with WORKSPACE.

bazel_dep(name = "protobuf", version = <VERSION>, repo_name = "com_google_protobuf")

Bazel with WORKSPACE

Users can also add the following to their legacy WORKSPACE file.

Note that with the release of 30.x there are a few more load statements to properly set up rules_java and rules_python.

http_archive(
    name = "com_google_protobuf",
    strip_prefix = "protobuf-VERSION",
    sha256 = ...,
    url = ...,
)

load("@com_google_protobuf//:protobuf_deps.bzl", "protobuf_deps")

protobuf_deps()

load("@rules_java//java:rules_java_deps.bzl", "rules_java_dependencies")

rules_java_dependencies()

load("@rules_java//java:repositories.bzl", "rules_java_toolchains")

rules_java_toolchains()

load("@rules_python//python:repositories.bzl", "py_repositories")

py_repositories()

Protobuf Compiler Installation

The protobuf compiler is written in C++. If you are using C++, please follow the C++ Installation Instructions to install protoc along with the C++ runtime.

For non-C++ users, the simplest way to install the protocol compiler is to download a pre-built binary from our GitHub release page.

In the downloads section of each release, you can find pre-built binaries in zip packages: protoc-$VERSION-$PLATFORM.zip. It contains the protoc binary as well as a set of standard .proto files distributed along with protobuf.

If you are looking for an old version that is not available in the release page, check out the Maven repository.

These pre-built binaries are only provided for released versions. If you want to use the github main version at HEAD, or you need to modify protobuf code, or you are using C++, it's recommended to build your own protoc binary from source.

If you would like to build protoc binary from source, see the C++ Installation Instructions.

Protobuf Runtime Installation

Protobuf supports several different programming languages. For each programming language, you can find instructions in the corresponding source directory about how to install protobuf runtime for that specific language:

Language Source
C++ (include C++ runtime and protoc) src
Java java
Python python
Objective-C objectivec
C# csharp
Ruby ruby
Go protocolbuffers/protobuf-go
PHP php
Dart dart-lang/protobuf
JavaScript protocolbuffers/protobuf-javascript

Quick Start

The best way to learn how to use protobuf is to follow the tutorials in our developer guide.

If you want to learn from code examples, take a look at the examples in the examples directory.

Documentation

The complete documentation is available at the Protocol Buffers doc site.

Support Policy

Read about our version support policy to stay current on support timeframes for the language libraries.

Developer Community

To be alerted to upcoming changes in Protocol Buffers and connect with protobuf developers and users, join the Google Group.