Two apps can both show a crypto balance and a send button while giving the user very different control. Before comparing colours or convenience, ask who can authorise a transfer and what happens when access is lost.
In a custodial arrangement, a service manages key control on the user’s behalf. With self-custody, the user controls the relevant access mechanism and carries the corresponding responsibility. Modern systems can use more complex recovery or shared-control designs, so read the particular product’s explanation.
Trace one ordinary action
Imagine requesting a withdrawal from a service. Which checks must the service complete, and can it delay or restrict the request under its terms? Now compare authorising an on-chain transaction from a self-custodial account. Who signs, and who could restore access if the device disappears?
MetaMask’s explanation of self-custody describes its own control model. It is useful as a product-specific example, not an endorsement or evidence that every app using the word wallet has the same arrangement.
Write the recovery path before funding the account
Find the official recovery documentation and identify what the user must retain. A familiar password-reset screen does not prove that a provider can recover every kind of account. Conversely, a service-held balance may depend on the provider’s continuing ability to honour withdrawals.
Never disclose private keys or a recovery phrase to someone offering support. Use verified documentation and understand the process without experimenting with an account holding money you cannot afford to lose.
Compare the arrangements in three columns: who controls access, who can change or restrict it, and what evidence or secret is needed for recovery. Add fees and supported networks separately; those features do not answer the custody question.
Neither model removes every risk. Service failure, account compromise, mistaken transactions and lost credentials belong in the comparison. The useful choice begins with understanding which responsibilities you are accepting, rather than assuming that a polished interface has already handled them for you.