The Complete Guide to 90s Web Design

1. Table Layouts: The Foundation of Every 90s Page

Before CSS existed in any practical sense, the HTML <table> element was the only tool available for creating multi-column page layouts. The <table> tag was designed for tabular data — rows and columns of numbers, comparison charts, schedules — but from approximately 1996 to 2003, it was repurposed as the primary layout mechanism for the entire World Wide Web. Every commercial website, every personal homepage, every corporate intranet used tables for layout. There was literally no alternative.

The technique worked like this: a designer would create an outer table with the full width of the page, then divide it into cells for the header, left navigation column, main content area, and right sidebar. Each of these cells might contain another table for finer-grained layout control. Complex pages routinely nested tables five to seven levels deep. The HTML source code for a simple three-column layout could easily exceed 200 lines before any actual content appeared.

The critical companion to table layouts was the spacer GIF — a transparent 1×1 pixel GIF image (typically named spacer.gif, blank.gif, or shim.gif) that was inserted into table cells and stretched to specific dimensions using width and height attributes. This was the only way to create precise spacing between elements. The technique was invented and popularized by David Siegel in his influential 1996 book Creating Killer Web Sites, which taught an entire generation of web designers how to achieve magazine-quality layouts using nothing but tables and transparent GIFs.

A typical three-column layout looked like this:

<table width="100%" border="0" cellpadding="0" cellspacing="0">
  <tr>
    <td colspan="3" bgcolor="#003366">
      <!-- Header / Banner -->
      <img src="banner.gif" width="750" height="100">
    </td>
  </tr>
  <tr>
    <td width="150" bgcolor="#336699" valign="top">
      <!-- Left Navigation -->
      <table width="100%" cellpadding="5">
        <tr><td><a href="index.html"><font color="#FFFFFF">Home</font></a></td></tr>
        <tr><td><a href="about.html"><font color="#FFFFFF">About</font></a></td></tr>
        <tr><td><a href="links.html"><font color="#FFFFFF">Links</font></a></td></tr>
      </table>
    </td>
    <td width="10">
      <!-- Spacer -->
      <img src="spacer.gif" width="10" height="1">
    </td>
    <td valign="top">
      <!-- Main Content -->
      Welcome to my homepage!
    </td>
  </tr>
</table>

The attributes bgcolor, cellpadding, cellspacing, valign, and border were the CSS of their era. Every visual property — background color, padding, alignment — was set directly on the HTML element. When CSS finally gained browser support, one of the first things the Web Standards movement campaigned for was the separation of presentation from structure — undoing exactly what table-based design had done.

2. Animated GIFs: The Visual Signature of the 90s Web

If table layouts were the skeleton of 90s web design, animated GIFs were its personality. The GIF89a format, finalized by CompuServe in 1989, supported multiple frames within a single image file, enabling simple animations without any JavaScript, Flash, or server-side processing. For a web where bandwidth was precious and browser capabilities were limited, animated GIFs were the perfect visual medium: small file sizes, universal browser support, and no plugins required.

The most iconic animated GIF of the era was the "Under Construction" sign. These came in hundreds of variations: a worker with a jackhammer, a yellow construction barrier, a blinking hard hat, a rotating traffic cone. The Internet Archive's GeoCities collection contains 322 unique "Under Construction" GIF designs, and that number represents only what was recovered from GeoCities alone. The "Under Construction" sign became a running joke of the era because nearly every personal homepage displayed one permanently — the site was always "under construction" because the webmaster was always adding to it, or had simply abandoned it with the sign still in place.

Other ubiquitous animated GIFs included:

• The Dancing Baby (Baby Cha-Cha) — a 3D-rendered animation created in 1996 using Autodesk Character Studio, widely considered one of the first viral internet memes
• Rotating globes — spinning Earth icons used next to "World Wide Web" links and international content
• Flaming text — words with animated fire effects, achieved either as GIFs or through specialized text-to-flame generators
• Spinning email icons — animated envelope or mailbox icons placed next to "Email me!" links
• Blinking arrows — pointing at navigation links, "Click here!" text, or new content
• Sparkle and glitter effects — star-shaped animations overlaid on text or images

