MetaMask Snaps can add transaction insights, notifications, support for additional blockchain protocols and new account-management methods directly to the MetaMask Extension. That flexibility is useful, but it also creates a new trust decision: a Snap is third-party software with specific permissions, its own developer and sometimes its own recovery process. Safe use begins before installation, not after the first warning appears.
Last reviewed: October 30, 2026. MetaMask Snaps, supported platforms, directory policies and individual Snap permissions can change. Check the current MetaMask interface and official documentation before acting. This independent guide is educational and is not financial, legal or security advice.
1. What is a MetaMask Snap?
A Snap is a mini application that runs inside the MetaMask browser extension and extends what the wallet can do. A Snap can provide information about a proposed transaction, communicate with another blockchain protocol, display notifications, store data or introduce a different account-management system. It is not a token, a blockchain or a normal browser extension installed separately from MetaMask.
MetaMask provides the Snaps platform and permission system. Individual Snaps are commonly built and maintained by third-party developers. This distinction matters when researching support, privacy and recovery: a problem with one Snap is not automatically a problem with the MetaMask platform, and MetaMask may not control the third party’s servers or data practices.
2. Snap, dapp and browser extension are different
| Component | Where it operates | Main decision |
|---|---|---|
| MetaMask Extension | Installed in the browser | Whether the wallet software and download source are authentic |
| Dapp | Usually a website or web application | Which account to connect and what to sign or send |
| Snap | Runs through the Snaps system inside MetaMask | Whether to install third-party code and grant its requested permissions |
A dapp connection and a Snap installation are not equivalent. Disconnecting a website does not necessarily uninstall a Snap, and uninstalling a Snap does not reverse transactions or token approvals already recorded onchain. Review each relationship through its appropriate settings.
3. What can Snaps add?
MetaMask documentation groups common uses into several broad areas. Security Snaps can provide transaction insights or threat signals. Interoperability Snaps can add support for protocols and networks beyond MetaMask’s native scope. Communication Snaps can deliver messages or notifications. Account Management Snaps can introduce accounts based on technologies or recovery models different from ordinary MetaMask accounts.
The category is only a description, not a safety rating. Two Snaps in the same category may request different permissions, contact different servers and use different recovery designs. Evaluate the exact Snap rather than trusting the category name.
4. Start with the official Snaps Directory
MetaMask recommends beginning with its Snaps Directory. A directory entry can help identify the developer, requested permissions, source-code repository and available security information. Snaps may also be installable from third-party websites, which makes domain verification especially important.
A listing is not an endorsement, investment recommendation or guarantee against loss. MetaMask’s FAQ describes third-party Snaps as third-party services used at the user’s risk. Treat the directory as a structured place to begin due diligence, not as permission to skip it.
5. Use the five-part Snap safety test
Before installing, review five connected questions:
- Source: Did you reach the installation page through an official, independently verified route?
- Developer: Can you identify who maintains the Snap, its documentation and its support channel?
- Permissions: Does each requested capability match the feature being advertised?
- Data: What information is processed locally, stored on the device or sent to outside servers?
- Recovery: How are Snap-managed accounts or essential data restored after device loss?
If any answer is unclear, pause. Convenience is not a reason to grant a permission you cannot explain.
6. Sandboxing helps, but it is not a guarantee
Snaps run in a sandboxed environment and use a permission model designed to limit what each Snap can do. This separates a Snap from unrestricted access to the browser or wallet. MetaMask also applies additional review requirements to certain protected or account-management capabilities.
Sandboxing does not prove that the Snap’s intended behavior is beneficial, that every external server is secure or that the developer’s privacy policy is suitable for you. Software can operate within granted permissions and still collect more information than expected, provide misleading output or become unavailable. The purpose of the permission screen is to support a decision, not to replace one.
7. Read permissions as capabilities, not technical noise
A Snap should request only the capabilities necessary for its stated purpose. Permission names may look technical, so translate each one into a practical question.
| Possible capability | What it may enable | Question to ask |
|---|---|---|
| Internet access | Communication with third-party servers | Which data leaves the device, where and why? |
| Store and manage data | Local encrypted or unencrypted Snap data | Is the data sensitive, portable and removable? |
| Transaction insights | Analysis shown during a transaction confirmation | What transaction context is inspected or transmitted? |
| Signature insights | Extra information before signing a message | Does the analysis cover this signature type? |
| Public keys or addresses | Protocol-specific account identification | Can this information link activity across services? |
| Dapp communication | Requests and data exchange with websites | Which dapps communicate with the Snap? |
| Snap communication | Data exchange between Snaps | Why is another Snap involved? |
| Notifications | Wallet or operating-system messages | Are notifications informational or action-inducing? |
| Periodic actions | Scheduled tasks | How often do they run and what external calls occur? |
| Account management | Creation or control of a specialized account | Who controls it and how is it recovered? |
8. Permission fit is more important than permission count
A useful Snap may legitimately need several permissions. A transaction-analysis Snap may need transaction insight and network access to compare an address with an external threat database. An interoperability Snap may need protocol-specific public keys. The concern is not simply a large number; it is a permission that has no clear relationship to the promised function.
Read the developer’s explanation before accepting. If a simple notification tool requests account management, or a local display feature requests broad network access without explaining its data flow, do not assume the request is harmless.
9. What Snaps should never ask you to type
MetaMask states that Snaps cannot access the Secret Recovery Phrase or Ethereum private keys through the Snaps permission system. That protection does not prevent a fraudulent website, form or person from asking you to disclose them manually.
- Never type your Secret Recovery Phrase into a Snap installation website.
- Never send a private key, password or recovery code to a developer or support account.
- Never upload a recovery screenshot for “verification.”
- Never approve a transaction described as wallet synchronization or account validation without independently verifying what it does.
A request for secret recovery material is a reason to stop, regardless of the logo, urgency or claimed support status.
10. Privacy begins with the data path
Ask whether a feature works locally or contacts an external service. Internet access may be necessary for current threat intelligence, cross-chain information or cloud-backed functionality. It may also reveal an IP address, queried account, website origin or transaction data to a provider, depending on implementation.
Read the Snap’s privacy policy and documentation. Identify the operator, data categories, retention period, deletion process and third parties. MetaMask does not automatically receive all information shared with a third-party Snap; the Snap developer may process it directly. Removing the Snap later does not necessarily delete data already sent to a remote server.
11. Public does not mean privacy-neutral
A blockchain address and public key are not secret in the same way as a private key, but sharing them can still affect privacy. A service may associate an address with an IP address, browser session, email account or activity on another network. Repeated queries can build a profile even when no private key is exposed.
Decide whether the feature justifies that linkage. Use separate operational accounts where appropriate, but do not assume separate addresses are untraceable when onchain transfers connect them.
12. Security Snaps provide signals, not certainty
A Security Snap can add a transaction-insights section to a MetaMask confirmation. Depending on the product, it may compare an address with phishing data, decode a transaction, simulate an outcome or estimate state changes. This can expose a mismatch between what a website promises and what a transaction may do.
No security database contains every new malicious address, and a simulation may not capture every future state or adversarial condition. A clean result is not approval to ignore the recipient, network, token amount and contract. A warning deserves investigation; an absence of warning is not proof of safety.
13. Interoperability Snaps change the recovery question
An Interoperability Snap may add access to a protocol that MetaMask does not otherwise manage in the same way. Before receiving assets, establish which account created the address, which network explorer can verify it, which asset pays fees and what recovery material applies.
Switching a displayed network does not move assets. Likewise, installing support for another protocol does not make similarly named tokens interchangeable across chains. Always confirm the destination network and address format with the receiving service.
14. Snap-managed accounts may follow a different model
Account Management Snaps can introduce MPC, smart-account or other account designs. The account may depend on keys or credentials generated specifically for the Snap, a third-party service, multiple factors or a recovery method unrelated to an ordinary MetaMask account.
Do not infer custody from the phrase “inside MetaMask.” Determine who can authorize transactions, whether a provider can block recovery, what happens if the provider closes and whether the design has been independently audited. If these details are unavailable, do not use the account for irreplaceable value.
15. Your MetaMask seed may not restore a Snap account
This is the most important operational distinction. MetaMask warns that the Secret Recovery Phrase used for ordinary MetaMask accounts may not recover accounts added through a Snap. Restoring MetaMask on a new device can restore the base wallet while leaving a Snap-managed account unavailable until its separate recovery process is completed.
Before funding such an account, perform a recovery review:
- Identify the exact backup or credential the Snap requires.
- Read the official restore procedure from beginning to end.
- Confirm which steps depend on the Snap developer’s service.
- Test with a small amount and a separate browser profile or spare device where appropriate.
- Store required secrets offline using the method recommended for that account design.
Never delete an Account Management Snap as a troubleshooting experiment until you understand the consequences for its accounts.
16. Install safely
- Open MetaMask from its known browser icon, not from a message link.
- Reach the official Snaps Directory or the verified developer site through a trusted route.
- Compare the domain character by character.
- Review the developer, source repository, documentation, audit information and update history.
- Read every requested permission and match it to a documented function.
- Check the privacy policy before granting network or data access.
- Install only if the remaining risk is appropriate for the account and assets involved.
Use a low-value test account for initial learning. A test account limits exposure, but it does not make a malicious signature or data disclosure harmless.
17. Source code and audits are useful evidence
Public source code permits specialists to inspect what software is intended to do and allows users to compare a release with a maintained repository. An audit can identify weaknesses within a defined version and scope. Neither proves that every future update is safe or that the deployed package always matches the reviewed code.
Look for a named auditor, date, version, scope, findings and remediation status. A badge without a report provides little evidence. For high-impact account-management functionality, MetaMask describes additional review requirements, but users should still understand the account and recovery design.
18. Review permissions after installation
MetaMask provides a Snaps settings area where installed Snaps and their permissions can be reviewed. Make this part of a periodic wallet audit. Remove software you no longer use and investigate any Snap you do not recognize.
Also review connected dapps and token approvals through their separate controls. A complete cleanup may require three different actions: disconnect a website, revoke an onchain allowance and uninstall a Snap.
19. Treat updates as new trust decisions
An update can fix vulnerabilities, add features or request new permissions. Read the change summary and any new permission prompt. A permission that was unnecessary in the old version may be required for a documented new feature, but it still deserves evaluation.
Verify updates through the Snap’s official installation route. Do not follow “critical update” links from direct messages. If an update unexpectedly expands access, wait for a clear explanation from independently verified developer channels.
20. Notifications can be a social-engineering channel
A permitted Snap may display notifications. Treat them as information, not automatic instructions. A message that creates urgency, asks you to visit a new domain or claims funds will be lost should be verified outside the notification.
Open the project’s official documentation from a bookmark, check the developer’s verified repository and compare announcements. Do not enter recovery information or sign a transaction merely because the alert appeared inside a familiar wallet interface.
21. Troubleshoot without making the problem larger
First separate a platform problem from an individual Snap problem. If every Snap fails, check the MetaMask Extension version and official MetaMask support information. If only one Snap fails, consult that developer’s official documentation and status channels.
- Record the account, network, time, error and transaction hash if one exists.
- Check the block explorer before repeating a transaction.
- Confirm MetaMask and the Snap are current through official routes.
- Review recent permission or account changes.
- Contact the verified Snap developer without sharing secret material.
- Reinstall only after checking backup and recovery consequences.
A pending interface does not prove that a transaction failed. Repeating it can create an unintended duplicate or spend another fee.
22. Disable, uninstall and revoke are not synonyms
| Action | Typical effect | What it does not automatically do |
|---|---|---|
| Disable a Snap | Temporarily stops its operation | Delete remote data or reverse transactions |
| Uninstall a Snap | Removes it from MetaMask | Revoke token approvals or guarantee account recovery |
| Disconnect a dapp | Ends the current website connection | Uninstall a Snap or revoke allowances |
| Revoke an approval | Changes an onchain token allowance | Delete a Snap or recover transferred assets |
Before uninstalling, export or secure anything the official Snap recovery procedure requires. After uninstalling, review remaining dapp connections, approvals and remote-service accounts separately.
23. If a Snap or installation site looks suspicious
- Reject pending requests and close the site.
- Open MetaMask through the known extension icon.
- Review installed Snaps and their permissions.
- Check Activity and appropriate block explorers for unknown transactions.
- Review token approvals independently.
- Preserve transaction hashes, domains and screenshots for investigation.
- If recovery words or private keys were disclosed, create a new wallet securely and move remaining assets after verifying the destination.
Do not accept help from people who contact you privately after you describe the incident. Recovery scammers commonly impersonate support and ask for the same secrets that legitimate support never needs.
24. Common MetaMask Snaps scams
- A cloned Snaps Directory promoted through a search advertisement.
- A fake Security Snap that asks for a seed phrase to “scan” the wallet.
- An urgent update delivered through Telegram, Discord or direct message.
- A Snap claiming it can recover transferred or frozen cryptocurrency.
- An airdrop that requires an unfamiliar Snap and opaque signature.
- A fake developer support account requesting screen sharing or secret exports.
- A lookalike repository with copied documentation and a changed installation link.
Branding is easy to copy. Verify through more than one official route and give more weight to exact domains, maintained repositories and coherent documentation than to follower counts or testimonials.
25. A practical pre-installation checklist
- I reached the Snap through a verified official source.
- I identified the developer and official support route.
- I understand the Snap’s purpose and each requested permission.
- I checked whether data leaves my device.
- I read the privacy policy and available audit material.
- I know whether it creates or controls a separate account.
- I know exactly how that account is backed up and restored.
- I am starting with limited value and a deliberate test.
- I will review updates rather than approve them automatically.
26. Monthly Snap hygiene
Open the Snaps settings and inventory what remains installed. Remove unused Snaps only after checking recovery requirements. Review changed permissions, developer announcements and privacy policies. Check connected dapps and token approvals separately. Keep MetaMask updated through official browser stores or MetaMask’s official site, and remove unrelated browser extensions you no longer trust.
Record non-secret operational details for important Snap-managed accounts: the Snap name, official domain, network, public address, recovery method and date of the last recovery review. Never store the recovery secret in the same plain-text note.
27. Frequently asked questions
Are MetaMask Snaps safe?
They use sandboxing and permission controls, and certain capabilities receive additional review. Individual Snaps are still third-party software. Safety depends on the developer, permissions, data handling, update process and the user’s decisions.
Can a Snap read my Secret Recovery Phrase?
MetaMask states that Snaps cannot access the MetaMask Secret Recovery Phrase or Ethereum private keys through the Snaps system. A malicious site or person may still ask you to type them manually. Never do so.
Can a Snap move my tokens?
Capabilities differ. A Snap may suggest or help manage transactions depending on its type and permissions, while MetaMask still presents confirmation flows. Read every transaction and signature. Never assume a Snap’s warning or interface makes a transaction harmless.
Is every Snap in the directory audited?
Do not assume so. Review the individual directory entry and audit report. MetaMask applies different requirements based on requested permissions, and a listing is not a guarantee or endorsement.
Can several Snaps run at the same time?
MetaMask says multiple Snaps can be installed and used simultaneously. More installed software also means more permissions, developers and data paths to review.
Will my MetaMask seed recover every Snap-managed account?
No. MetaMask explicitly warns that the base wallet’s Secret Recovery Phrase may not restore accounts added through Snaps. Follow and test the specific Snap’s recovery procedure before depositing meaningful funds.
Does uninstalling a Snap revoke token approvals?
No. Snap installation, dapp connection and onchain token allowances are separate. Review and revoke unwanted approvals through an appropriate trusted tool.
Can a Snap collect personal data?
Data access depends on its permissions and design. Information shared with a third-party Snap may be processed directly by its developer. Read its privacy policy and assess network access before installing.
What should I do if a Snap asks for my seed phrase?
Stop immediately. Do not enter or send it. Close the page, verify installed Snaps from the MetaMask interface and report the suspicious domain through official channels.
Official sources and further reading
- MetaMask Help — MetaMask Snaps FAQs — official explanations of sandboxing, third-party responsibility, data access, availability and account boundaries.
- MetaMask Help — How Snap permissions work — descriptions of permissions and the steps for viewing permissions already granted.
- MetaMask Help — Snaps guide library — installation, updates, settings, backups, account management, removal and troubleshooting resources.
- MetaMask Help — What are Security Snaps? — transaction insights, phishing checks, simulations and privacy considerations.
- MetaMask Help — Troubleshoot Snaps — official steps for distinguishing platform problems from issues with an individual Snap.
- MetaMask Developer Documentation — Snaps — technical overview of stable Snaps features, including non-EVM networks, data storage, notifications and transaction insights.
- MetaMask News — official product announcements and current MetaMask updates.
MetaMask Snaps can make a wallet more capable, but every new capability creates a boundary to understand. Verify the source, investigate the developer, minimize permissions, trace the data path and prove the recovery plan before meaningful funds depend on it.