# How the Zoom Meeting SDKs are versioned The Zoom Meeting SDKs follow the [semantic versioning](https://semver.org/) scheme. ## Versions with new features and bug fixes The Zoom Meeting SDKs are versioned, and are compatible (backwards compatible) with other [Zoom Meeting SDK versions](/changelog/meeting-sdk). That being said, new features and new bug fixes are included in each new version. For example, Meeting SDK (Web) version 2.4.0 and version 2.3.5 can join a session together, but a feature like [virtual background](https://support.zoom.us/hc/en-us/articles/210707503-Changing-your-Virtual-Background-image) introduced in version [2.4.0](/changelog/meeting-sdk/web/2.4.0), would only be available in 2.4.0 and not in prior versions. ## Versions with new requirements A new version could have a new requirement (also referred to as a breaking change), but prior versions would remain as they are. For example, in versions [2.7.0+](/changelog/meeting-sdk/web/2.7.0), the [sdkKey will be required](/docs/internal-apps/jwt-app-migration/#jwt-app-type-to-sdk-app-type-migration) in the [Meeting SDK for web join function](/docs/meeting-sdk/auth/#generate-a-meeting-sdk-jwt) (instead of the apiKey), but this is not a requirement in prior versions. ## Minimum support versions The [Zoom Software Quarterly Lifecycle Policy](https://support.zoom.us/hc/en-us/articles/360059429231) also applies to the Meeting SDKs. ## Why version the SDKs? SDK Versioning is good because it locks you into a set of functionality that won’t be affected by changes in new versions. Then, when you are ready to do a version upgrade, you can review the respective details and implement any new requirements before you do a deployment. It is uncommon for new versions to have new requirements or breaking changes. If they do, we mention it on the [changelog](/changelog/), and [devforum](https://devforum.zoom.us/c/announcements/37), and commonly via email (sent to the Zoom account owner and admins email).