The tools for creating these animations were dedicated desktop applications. Alchemy Mindworks' GIF Construction Set (1995) and Microsoft GIF Animator (1996, free) were the two most popular. Ulead GIF Animator and Macromedia Fireworks followed later. These tools allowed designers to import individual frames, set delays between them, configure looping behavior, and optimize the file size — a critical concern when a 50 KB GIF could take ten seconds to download on a 28.8 Kbps modem.

3. The <blink> and <marquee> Tags

No discussion of 90s web design is complete without the two most infamous HTML tags ever created: <blink> and <marquee>. They were browser-war products, each created by one side of the Netscape-Microsoft rivalry, and they represent the era's approach to the web perfectly: if you could make text do something, you should make text do that thing.

The <blink> tag was a Netscape Navigator exclusive. It was created by Lou Montulli, one of the original Netscape engineers, allegedly during a late-night session at a bar in 1994. The story, which Montulli has confirmed in interviews, is that the group was discussing which HTML tags should be added, and someone jokingly suggested a tag that made text blink on and off. The next morning, one of the engineers had actually implemented it. The tag had no attributes — no speed control, no on/off toggle. Text between <blink> and </blink> simply flashed on and off at a fixed interval, forever.

<!-- Netscape Navigator only -->
<blink>WELCOME TO MY HOMEPAGE!!!</blink>

<p><blink>*** NEW: Check out my <a href="links.html">links page</a>! ***</blink></p>

Microsoft's answer was <marquee>, introduced in Internet Explorer 2.0 (1995). Where <blink> was crude, <marquee> was surprisingly full-featured. It supported attributes for direction (left, right, up, down), scroll speed (scrollamount, scrolldelay), behavior (scroll, slide, alternate), and dimensions. Text would smoothly scroll across the page like a news ticker or a Times Square display.

<!-- Internet Explorer -->
<marquee direction="left" scrollamount="3" bgcolor="#FFFF00">
  <font color="red" size="4"><b>Welcome to my site! Please sign my guestbook!</b></font>
</marquee>

<!-- Bouncing text -->
<marquee behavior="alternate" scrollamount="5">
  *** HOT NEWS *** HOT NEWS *** HOT NEWS ***
</marquee>

Both tags were deprecated in later HTML standards. The <blink> tag was never part of any official specification and was removed from Firefox (the last browser to support it) in version 23, released in 2013. The <marquee> tag, remarkably, still works in all major browsers as of 2026 — Chrome, Firefox, Safari, and Edge all render it, despite the HTML5 specification marking it as obsolete. It is one of the longest-surviving deprecated tags in web history.

4. Background Patterns, Colors, and Music

The default appearance of a web page in the mid-1990s was black text on a gray background (Netscape) or white background (Internet Explorer). Webmasters who wanted something more distinctive turned to the <body> tag's attributes: bgcolor for solid colors, background for tiled images, text for default text color, and link, vlink, alink for link colors in their various states.

Tiled background images were everywhere. The browser would take a small image (typically 100×100 pixels or smaller) and repeat it horizontally and vertically to fill the entire page background. Popular patterns included:

• Stars and space — dark backgrounds with scattered stars, popular on sci-fi and astronomy sites
• Marble and stone textures — faux marble in blue, green, or gray, suggesting authority and sophistication
• Parchment and paper — aged paper textures for literature, history, and medieval-themed sites
• Geometric patterns — repeating diamonds, stripes, and tile patterns
• Nature themes — clouds, water, wood grain, leaf patterns

The most distinctive color scheme of the era was the "hacker" aesthetic: bright green text on a black background, directly mimicking the monochrome phosphor monitors of the 1970s and 1980s. The code was simple:

