No description
Find a file
Jason Aragorn Tobias Lunn b70d2497e2 Add test for RepeatedField concatenation and arena lifetime.
PiperOrigin-RevId: 943843380
2026-07-07 05:59:28 -07:00
.bazelci Update Bazel CI presubmit matrix 2026-05-05 08:59:10 -07:00
.bcr internal change 2026-05-13 13:11:37 -07:00
.github Fail loudly if we try to use a prebuilt protoc with unreleased code (#28167) 2026-07-06 15:01:10 -07:00
bazel Fail loudly if we try to use a prebuilt protoc with unreleased code (#28167) 2026-07-06 15:01:10 -07:00
benchmarks Second batch of ignored return value fixes; caught an off-by-one bounds check in the JSON benchmark 2026-06-29 19:45:53 -07:00
build_defs Fix arch tests by adding file to the Docker images 2026-03-10 11:06:34 -07:00
ci Add Bazel9 test 2026-04-30 10:53:12 -07:00
cmake Add new upb_Message_NextUnknown2 and upb_Message_DeleteUnknown2 functions to support non-canonical extensions in unknown field iteration/deletion. 2026-07-05 19:52:56 -07:00
compatibility add refresh_gencode.sh script to Java smoke tests (#25671) 2026-02-03 19:06:19 -08:00
conformance Make default_symbol_visibility STRICT in edition 2026 2026-06-25 13:11:42 -07:00
csharp Auto-generate files after cl/938151844 2026-06-25 20:21:21 +00:00
docs Register proto2type extension number 1307 (#28153) 2026-06-23 10:12:36 -07:00
editions Make default_symbol_visibility STRICT in edition 2026 2026-06-25 13:11:42 -07:00
editors Update Vim syntax files to support edition keyword (which is weirdly already 2025-10-10 11:07:10 -07:00
examples Fail loudly if we try to use a prebuilt protoc with unreleased code (#28167) 2026-07-06 15:01:10 -07:00
go go_features: prepare Go-specific optimize_mode 2025-10-03 01:22:29 -07:00
google3/third_party/java_src/protobuf/current/javatests/com/google/protobuf/utf8validation Add UTF-8 validation documentation and tests for proto2, proto3, and editions for Java Protobuf 2026-06-12 14:31:25 -07:00
hpb Automated Code Change 2026-06-14 20:30:35 -07:00
hpb_generator Second batch of ignored return value fixes; caught an off-by-one bounds check in the JSON benchmark 2026-06-29 19:45:53 -07:00
java Add a warning for potential OneofDescriptor collisions prior to Q1 2027 breaking changes. 2026-07-06 07:37:05 -07:00
lua Automated Code Change 2026-07-02 01:48:16 -07:00
objectivec Use XCTAssertEqualObjects to compare enum values with NSNumbers in the GPBDescriptorTests. 2026-06-15 06:55:05 -07:00
patches Add Bazel9 test 2026-04-30 10:53:12 -07:00
php Correct add_descriptor_set size from an int to a size_t 2026-07-06 12:50:58 -07:00
pkg Add new upb_Message_NextUnknown2 and upb_Message_DeleteUnknown2 functions to support non-canonical extensions in unknown field iteration/deletion. 2026-07-05 19:52:56 -07:00
python Format descriptor_pool.cc to eliminate pre-existing lint issues. 2026-07-06 21:38:41 -07:00
ruby Add test for RepeatedField concatenation and arena lifetime. 2026-07-07 05:59:28 -07:00
rust Remove -release suffix from Rust Crates.io release if minor version >= 36 2026-06-30 10:46:57 -07:00
src Enable message globals. 2026-07-06 09:16:24 -07:00
third_party Automated rollback of commit 29ef75d62c. 2026-06-19 06:54:42 -07:00
toolchain Add support for bazel 9.x (#26201) 2026-03-04 13:59:16 -08:00
upb Add aliases for reflection and reflection_internal in preparation for c/cc split 2026-07-07 05:55:49 -07:00
upb_generator Update call sites that ignore return values for allocation failures 2026-06-26 05:57:02 -07:00
.bazelignore Internal changes 2024-10-17 11:33:01 -07:00
.bazeliskrc Add Bazel9 test 2026-04-30 10:53:12 -07:00
.bazelrc Fail loudly if we try to use a prebuilt protoc with unreleased code (#28167) 2026-07-06 15:01:10 -07: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 Upgrade C# Protobuf projects to .NET 8.0. 2026-05-21 10:07:55 -07:00
appveyor.yml Upgrade to MSVC 2017 (#10437) 2022-08-22 14:29:12 -07:00
BUILD.bazel Fix typo in BUILD rule name 2026-05-29 10:29:19 -07:00
CMakeLists.txt cmake: support narrowly constrained lite-only runtime builds (#27407) 2026-06-01 19:03:05 -07: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 Upgrade C# Protobuf projects to .NET 8.0. 2026-05-21 10:07:55 -07: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 Add Bazel9 test 2026-04-30 10:53:12 -07:00
MODULE.bazel First implementation of C# nullable reference types enablement using the current (unreleased) edition. 2026-06-03 09:21:54 -07:00
PrivacyInfo.xcprivacy Add PrivacyInfo.xcprivacy (#15557) 2024-01-25 00:31:38 -08:00
protobuf.bzl Add deprecation warning for internal_py_proto_library prior to Q1 2027 breaking changes. 2026-07-06 11:09:17 -07:00
Protobuf.podspec Updating version.json and repo version numbers to: 36.0-dev (#26991) 2026-04-20 13:14:04 -07:00
protobuf_deps.bzl First implementation of C# nullable reference types enablement using the current (unreleased) edition. 2026-06-03 09:21:54 -07: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: 36.0-dev (#26991) 2026-04-20 13:14:04 -07:00
README.md Dropped support for Bazel 7. 2026-02-14 14:50:17 -08:00
regenerate_stale_files.sh Fix for performance penalty in deep dependencies (#20392) 2026-05-22 09:26:03 -07:00
SECURITY.md Update bug report and feature templates to be clearer about being on supported versions and filing security issues to VRP 2026-03-16 10:18:13 -07:00
version.json Updating version.json and repo version numbers to: 36.0-dev (#26991) 2026-04-20 13:14:04 -07:00
WORKSPACE Dropped support for Bazel 7. 2026-02-14 14:50:17 -08: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 8 +. 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.