{
  "$schema": "https://degreesofsatoshi.com/encyclopedia/schemas/article-v1.json",
  "schemaVersion": "1.0.0",
  "id": "metamask-missing-restored-accounts",
  "canonical": "https://degreesofsatoshi.com/encyclopedia/metamask-missing-restored-accounts/",
  "collection": "ethereum",
  "title": "Why are accounts missing after restoring MetaMask?",
  "description": "Find missing MetaMask accounts after phrase restoration by checking derivation order, import method and the original address.",
  "aliases": [
    "MetaMask account missing after restore",
    "restore imported wallet accounts"
  ],
  "dates": {
    "published": "2026-10-02",
    "modified": "2026-10-02",
    "verified": "2026-10-02T19:27:58.939Z",
    "dataAsOf": "2026-10-02"
  },
  "authorship": {
    "publisher": "Degrees of Satoshi editorial project",
    "process": "AI-assisted research and drafting with a separate automated source-verification pass; no external expert or named human review is implied."
  },
  "quickAnswer": {
    "text": "Restoring a MetaMask phrase restores access to accounts derived from it, but the interface may not immediately display all of them. Add derived accounts in the original sequence and compare full addresses. Accounts imported from separate private keys or connected hardware wallets are different: the restored phrase does not recreate their keys.",
    "claimId": "metamask-missing-restored-accounts-quick-answer",
    "sourceIds": [
      "x425-eth-mm-restore",
      "x425-eth-mm-path"
    ]
  },
  "keyFacts": [
    {
      "label": "Same phrase",
      "value": "The same supported derivation sequence produces the same addresses.",
      "sourceIds": [
        "x425-eth-mm-restore",
        "x425-eth-mm-path"
      ],
      "id": "same-phrase",
      "claimId": "metamask-missing-restored-accounts-fact-same-phrase"
    },
    {
      "label": "Display order",
      "value": "Some derived accounts may need to be added again.",
      "sourceIds": [
        "x425-eth-mm-restore"
      ],
      "id": "display-order",
      "claimId": "metamask-missing-restored-accounts-fact-display-order"
    },
    {
      "label": "Imported keys",
      "value": "A separately imported account is not generated by the current phrase.",
      "sourceIds": [
        "x425-eth-mm-restore"
      ],
      "id": "imported-keys",
      "claimId": "metamask-missing-restored-accounts-fact-imported-keys"
    }
  ],
  "prerequisites": [
    "ethereum-accounts"
  ],
  "sections": [
    {
      "id": "identity",
      "heading": "Look for an address, not an account label",
      "sourceIds": [
        "x425-eth-mm-restore"
      ],
      "paragraphs": [
        "Account names such as “Savings” are interface labels. Record the original public address and network from your own records, then compare that address with restored accounts. A renamed account does not become a different onchain owner.",
        "MetaMask’s current documentation describes automatic restoration behavior that depends on onboarding and backup settings. Do not interpret an incomplete account list as evidence that the blockchain balance disappeared."
      ]
    },
    {
      "id": "sequence",
      "heading": "A later derived account may be hidden",
      "sourceIds": [
        "x425-eth-mm-restore"
      ],
      "paragraphs": [
        "Suppose your tokens were held by the fourth account generated from one phrase. After restoration, the interface shows only the first account. Adding the next derived accounts in order can reveal the original fourth address; it does not transfer the tokens to new owners.",
        "Automatic discovery based on ETH activity can miss an account that holds tokens but no ETH. Confirm the full address before deciding that a candidate account is the recovered one."
      ]
    },
    {
      "id": "imports",
      "heading": "Separate account origins need separate recovery",
      "sourceIds": [
        "x425-eth-mm-restore",
        "x425-eth-mm-path"
      ],
      "paragraphs": [
        "An account imported from a private key is outside the current phrase’s derivation tree. A connected hardware account is controlled by the device’s keys. Reconnect or recover those through their documented methods rather than repeatedly generating unrelated accounts.",
        "If the phrase came from another wallet, its derivation path may differ. Record the originating wallet and path support; never send the phrase to a person offering to search it for you."
      ]
    }
  ],
  "faq": [
    {
      "question": "Does adding an account after restoration create a new balance?",
      "answer": "No. It reveals an address controlled by the restored derivation sequence. Existing onchain holdings remain associated with their original addresses.",
      "sourceIds": [
        "x425-eth-mm-restore"
      ]
    },
    {
      "question": "Can missing tokens mean I restored the wrong account?",
      "answer": "Yes, but first distinguish the address, selected network and token display. Correct account restoration and correct token detection are separate checks.",
      "sourceIds": [
        "x425-eth-mm-restore",
        "x425-eth-mm-tokens"
      ]
    }
  ],
  "claims": [
    {
      "id": "metamask-missing-restored-accounts-quick-answer",
      "articleSlug": "metamask-missing-restored-accounts",
      "statement": "Restoring a MetaMask phrase restores access to accounts derived from it, but the interface may not immediately display all of them. Add derived accounts in the original sequence and compare full addresses. Accounts imported from separate private keys or connected hardware wallets are different: the restored phrase does not recreate their keys.",
      "sourceIds": [
        "source-bc836c2e8d5b3936",
        "source-302a9de796759a11"
      ],
      "sourceLocators": [
        {
          "sourceId": "source-bc836c2e8d5b3936",
          "locator": "Restored accounts; imported accounts"
        },
        {
          "sourceId": "source-302a9de796759a11",
          "locator": "Derivation path"
        }
      ],
      "scope": {
        "collection": "ethereum",
        "dataAsOf": "2026-10-02",
        "blockHeight": null
      },
      "qualification": "",
      "evidenceStatus": "documented",
      "verification": {
        "status": "verified",
        "method": "independent automated source review",
        "checkedAt": "2026-10-02T19:27:58.939Z",
        "reviewer": "Independent automated verification agent verify_bitcoin_stablecoins_100",
        "notes": [
          "Fresh restore guide explicitly gives Account4/token-without-mainnet-ETH example and distinction between automatic backup/sync discovery and manual derived-account order. Hardware/private-key imports remain separate; public address versus label comparison valid."
        ]
      }
    },
    {
      "id": "metamask-missing-restored-accounts-fact-same-phrase",
      "articleSlug": "metamask-missing-restored-accounts",
      "statement": "Same phrase: The same supported derivation sequence produces the same addresses.",
      "sourceIds": [
        "source-bc836c2e8d5b3936",
        "source-302a9de796759a11"
      ],
      "sourceLocators": [
        {
          "sourceId": "source-bc836c2e8d5b3936",
          "locator": "Restored accounts; imported accounts"
        },
        {
          "sourceId": "source-302a9de796759a11",
          "locator": "Derivation path"
        }
      ],
      "scope": {
        "collection": "ethereum",
        "dataAsOf": "2026-10-02",
        "blockHeight": null
      },
      "qualification": "",
      "evidenceStatus": "documented",
      "verification": {
        "status": "verified",
        "method": "independent automated source review",
        "checkedAt": "2026-10-02T19:27:58.939Z",
        "reviewer": "Independent automated verification agent verify_bitcoin_stablecoins_100",
        "notes": [
          "Fresh restore guide explicitly gives Account4/token-without-mainnet-ETH example and distinction between automatic backup/sync discovery and manual derived-account order. Hardware/private-key imports remain separate; public address versus label comparison valid."
        ]
      }
    },
    {
      "id": "metamask-missing-restored-accounts-fact-display-order",
      "articleSlug": "metamask-missing-restored-accounts",
      "statement": "Display order: Some derived accounts may need to be added again.",
      "sourceIds": [
        "source-bc836c2e8d5b3936"
      ],
      "sourceLocators": [
        {
          "sourceId": "source-bc836c2e8d5b3936",
          "locator": "Restored accounts; imported accounts"
        }
      ],
      "scope": {
        "collection": "ethereum",
        "dataAsOf": "2026-10-02",
        "blockHeight": null
      },
      "qualification": "",
      "evidenceStatus": "documented",
      "verification": {
        "status": "verified",
        "method": "independent automated source review",
        "checkedAt": "2026-10-02T19:27:58.939Z",
        "reviewer": "Independent automated verification agent verify_bitcoin_stablecoins_100",
        "notes": [
          "Fresh restore guide explicitly gives Account4/token-without-mainnet-ETH example and distinction between automatic backup/sync discovery and manual derived-account order. Hardware/private-key imports remain separate; public address versus label comparison valid."
        ]
      }
    },
    {
      "id": "metamask-missing-restored-accounts-fact-imported-keys",
      "articleSlug": "metamask-missing-restored-accounts",
      "statement": "Imported keys: A separately imported account is not generated by the current phrase.",
      "sourceIds": [
        "source-bc836c2e8d5b3936"
      ],
      "sourceLocators": [
        {
          "sourceId": "source-bc836c2e8d5b3936",
          "locator": "Restored accounts; imported accounts"
        }
      ],
      "scope": {
        "collection": "ethereum",
        "dataAsOf": "2026-10-02",
        "blockHeight": null
      },
      "qualification": "",
      "evidenceStatus": "documented",
      "verification": {
        "status": "verified",
        "method": "independent automated source review",
        "checkedAt": "2026-10-02T19:27:58.939Z",
        "reviewer": "Independent automated verification agent verify_bitcoin_stablecoins_100",
        "notes": [
          "Fresh restore guide explicitly gives Account4/token-without-mainnet-ETH example and distinction between automatic backup/sync discovery and manual derived-account order. Hardware/private-key imports remain separate; public address versus label comparison valid."
        ]
      }
    }
  ],
  "sources": [
    {
      "id": "x425-eth-mm-restore",
      "label": "Missing accounts after restoring MetaMask",
      "publisher": "MetaMask",
      "url": "https://support.metamask.io/configure/accounts/how-to-add-missing-accounts-after-restoring-with-secret-recovery-phrase/",
      "locator": "Restored accounts; imported accounts",
      "note": "Derived accounts and separately imported accounts do not have identical restoration paths.",
      "version": "Documentation snapshot retrieved 2 October 2026; response hash recorded separately",
      "checkedAt": "2026-10-02T18:55:24.232Z",
      "contentSha256": "98687db6d3feaafdea019e53c6c610f3446ed8dd43e9fa96bb87e80f144476a5",
      "recordId": "source-bc836c2e8d5b3936"
    },
    {
      "id": "x425-eth-mm-path",
      "label": "Importing a seed phrase from another wallet",
      "publisher": "MetaMask",
      "url": "https://support.metamask.io/configure/wallet/importing-a-seed-phrase-from-another-wallet-software-derivation-path/",
      "locator": "Derivation path",
      "note": "Wallet recovery compatibility and path-dependent address discovery.",
      "version": "Documentation snapshot retrieved 2 October 2026; response hash recorded separately",
      "checkedAt": "2026-10-02T18:55:24.713Z",
      "contentSha256": "5283f25ceb99b7d71fb15a0004c93fe9b57a37e1ddc1a6db9ab56bc3de26d6bf",
      "recordId": "source-302a9de796759a11"
    },
    {
      "id": "x425-eth-mm-tokens",
      "label": "Displaying tokens in MetaMask",
      "publisher": "MetaMask",
      "url": "https://support.metamask.io/manage-crypto/tokens/how-to-display-tokens-in-metamask",
      "locator": "Enhanced detection; custom tokens; hiding tokens",
      "note": "Wallet display and token contract identity are separate from onchain holdings.",
      "version": "Documentation snapshot retrieved 2 October 2026; response hash recorded separately",
      "checkedAt": "2026-10-02T18:55:24.137Z",
      "contentSha256": "175816d8d6f117fbbe963b8005cd04b9a2757ed1c45ad4142a88f32bfce31d67",
      "recordId": "source-85b8c7c22a802fdd"
    }
  ],
  "related": {
    "articles": [
      "ethereum-accounts",
      "erc-20-tokens",
      "metamask-password-and-recovery-phrase",
      "ethereum-tokens-not-showing"
    ],
    "dossiers": [],
    "wallets": []
  },
  "revisionHistory": [
    {
      "date": "2026-10-02",
      "kind": "published",
      "summary": "First publication after primary-source research and separate automated verification."
    }
  ],
  "citation": "Degrees of Satoshi editorial project. “Why are accounts missing after restoring MetaMask?.” Published 2026-10-02; updated 2026-10-02. https://degreesofsatoshi.com/encyclopedia/metamask-missing-restored-accounts/"
}