<body bgcolor="#000000" text="#00FF00" link="#00CCFF" vlink="#999999">
  <font face="Courier New" size="3">
    Welcome to the Matrix...
  </font>
</body>

And then there was background music. Two competing methods existed for auto-playing audio when a visitor loaded the page. Internet Explorer supported <bgsound src="song.mid" loop="infinite">, while Netscape used <embed src="song.mid" autostart="true" hidden="true">. The audio format was almost always MIDI (.mid files), because MIDI files were extraordinarily small — typically 2 to 5 KB per song — which mattered enormously on dial-up connections. A WAV or MP3 file of the same song would have been hundreds of kilobytes or several megabytes. MIDI files did not contain recorded audio; they contained instructions for the computer's sound card to synthesize the music, which is why the same MIDI file sounded different on every computer. Popular choices included video game themes, movie soundtracks, and classical music rendered as MIDI.

5. Frames and Framesets: The Layout That Broke the Web

Frames were introduced in Netscape Navigator 2.0 (1996) and quickly adopted by Internet Explorer. The concept was compelling: divide the browser window into multiple independent panes, each loading a separate HTML file. A typical framed site had a top frame for the site header and navigation bar, a left frame for the section menu, and a large right frame for the main content. When a visitor clicked a link in the left menu, only the right frame reloaded — the navigation stayed in place. This was the 90s equivalent of a single-page application.

<!-- frameset.html -->
<frameset rows="80,*">
  <frame src="header.html" name="top" scrolling="no" noresize>
  <frameset cols="180,*">
    <frame src="nav.html" name="menu" scrolling="auto">
    <frame src="welcome.html" name="content">
  </frameset>
</frameset>
<noframes>
  <body>Your browser does not support frames.</body>
</noframes>

<!-- nav.html -->
<a href="page1.html" target="content">Page 1</a><br>
<a href="page2.html" target="content">Page 2</a><br>
<a href="page3.html" target="content">Page 3</a>

The problems with frames became apparent almost immediately. Bookmarking was broken — the browser's URL bar always showed the frameset URL, not the URL of the content currently displayed in any frame. Visitors could not bookmark or share a link to a specific page within the site. The back button behaved unpredictably, sometimes navigating within a frame and sometimes navigating away from the entire frameset. Search engines struggled with frames because they indexed individual frame documents without the context of the frameset, leading to visitors arriving at isolated pages with no navigation. Printing was problematic — browsers often printed only one frame, and which frame depended on where the user had last clicked.

The <iframe> (inline frame), introduced in HTML 4.0, allowed embedding one page within another as a rectangular region within the parent page. Unlike framesets, iframes were part of the normal document flow. The <iframe> tag survived and remains a standard part of HTML5, used today for embedding YouTube videos, Google Maps, third-party widgets, and sandboxed content. The <frameset> tag was removed from the HTML5 specification entirely.

6. Image Maps: Clickable Regions on a Single Image

Image maps allowed designers to define clickable regions (hotspots) on a single image, with each region linking to a different URL. The technique used the <map> element containing <area> elements, each specifying a shape (rect, circle, or poly) and coordinates within the image.

<img src="navbar.gif" usemap="#navigation" border="0">
<map name="navigation">
  <area shape="rect" coords="0,0,100,50" href="home.html" alt="Home">
  <area shape="rect" coords="100,0,200,50" href="about.html" alt="About">
  <area shape="rect" coords="200,0,300,50" href="gallery.html" alt="Gallery">
  <area shape="circle" coords="350,25,20" href="email.html" alt="Contact">
</map>

There were two types. Client-side image maps (the example above) processed the click coordinates in the browser and were fast. Server-side image maps sent the click coordinates to the server as a query string (image.map?203,47), which then determined the target URL — slower and requiring server configuration, but supported in earlier browsers before client-side maps were available.

