This release is a pre-release and may not be stable for production use.
DiceBear avatar styles
This repository contains all official avatar style definitions for
DiceBear. An avatar style definition is a JSON file
that describes how to create an avatar. It contains all necessary information
like available elements and colors. The JSON files are ideal for creating
avatars in different programming languages with the corresponding DiceBear
wrapper. The JSON schema for the avatar style definitions can be found in the
@dicebear/schema package.
Generate definitions
Most of the JSON files were created using the
DiceBear Exporter
for Figma. The used Figma files are linked in the figma folder. Files created
with this plugin are marked accordingly and should not be adjusted manually, but
exported again with the Figma plugin.
Usage
JavaScript
npm install @dicebear/styles
import adventurer from "@dicebear/styles/adventurer.json" with { type: "json" };
import lorelei from "@dicebear/styles/lorelei.json" with { type: "json" };
PHP
composer require dicebear/styles
$basePath = \Composer\InstalledVersions::getInstallPath('dicebear/styles');
$adventurer = json_decode(file_get_contents($basePath . '/src/adventurer.json'), true);
$lorelei = json_decode(file_get_contents($basePath . '/src/lorelei.json'), true);
Python
pip install dicebear-styles
import json
from importlib.resources import files
adventurer = json.loads(files('dicebear_styles').joinpath('adventurer.json').read_text('utf-8'))
lorelei = json.loads(files('dicebear_styles').joinpath('lorelei.json').read_text('utf-8'))
Rust
Each style is gated behind a feature of the same name, so a binary only embeds the
styles it opts into (use the all feature to pull in every style):
cargo add dicebear-styles --features adventurer,lorelei
The enabled styles are embedded at compile time and exposed as raw JSON
(&'static str). Parse them with serde_json:
use dicebear_styles::{ADVENTURER, LORELEI};
let adventurer: serde_json::Value = serde_json::from_str(ADVENTURER)?;
let lorelei: serde_json::Value = serde_json::from_str(LORELEI)?;
// Or look one up by name at runtime (None if unknown or its feature is off):
let style = dicebear_styles::get("adventurer");
// all() lists every style compiled into this build.
let all = dicebear_styles::all();
Go
go get github.com/dicebear/styles/v11
Every style is embedded at compile time and exposed as raw JSON (string), both
as an exported variable and by name via Get. Parse it with encoding/json:
import (
"encoding/json"
styles "github.com/dicebear/styles/v11"
)
var adventurer map[string]any
_ = json.Unmarshal([]byte(styles.Adventurer), &adventurer)
// Or look one up by name (ok is false if the style is unknown):
raw, ok := styles.Get("lorelei")
// All() lists every embedded style.
all := styles.All()
Dart
dart pub add dicebear_styles
Each style is a Dart string constant in its own library, so a compiled app only
embeds the styles it imports. Parse the raw JSON with dart:convert:
import 'dart:convert';
import 'package:dicebear_styles/adventurer.dart';
import 'package:dicebear_styles/lorelei.dart';
final adventurerStyle = jsonDecode(adventurer);
final loreleiStyle = jsonDecode(lorelei);
Or import the umbrella library, which pulls in every style and adds a runtime lookup by name:
import 'package:dicebear_styles/dicebear_styles.dart' as styles;
// null if the style is unknown:
final raw = styles.get('adventurer');
// `all` lists every embedded style.
final names = styles.all;
C#
dotnet add package DiceBear.Styles
Every style is embedded in the assembly and exposed as raw JSON (string), both
as a property and by name via Get. Parse it with System.Text.Json:
using System.Text.Json;
using DiceBear;
var adventurer = JsonDocument.Parse(Styles.Adventurer);
// Or look one up by name (null if the style is unknown):
var raw = Styles.Get("lorelei");
// All() lists every embedded style.
var all = Styles.All();
Each property reads its resource on every call, so hand the text to whatever parses it once and keep that result rather than the raw string.
Contributing
See CONTRIBUTING.md for local development, testing, and the release process.
License
Each avatar style is under its own license, named in the definition file itself. The language shims, the build scripts and the package manifests are under the MIT license. Both parts are spelled out in LICENSE.md.
Sponsors
Advertisement: Many thanks to our sponsors who provide us with free or discounted products.
Metadata
Release files for dicebear-styles 11.0.0rc3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| dicebear_styles-11.0.0rc3.tar.gz | 674.1 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| dicebear_styles-11.0.0rc3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.4 MB
Release files / dicebear_styles-11.0.0rc3.tar.gz
| Download URL | dicebear_styles-11.0.0rc3.tar.gz |
|---|---|
| Size | 674.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
49704933e7c7b726c362a90f49dff0c621c0a0d4ac42922eced11f70ceec3ce4
|
|
BLAKE2b-256 checksum How to use checksums |
19aee8502fe63165e815d6081085d0db2e9c249ff63ed1bfdabc581c9f9c74b8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 7, 2026.
Transparency logRelease files / dicebear_styles-11.0.0rc3-py3-none-any.whl
| Download URL | dicebear_styles-11.0.0rc3-py3-none-any.whl |
|---|---|
| Size | 716.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ecbcdad184d90f8205c4e7090442f5e47bd387fe1dd807f2d61bc9c3ffce01f3
|
|
BLAKE2b-256 checksum How to use checksums |
05e0165de5957f5ba33470990132eb2a5e7db403c55978916d1cd94d07cffb19
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 7, 2026.
Transparency logSecurity for dicebear-styles 11.0.0rc3
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for dicebear_styles-11.0.0rc3.tar.gz
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 Sep 7, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.