Skip Main Navigation

20 reasons to drop IE8 like it's hot

August 15, 2015 · 30 min read

Ah, good ol’ IE8. I’m taking a break from the Learning ES6 series to talk about how we should stop supporting the browser that everyone loves to hate: Internet Explorer 8. The bane of our collective existence as web developers. Whether you’re a developer, designer or manager, you know you desperately want to stop supporting it. In this blog post I want to build a case against supporting IE8, examining empirical facts as well as qualitative feelings. My hope is that afterwards you will be well-equipped to make a compelling argument for dropping IE8 like it’s hot.

Despite the playful title of this blog post, this topic is serious business. I feel that we as developers are wasting our time supporting IE8. But there are very legitimate reasons why it’s still supported and why it’s difficult to stop supporting it. So instead of just having a soapbox bash-fest complaining about IE8, let’s instead treat this situation like a court case. We’ll present a case so compelling against IE8 that the judge (aka the boss) will have no choice but to rule in our favor. Cue that Law & Order music!


Microsoft’s Internet Explorer 8 was released way back in 2009 and yet many developers are saddled with the burden of supporting a browser so feature incomplete that it doesn’t support ES5 let alone HTML5, CSS3 or ES6. The main reason IE8 has lasted so long is because it’s the latest version of IE that will run on Microsoft Windows XP, arguably the most popular Windows operating system.

Because web surfers are unable to upgrade their OS, either because it’s personally too costly or their organization prevents them from doing so, many are stuck using IE8 and are unable to upgrade to a newer version of Internet Explorer. However, the latest versions of other browsers like Chrome or Firefox are still available on XP so it is possible for these users to use a modern browser. IE8 traffic is continuing to decline as well. Worldwide traffic across all devices is less than 2%. It would be even lower if the billion users in China were removed.

As any web developer still dealing with IE8 knows, building for, testing with, and debugging on Internet Explorer is pretty difficult. Time spent worrying about IE8 could be better spent building out cool new functionality on the modern browsers that can support it. That’s why sites like Google, The New York Times, SalesForce, and even Microsoft itself are all no longer supporting IE8, choosing to focus on building powerful new web experiences.

These reasons along with additional mounds of evidence should be enough to convince “the powers that be” that IE8 support should be dropped. And while we’re at it, we might as well drop support for IE9 and IE10 as well! They receive even less traffic than IE8.

Intrigued? Want the nitty gritty details? Keep on reading…

Opening Arguments

Any website created within the last couple of years probably didn’t bother worrying about IE8. They should count themselves lucky. Unfortunately for an older site, IE8 was the big kid on the block, so it had to be supported. And now dropping IE8 support has a tangible cost because it most likely will mean some amount of lost revenue over time.

By the time I left Zazzle, we were still “officially” supporting Internet Explorer 8 although it progressively received less and less love. There were continuous discussions about officially not supporting IE8, but it never got traction because IE8 still accounted for a (small) percentage of revenue.

When I arrived at Eventbrite in May, they had only just recently deprecated Internet Explorer 7! So a lot of my motivation for this blog post is to convince my team that we should go ahead and deprecate IE8 as well. There are just too many reasons why it should be dropped. And hopefully by also sharing these reasons publicly, we can quickly enter a world where IE8 is just a figment of our collective imaginations across the developer community.

At Eventbrite we have a much more formalized process around browser support and deprecation that I really like. Essentially we having a grading system for all browsers:

  • “A grade” - These browsers are supported sitewide. All flows should function according to design and there should be minimal to zero deviations in visual parity to the design. Progressive enhancement for CSS3 features is allowed. These browsers are actively tested.
  • “B grade” - All flows should function properly across the site and all content should be accessible. However, only “key” flows need to have visual design parity. These browsers are only occasionally tested.
  • “C grade” - Content on “key” flows should be accessible and the page shouldn’t look overtly broken. Design bugs in other parts of the site most likely will not be fixed. Only the “key” flows are tested.
  • “Unsupported” - If the page works, great! But don’t be surprised if there are many bugs. They won’t get fixed. They probably won’t be found because there’s no testing anyway.

Then there is a formal proposal process to downgrade a browser. Right now IE8 is a “B grade” browser with talks to downgrade to “C grade.” I would like to kick it all the way to “Unsupported” never to be seen again!

