Discord Protocol Buffers
Reverse-engineering Discord's protobufs.
This repository provides protocol buffer files for all protobufs found in Discord's client source, automatically generated and automatically updated. The protobufs are provided as .proto files in the out/ directory.
These protobufs are used by Discord clients for transmitting data like user settings and premium marketing.
Usage
Installation
Note: These packages are automatically updated when changes are detected in the protobufs. As Discord often updates their protobufs, pinning to a specific version may be advisable.
# with npm
npm install discord-protos
# with yarn
yarn add discord-protos
# with pnpm
pnpm add discord-protos
# with pip
pip install discord-protos
Example
JavaScript:
const { PreloadedUserSettings } = require('discord-protos');
const encoded = PreloadedUserSettings.toBase64({
status: {
status: {
value: "online",
},
customStatus: {
text: "Hello World",
emojiId: 0n,
emojiName: "",
expiresAtMs: 0n,
createdAtMs: 0n,
},
},
});
const decoded = PreloadedUserSettings.fromBase64(encoded);
console.log(encoded, decoded);
Python:
import base64
from google.protobuf.json_format import ParseDict
from discord_protos import PreloadedUserSettings
settings = PreloadedUserSettings()
payload = ParseDict({
'status': {
'status': 'online',
'custom_status': {
'text': 'Hello World',
},
},
}, settings).SerializeToString()
encoded = base64.b64encode(payload).decode('ascii')
decoded = PreloadedUserSettings.FromString(base64.b64decode(encoded))
print(encoded, decoded, sep='\n')
The following table shows which protobuf user settings correspond to which .proto file (the Python package also provides a UserSettingsType enum for convenience).
| Type | Value | File | Use |
|---|---|---|---|
| 1 | PRELOADED_USER_SETTINGS |
PreloadedUserSettings.proto | General Discord user settings. |
| 2 | FRECENCY_AND_FAVORITES_SETTINGS |
FrecencyUserSettings.proto | Frecency and favorites storage for various things. |
| 3 | TEST_SETTINGS |
- | Unknown. |
See Userdoccers for more information.
Development
Running pnpm load will extract and save the latest protobufs to the discord_protos/ directory.
1 maintainer
Metadata
1 maintainer
Release files for discord-protos 1.2.365
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| discord_protos-1.2.365.tar.gz | 213.5 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| discord_protos-1.2.365-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 456.4 kB
Release files / discord_protos-1.2.365.tar.gz
| Download URL | discord_protos-1.2.365.tar.gz |
|---|---|
| Size | 213.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
dc4b24708949abda191b30198a70df7e3e775c535456e598191e38d729552c25
|
|
BLAKE2b-256 checksum How to use checksums |
438f1ce2c2cdfe71bfa7b30f96eaf232c467a9d3395c4e27cd9457d860bde2d3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 6, 2026.
Transparency logRelease files / discord_protos-1.2.365-py3-none-any.whl
| Download URL | discord_protos-1.2.365-py3-none-any.whl |
|---|---|
| Size | 243.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
56fe0ea8466a95991a9d97723739234f86f8b0520280f7a1c742f071c2ee1f28
|
|
BLAKE2b-256 checksum How to use checksums |
13217480fd8ce566ebbd59890e639c2938f9fcc6199fc094504d3b7034a08279
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 6, 2026.
Transparency log
