Pimcore versions, support and end of life

Pimcore ships the core package pimcore/pimcore and its modules as platform versions such as 2025.4 or 2026.3. This page maps every platform version to its core version and gives the end dates for free community support and for Long-Term Support (LTS), plus first release and PHP requirement. Every value comes from the Pimcore documentation or from package metadata. Checked on October 1, 2026.

Short answer

• The newest platform version is 2026.3, released on 2026-09-29 (Packagist, metapackage pimcore/platform-version, Measured).
• Pimcore 11 has LTS only in platform version 2024.4 (core 11.5), until December 2026 (Pimcore docs, Platform Versions, Measured).
• Pimcore 12 has LTS in platform version 2025.4 (core 12.3) until December 2028 (Pimcore docs, Platform Versions, Measured).
• In 2026, Pimcore includes LTS only in the Enterprise and Enterprise PaaS editions (Pimcore docs, Measured).
• According to Pimcore in 2026, community support for a platform version ends when the next one is released (Pimcore docs, Measured).

Versions and end-of-support dates

Label per cell: Measured unless stated otherwise. Estimated: own derivation from the support policy (first release of the next platform version). As of 2026-10-01.

How to read the cells:

• Derived means: Pimcore publishes no end date for this version. Under the support policy, community support ends with the release of the next platform version, so the table shows that release date.
• No LTS means: the version has no LTS mark in Pimcore's release table (as of 2026-10-01).
• 2022.0 (Pimcore 10.6) has a published date. On 2023-06-14 a Pimcore maintainer announced that the last bugfix release on August 16, 2023 would also be the end of life of Pimcore 10 (GitHub Discussions).
• Two more releases followed on 2023-08-21: 10.6.8 with a security fix and 10.6.9 with fixes to database migrations. They are the last public 10.6 releases (GitHub releases).
• For Pimcore 10.0 to 10.5, support had already ended on 2023-06-21 with 10.5.24, according to the same announcement. Two days later 10.5.25 followed, which reverted one change. LTS existed only for 10.6.
• For 2022.0 the first-release column shows the first stable release of core 10.6, because Pimcore only published the 2022.0 metapackage retroactively on 2023-12-13.
• 2025.4: LTS until December 2028 does not cover Pimcore Studio. After the release of 2026.1, Pimcore announced three more months of bug fixes for Studio compatibility in 2025.4 (Pimcore blog, 2025-12-09). See the Classic Admin UI section for details.

Table sources: release table and module details in the Pimcore docs, release dates from the metapackage pimcore/platform-version on Packagist, PHP requirement from composer.json of the latest release in each core line (pimcore/pimcore on Packagist). All values Measured; community end dates marked as derived are our own derivation.

How long does LTS run? Two statements from Pimcore

Pimcore states different durations in two places. Both, verbatim:

• Docs, 2026: "LTS provides 3 years of extended support beyond the regular release cycle" (Pimcore docs, Platform Versions).
• Product page, undated, retrieved 2026-10-01: "Secure operations at up to 2 years after the end of regular support" (pimcore.com, Long Term Support).

In context:

• In the release blog for 2025.4 of 2025-12-09 Pimcore also writes: "Extended 3‑year LTS support from release date" (Pimcore blog).
• The dates in the release table fit either statement, depending on the version.
• For 2023.3 and 2024.4, LTS ends two years after the first release; for 2025.4 it is three years (our calculation from the table and the release dates).
• For planning, use the date of the specific version in the table above. If you buy LTS, have that date confirmed in your contract.

According to the docs, LTS covers two kinds of fixes (Pimcore docs, Measured):

• Security fixes for CVE-rated vulnerabilities with critical severity.
• Critical bug fixes, limited to issues that can cause data loss or destroy infrastructure.

Classic Admin UI: removed from 2026.1

• Pimcore wrote on 2025-12-09: "Platform Version 2025.4 is the final release supporting Admin UI Classic. Starting with 2026.1, it will be removed entirely." (Pimcore blog, Measured).
• The module lists of all platform versions from 2026.1 on no longer contain pimcore/admin-ui-classic-bundle; 2025.4 still ships it in version 2.3 (Pimcore docs, module details, Measured, checked 2026-10-01).
• composer.json of the Classic package in version 2.3 requires pimcore/pimcore ^12.3, and ^12.3.12 from 2.3.8 on. This rules out core 2026.x (GitHub, Packagist, Measured).
• The repository pimcore/admin-ui-classic-bundle is archived on GitHub, with the last push on 2026-08-12. The README says: "This bundle has reached end of life." (GitHub, Measured, checked 2026-10-01).
• The successor is Pimcore Studio. On 2026-04-14 Pimcore announced that Studio is "generally available and fully supported for enterprise use", for both 2026.1 and 2025.4 (Pimcore blog, Measured).
• For 2025.4, LTS does not cover Studio. Pimcore wrote on 2025-12-09: "Pimcore Studio is not part of Platform Version 2025.4 and thus also not part of the LTS promise." According to the same post, 2025.4 gets three more months of bug fixes for Studio compatibility after 2026.1 is released (Pimcore blog, Measured).