Unfortunately, you can’t just say “hey, let’s stop supporting IE8!” and it happen immediately. If your site has been supporting IE8 for years there will be real revenue lost by no longer supporting it. So in order to convince folks, you need to come armed with data and facts to present a compelling argument, especially for ecommerce sites where the revenue loss can be calculated directly.

Arguments for IE8

Before we bury Internet Explorer 8 under a mountain of evidence, let’s give it a chance to mount its own defense. It can explain why we’re at a place where we’re still supporting a browser in 2015 that was built in 2009 and why it’s not so easy to get rid of it.

Exhibit 1: Windows XP needs IE8

Microsoft Windows XP logo

Essentially what it boils down to is that Windows XP users cannot upgrade their Internet Explorer browser past IE8. Internet Explorer 9 won’t work on Windows XP. Furthermore, newer versions of Windows have either been terrible (like Windows Vista & Windows 8) or have much higher system requirements (like the new Windows 10). This means that XP users have trouble upgrading to an operating system that supports a higher version of Internet Explorer. Their only option is to get a newer computer, which is costly whether they are an individual or part of a company.

And speaking of companies, most IT departments at big organizations prevent employees from installing applications or new browsers. It’s a “security risk.” So even if a work employee wanted to switch to the browser they use at home, they wouldn’t be able to. Therefore they have to wait until their IT department first switches all computers onto a newer version of Windows. This is how we’re in a world where we have millions of people on a browser from 2009 running on an OS from 2001.

Exhibit 2: People are still using IE8

About 2% of Internet traffic worldwide comes from Internet Explorer 8. While that may not seem like much, what company wants to throw away 2% of revenues? In a world where an experiment (A/B test) is a success if it results in a conversion lift of just 2% and a failure if there’s any drop off in conversions, potentially losing 2% of traffic is a tough pill to swallow. Furthermore small percentage points of revenue can still be millions and millions of dollars being left on the table.

Arguments against IE8

The reasons for supporting Internet Explorer 8 are pretty significant, especially when you factor in the likely loss in revenue. But let’s take a look at the (many) reasons why we should no longer be supporting IE8. Once you’ve heard them all, you too will be convinced that they overcome the reasons in support of IE8.

Exhibit 1: IE8 is over 6 years old(!!!)

Internet Explorer officially debuted on March 19, 2009 and was actually widely praised. It initially started off feature-rich, but because it was never updated to add new features being added to other browsers, it quickly became outdated. Browsers age in dog years. Microsoft deserves the blame for choosing to only have major releases spread apart over years instead of continuous micro updates like the evergreen browsers of today.

In fact, IE8 doesn’t even have an auto-upgrade feature. IE8 users have to manually update their browser to IE9. It feels as if the developer community is always dragging along IE browsers because they have sizable market share, yet update so slowly. Thankfully this should be alleviated with the new Microsoft Edge browser.

Just for kicks, let’s look at what other browser were around back in early 2009 when IE8 was released:

  • Chrome - Version 2 (now 44)
  • Firefox - Version 3 (now 39)
  • Safari - Version 4 (now 8)
  • Opera - Version 9 (now 31)

Exhibit 2: Other (newer) browsers are available for WinXP

Now the defense mentioned that work employees are unable to upgrade their IE8 browser because of restrictions. That’s true, but not for everyone. Some people are just lazy. Others are ignorant to the fact that “Internet Explorer” and the “Internet” are not the same thing. The latest versions of Chrome, Firefox and Opera all run on Windows XP. They could switch! By the way, Apple stopped supporting Safari on Windows in 2009 so that’s why that’s not a viable option.

So for those users who are able to switch, but are just unaware that they can do so, sites can add a banner alerting those users to the fact that their browser is out of date and that they need to upgrade or switch to a different modern browser. The banner can even link to Browse Happy to list out their browser options.

Exhibit 3: IE8 has minimal traffic

Top 12 browser versions combining from Q2 to Q3 2015

