No description
Find a file
Protobuf Team Bot 71e600c2ed go_features: prepare Go-specific optimize_mode
PiperOrigin-RevId: 814584528
2025-10-03 01:22:29 -07:00
.bazelci Add .bazelci/presubmit.yml to test protobuf on Bazel CI 2025-02-26 08:39:06 -08:00
.bcr Internal Change. 2025-05-27 17:49:25 -07:00
.github add 33.x to test_release_branches 2025-10-01 14:00:24 -07:00
bazel Migrate proto_descriptor_set (#23369) 2025-10-02 10:01:01 -07:00
benchmarks Automated Code Change 2025-07-14 14:35:52 -07:00
build_defs Automated Code Change 2025-08-26 10:25:14 -07:00
ci Enable more --incompatible flags that are enforced by the BCR presubmit 2025-07-24 10:56:58 -07:00
cmake Add bzlmod support for python release 2025-09-25 20:03:17 -07:00
compatibility Add gencode smoke tests (#23547) 2025-09-29 14:06:33 -07:00
conformance Change which impl the cpp conformance testee uses for JSON parse/serialize. 2025-08-28 10:26:01 -07:00
csharp Updating version.json and repo version numbers to: 34.0-dev (#23738) 2025-10-02 10:51:16 -07:00
docs Add another typescript protobuf plugin to the docs (#23154) 2025-08-16 11:25:16 -07:00
editions Add Java (mutable) language feature handling to 2024 transform. 2025-09-18 08:56:54 -07:00
editors protobuf-mode: add edition keyword for syntax highlighting 2024-08-23 07:17:25 -07:00
examples protobuf/examples/go: update Go Protobuf dependency version 2025-09-18 11:40:55 -07:00
go go_features: prepare Go-specific optimize_mode 2025-10-03 01:22:29 -07:00
hpb hpb: add MakeHandle support that double-checks matching minitables 2025-10-01 08:03:05 -07:00
hpb_generator hpb: add MakeHandle support that double-checks matching minitables 2025-10-01 08:03:05 -07:00
java Clarify the public APIs of GeneratorNames helpers. 2025-10-02 15:47:41 -07:00
lua Removed unused aliases 2025-06-20 09:59:24 -07:00
objectivec Auto-generate files after cl/808581123 2025-09-18 15:10:33 +00:00
patches Add java bazel 8 tests and make java builds compatible with bazel 8. 2025-04-07 09:32:55 -07:00
php Updating version.json and repo version numbers to: 34.0-dev (#23738) 2025-10-02 10:51:16 -07:00
pkg Automated Code Change 2025-08-26 10:25:14 -07:00
python Updating version.json and repo version numbers to: 34.0-dev (#23738) 2025-10-02 10:51:16 -07:00
ruby Updating version.json and repo version numbers to: 34.0-dev (#23738) 2025-10-02 10:51:16 -07:00
rust Internal change. 2025-10-02 02:58:51 -07:00
src Deprecate ClassName methods in favor of new QualifiedClassName ones. 2025-10-02 13:17:20 -07:00
third_party utf8_range: Remove unused DEFAULT_VISIBILITY 2025-08-26 02:23:37 -07:00
toolchain Automated Code Change 2025-08-26 10:25:14 -07:00
upb Internal change 2025-09-30 09:34:36 -07:00
upb_generator Internal change. 2025-09-18 17:40:56 -07:00
.bazelignore Internal changes 2024-10-17 11:33:01 -07:00
.bazeliskrc Upgrade to Bazel 7.6.1 2025-07-07 12:22:23 -07: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
.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 [dotnet, csharp] Run tests for supported platforms .NET 6, .NET Framework 4.6.2 (#12378) 2023-04-10 13:28:23 -07:00
appveyor.yml Upgrade to MSVC 2017 (#10437) 2022-08-22 14:29:12 -07:00
BUILD.bazel Add alias for timestamp_upb_proto. 2025-08-27 21:56:54 -07:00
Cargo.bazel.lock Migrate rust protobuf test matchers from empty to is_empty. 2025-06-25 14:41:05 -07:00
Cargo.lock Migrate rust protobuf test matchers from empty to is_empty. 2025-06-25 14:41:05 -07:00
CMakeLists.txt Updating version.json and repo version numbers to: 34.0-dev (#23738) 2025-10-02 10:51:16 -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 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 Updating version.json and repo version numbers to: 34.0-dev (#23738) 2025-10-02 10:51:16 -07: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 Fix migration notice about py_proto_library 2025-03-19 17:39:04 -07:00
Protobuf.podspec Updating version.json and repo version numbers to: 34.0-dev (#23738) 2025-10-02 10:51:16 -07:00
protobuf_deps.bzl Add bzlmod support for python release 2025-09-25 20:03:17 -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: 34.0-dev (#23738) 2025-10-02 10:51:16 -07:00
README.md Test against bazel 8.0.0, update dependencies to bazel 8 compatible versions, and remove protobuf_extra_deps. 2025-01-27 11:39:04 -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: 34.0-dev (#23738) 2025-10-02 10:51:16 -07:00
WORKSPACE Port proto_library tests to Starlark 2025-08-08 04:17:59 -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 2023 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.