Graphed LogoGraphed
Graphed LogoGraphed
How It WorksAgentsIntegrationsPricing

How to Check Looker Version

Cody Schneider••7 min read

Finding your Looker version number might seem like a small detail, but it’s often the first step in troubleshooting an issue, checking feature compatibility, or getting help from support. This guide will show you several easy ways to find your exact Looker version number and explain why this information is so important to have handy.

GraphedGraphed

Build AI Agents for Marketing

Build virtual employees that run your go to market. Connect your data sources, deploy autonomous agents, and grow your company.

Watch Graphed demo video

Why Does Your Looker Version Matter?

Before we jump into the "how," let's quickly cover the "why." Knowing your version number is more than just a piece of technical trivia. It’s a critical piece of information that impacts your entire experience with the platform.

1. Feature Availability and Compatibility

Looker is constantly evolving, with new features, visualizations, and updates being rolled out regularly. Access to these new capabilities is directly tied to the version of Looker you're running. If you read about an exciting new visualization type in the release notes but can't find it in your instance, there's a good chance you’re on an older version. Knowing your version helps you understand what's available to you and what you need to do to access the latest tools.

2. Bug Fixes and Security Patches

Software development is an iterative process, and bugs are an inevitable part of it. Every Looker release includes a list of bug fixes and, more importantly, security patches. If you experience an unexpected glitch or odd behavior, checking the release notes for your version (and subsequent versions) can confirm whether it's a known issue that has since been fixed. Running an outdated version could leave your instance exposed to security vulnerabilities that have already been patched by the Looker team.

Free PDF · the crash course

AI Agents for Marketing Crash Course

Learn how to deploy AI marketing agents across your go-to-market — the best tools, prompts, and workflows to turn your data into autonomous execution without writing code.

3. Support and Troubleshooting

If you ever need to contact Looker support or ask a question in a community forum, one of the first things they will ask for is your instance's version number. Different versions can have different behaviors and bugs. Providing your version number from the start gives support staff the exact context they need to diagnose your problem effectively, saving you a lot of time and back-and-forth communication.

4. Environment Consistency for Developers

For development teams, maintaining consistency between different environments (like staging and production) is vital. A developer might be working on new LookML in a staging environment running the latest version, but if the production instance is several versions behind, the new code might not work as expected when deployed. Knowing and aligning the versions across environments prevents these kinds of compatibility surprises.

Method 1: The Easiest Way for Any User (The Help Menu)

This is the most straightforward method and is accessible to every user, regardless of their permission level. If you just need the version number quickly, this is the way to go.

Follow these simple steps:

  • Step 1: Open the User Menu. In the top-right corner of the Looker interface, click on your profile icon. This will open a dropdown menu with several options.
  • Step 2: Select 'Help'. Near the bottom of the dropdown menu, click on the Help option.
  • Step 3: Find Your Version Number. A new panel or pop-up will appear. Your Looker version number will be clearly displayed, typically near the top. It will be a series of numbers separated by periods, like 24.4.2 or something similar.

That's it! In just three clicks, you have the exact information you need.

Method 2: For Administrators (The Admin Panel)

If you have admin permissions in Looker, you have another reliable way to find the version, which also provides a wealth of other information about your instance's health and configuration.

Here’s how to do it:

  • Step 1: Navigate to the Admin Section. From the main navigation menu (usually on the left), select Admin.
  • Step 2: Go to the 'Overview' Page. Under the Server subsection, click on Overview. On some older versions, you might find this under a "General" or similar page.
  • Step 3: View the Version and Instance Details. The Overview page acts as your instance's control panel. It will display crucial system information, including internal database details, user counts, and prominently, the Looker Version.

This method is excellent for admins because it places the version number in the context of other important system statistics, making it a great page to bookmark for routine system health checks.

GraphedGraphed

Build AI Agents for Marketing

Build virtual employees that run your go to market. Connect your data sources, deploy autonomous agents, and grow your company.

Watch Graphed demo video

Method 3: For Developers (Using the Looker API)

For more technical users, developers, or anyone looking to automate processes involving Looker, checking the version programmatically via the API is the most efficient method. This is perfect for scripts that need to verify compatibility before running or for a system that logs the health of multiple Looker instances.

You can query the /versions endpoint to get what you need.

Prerequisites:

You’ll need API credentials to authenticate your request. You can generate these in the Admin > Users section by editing your user profile, provided you have the necessary permissions.

Using a cURL Command

You can make a simple call from your terminal to get the version information. Replace your your.looker.instance.com with your Looker instance URL and YOUR_API_TOKEN with your unique access token.

curl -X GET -H "Authorization: token YOUR_API_TOKEN" "https://your.looker.instance.com:19999/api/4.0/versions"

The API Response

The API will return a JSON object containing details about the Looker API and, most importantly, the release version of your instance.

{
  "looker_release_version": "24.4.2",
  "current_version": {
    "version": "4.0",
    "full_version": "4.0.24.4",
    /* ... other API details ... */
  },
  "supported_versions": [
    /* ... list of supported API versions ... */
  ]
}

The value you're looking for is looker_release_version.

Free PDF · the crash course

AI Agents for Marketing Crash Course

Learn how to deploy AI marketing agents across your go-to-market — the best tools, prompts, and workflows to turn your data into autonomous execution without writing code.

Using the Built-in API Explorer

If you’re not comfortable with the command line, Looker has a built-in tool that makes this easy. Navigate to Admin > API. This interactive interface lets you test any API endpoint. Search for the "Version" endpoint, click Run It, and you'll see the same JSON response directly in your browser.

What Do the Looker Version Numbers Mean?

Looker follows a straightforward versioning system: YY.M.P.

  • YY: The year of the major release (e.g., 24 for 2024).
  • M: The number of the release within that year. They are released on a regular cadence, so 24.4 represents the fourth release of 2024.
  • P: The patch number. This number increments for small updates that address bugs or security fixes within a major release. For instance, 24.4.1 is the first patch applied to the 24.4 build.

You may also hear about Extended Support Release (ESR) versions. These are specific versions that Looker supports with bug fixes for a longer period, making them a good choice for organizations that prefer stability over having the absolute latest features.

What to Do After You Find Your Version

Once you have your version number, what’s next? Here are a few practical steps you can take:

  1. Check the Official Release Notes: Google "Looker X.Y release notes" (inserting your version number) to find the official documentation. This will give you a complete list of new features, changes, and bug fixes introduced in your version. It's the best way to understand what's different if you've recently upgraded.
  2. Diagnose Issues: If you're experiencing a problem, cross-reference the release notes for your version to see if it's a documented known issue or if it was fixed in a later release.
  3. Plan an Upgrade: If you find you’re several versions behind, you can work with your instance administrator to plan an upgrade. Looking at the release notes for subsequent versions will help you build a case by highlighting the new features and security improvements you're missing out on.

Final Thoughts

Whether you’re a regular user, an admin, or a developer, knowing how to find your Looker version is a fundamental skill. Using the Help Menu, the Admin Panel, or the API, you can quickly find this information and use it to troubleshoot an issue, plan an upgrade, or explore new features.

For Looker users, getting performance data into a dashboard is second nature, but stitching together data from other marketing and sales tools can feel like a return to the dark ages of spreadsheets. We’ve designed a much simpler way to handle this. You can connect sources like Google Analytics, Shopify, and Salesforce and then use simple, natural language to create the exact report you need in seconds with Graphed. It automates away the manual report-building drudgery, freeing you up to focus on the insights, not just the setup.

Related Articles