The defense mentioned that IE8 makes up about 2% of traffic. Well, that’s a really tiny percentage! And in fact that actual number is 1.91% of worldwide traffic across all devices and is steadily dropping monthly according to StatCounter. It is the 8th most trafficked browser when you group the various Chrome and Firefox evergreen versions together. Other notable stats:

  • IE8 accounts for 2.55% of North American traffic and 2.72% in the U.S.
  • Europe’s IE8 traffic is 1.31% and Asia’s is 1.84%.
  • China may very well be the largest user base of IE8 at 5.45%
  • When just looking at desktop traffic, IE8 comprises 3.18%. It’s 4th after Chrome, Firefox & IE11
  • Not surprisingly Windows XP still makes up 6.21% of traffic

StatCounter provides a code snippet that web developers can put on their websites to track their traffic. It’s been around since before Google Analytics. Because they’re used on such a vast array of websites, they may be the best authority on global traffic numbers. Besides Google of course. But we’ll talk about Google in more detail in a little bit.

Of course what’s most important is a particular site’s own traffic distribution across browsers. It doesn’t matter if global IE8 traffic is less than 2% if a specific site’s traffic is 50% IE8. However, it’s more likely that a given site’s numbers are less than the worldwide numbers. As sites pay less and less attention to IE8 (even if it is “officially” supported), the site’s functionality progressively degrades in IE8, which in turn decreases its IE8 traffic. This is the case currently with Eventbrite. Our numbers are actually significantly less than the global numbers.

Exhibit 4: Traffic % and revenue % are not the same

Most sites track the success of their site by its conversion rate. A simplified explanation is that it is the number of people who successfully complete some important task divided by the total number of visitors to the site. That important task could be a purchase, click on an ad, share/like/post, etc.

Sites also have the concept of average order size (AOS). This is mostly used for ecommerce sites, but could still apply broadly. Essentially it answers the question: when a person purchases, clicks or shares, how much of it do they do? A person who spends $100 on a site is more valuable than someone who only spends $10 with each order.

It’s well-known that browsers on Apple devices tend to generate more revenue on ecommerce sites. This isn’t because Apple devices are better, but because of the demographic of users who own Apple devices. They, on average, have more money to spend. That’s how they have Apple devices in the first place! Now think about the demographic of users still stuck on IE8 and XP. Would you classify them as big spenders or otherwise highly active? Probably not.

Of course each individual site will have to look at their own data to see how things shake out. But contrary to what the defense would lead you to believe, a 2% loss of traffic from dropping IE8 probably will not mean a 2% loss in revenue. It will likely be much lower.

Exhibit 5: Other big companies have dropped IE8

In 2011, Google announced that their Google Apps services would “only support the latest version of Google Chrome as well as the current and prior major release of Firefox, Safari and Internet Explorer on a rolling basis.” Each time a new version of one of those browsers is released, they begin to “support the newly released version and stop supporting the third oldest version.” So in keeping with their plan, Google officially dropped support for Internet Explorer 8 on November 15, 2012 on the heels of the IE10 release. After that date, users accessing Google Apps service via IE8 got a message recommending that they upgrade their browser (see Exhibit 2).

Why did Google adopt this policy? Here’s their official statement:

At Google, we’re committed to developing web applications that go beyond the limits of traditional software. Our engineering teams make use of new capabilities only available in modern, up-to-date browsers which also provide improved security and performance.

At the end of 2013, Google announced that Google Analytics would stop supporting IE8. Google Analytics would of course still measure IE8 traffic, you just would no longer be able to reliably read your reports in IE8.

Other notable companies giving IE8 the boot:

But none of those companies can compare to Microsoft deciding to distance itself from IE8. It’s very own browser! On April 18, 2014, Microsoft ended support for Windows XP, begging users to upgrade to a modern operating system like Windows 8.1. This also unofficially ended support for IE8 as well; at least for IE8 running on WinXP. But Microsoft will officially stop supporting Internet Explorer 8 on January 12, 2016. At that point, there’s absolutely no reason for websites to continue to hang on. But we don’t have to wait until 2016! Drop it now!

Exhibit 6: Windows XP has security issues

Malicious hackers continue to exploit operating systems. Windows XP is one of their favorite playgrounds. And now that Microsoft has ended support for WinXP, any exploits found won’t even be patched! Shouldn’t this be enough motivation for IT departments still stuck on XP to final move to a new OS like Windows 10?

