Google Blink HTML Easter Egg: The Flashing Tribute to a Dead Tag
Search “blink html” (or type <blink>) on Google and watch every occurrence of the words “blink” and “HTML” in your search results flash on and off. It is a CSS-animated tribute to the legendary deprecated <blink> tag from the 1990s web — and it still works in 2026.
There is a moment, right after you hit Enter on “blink html” in Google Search, where the results page starts doing something odd. Words flicker. Not all words — just the words “blink” and “HTML,” scattered through titles and descriptions, pulsing in and out of visibility like a slow heartbeat. It is subtle enough to be confusing the first time. Then you remember the old web, and you smile.
This is one of Google’s quietest Easter eggs, and one of its most historically meaningful. The <blink> tag was the internet’s first great visual gag — invented in the mid-1990s, beloved by early website builders, despised by designers, and eventually killed off by every major browser. Google never forgot it. Every time someone searches for it, the ghost of the blinking web comes briefly back to life.
Triggering
How to Trigger the Google Blink HTML Easter Egg
This egg works on desktop and mobile, in Chrome, Firefox, Safari, and Edge. You do not need to be logged in, and there is no time limit on the effect.
- Open google.com in any browser.
- Type blink html in the search bar. You can also type the literal tag: <blink>.
- Press Enter or tap the search button.
- Watch the results page. The words “blink” and “HTML” in result snippets and titles will flash on and off in a slow, regular rhythm.
- Scroll down — the effect applies to every result on the page, not just the top few.
Pro tip: The blinking is most visible in the snippet text below each result title, where “blink” often appears in context quotes. The words “HTML” in page titles also pulse. The best place to watch it is on results from HTML reference sites where both words appear together repeatedly.
The companion Easter egg is just as interesting: search “marquee html” and Google will make the result count at the top of the page scroll horizontally — a tribute to the <marquee> tag that was the <blink> tag’s equally-reviled sibling from the same era.
What Is Actually Happening? (It’s Not the Real Tag)
A common misconception, repeated on many websites, is that Google somehow enables the actual <blink> HTML element in search results. That is not what happens. The real <blink> tag has been non-functional in all major browsers since Firefox removed it in version 23 (August 2013). Chrome never supported it. Safari never supported it. It was never in the W3C HTML specification.
What Google actually does is inject a CSS animation on matching text when it detects this specific search query. The technical mechanism is a variation of this pattern:
/* CSS recreation of the blink effect — safe, modern implementation */ @keyframes blink-effect { 0%, 100% { visibility: visible; } 50% { visibility: hidden; } } .blink-term { animation: blink-effect 1s step-end infinite; }
This approach uses visibility: hidden (not display: none, which would cause layout shifts), applies it in one-second cycles, and uses step-end timing to create the characteristic hard on/off flash rather than a smooth fade. It matches the original behavior of the real <blink> tag almost exactly.
Key accuracy point: Google does not use the <blink> HTML element in search results. Competitors who claim otherwise are wrong. The effect is a CSS animation applied by Google’s search JavaScript when it recognizes the query. The real <blink> element does nothing in any modern browser.
The History of the <blink> Tag
The story of the <blink> tag begins in a bar in Mountain View, California, sometime in 1994. Lou Montulli, an engineer at Netscape Communications, was out with colleagues after a conference. He mentioned, apparently as a joke, that the only text effect the terminal he was using could not do was blinking text. A colleague thought it was the funniest thing she had heard. The next morning, Montulli implemented it as a quick weekend hack. He never meant for it to go out in a production browser.
It went out in a production browser.
Netscape Navigator included <blink> starting with version 1.0, and early web developers seized on it with enthusiasm. Without CSS, without JavaScript-based animation, and without much else in the way of visual interest, the ability to make text flash was genuinely novel. Fan sites, early e-commerce pages, and university home pages across the early web pulsed and flickered with the tag’s output.
The backlash was equally fast. Jakob Nielsen, the web usability researcher, called <blink> “the most loathed element on the web.” Web designers routinely listed it alongside <marquee> as the two HTML elements that most reliably signaled an unprofessional site. The tag became a shorthand for everything garish and amateurish about early web design.
The Netscape vs. Microsoft Bargain
In February 1996, the browser wars were at their peak. Netscape and Microsoft were competing feature-for-feature, and both companies were implementing tags the other did not support. According to multiple accounts, there was an informal understanding at the time: Netscape would ship <blink> and Microsoft would ship <marquee>, each adding a novelty tag the other browser would not recognize. Neither tag was ever submitted to the W3C for standardization. Both were implemented in individual engines and both became notorious.
Internet Explorer never supported <blink>. The WebKit engine (Safari, and later Chrome’s Blink fork) never supported it. Only Gecko-based browsers (Firefox, Netscape, early Opera) ever rendered it. This means the tag was never truly cross-browser and always produced inconsistent results — blinking in Firefox, invisible in IE, blinking again in Firefox 22, then silent forever from Firefox 23 onward.
When Was the <blink> Tag Finally Removed?
| Browser | Support for <blink> | Removed / Never Supported |
|---|---|---|
| Netscape Navigator | Full support from version 1.0 (~1994) | Discontinued 2007 |
| Firefox | Supported until version 22 | Removed in Firefox 23 (August 2013) |
| Internet Explorer | Never supported | N/A |
| Safari / WebKit | Never supported | N/A |
| Chrome / Blink | Never supported | N/A |
| Edge (modern) | Never supported | N/A |
The W3C HTML5 specification formally marked <blink> as obsolete. It remains recognized as a token in the HTML parsing algorithm (so browsers do not throw errors on it) but renders no visual effect in any current browser.
Accessibility Warning: The Real Reason Blink Text Was Banned
The web design community’s rejection of <blink> was not purely aesthetic. There is a legitimate medical reason why flashing content is restricted on the modern web.
WCAG 2.2, Success Criterion 2.2.2 (Pause, Stop, Hide) requires that any content that blinks for more than five seconds must have a mechanism for the user to pause, stop, or hide it. The <blink> tag provided no such mechanism. It could not be paused. It could not be stopped except by closing the tab.
More critically, rapidly flashing content can trigger photosensitive epileptic seizures. WCAG 2.3 (Three Flashes or Below Threshold) addresses this directly, requiring that nothing flash more than three times per second. The original <blink> tag typically fired at roughly one flash per second — which falls under the threshold for seizure risk — but many amateur implementations varied widely in rate.
Accessibility note: Google’s Easter egg blinks at a safe, slow rate (approximately once per second) and is triggered only briefly on a single search query. However, if you recreate the blink effect in CSS for a real website, always include a prefers-reduced-motion override and a user-accessible pause control. Users with vestibular disorders, migraines, or photosensitive conditions may find any blinking content uncomfortable.
How to Safely Recreate Blink in CSS Today
If you want to use the blink effect in modern web development — for a retro themed project, a demo, or an educational page — here is the accessible way to implement it:
/* Accessible CSS blink — respects user motion preferences */ @keyframes blink-safe { 0%, 100% { visibility: visible; } 50% { visibility: hidden; } } .retro-blink { animation: blink-safe 1s step-end infinite; } /* Critical: disable for users who prefer reduced motion */ @media (prefers-reduced-motion: reduce) { .retro-blink { animation: none; } }
The prefers-reduced-motion media query checks the operating system’s “Reduce Motion” setting (available on macOS, iOS, Android, and Windows). When a user has enabled this preference, the animation is disabled entirely. This is the single most important accessibility addition for any animating content.</p<>figure class=”dbr-fig”>
The Blink Easter Egg vs. Other Google Visual Easter Eggs
| Easter Egg | Query | Visual Effect | Status 2026 |
|---|---|---|---|
| Blink HTML | blink html | Words “blink” and “HTML” flash in results | ✅ Active |
| Marquee HTML | marquee html | Result count scrolls horizontally | ✅ Active |
| Do a Barrel Roll | do a barrel roll | Entire page rotates 360° | ✅ Active |
| Askew / Tilt | askew | Page tilts at a slight angle | ✅ Active |
| Google in 1998 | google in 1998 | Results styled like 1998 Google interface | ✅ Active |
What makes the blink Easter egg stand out in this company is its specificity. The other visual effects transform the entire results page. The blink egg surgically identifies individual words in the content and animates only those — a technically more complex implementation that required Google engineers to intentionally write and maintain a CSS injection rule keyed to a specific query.
More Google Easter Eggs Worth Trying
Why Google Keeps This Easter Egg Alive
The web development community has a complicated relationship with <blink>. It is simultaneously a punchline and a piece of history — proof that the early web was built by people who thought the medium should be fun, not just functional. Lou Montulli, who invented it, has given interviews describing the moment the tag went live as one of the unintended consequences of his career. He has also said, with evident good humor, that he has made peace with it.
Google engineers have always included people who came of age on the 1990s web. The decision to honor <blink> with a search Easter egg fits a pattern: these are the same people who brought back Pac-Man as a search result, who trigger a pixel-perfect barrel roll when you type a Star Fox quote, and who keep a functional version of the old Google interface available by searching “Google in 1998.” The blink Easter egg is a wink at web history from people who lived it.
There is also a practical reason to keep it: it works perfectly as a teaching demonstration. A developer showing a class why certain HTML elements were deprecated can type “blink html” into Google and instantly show what the tag did, in motion, without needing to find a running Netscape Navigator installation or spin up a legacy browser environment.
Frequently Asked Questions
Does the Google blink HTML Easter egg still work in 2026?
Yes. As of October 2026, searching “blink html” on Google triggers the Easter egg on the results page, causing the words “blink” and “HTML” to flash in all result snippets and titles. It works on desktop and mobile.
Does Google actually use the <blink> HTML tag in search results?
No. Google simulates the blinking effect using CSS animation. The real <blink> element has been non-functional in all modern browsers since Firefox removed it in version 23 (August 2013). Chrome and Safari never supported it. Google’s approach injects a CSS keyframe animation that mimics the on/off flash of the original tag.
Who invented the <blink> tag?
Lou Montulli, an engineer at Netscape Communications, created the <blink> tag in the mid-1990s. He has described it as a weekend hack he never intended to ship. It went out in Netscape Navigator and became one of the most recognizable — and controversial — HTML elements of the early web era.
When was the <blink> tag removed from browsers?
Firefox removed the <blink> tag in version 23, released in August 2013. It was never supported by Internet Explorer, Safari/WebKit, or Chrome/Blink. The W3C HTML5 specification formally marked it as obsolete, though browsers still parse the token without errors — they just render no visual effect.
What does the companion “marquee html” Easter egg do?
Searching “marquee html” on Google causes the result count at the top of the search page (the “About X results” line) to scroll horizontally across the page, mimicking the behavior of the <marquee> HTML tag — the other infamous 1990s novelty element invented by Microsoft for Internet Explorer.
Does the Google blink Easter egg work on mobile?
Yes, the blink HTML Easter egg works on mobile browsers. Search “blink html” in the Google app or a mobile browser and the result words will flash just as they do on desktop. The CSS animation Google uses is fully cross-platform.
Is flashing content safe for all users?
Google’s implementation blinks at approximately once per second, which is below the threshold (three flashes per second) that WCAG 2.3 identifies as a seizure risk. However, users with photosensitive epilepsy, vestibular disorders, or migraine sensitivities may still find any blinking content uncomfortable. The effect disappears when you navigate away from the search results page.
Was the <blink> tag ever in the W3C HTML standard?
No. The <blink> tag was never part of any W3C HTML specification. It was a proprietary Netscape extension, implemented in Gecko-based browsers only. HTML5 acknowledged its existence as a parsing token to ensure backward compatibility, but marked it as an obsolete feature that should not be used.
What is the CSS code to recreate the blink effect safely?
A safe, accessible CSS recreation uses keyframe animation on visibility: @keyframes blink { 50% { visibility: hidden; } } combined with animation: blink 1s step-end infinite on the target element. Always include a @media (prefers-reduced-motion: reduce) override that sets animation: none, so users who have enabled their OS’s reduced-motion setting see static text instead.
What other text-related Google Easter eggs are there?
Beyond blink html and marquee html, Google has several query-based Easter eggs. Searching “askew” or “tilt” tilts the entire results page at an angle. Searching “do a barrel roll” spins the page 360°. Searching “recursion” prompts “Did you mean: recursion” — which links back to the same results page. Searching “anagram” returns “Did you mean: nag a ram.”
Found Your Inner 1990s Webmaster?
There are 17 more Google Easter eggs waiting to be triggered — from space battles to coin flips.
Summary
The Google blink HTML Easter egg is a small, quiet tribute to a large, loud chapter of web history. Search “blink html” and the results page becomes a brief time machine, flashing the way early websites once did before designers and accessibility standards agreed that making text strobe was probably a bad idea.
What makes the egg worth knowing about in 2026 is not just the fun of seeing it — it is the technical detail behind it. Google did not resurrect a dead HTML element. Instead, engineers wrote and maintain a live CSS animation that simulates the effect, applied specifically when this query is detected. It is a considered, deliberate piece of engineering in service of a nostalgic joke. The early web deserves no less.
Sourced Sources: Search Engine Land, Mozilla Developer Network (MDN Web Docs), W3C HTML5 Specification, TimWorks and Timeworks YouTube channel transcripts, WCAG 2.2 Success Criteria 2.2.2 and 2.3.1, Lou Montulli personal accounts cited in Netscape engineering histories.