The usual framing goes like this. An early, read-only web gave way to a web of platforms where users created the content but the platforms owned the accounts, the data and the payment rails. Web3 proposes a third arrangement: your keys are the account, your assets sit on a public ledger, and the applications you use are <a href="/glossary/dapp/">dapps</a> whose logic runs as smart contracts anybody can inspect. Signing in becomes proving you control an address rather than handing over a password.
In practice that means a handful of concrete things: wallets instead of usernames, tokens as membership or ownership records, on-chain trading and lending, and governance by token vote instead of by company policy. Portability is the genuine advantage. If your assets live on a shared ledger, a single application closing down does not take them with it, and a competing front-end can read the same state.
The honest caveats are substantial. Much of what is labelled Web3 leans on centralised pieces: hosted front-ends, node providers, oracles and admin keys that can pause or upgrade a contract. Critics argue that the term describes an aspiration, and that <a href="/glossary/decentralization/">decentralisation</a> is often thinner than the branding suggests. Others use Web3 simply as a fashionable synonym for crypto. Both criticisms have force, and the label alone tells you nothing about how a given project is actually built.
For a newcomer the practical takeaway is the shift in responsibility. Self-custody removes the intermediary and also removes the safety net: no password reset, no chargeback, no support desk to reverse a mistaken transfer. That trade-off is the real substance behind the buzzword, and it is worth understanding before you connect a wallet to anything.
Key takeaways
- Web3 is a contested label, so treat it as a starting question rather than a description of how a product works.
- The consistent idea underneath is wallet-based ownership and identity instead of platform-held accounts.
- Plenty of Web3 products still depend on centralised hosting, admin keys and intermediaries, so check the specifics.
Web3 — frequently asked questions
Is Web3 just another word for crypto?
Often, yes, and that is part of why the term is criticised. Crypto usually points at assets and markets, while Web3 points at applications and ownership of identity and data. Plenty of projects use whichever word suits the audience. When you see it, look past the label at what the product actually does and which parts of it are genuinely decentralised.
Do I need a wallet to use Web3 apps?
Almost always, since your wallet is how you sign in and authorise actions. Start small and keep balances low until you trust an application, and read every signature request before approving it: some grant ongoing permission to move your tokens rather than authorising a single transaction. Our <a href="/toolkit/">toolkit walkthroughs</a> cover wallet setup step by step.
New to crypto, or filling in the gaps? Work through the essentials in Learn, browse every term A–Z, or see live prices for the coins these concepts power.