Image maps were used for graphical navigation menus (a single banner image with clickable buttons), campus and building maps for universities and businesses, fantasy game world maps where clicking a region took you to information about that location, and geographic maps where clicking a state or country loaded regional content. The technique fell out of favor as CSS-based navigation became possible, but image maps remain valid HTML5 and are still occasionally used for interactive diagrams and floor plans.

7. Hit Counters, Guestbooks, and Webrings

Three features were so ubiquitous on 90s personal homepages that their absence was more notable than their presence: the hit counter, the guestbook, and the webring badge.

The hit counter was a visible display of how many times a page had been visited. It typically appeared at the bottom of the page with text like "You are visitor #00004827", rendered either as a simple text number or as a graphical counter using digit images (odometer-style, LED-style, or styled digits). Counters were implemented as CGI scripts that incremented a number stored in a text file on the server each time the page loaded. Matt Wright's Counter and TextCounter were among the most widely installed counter scripts of the era, distributed through Matt's Script Archive on this very domain. Third-party counter services like WebCounter, Site Meter, and StatCounter later offered hosted counters that required only an <img> tag. For a deeper look at how web counters worked and their evolution into modern analytics, see our dedicated article on the history of web counters.

The guestbook was the 90s version of a comments section. Visitors could leave their name, email address, homepage URL, and a message. The entries were displayed in reverse chronological order on a public page. Matt Wright's Guestbook was the definitive implementation, installed on hundreds of thousands of sites. Guestbooks served a social function that would later be filled by blog comments, social media, and eventually platforms like Facebook and Twitter. Signing someone's guestbook was an act of digital courtesy — an acknowledgment that you had visited and appreciated their work.

The webring was a navigation system that linked related websites in a circular chain. Each participating site displayed a webring badge with "Previous", "Next", and "Random" links. Clicking "Next" took you to the next site in the ring; clicking through the entire ring would eventually bring you back to where you started. Webrings were organized by topic — there were webrings for Star Trek fan sites, cat lover sites, poetry sites, medieval history sites, and thousands of other subjects. WebRing.org, the largest directory, hosted over 80,000 webrings at its peak. Webrings were a pre-search-engine discovery mechanism: they solved the problem of "how do I find other websites about this topic?" before Google existed.

8. Font Tags, Rainbow Text, and the <center> Tag

Without CSS, every typographic choice had to be expressed using HTML tags. The <font> tag was the instrument, and its three attributes — face, color, and size — were the extent of the designer's control over typography.

<font face="Comic Sans MS" color="#FF0000" size="7">
  <b>Welcome to My Homepage!!!</b>
</font>

<!-- Rainbow text: each letter a different color -->
<font color="#FF0000">W</font><font color="#FF7700">e</font><font color="#FFFF00">l</font><font color="#00FF00">c</font><font color="#0000FF">o</font><font color="#8B00FF">m</font><font color="#FF0000">e</font><font color="#FF7700">!</font>

Comic Sans MS (designed by Vincent Connare in 1994 for Microsoft) became the most commonly used — and later most ridiculed — typeface on the web. Other favorites included Times New Roman for "serious" sites, Arial and Verdana for readability, and Courier New for the hacker aesthetic. The face attribute accepted a comma-separated list of fallback fonts, but in practice most webmasters specified a single font and hoped for the best.

Rainbow text — wrapping each individual character in its own <font> tag with a different color value — was surprisingly common. The technique was tedious to do by hand, so webmasters used dedicated "rainbow text generators" that accepted a string of text and produced the HTML. A single sentence of rainbow text could generate more HTML than the rest of the page combined.

The <center> tag was the universal alignment tool. Nearly every page element — headings, images, paragraphs, tables — was wrapped in <center> tags. Combined with <br> tags for vertical spacing (since margin and padding did not exist without CSS), these two tags controlled the spatial arrangement of content on the page. It was crude, but it worked in every browser.

9. Email Links, Browser Badges, and Award Icons