Microsoft on its official “stop using Windows XP” page listed the following potential risks of continuing to run Windows XP SP3 after support stopped on April 8, 2014:

  • Security. Without critical Windows XP security updates, your PC may become vulnerable to harmful viruses, spyware, and other malicious software which can steal or damage your business data and information. Anti-virus software will also not be able to fully protect you once Windows XP itself is unsupported.
  • Compliance. Businesses that are governed by regulatory obligations such as HIPAA may find that they are no longer able to satisfy compliance requirements. More information on HHS’s view on the security requirements for information systems that contain electronic protected health information (e-PHI) can be found here (HHS HIPAA FAQ - Security Rule).
  • Lack of Independent Software Vendor (ISV) support. Many software vendors will no longer support their products running on Windows XP as they are unable to receive Windows XP updates. For example, the new Office takes advantage of the modern Windows and will not run on Windows XP.
  • Hardware manufacturer support. Most PC hardware manufacturers will stop supporting Windows XP on existing and new hardware. This will also mean that drivers required to run Windows XP on new hardware may not be available.

Exhibit 7: Windows XP and https don’t mix (well)

HTTPS Everywhere logo

At Google I/O 2014, Google called for “HTTPS everywhere” on the web. Every site should provide extra security by running their entire site on https. Gone are the days when log-in and checkout were the only portions of the site in https. Google is also starting to use https as a ranking signal.

SHA-2 is now the standard for providing https encryption on the web. However, any SHA-2 encrypted website being viewed by IE8 running on XP SP1 or XP SP2 simply won’t work. It only works on Windows XP, Service Pack 3. And only because Windows added it to SP3 after the fact. Apparently Eventbrite ran into this very problem shortly before I started. As a result, Internet Explorer 8 on SP1 or SP2 was officially moved to “Unsupported.”

Exhibit 8: IE8 has no ECMAScript 5 support

