What's my Baseline?

Jeremy Wagner

Published: August 7, 2025

Feature adoption on the web has long been a problem for developers. Quite often, web developers and related project stakeholders have a heightened sense of risk when adopting new features: How recently was the feature released? What specific browser versions is it supported in? Will our users experience problems if we adopt the feature?

Baseline was introduced to help solve these problems by giving developers targets they can use. We've discussed how to choose a Baseline target for your application, as well as how you can set your chosen target (including a step-by-step codelab). By selecting a target that aligns with your project's goals and user base, adoption of new features—even newer features—avoids the headache of tracking specific browser versions, mapping that to user data, and deciding which specific features make the cut.

There are many targets you can choose—including the moving Baseline Widely available target, which generally has wide support—but we're embarking on an awareness campaign this month to see what Baseline target you're selecting for your project, and how you got there!

To get started:

  1. Read the guide on how to select your Baseline target to learn how the process works.
  2. Use the data at your disposal—such as your Google Analytics data and the Google Analytics Baseline checker tool, for example—and determine which target has the best balance between user support and the features you would like to use.
  3. If you can't use Google Analytics data, consider using what analytics data you do have to create your own custom tooling to determine support across Baseline targets. The baseline-browser-mapping package can help you with this. For an idea of how this works, you can see how baseline-browser-mapping package is used by the Google Analytics Baseline checker tool to do this.
  4. As a last resort, you can use data on Baseline targets from RUM Archive as a source of information for choosing your own Baseline target.
  5. Once you've selected your Baseline target, share your results by posting on LinkedIn, X, or Bluesky with the hashtag #WhatsMyBaseline.

If possible, we'd also like to hear about the process you used to select your Baseline target, particularly about the support threshold that mattered most to you, and how that related to the features you wanted to use and your application's audience.

We're excited to see how developers and related project stakeholders will respond to this campaign, and how it can inform how we here at Chrome talk about Baseline by seeing real implementations of it in projects across the web!