Web1: publish and link
Web1 mainly describes pages that visitors read and authors update. Imagine a museum website with opening hours, history and links to its galleries. The browser requests a page and a server returns the files.
HTML organizes content, CSS handles presentation, and JavaScript can add interaction. A modern static page can still be fast, accessible and discoverable. Static does not mean useless or obsolete.
Web2: participate and use applications
Web2 emphasizes profiles, user contributions and actions such as commenting, booking, collaborating and buying. An application can read and update a database, distinguish accounts and provide personalized results.
A booking site stores your request, updates availability and sends confirmations. Its operator often controls accounts and service rules. Open, federated and self-hosted projects also exist: Web2 does not always mean one large platform.
Web3: add on-chain verification and control
Here, Web3 describes applications using blockchain records for selected features: token ownership, transfers, smart-contract rules or name management. A smart contract is code executed by a network according to its rules.
The visible website is often still HTML, CSS and JavaScript. A wallet manages an account and presents signing requests; a node or RPC service lets the application read and submit network data. A dapp may therefore also depend on conventional interfaces, servers and services.
Blockchain alone does not guarantee a sound project, anonymity, interface availability or the absence of administrators. To understand actual control, inspect each component.
Where does one model end and another begin?
An association’s site could combine public pages, a member area and a blockchain-verifiable certificate. The first layer resembles Web1, the second Web2, and the third introduces Web3. A “connect wallet” button alone does not prove the entire system is decentralized.
What you can do: an operational comparison
| Aspect | Web1 | Web2 | Web3 |
|---|---|---|---|
| Typical experience | Read pages and follow links | Publish, book and collaborate | Also use on-chain state or assets |
| Website name | Usually DNS | Usually DNS | DNS, blockchain name or both |
| Where data lives | Files published by the author | Application databases and services | Some on-chain; files and services elsewhere |
| Who can change it | Author or publisher | Users under application permissions | Authorized accounts and system rules |
| Wallet required? | No | Usually not | Only for features that require it |
| Key limitation | Author-managed updates | Reliance on operators and services | Compatibility, keys, costs and hybrid dependencies |
When is a blockchain useful?
- Just publishing information? A static page and DNS domain may be enough.
- Managing bookings or private records? Consider an application with a database, permissions and an accountable operator.
- Do several parties need to verify shared state without relying only on your database? Assess a blockchain component, its costs, keys and rules.
The right choice meets the need with proportionate complexity. A hybrid system can be more practical than a complete migration.
Answers to common questions
Has Web1 ended?
No. Publishing static pages remains useful. Web1 is a descriptive model, not an expired protocol.
Must I leave Chrome or Safari to use Web3?
Not necessarily. Many Web3 interfaces are ordinary HTTPS pages. Resolving a specific blockchain name and signing with a wallet still require compatible support.
Is a website with artificial intelligence automatically Web3?
No. AI concerns how data and content are processed; Web3, in this course, concerns blockchain and related mechanisms. They can be combined or used separately.
Sources and further reading
Primary documentation consulted for this guide. Product, network and integration support can change: check current requirements before configuring a service.