Weave Code
Styles Laravel Package
dicebear/styles
Official collection of avatar styles for DiceBear, the open-source avatar library. Browse dozens of customizable SVG and PNG styles—adventurer, avataaars, bottts, and more—all exposed through a consistent API for generating unique user avatars.
Official DiceBear avatar styles.
Frequently asked questions about Styles
- Can I install dicebear/styles with Composer in a Laravel app?
- No. dicebear/styles is an npm/JavaScript distribution of SVG style definitions and contains no composer.json, so it cannot be required into a Laravel application. To use these styles from Laravel you have to run them out-of-process: pre-render SVGs in a Node build or queue job, run a small Node sidecar that wraps @dicebear/core, or call the public api.dicebear.com service. The only native PHP option is the older dicebear/avatars package, which is a different, frozen codebase.
- What does dicebear/styles actually contain?
- It is a collection of avatar style definitions, where each style supplies SVG path and shape data plus an option schema describing things like backgroundColor, radius, scale, and flip. It does not contain the generation engine itself; that lives in @dicebear/core, which combines a style with a seed to produce deterministic output. In other words it is a content and asset dependency, not an application library.
- What is the most practical way to generate DiceBear avatars in a Laravel project?
- Build-time pre-rendering is the cleanest fit. Run a Node job in CI, a queue worker, or an Artisan-triggered script over the styles you need, emit the SVGs to storage/app/public or S3 keyed by a hash of style, seed, and options, and serve them through your CDN. Laravel owns identity and persistence, Node owns rendering, and PHP-FPM workers never touch a JS runtime. If any style option is user-influenced, avoid serving the SVG inline without sanitization, since inline SVG is an XSS vector.
- Is there a native PHP or Laravel package for DiceBear avatars?
- There is an older PHP port, dicebear/avatars, from the v4 era. It runs natively without a JS runtime but has a frozen feature set and a different style catalogue than the styles shipped in this npm package. Do not assume parity between the two, and check whether the specific styles you want exist in the PHP port before committing to it.
- How do I stop users' avatars from changing when DiceBear styles get updated?
- Avatar geometry for a fixed seed can change between style versions, so treat rendering as a versioned operation. Pin exact versions of @dicebear/core and each individual style package, commit a lockfile, and vendor the generated SVG files rather than re-rendering on every request. Seed from a stable identifier such as a user UUID rather than an email address, because emails change and would silently rotate avatars.
- Should I call api.dicebear.com instead of self-hosting?
- The public API has zero build cost, but your seeds and identifiers leave your perimeter, and you inherit someone else's rate limits and uptime. If seeds are derived from emails or internal user IDs, that is likely a privacy problem worth avoiding. Self-hosting a Node sidecar or pre-rendering gives you control over availability, caching, and data residency at the cost of an extra deployable.
- What licensing issues should I check before shipping DiceBear styles?
- The repository reports NOASSERTION, and DiceBear style art has historically carried CC0 or MIT-style terms with per-style nuances. Legal clearance is a hard gate before shipping derived or pre-rendered assets in a commercial product. Review the licence for every individual style you plan to use rather than assuming the umbrella package is uniformly licensed.
- Should I depend on the whole dicebear/styles bundle or individual style packages?
- Use the individual @dicebear/<style> packages and pin exact versions; never depend on the umbrella bundle in production. The umbrella pulls in every style's path data, which inflates cold-start time and image size in a sidecar or Lambda. Vendoring the generated SVGs also protects you if an npm package is later unpublished.
- Which styles are included and do they all take the same options?
- The collection covers dozens of styles including adventurer, avataaars, bottts, and many more, all exposed through a consistent generation API. The option schemas differ per style, though: backgroundColor, radius, scale, and flip are common but not universal. Your generator wrapper needs per-style validation rather than one shared options DTO, and the npm package and the public HTTP API are versioned independently.
- How actively maintained is dicebear/styles, and what is the risk?
- The repository has a small footprint, low star count, no visible maintainer SLA, and no attributed owner, so bus factor is a genuine concern. Mitigate it by pinning versions, committing a lockfile, and storing the rendered SVGs in your own object storage so you are not dependent on npm availability at request time. If long-term support matters, budget for owning the generator artifact yourself.
Weaver
How can I help you explore Laravel packages today?