Cross-game 3D avatar platform: users build a single GLB avatar via the hosted Avatar Creator and reuse it across thousands of games and apps. Provides React, React Native, Unity, and Unreal SDKs plus the Visage web renderer. NOTE: Ready Player Me is sunsetting on January 31, 2026 — Wolf3D / Avatar SDK is the recommended migration path.
- 01drop-in 3D avatar creator UI
- 02GLB avatar rendering on the web (Visage / three.js)
- 03Unity / Unreal avatar pipelines
- 04metaverse and social app onboarding
- 05NFT / wallet-linked PFP-to-3D-avatar flows
- pnpm add @readyplayerme/react-avatar-creator @readyplayerme/visage three
| Variable | Scope | Description |
|---|---|---|
| NEXT_PUBLIC_RPM_SUBDOMAIN | Client | Ready Player Me partner subdomain (e.g. 'demo' for demo.readyplayer.me). |
| NEXT_PUBLIC_RPM_APP_ID | Client | Ready Player Me Studio application ID for branded creator + avatar persistence. |
Mount `<AvatarCreator subdomain={subdomain} config={{ clearCache: true, bodyType: 'fullbody', quickStart: false, language: 'en' }} onAvatarExported={({ data }) => setAvatarUrl(data.url)} />` from `@readyplayerme/react-avatar-creator` to embed the creator. Render the resulting `.glb` URL with `<Avatar modelSrc={avatarUrl} />` from `@readyplayerme/visage` (built on three.js / @react-three/fiber). For Unity/Unreal, use the official RPM SDK to download and instantiate the same GLB. Avatars are not NFTs by default — wallet-link them by storing the avatar URL in a token URI or off-chain profile.
- ⚑Ready Player Me is sunsetting January 31, 2026 — new integrations should target Avatar SDK / Wolf3D, and existing integrations need a migration plan before the cutoff date.
- ⚑Avatars are GLB files hosted by Ready Player Me. They are not on-chain NFTs; if you want them to be ownable assets, mint a token whose URI references the GLB and accept that RPM controls hosting (single point of failure).
- ⚑Custom assets (clothing, accessories) require a Studio plan and are sandboxed per app ID — assets uploaded to one app are not visible in another, breaking the 'one avatar everywhere' promise for branded items.
- ⚑The React Avatar Creator iframe relies on `postMessage` events; strict CSPs or sandboxed iframes block these and avatars never export. Whitelist `*.readyplayer.me` and avoid `sandbox` without `allow-scripts allow-same-origin`.
- ⚑GLB files are large (3–8 MB typical) — render them through a CDN, lazy-load on viewport, and avoid loading multiple full-body avatars simultaneously on mobile.
- ⚑Visage assumes a WebGL2 context; older mobile browsers and some embedded webviews fall back to WebGL1 and silently fail to render PBR materials.