APOC and Cypher versions

With the release of Cypher 25 (coinciding with the release of Neo4j 2025.06), users can specify the version of Cypher in which they want to run their queries, choosing between Cypher 5 and Cypher 25.

APOC 2025.06 includes many changes only compatible with Cypher 25, and the last updates to Cypher 5. Any changes to APOC in APOC 2025.07+ are only compatible with Cypher 25.

The Cypher version can be set for individual queries or as the default language for a database.

All new databases created after the release of 2025.06 will continue to use Cypher 5 as their default language.

For more information, see the Cypher Manual → Select Cypher version.

Using APOC with different Cypher versions

APOC procedures and functions are tied to a specific Cypher language version. Therefore, just as Neo4j 2025.06 behaves differently depending on the version of Cypher used, so does APOC 2025.06. For example, APOC 2025.06 removed Cypher 25 support of the procedure apoc.create.uuids(), meaning it is not available to queries running Cypher 25. However, it can still be used on APOC 2025.06 if queries are prepended with CYPHER 5, or if the database’s default version is set to CYPHER 5. If a query uses Cypher 5, APOC procedures and functions will behave as they did in the 2025.06 release. After this, APOC’s Cypher 5 functionality is frozen.

Using a procedure removed in Cypher 25 with APOC 2025.06+

CYPHER 5
CALL apoc.create.uuids(10)

For a full list of any changes introduced to APOC 2025.06 or later (and, therefore, only available in Cypher 25), see the Deprecations and additions page.

For information about the APOC 5.26 LTS release, see the APOC 5 User Guide.

The documentation for APOC 2025.06 and later will default to using Cypher 25. However, when relevant, it will provide examples showing the differences between running an APOC procedure using Cypher 5 and Cypher 25.