MetaMask Embedded
MetaMask’s embedded wallet SDK, formerly Web3Auth: email, social, or an existing wallet, then a non-custodial key.
- Capture
- Partial: 2 of 5 screens
- Last captured
- Oct 20, 2026
- Flow draft
- 5 screens
No public demo linked.
MetaMask Embedded Wallets is Consensys’ embedded wallet stack. The product was Web3Auth. Package names in the SDK still say Web3Auth. The user-facing promise is a wallet inside your app, with Web2 logins, and no browser extension required for that path.
Authentication is configured in the MetaMask Developer Dashboard. The default modal is opened with connect(). A custom UI can call connectTo() and skip the modal. Supported methods include email and SMS passwordless login, a long social list, external wallets including MetaMask itself, and any JWT provider.
Public pricing gates parts of the UI. The default login modal is on the free Base plan. Whitelabel login starts at Growth. The docs say the embedded wallet UI starts at Scale. Those features are available on sapphire_devnet for tests, which is the mode this site will use.
Who it is for
Apps that want the MetaMask name in the login, or that already speak Web3Auth and need the same MPC wallet under the new brand.
Sign-in, as documented
- Email passwordless: one-time code or magic link
- SMS one-time passcode
- Social: Google, Apple, X, Facebook, Discord, Twitch, GitHub, Farcaster, Reddit, Kakao, LinkedIn, Line, WeChat, Telegram
- External wallets, including MetaMask and WalletConnect
- Custom JWT or OIDC: Auth0, Firebase, Cognito, or your own
- Passkeys from the Growth plan up, according to the public pricing card
Wallet model
MPC wallets using threshold signatures and Shamir secret sharing. MetaMask describes this as self-custody: the key is not stored in one place. Native smart accounts use the MetaMask Delegation Toolkit on EVM chains. EVM and Solana are first-class; the SDK is described as chain-agnostic beyond that.
Expected flow
Dated frames are screenshots of the vendor’s default UI from the lab capture on Oct 20, 2026. Empty frames are still pending. The sequence itself is still a reading of the public docs.
01Host app calls connect
MetaMask Embedded lab entry. The host control opens the vendor’s default UI.
02Login modal
MetaMask Embedded opened its default UI. An email field was not found, so the code screen is still pending.
No screenshot
03Provider or code
OAuth leaves the modal. Email stays for a code. An external MetaMask login asks for a signature instead.
The default modal opens and offers Continue with Email/Phone, but that control does not advance on http://localhost:3000. The console reports hCaptcha rejecting localhost. Re-run with BASE_URL=https://www.kycflows.com after www.kycflows.com and kycflows.com are allowed origins on this client. A dashboard test account under Project Settings → Advanced is still required to pass the code, and email passwordless has to stay enabled. This run does not read a real inbox.
No screenshot
04Wallet provisioning
The embedded key is created or restored via MPC. We have not seen whether this is a visible step or a spinner.
No screenshot
05Return to the app
The SDK exposes a provider. Any “wallet home” UI beyond that is plan-gated and not yet captured.
Metrics
Documented rows cite a public page. Pending rows wait for the first capture. A blank is not a zero.
Screens in this draft
5 expected screens
Assumes the default modal. connectTo() with a single social button removes the picker.
Whitelabel, as published
Growth for login chrome, Scale for wallet UI
From MetaMask’s whitelabel docs. Devnet unlocks the features for testing.
Steps to a wallet
Pending first capture
Default modal, email passwordless, Base plan.
Fields the user fills
Pending first capture
We will not guess the code length.
Time to first wallet
Pending first capture
Pending first capture on devnet.
Context switches
Pending first capture
Social providers and the email inbox are the obvious ones.
Pricing snapshot
Priced in monthly active wallets. One MAW is a user who logs in or holds a session at least once in a calendar month. As of Oct 19, 2026, from metamask.io/developer/embedded-wallets.
| Plan | Price | What the page says |
|---|---|---|
| Base | Free · 1,000 MAW, then $0.050 | Email, SMS, wallet, and social logins, MFA, and the customizable default modal. |
| Growth | $69 / month · 3,000 MAW, then $0.045 | Adds passkeys, third-party auth, whitelabeled login, and native account abstraction. |
| Scale | $399 / month · 10,000 MAW, then $0.040 | Adds pregenerated wallets and the embedded wallet UI, plus wallet services. |
| Enterprise | Custom | Volume MAW discounts, custom domains, and an uptime SLA. |
- A June 2, 2026 MetaMask post describes the free tier as 1,000 MAW and paid plans starting at $69. That matches the pricing cards reviewed for this snapshot.
- SMS is not a free-forever channel at volume. Secondary writeups mention a small free SMS allowance; confirm it on the dashboard before you budget it.
Read this before you quote the page
- There is no single public end-user demo URL we are willing to call the product. Captures will come from a devnet app, and the frame stays empty until then.
- This is not the MetaMask browser extension. External MetaMask login is one method inside the embedded product.
Change history
Wallet-first notes open, with empty frames
Five wallet vendors and Didit are on the shelf, with six comparisons. Every screenshot frame says capture pending. Measured rows — steps, fields, time — are blank on purpose. Nothing here was timed.
MetaMask Embedded Wallets takes the Web3Auth name off the front door
Consensys published the embedded-wallet product under the MetaMask brand. The post describes a free tier of 1,000 monthly active wallets and paid plans from $69. SDK packages still say Web3Auth. We have not captured the modal.