Firefox Hardware Report for Web Developers

Suppose you’re developing a sophisticated web game or application, and you’re wondering — will it actually be able to run? What hardware should I be targeting to get the widest possible audience? Existing hardware reports (such as those from Valve and Unity) are excellent, but represent a different group of hardware users than the majority of people who use the web.

We’ve been working on the next-generation web game platform for years now, and often receive questions from web developers about the hardware market. Today we’re releasing the Firefox Hardware Report to help answer those questions and inform your development decisions.

On this site you’ll find a variety of data points showing what hardware and OSes Firefox web users are using on the web, and trends over time. This includes CPU vendors, cores, and speeds; system memory; GPU vendors, models, and display resolution; Operating System architecture and market share; browser architecture share, and finally, Flash plugin availability. Some charts (such as the GPU models) have an expanded view showing all of the models captured. You’ll also discover all sorts of interesting stats — like 30% of Firefox users have 4 GB of RAM; that Intel makes 86% of users’ CPUs and 63% of their GPUs; or that the most popular screen resolution (with 33% of users) is 1366×768.

Firefox Hardware Survey

The Firefox Hardware Report is a public report of the hardware used by a representative sample of the population from Firefox’s desktop release channel. The source data for the Hardware Report was collected through the Firefox Telemetry system, which automatically collects browser and platform information from machines using Firefox. We use this data to prioritize development efforts and to power this report.

Once data is collected, we aggregate and anonymize it. During the aggregation step, less common screen resolutions and OS versions are handled as special cases — resolutions are rounded to the nearest hundred and version numbers are collapsed together in a generic group. Any reported configurations that account for less than 1% of the data are grouped together in an “Other” bucket. At the end of the process, the aggregated, anonymized data is exported to a JSON file and published on the report website.

To learn more about how we created this report, take a look at our blog post on the Mozilla Tech Medium. The code used to generate the reported data and website is available on GitHub.

This is just our first step, and we hope to expand this data set over time. In the meanwhile, please let us know what you think — is this data useful? What other data points might be helpful in the future? Do you have visualization suggestions? We look forward to your email feedback, with thanks!

About Andre Vrignaud

Andre Vrignaud works as Mozilla's VR, AR, and Games Platform Strategist, with a focus on empowering web developers, publishers, and tool creators by enabling high-end, plugin-free games and WebVR experiences on and across billions of connected devices. With a side of net neutrality and privacy advocacy.

More articles by Andre Vrignaud…

About Rebecca Weiss

Rebecca is the manager of the Product Data Science team for Firefox. Her team aims to add a dose of empiricism to product strategy and also advance the state of data literacy about the web and beyond.

More articles by Rebecca Weiss…


2 comments

  1. Mehdy

    It would be great if browsers could also report antivirus status so websites can alert users.

    December 15th, 2016 at 21:21

  2. J. Lester Novros II

    I’d be interested in seeing stats for fuill screen browser windows in resolutions upwards of, say, 1280×1024.

    December 18th, 2016 at 07:28

Comments are closed for this article.