The bottom of a 90s homepage was a curated collection of badges, links, and declarations that collectively told visitors everything about the webmaster's technical environment and social aspirations.

The mailto link was the universal contact method. Before contact forms powered by FormMail or PHP became common, the only way for a visitor to contact a webmaster was through a direct email link:

<a href="mailto:[email protected]">
  <img src="email.gif" border="0"> Email the Webmaster
</a>

The "Best Viewed In" badge was a direct consequence of the browser wars. Because Netscape Navigator and Internet Explorer rendered HTML differently and supported different proprietary tags, many webmasters optimized their sites for one browser and displayed a badge recommending it:

• "Best Viewed in Netscape Navigator 3.0 at 800×600"
• "Optimized for Internet Explorer 4.0"
• "Best Viewed at 1024×768 with 16-bit color"

These badges typically included the browser's official logo, provided by Netscape and Microsoft as part of their campaigns to win market share. The badges were not just decoration — they were genuine compatibility warnings, because a page built with Netscape-only features like <blink>, <layer>, and JavaScript 1.2 could look completely broken in Internet Explorer, and vice versa.

The "Under Construction" notice was often permanent. Sites would display it for months or years, either because the webmaster intended to add more content eventually, or because they had moved on and simply never removed it.

Award badges were a primitive reputation system. Sites like "Cool Site of the Day" (established 1994 by Glenn Davis), "Project Cool Sighting", "Top 5% of the Web" (by Lycos), and "Hot Site" awards would select websites and provide a badge that the winning webmaster could display. These badges functioned as social proof, and collecting them was a point of pride. Some webmasters dedicated entire pages to displaying their awards.

10. CGI Scripts: The Dynamic Elements

Every interactive element on a 90s website — every form that processed input, every counter that incremented, every guestbook that accepted entries, every search that returned results — was powered by a CGI script. The Common Gateway Interface was the protocol that allowed web servers to execute external programs in response to HTTP requests, and for nearly a decade it was the only widely available method for adding dynamic functionality to a website. For a comprehensive explanation of how CGI worked, see our guide to CGI technology.

The three most essential CGI scripts were:

• FormMail — processed HTML form submissions and emailed the data to the webmaster. The most widely installed CGI script in history, FormMail eventually became a major security vulnerability when spammers discovered it could be exploited as an open email relay.
• Guestbook — allowed visitors to leave messages that were displayed on a public page. The social layer of the 90s personal web.
• Counter — tracked and displayed page visit counts. The analytics platform of its era, reduced to a single number.

These scripts, and dozens of others, were written in Perl and distributed through archives like Matt's Script Archive (hosted on this domain from 1995), the CGI Resource Index, and Extropia. Installing a CGI script required uploading the .pl file to the server's cgi-bin directory, setting file permissions to 755, and editing configuration variables in the script. The process was straightforward but unforgiving — a single wrong file permission, a missing Perl module, or an incorrect path would produce the dreaded "500 Internal Server Error". For a look at what eventually replaced CGI, see our article on the technologies that came after.

11. What Killed 90s Web Design

The transition away from 90s web design was not a single event but a gradual shift driven by three forces: technology, advocacy, and economics.

CSS (Cascading Style Sheets) was the enabling technology. CSS1 was published as a W3C recommendation in December 1996, and CSS2 followed in May 1998. But the specifications and browser implementation were two very different things. Internet Explorer 3 (1996) and Netscape Navigator 4 (1997) both claimed CSS support, but their implementations were buggy, incomplete, and incompatible with each other. It was not until Internet Explorer 5 for Mac (2000) and Internet Explorer 6 for Windows (2001) that any browser offered CSS support comprehensive enough to build real layouts. Even then, cross-browser CSS was an exercise in frustration, requiring elaborate hacks and workarounds. Practical, widespread CSS adoption did not occur until 2002–2004.

