Version support

Today
Metabase 63
Metabase 62
Metabase 61
Metabase 60
Metabase 59
Metabase 58 (LTS)
Metabase 57
Metabase 56
Metabase 55
Metabase 54
202520262027
LTS releaseStandard releaseToday

Support dates

VersionReleasedEnd of life
Metabase 63July 7, 2026September 7, 2026
Metabase 62June 1, 2026September 1, 2026
Metabase 61April 30, 2026September 1, 2026
Metabase 60March 26, 2026September 1, 2026
Metabase 59February 12, 2026September 1, 2026
Metabase 58 (LTS)December 17, 2025February 17, 2027
Metabase 57November 1, 2025May 31, 2026
Metabase 56August 1, 2025May 31, 2026
Metabase 55June 2, 2025May 31, 2026
Metabase 54March 25, 2025May 31, 2026

Grayed-out versions have reached end of life and no longer receive updates.

  • Every Metabase release receives bug fixes and security updates until its end-of-life (EOL) date.
  • Long-Term Support (LTS) releases have longer lives: LTS versions are supported for 14 months, while non-LTS versions usually EOL after 2 months.
  • If you’re on Metabase Cloud, we handle all the upgrades for you. Let us know if you’d like to pin your Metabase to the LTS version.

Metabase release versioning

We follow our own flavor of the semantic versioning guidelines. Standard semantic versioning uses Major.Minor.Patch format, but we’ve adapted it to distinguish the open-source version of Metabase from the paid, source-available version of Metabase (available in the Pro and Enterprise plans).

With Metabase releases, we prefix the version with a 0 or 1, depending on the license.

The Metabase version schema

License.Major.Minor.Patch

For example, v0.63.3.1 would be for a patch (1) for the third (3) minor release of Metabase 63, the open-source edition (0).

License

  • 0 for the free, open-source version (sometimes called OSS, for open-source software).
  • 1 for the “Enterprise Edition”, the source-available version of Metabase that ships with bells and whistles you can unlock with a Pro or Enterprise plan. This is also the version we run for Metabase Cloud’s Starter plan (though without the pro features enabled).

Major

We release major versions when we introduce new features or breaking changes. See release announcements.

Minor

We issue minor releases when we add bug fixes and refinements to existing features. See the changelog.

Patch

We automatically issue patch releases nightly so we can fix bugs or security issues as soon as we can.

.x releases

You’ll see releases ending as .x in releases on GitHub. These are placeholder links. The actual link will go to the latest patch. For example:

  • metabase/metabase:v0.63.2.x will automatically pull the latest patch version in for the minor version {latest}.2 (like v0.63.2.1, v0.63.2.2, etc.).

  • metabase/metabase:v0.63.x will automatically pull the latest patch version in for latest minor version.

We do not recommend using mutable tags like .x in production

Other release terms

The beta release

The beta release is the beta release of a new major version of Metabase. So for Metabase version 63, the beta releases would be:

  • v0.63.0 (the OSS version)
  • v1.63.0 (the EE version)

The gold release

The gold release is the first stable release of a new major version of Metabase. So for Metabase version 63, the gold releases would be:

  • v0.63.1 (the OSS version)
  • v1.63.1 (the EE version)

Cloud builds

If you see a version followed by an -X, like v1.63.2-X01, these are version numbers related to builds for customers on Metabase Cloud.

Docs for each release

See a list of docs for all major versions.

Further reading