As we learned in the History of ECMAScript blog post, ECMAScript 5 was released in December 2009, nine months after Internet Explorer 8. Therefore, IE8 doesn’t have any ES5 support. Quick overview on ES5 features lacking in IE8:

  • Strict mode
  • Array methods like indexOf, forEach, map & filter
  • Object methods like keys & create
  • String methods like trim
  • Function.prototype.bind
  • Reserved words as keys for object literals
  • Allowance for dangling commas (can be fixed by JS minifiers)
  • JSON parse & stringify (technically works but IE8 has to be in standards mode

We also learned in the Using ES6 right now blog post that the best way to use ES6 is to transpile it down to ES5. But IE8 doesn’t support ES5 So there’s a good chance that our transpiled code won’t be able to run successfully in IE8. Stop holding us back IE8!

Exhibit 9: IE8 has no HTML5 support

HTML5 logo

The fifth revision of the HTML standard (aka HTML5) was officially completed and released in October 2014. However a lot of its functionality had made its way to browsers long before. IE8 does not support any HTML5. Neither does IE9. IE10 only supports a little bit.

HTML5 introduced a number of new elements, new attributes on existing elements, and new native JavaScript APIs. According to, there are 42 different HTML5 features none of which IE8 supports. Here are some of the most popular ones:

A lot of these HTML5 features do come with JavaScript shims via external libraries, but those introduce more problems we’ll get to in Exhibits 14 & 15.

Exhibit 10: IE8 has no CSS3 support

CSS3 logo

Coupled with HTML5 was CSS3, which greatly expanded the expressiveness and capabilities of CSS. Many things that developers had to resort to coding in JavaScript could now be done more optimally in CSS. Here’s a tasty list:

Exhibit 11: IE8 has no ECMAScript 6 support

ES6 logo

Naturally if IE8 doesn’t support ES5, it’s definitely not going to support ES6. You can find the full features list in the Goals & Features of ECMAScript 6 blog post. And remember, since IE8 doesn’t support ES5 there’s a possibility that your transpiled ES6 code will not work in IE8 either. Way to hold the Web back, IE8…

Exhibit 12: Graceful degradation doesn’t work

Graceful degradation was a big promise in 2013 and 2014 during the big HTML5 hoopla. Web developers could start using new HTML5 and CSS3 features immediately because the old browsers that didn’t support them will gracefully ignore the functionality that it doesn’t understand. While this was technically true, in practice it really was not.

Graceful degradation worked well for what can be described as “icing” features. These features like input placeholders, rounded corners, and transitions. It didn’t work so well for “cake” features like layout. Flexbox made layout ridiculously easy with CSS3, but the “graceful degradation” result is a broken layout in IE8. So in order to not have a broken experience in a supported browser, we developers are left with float or inline-block hacks. Ugh.

Exhibit 13: Mobile first fails

Wireframe of a site on different sized devices

Mobile marketshare increases every month as more and more users access their favorite websites on their mobile devices. While StatCounter says about 40% of traffic is non-desktop, many sites are seeing more than half of their traffic come from mobile. This is why Luke Wroblewski pushed for mobile-first design way back in 2009, publishing his Mobile First book in 2011.

Even if we get mobile-first designs from designers, we still cannot implement mobile-first because of IE8. Ideally we would write our CSS such that the default styling is for narrow (mobile) screens. Then using media queries, we can write CSS for devices larger than narrow screens such as tablets. We could continue the process targeting large desktop screens and even huge TV screens.

But because IE8 does not support media queries (see Exhibit 10), we’re left with two sucky options. We write our CSS such that the default styling is for large screens and work our way down. This is effectively mobile-last implementation and usually results in overriding a lot of CSS rules to remove stylings not needed at smaller screen sizes. Our other option is to do a mobile-first implementation and have separate IE8-specific CSS. This results in a large amount of duplicate code between it and the CSS targeting the desktop screen sizes.

Exhibit 14: IE8 forces code bloat on modern browsers

I’ve already alluded to it in Exhibits 8, 9 & 13, but it’s worth focusing in on the problem of code bloat. Because IE8 doesn’t support so many features available in today’s modern browsers, many people have come up with workarounds:

  • Trick IE8 into thinking it has modern functionality via shims/polyfills (like eventie, classie & doc-ready)
  • Leverage libraries that provide the missing functionality
  • Detect via Modernizr that IE8 doesn’t have functionality so we can use fallback code (like Flash for HTML5 video)

All of these approaches result in additional code that would not be needed if IE8 had native support for the functionality. Modern browsers get all of this just-for-IE8 code as well even though they have native support. Modern browsers are heavier because of IE8.

Think about libraries like jQuery and underscore.js that are used so widely that they’re basically standard. But when you look at underscore.js’s API, a lot of its methods are just wrappers over what’s now become native functionality introduced with ES5 and ES6. But the library still needs to implement the functionality itself in JavaScript to support the browsers like IE8 that don’t have the native support. How much lighter would underscore.js be if it could rely on the native JavaScript support?

And what about jQuery? They introduced jQuery 2.0 back in 2013 and were able to shave off 12% of code simply by no longer supporting IE 6/7/8. This was a step in the right direction; moving the web forward. jQuery’s developers could stop worrying about IE8 and focus on evergreen browsers. However, jQuery announced jQuery 3.0 that is supporting two parallel codebases. The preferred jQuery 3.0 targets evergreen browsers and is the successor to jQuery 2. But there is also jQuery Compat 3.0, which succeeds original jQuery and continues to support legacy browsers. So much for the jQuery team not having to waste their time with IE8…

Exhibit 15: IE8 runs even slower emulating modern browsers

What happens when your site needs to display videos and in order to support IE8 you use a library that falls back “gracefully” from HTML5 video to Flash? What happens when an animation is critical to some site functionality so you have to resort to using jQuery instead of making use of CSS3 transitions? What happens when your site relies on geolocation and in order to support IE8 you need to include a large library that uses IP address location when the geolocation API is unavailable?

What happens when you try to get IE8 to support functionality that it was never intended to support? You throw a lot more code at it and it runs even slower! Think about all the extra CSS hacks needed to try to emulate CSS3 flexbox for IE8. Think about all the jQuery written by developers to simulate media queries, calc(), and HTML5 placeholders. Not only are we creating a bloated code base for modern browsers (revisit Exhibit 14), but we’re also slowing down the very browser we’re trying to support. It may be functional, but it’s barely usable.

Exhibit 16: UI frameworks aren’t supporting IE8

The proliferation of UI frameworks is what has enabled developers to keep building more complex websites. Everyone doesn’t have to reinvent their own wheel every time they build an app. One person (or a group of people) can invent a wheel and share it with thousands of people on Github.

The UI framework developers are also getting tired of having to support IE8. We already discussed jQuery, what they did with jQuery 2 and what they wish they could do with jQuery 3. But it’s not just jQuery. Other frameworks are dropping IE8 as well:

All of them cite wanting to “move forward” and “not be slowed down” by having to support such a legacy browser.

Exhibit 17: Testing IE8 is a pain

Ideally if you officially support a browser, you should test features on that browser before shipping it to your users. That’s not so easy with older versions of Internet Explorer, including IE8. How does one get their hands on a 6-year-old browser? A Microsoft-supplied virtual machine of course! We at least have to applaud Microsoft for providing a way for developers, particularly those not on Windows, to test IE browsers.

But even if you are able to get a multi-gigabyte VM running or even if you are able to use IE11 and change the document mode down to IE8, you’re still testing on IE8! It’s just another browser to have to test. As a result, it doesn’t get tested in development. And unless it’s a big feature, it probably won’t get tested during QA either. More than likely it’ll be users calling into Customer Support who will first notice the IE8-specific issue.

Exhibit 18: Debugging visual issues in IE8 is a pain

Screenshot of IE7 tax site

As a developer, which would you rather be doing? Debugging why a <div> that should have some height is collapsed in IE8, or moving on to the next new feature? Yeah, I thought so. In my opinion, the debugging tools in IE browsers are subpar compared to other browsers. And this is particularly true for IE8 and debugging CSS.

The cost in having to fix bugs in a legacy browser is real. So real that a company called Kogan in Australia implemented the world’s first Internet Explorer 7 Tax back in 2012 for IE7 users. At the time, they added a 6.8% surcharge on all purchases “by anyone still insistent on using the antique browser.”

Exhibit 19: IE has a bad rep

Screenshot of "Break up with Internet Explorer 8" site

All Internet Explorer browsers now have a bad reputation for being terrible browsers. IE11 is actually a pretty good browser. It is as standards compliant as the other modern browsers, but because of IE8 (and its predecessors) it still has the “IE stench.” That “stench” is so strong that Microsoft is completely forgoing the Internet Explorer name and rebranding its new browser as Microsoft Edge. Edge will be an evergreen browser so it’ll always be up to date with the latest features.

But we’re still stuck with IE8, much to the disdain of web developers worldwide. So in order to publicly share their disgust, Break Up with IE8 was born. There you can share your IE8 break-up letter with the public.

Exhibit 20: Once IE8 goes, so does IE9 & IE10!

Let’s end on a positive note. If we look back at StatCounter’s global traffic numbers, IE8 actually had more traffic than IE9! And IE9 had more than IE10. The vast majority of IE9 and IE10 users can upgrade to IE11 and have already done so. The only real reason to support IE9 & IE10 right now is because we’re still supporting IE8. But after these compelling arguments, IE8 is all but out the door. And it might as well take IE9 and IE10 with it.

This means that if we drop IE8 (and IE9 & IE10 with it), we only need to support IE11 and Edge. We’ll now all be on the Google support policy. And with Microsoft giving away free upgrades to Windows 10, soon most people will be on Microsoft Edge as well. If Microsoft gets its way and everyone quickly gets on Edge, we only need to actively support 5 browsers: Chrome, Firefox, Safari, Opera, and Edge. What a wonderful world that would be!

Closing Arguments

If you’ve actually read this far, congratulations! You’ve definitely been inundated with more evidence than you thought you ever needed. It’s pretty much an open and shut case, right? Now what’s left is for the judge (aka the boss) to rule in favor of dropping IE8. All I ask is that you celebrate the verdict in style. It’s certainly well-earned.

Now my personal objective is to take this evidence to my team at Eventbrite and try to get IE8 kicked completely off the supported list. Let’s just skip the whole “C browser” stage altogether. We can make IE9 the “C browser” and IE10 the “B browser,” even though I’d prefer that they all get kicked off of the list. Wish me luck! I’ll report back with updates.

Feedback? Additions? Differing opinion? Feel free to leave a comment or tweet me @benmvp.

Subscribe to the Newsletter

Get notified about new blog posts, minishops & other goodies

Hi, I'm Ben Ilegbodu. 👋🏾

I'm a Christian, husband, and father of 3, with 15+ years of professional experience developing user interfaces for the Web. I'm a Frontend Architect at Stitch Fix, frontend development teacher, Google Developer Expert, and Microsoft MVP. I love helping developers level up their frontend skills.

Discuss on Twitter // Edit on GitHub