The Web Standards movement was the advocacy force. Jeffrey Zeldman, through his website and the publication A List Apart (founded 1998), became the most influential voice calling for standards-based web design. The Web Standards Project (WaSP), founded in 1998, pressured browser makers to improve their CSS implementations and campaigned for web developers to abandon table-based layouts. Zeldman's book Designing with Web Standards (2003, New Riders) became the definitive manifesto of the movement, selling hundreds of thousands of copies and systematically making the case for semantic HTML and CSS layout.

The table-less design movement (2003–2005) was the practical outcome. Pioneering sites like the CSS Zen Garden (launched May 2003 by Dave Shea) demonstrated that pure CSS could produce visually stunning layouts without a single <table>, <font>, or spacer GIF. The Zen Garden presented the same HTML content styled with completely different CSS files, proving that presentation could be fully separated from structure. It became the most persuasive argument for CSS-based design and was cited in virtually every web design tutorial and textbook for the next five years.

Economics also played a role. As the web professionalized after the dot-com crash (2000–2001), clients began demanding sites that were accessible, search-engine-friendly, and maintainable. Table-based layouts were none of these things. A table layout was nearly impossible to maintain or redesign without rebuilding from scratch. CSS-based layouts could be completely restyled by changing a single stylesheet. For businesses paying web development agencies by the hour, the economic argument for standards-based design was compelling.

12. The 90s Web Design Revival

The aesthetics of 90s web design have returned — not as a failure of progress, but as a deliberate creative choice rooted in nostalgia, rebellion against design homogeneity, and a genuine philosophical movement about what the web should be.

The Y2K aesthetic trend, which peaked in fashion and graphic design around 2022–2024, extended naturally to web design. The visual language of the late 90s and early 2000s — metallic textures, bright gradients, pixelated graphics, chunky sans-serif fonts — became fashionable in advertising, album covers, and brand identities. Web designers adopted these elements with full knowledge of their history, creating sites that quoted the 90s aesthetic while being built with modern CSS Grid, variable fonts, and responsive design.

Neocities (neocities.org), founded by Kyle Drake in 2013 as a spiritual successor to GeoCities, has grown to host over 1.5 million websites. Many Neocities sites are explicitly designed in the 90s style, complete with tiled backgrounds, visitor counters, guestbooks, and navigation frames recreated with CSS. The platform provides free static hosting and encourages hand-coded HTML and CSS — a deliberate contrast to the WordPress/Squarespace/Wix ecosystem that generates most of the modern web.

Specific 90s design elements have been revived as modern tools and components:

• 88×31 pixel buttons — the standard size for "Best Viewed In" and webring badges — have returned as a linking convention among indie web creators. Sites display collections of these tiny buttons linking to friends, communities, and projects.
• Webrings have been rebuilt using modern web technologies. Webring.xxiivv.com and numerous smaller webrings connect indie web sites exactly as their 90s predecessors did.
• Hit counters have returned as both functional tools and ironic decoration. Libraries like react-retro-hit-counter render pixel-art counter displays in React applications.
• Guestbooks are back, with services like smartguestbook.com and self-hosted alternatives providing the same sign-and-leave-a-message functionality.

The IndieWeb movement provides the philosophical framework. IndieWeb advocates for personal website ownership, content federation, and open web standards as an alternative to centralized social media platforms. Many IndieWeb sites deliberately adopt retro aesthetics as a visual declaration of independence from the templated, algorithmic web. The glossary of web terminology on this site reflects the same philosophy: preserving the language and concepts of the original web for a new generation of developers.

The 90s web was chaotic, inconsistent, often ugly, and sometimes unusable. It was also deeply personal, endlessly creative, and built by millions of individuals who taught themselves HTML in order to have a presence on the most exciting new medium in a generation. The revival of its aesthetic is, in part, a recognition that something valuable was lost when the web became professional, uniform, and corporate — and that the best way to honor the original web is to keep building on it, one hand-coded page at a time.