How installs of Studio and Classic develop is shown on Pimcore statistics.

Licence change with Pimcore 12

• Up to core 11.5 (platform version 2024.4), Pimcore was dual-licensed: GPLv3 by default, or the commercial Pimcore Commercial License (PCL) under a separate agreement. Without that agreement GPLv3 applied (LICENSE.md, v11.5.14, Measured).
• Up to core 11.5, composer.json states the licence GPL-3.0-or-later (GitHub, v11.5.14); from core 12.0 (platform version 2025.1) it states "proprietary" (GitHub, v12.0.0). Both Measured.
• Since then the Pimcore Open Core License (POCL) applies. The current version is marked "Last Update: June 2025" and has shipped since core 12.0.2 (LICENSE.md on branch 2026.x, Measured).
• Cores 12.0.0 and 12.0.1 contained the "April 2025" version (LICENSE.md, v12.0.0, Measured).

The revenue threshold for free production use, in the words of the POCL:

"An organization with total global revenue not exceeding €5 million (€5M) or equivalent amount in other currency annually ("Threshold") may qualify for a free license for Production Use of the Open Core Software, provided such organization is not a part, subsidiary, affiliate, or shell company to another organization, entity, or company group whose total combined revenue exceeds the Threshold."

What the POCL sets out in detail:

• Organisations with global annual revenue of no more than €5 million may qualify for a free production licence.
• If the organisation belongs to a group or is affiliated with another organisation, combined revenue counts.
• Eligibility is self-certified. Pimcore reviews it and decides at its own discretion.
• Non-profit and educational organisations can also be licensed free of charge.
• Demos, prototypes and proofs of concept have been free since the June 2025 version. Showing features of the Enterprise Edition in them requires a paid developer licence (Pimcore Developer License Agreement, PDLA).

Two more clauses matter for operators and service providers.

Pimcore may charge licence fees retroactively: "Pimcore is entitled to charge license fees retroactively from the date on which Customer exceeded the Threshold." (POCL).

Development already counts. If the operator, a partner or any other service provider acting on its behalf starts building a solution intended or likely to go live, the POCL treats this as production use from the start, and the revenue threshold applies from day one: "If the Customer or a Partner or any other third person acting on the Customer’s behalf initiates development of a solution […], such use from its beginning shall be deemed Production Use" (POCL, section 1.2.2). Pimcore may agree individual transition periods in writing.

This page reproduces the licence text and is not a legal assessment. What the licence change means for the choice between Community and Enterprise is covered in Pimcore Enterprise or Community.

What this means if you run Pimcore 10 or 11

• For Pimcore 10, LTS ended in August 2025 as well. LTS existed only for 10.6.
• For Pimcore 11, LTS remains only on 11.5 (platform version 2024.4), only in Enterprise and Enterprise PaaS, until December 2026.
• If you run 11.0 to 11.4, you have neither community support nor LTS.
• Once these dates have passed, the published support policy provides no support for either line.

After community support ended (derived, see the table), Pimcore published further patch versions (Packagist, Measured):

• Core 11.5: further versions up to 11.5.14.1 on 2026-01-16, with the licence GPL-3.0-or-later. They are governed by GPLv3.
• Core 12.3: versions 12.3.5 to 12.3.12.1 from 2026-04-23 to 2026-08-07, with the licence "proprietary" and the POCL in the repository. They are governed by the POCL including its revenue threshold.
• Whether these versions form part of an LTS service is not addressed by the licence text.

We describe how a move works under Upgrades and migration.

Method

The basis is primary sources, all checked on October 1, 2026:

• The mapping of platform version to core version comes from the module details of each platform version in the Pimcore docs. LTS end dates come from the release table on the same page.
• First release is the date on which Pimcore published the platform version as the Composer metapackage pimcore/platform-version on Packagist. The exception is 2022.0, see the note below the table.
• End of community support: only Pimcore 10 has a published date. For 2025.4, Pimcore names a period relative to the release of 2026.1: three months of bug fixes for Studio compatibility. All other dates are derived from the support policy and marked as such.
• PHP: the version constraint in composer.json of the latest stable release of the core line, written here as the list of allowed PHP versions. For core 12.3, for example, Pimcore allows PHP 8.3 and 8.4.
• We link to the overview page of the docs, not to the individual version pages. Their addresses are numbered and shift with every new platform version.

Limits: all dates are vendor statements or package metadata. Individual contracts may set other terms. The curated values are available for download as the JSON file pimcore-lifecycle.json. We check them with every new Pimcore release.

Frequently asked questions

Changes

• 2026-10-01: First version. All values checked against the primary sources, platform version 2026.3 added.