> ## Documentation Index
> Fetch the complete documentation index at: https://docs.gelato.cloud/llms.txt
> Use this file to discover all available pages before exploring further.

# Embedded Wallets

For frontend applications, users need a way to sign transactions. There are two main approaches:

**Browser Extension Wallets** - Users connect existing wallets like MetaMask, Rabby, or Coinbase Wallet. This requires users to have a wallet already installed.

**Embedded Wallets** - Wallets created within your application using familiar login methods like email, phone, or social accounts. This provides a smoother onboarding experience for users new to Web3.

## Supported Embedded Wallet Providers

Gelato integrates with the following embedded wallet providers:

<Columns cols={2}>
  <Card title="Dynamic" href="https://docs.dynamic.xyz/">
    Multi-chain embedded wallets with social login and email authentication.
  </Card>

  <Card title="Privy" href="https://docs.privy.io/">
    User-friendly embedded wallets with email, SMS, and social login options.
  </Card>

  <Card title="Web3Auth" href="https://web3auth.io/docs/">
    Non-custodial embedded wallets using MPC technology and social logins.
  </Card>

  <Card title="Turnkey" href="https://docs.turnkey.com/">
    Secure embedded wallets with institutional-grade key management.
  </Card>
</Columns>

## How It Works

Embedded wallet providers handle key generation and management, allowing users to sign transactions without managing seed phrases. When integrated with Gelato:

1. User logs in via email, social account, or other supported method
2. The embedded wallet provider creates or retrieves the user's wallet
3. Your application uses the wallet to sign UserOperations
4. Gelato Bundler submits the transactions on-chain

## Implementation

For detailed integration guides with code examples, see the [Embedded Wallets How-To Guide](/paymaster-&-bundler/how-to-guides/embedded-wallets).