The earliest web browser, WorldWideWeb, was created in 1990 by Tim Berners-Lee at CERN.
The short version: a NeXT computer on a lab desk at CERN ran the first browser-editor in 1990. Tim Berners-Lee wrote it, named it WorldWideWeb, and used it to read and write pages through the new HTTP protocol. Later, the program took the name Nexus to avoid confusion with the larger system called the World Wide Web. That single tool unlocked a way to view hyperlinked documents across machines and set the tone for everything that followed.
What Counts As The First Browser
Two facts settle it. First, the earliest tool wasn’t just a reader. It could edit pages, save them, and follow links. Second, it shipped as working software in 1990 at a research lab and spread to colleagues soon after. Many projects arrived in the next few years, but this one came first in both date and function.
Early Browser Timeline And Features
Here’s a clear snapshot of the first wave. It shows the names you’ll see in history books, the year they appeared, and what made each one stand out.
| Browser | Year | Notable Traits |
|---|---|---|
| WorldWideWeb (renamed Nexus) | 1990 | GUI on NeXT; read-write editor; first to browse and author HTML |
| Line Mode Browser | 1991 | Text-only; ran on many systems; helped adoption beyond NeXT |
| ViolaWWW | 1992 | Early scripting; forms; basic stylesheet ideas; applet-like widgets |
| Lynx | 1992 | Text browser; fast; useful on slow links and terminals |
| Erwise | 1992 | Early X-Window GUI; student project from Helsinki |
| Mosaic | 1993 | Inline images with text; easy setup; cross-platform reach |
| Cello | 1993 | Windows-focused; helped law and policy circles get online |
| Netscape Navigator | 1994 | Commercial polish; rapid updates; mass audience growth |
Who Built The Earliest Web Browser: Facts And Timeline
Tim Berners-Lee wrote the first client in the second half of 1990 on a NeXT machine, pairing it with an HTTP server. The tool let users open a document, click a link, and jump to the next page without manual file fetches. Editing sat beside reading, so a page could be revised in place. That tight loop of read, change, and publish made early collaboration smooth. By 1991, colleagues at CERN and a small group of researchers elsewhere were trying it out and passing notes on a mailing list about bugs and ideas.
Why Nexus Was More Than A Viewer
Calling it a browser undersells it. The program was a writer as well, a what-you-see-is-what-you-get editor for simple HTML. That meant one window for both sides of the work: drafting and reading. In the lab, that saved time. In practice, it also taught early users that the web wasn’t a broadcast medium. Anyone with access could publish a page that others could reach through a link.
Why This Happened On NeXT
The NeXTSTEP environment shipped with strong libraries and an Interface Builder that sped up GUI apps. That stack let one person ship a polished client faster than writing everything from scratch on less friendly platforms. Once the proof of concept worked, the team encouraged ports and new clients so the idea could travel beyond a single machine line.
Mosaic, Credit, And Popularity
Mosaic didn’t arrive first. It landed in 1993, and it did something users loved from day one: show images inline with text. That small shift made pages feel like pages, not lists with blue words and separate image viewers. Setup was also simpler. The mix of visuals and ease kicked off a surge in use on Windows, Unix, and Mac. Many people met the web through this program, so history often pairs Mosaic with the web’s first big growth spurt.
Inline Images Were A Turning Point
Before that, many clients loaded pictures in another window or by launching a helper app. Two windows per page slowed reading. With Mosaic, the diagram sat beside the paragraph that referenced it. That change made science pages clearer, product pages nicer, and hobby pages more fun. It also set a baseline that every later client kept.
Why People Mix Up “First” And “First To Spread”
Ask ten people which program started it all and you’ll hear two names: the 1990 NeXT client and the 1993 cross-platform one. The first came earlier and defined the model. The second reached more homes and offices. Both hold a place in the canon, but the date stamp on the pioneer is 1990, not 1993.
How The Early Pieces Fit Together
To see how this unfolded, think in layers. One layer handled links and the HTTP protocol. Another layer handled the page language that became HTML. On top sat the client program that rendered the text and links and, in some cases, images and forms. The 1990 client touched every part: it could author HTML, request documents, and display them. Later tools split duties, added features, and raced ahead on speed and cross-platform support.
Five Ground Rules The First Wave Set
- Links Over Files: Click text to jump. No manual FTP commands for each move.
- Open Specs: Share the protocol and language so others can build clients and servers.
- Plain Defaults: Start with text and add images and forms without breaking reach.
- Low Friction: One step install is the goal. If setup hurts, adoption stalls.
- Read-Write Ideal: Writing should sit near reading. Publishing shouldn’t need extra gates.
Primary Sources You Can Trust
You can read a short account from the person who wrote the 1990 client and see why it began life as a browser-editor. Here’s the official page describing the WorldWideWeb browser. For the rise of Mosaic and why inline images mattered on day one, the University of Illinois has a short explainer on the Mosaic project notes. Both links come straight from the teams that built and documented those tools.
Common Myths, Cleared Up
“Mosaic Was First”
No. Mosaic became the first client most households tried. The earlier NeXT program predates it by about three years and already had a GUI with editing.
“The Original Client Was Text Only”
No. The 1990 program used a graphical interface on NeXT. Text-only clients existed, too, and helped the web spread on a wide range of systems.
“The First Wave Had No Forms Or Scripting”
Not true. Some early clients added forms and even simple scripts. That work previewed the rich apps that arrived later in the decade.
What Made Each Early Client Distinct
Each one stood out by solving a different bottleneck. One made the concept real and editable. One ran on almost anything. One added forms and scripts. One blended pictures into the page. That variety pulled in different groups at once: researchers, students, publishers, and office workers. The net effect was a network that felt useful to more people in more places.
| Milestone | What Changed | Why It Mattered |
|---|---|---|
| 1990 NeXT Client | GUI read-write tool; HTTP client and editor built together | Set the model for pages, links, and live editing |
| 1991 Line Mode | Low-resource, text-only client on many platforms | Let universities and labs join without new hardware |
| 1992 ViolaWWW | Scripting, forms, early stylesheet ideas | Hinted at interactive pages and app-like behavior |
| 1993 Mosaic | Inline images; easier install; Windows and Mac builds | Brought a broad audience onto the web |
How Historians Date The First Browser
Dating software can be messy when code ships in stages or jumps between machines. In this case, records are clear. The 1990 NeXT program ran at the lab by year-end with both a server and a client in place. Mailing-list posts and lab notes back that up. The rename to Nexus came later, once the term “World Wide Web” settled on the broader system and the team wanted fewer mix-ups. That clarity is why reference works point to 1990.
The Broader Chain Of Influence
The NeXT client showed that linked documents and simple markup could work at scale inside a lab. Line Mode took reach wider. ViolaWWW teased interactivity. Mosaic made the page feel modern with images beside text. Netscape added pace and market polish. Each step borrowed from the last and pushed one layer forward. The result was a steady climb from a lab tool to something anyone with a modest PC could use after a quick install.
Why The Origin Story Still Matters
Knowing who built the first client tells you what the web tried to be from day one: a place to share research notes, publish text fast, and hop across documents with a click. The read-write goal wasn’t a late add. It was baked in. When you glance at a modern editor that lets you publish in a browser tab, you’re seeing that same idea carried forward with new polish.
Quick Answers To The Big Question
Who Wrote The First Client?
Tim Berners-Lee, while working at a research lab in Switzerland.
What Was It Called?
WorldWideWeb at first, later Nexus.
When Did It Run?
Late 1990, on a NeXT machine alongside the first HTTP server.
Which Client Popularized The Web?
Mosaic, in 1993, by blending images into pages and shipping on common platforms.
How To Cite This Story In Your Writing
Link to a primary page that describes the 1990 client and its read-write nature, and link to a page from the Illinois team for Mosaic’s role. Those two anchors cover the “who” and the “why people remember Mosaic” parts. They also help readers jump to deeper technical notes when they want to check dates or features.