Avatar creation
Build an avatar, explore styles, customize its appearance, and preview the result.
Avatar Studio Lab is a place to create, customize, manage, and carry your digital presence — without making one platform the gatekeeper.
Foundation prototype · portable HTML edition
The first release establishes the experience and the boundaries between its parts. Creation tools and account services can be connected incrementally.
Build an avatar, explore styles, customize its appearance, and preview the result.
Organize profiles, projects, galleries, permissions, and the ways you choose to present yourself.
Keep portable copies of your avatar and its metadata. Move between services without starting over.
The master identity layer belongs to the person. Social logins and verification providers may help with onboarding, but none should own the identity.
A durable account and profile model that can support multiple sign-in and recovery methods.
World ID and other providers can be connected when useful. They are optional integrations, not the sole source of identity.
Keep the public experience, application logic, data, and optional Web3 features separate. That makes the studio easier to move, maintain, and expand.
Landing page, gallery, studio entry, and project information.
Create, customize, preview, save, and export avatar projects.
Profiles, project ownership, sharing controls, and recovery options.
Images, 3D files, metadata, version history, and backups.
Wallets, decentralized names, collectibles, and verifiable credentials when chosen.
Static HTML can live on IPFS or Cloudflare Pages. Backend services can be added separately.
Start with the portrait. No account. An email or a role is a reveal you choose for each place to see. A guise is a temporary persona you wear into a place, then take off. A fitting is a look you can try and remove. A login or a scan is not the original. The original stays in this browser, and in the file you export.
More than one email. More than one role. Hiding one does not delete you.
Put it on to enter work, public, or friends. Take it off when you leave. It is not a second you.
Try a different portrait. Remove the fitting. The original is still underneath.
Friction rule: make the portrait first. Add a reveal only when you want one. Every addition comes off.
Let people enter and explore before asking for more information. Reveal additional capabilities as they become useful.
Make integrations replaceable. Keep export, recovery, and migration in the design from the beginning.
Design rule: the person stays in control; providers are replaceable; the studio remains portable.