With the release of a new major Google Mobile Ads SDK version, earlier
major versions may be given a sunset date. After an SDK version is sunset,
ad traffic from that version is at risk of receiving automatic no fill due to
stopped ad serving.
Benefits of a deprecation schedule
Introducing a predictable deprecation schedule offers the following benefits:
Ability to predict and plan for SDK updates with a year of lead time.
Legacy SDK code that only exists to support old versions can be deleted,
thereby decreasing SDK size and lowering the risk of bugs.
Engineering resources can focus more on support for newer SDKs and
innovation of new SDK features.
Timetable
The following table lists the specific deprecation and sunset dates for each
version. We encourage you to migrate to the newest version as soon as possible
after its release.
1A more specific sunset date will
be announced on theGoogle Ads Developer
blog, and updated
on this page with two months notice.
Differences between supported, deprecated, and sunset
Term
Supported
Deprecated
Sunset
SDK Versions
All releases with major release N and N-1, where N is the latest major
version.
All releases with major release N-2.
All releases with major release N-3 or below. Releases with major version
N-3 will sunset approximately two months after major version N is
released.
Ad serving
Ads serve to this version.
Ads serve to this version.
Adsat risk of not servingto this version. We will regularly
review usage of all sunset versions going forward to consider disabling
ad serving. The oldest versions with lower usage and higher maintenance
costs will be targeted first. When ad serving is disabled, ad requests
return a no fill with an error indicating that this version is sunset.
Technical SDK support questions specific to this version are no longer
supported on theGoogle Mobile Ads SDK developer forum.
You will be asked to validate the issue in a supported version to receive
full support.
Technical SDK support questions specific to this version are no longer
supported on theGoogle Mobile Ads SDK developer forum.
You will be asked to validate the issue in a supported version to receive
full support.
Lifecycle of a major SDK version
In general, a new major version will live in thesupportedstate for about
two years, and in adeprecatedstate for an additional year before moving
to asunsetstate.
The deprecation and sunset timelines for Google Mobile Ads SDK revolve
around major SDK releases. We plan to have one major version release in the
first quarter of each year. The release of a new major version triggers changes
in support for earlier major versions.
When a new major version N is released:
All SDK versions with major version N-2 are considereddeprecatedimmediately.
All SDKs versions with major version N-3 willsunsetafter
approximately two months.
Exceptions
This deprecation schedule provides a framework for predictable lifetimes for an
SDK version. However, there may be exceptions in the future. This schedule does
not preclude us from sunsetting an SDK version at an earlier date, but we are
committed to providing proactive communication with ample lead time for any
future changes.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-09-04 UTC."],[[["\u003cp\u003eGoogle Mobile Ads SDK versions are given sunset dates, after which ad traffic may stop serving ads.\u003c/p\u003e\n"],["\u003cp\u003eDevelopers have a year lead time to plan for SDK updates after a deprecation announcement.\u003c/p\u003e\n"],["\u003cp\u003eMigrating to newer versions helps reduce SDK size, lower bug risks, and allows Google to focus on newer features.\u003c/p\u003e\n"],["\u003cp\u003eVersions v23.x.x and v22.x.x are currently supported, while v21.x.x is deprecated and v20.x.x and earlier are sunset.\u003c/p\u003e\n"],["\u003cp\u003eSDK versions 6.x.x and below have ad serving disabled.\u003c/p\u003e\n"]]],[],null,["Select platform: [Android](/admob/android/deprecation \"View this page for the Android platform docs.\") [iOS](/admob/ios/deprecation \"View this page for the iOS platform docs.\") [Unity](/admob/unity/deprecation \"View this page for the Unity platform docs.\") [Flutter](/admob/flutter/deprecation \"View this page for the Flutter platform docs.\")\n\n\u003cbr /\u003e\n\nWith the release of a new major Google Mobile Ads SDK version, earlier\nmajor versions may be given a sunset date. After an SDK version is sunset,\nad traffic from that version is at risk of receiving automatic no fill due to\nstopped ad serving.\n\nBenefits of a deprecation schedule\n\n: Introducing a predictable deprecation schedule offers the following benefits:\n\n - Ability to predict and plan for SDK updates with a year of lead time.\n - Legacy SDK code that only exists to support old versions can be deleted, thereby decreasing SDK size and lowering the risk of bugs.\n - Engineering resources can focus more on support for newer SDKs and innovation of new SDK features.\n\nTimetable\n\nThe following table lists the specific deprecation and sunset dates for each\nversion. We encourage you to migrate to the newest version as soon as possible\nafter its release.\n\n| Versions | Status | Release date | Deprecation date | Sunset date | Migration guide |\n|----------------------------------------------------|------------|-------------------|--------------------|--------------------------------|-----------------------------------------------------------|\n| [v24.x.x](/admob/android/rel-notes#24.0.0) | Supported | February 24, 2025 | Q1 2027 | Q2 2028 | |\n| [v23.x.x](/admob/android/rel-notes#23.0.0) | Supported | March 7, 2024 | Q1 2026 | Q2 2027 | [Migrate to v24](/admob/android/migration#migrate-to-v24) |\n| [v22.x.x](/admob/android/rel-notes#22.0.0) | Deprecated | March 29, 2023 | February 24, 2025 | Q2 2026[^1^](#sunset-footnote) | [Migrate to v23](/admob/android/migration#migrate-to-v23) |\n| [v21.x.x](/admob/android/rel-notes#21.0.0) | Deprecated | May 25, 2022 | March 7, 2024 | June 30, 2025 | [Migrate to v22](/admob/android/migration#migrate-to-v22) |\n| [v20.x.x](/admob/android/rel-notes#20.0.0) | Sunset | April 5, 2021 | March 29, 2023 | June 30, 2024 | [Migrate to v21](/admob/android/migration#migrate-to-v21) |\n| [v7.x.x - v19.x.x](/admob/android/rel-notes#7.0.0) | Sunset | March 19, 2015 | September 30, 2022 | June 30, 2023 | [Migrate to v20](/admob/android/migration#migrate-to-v20) |\n\n^1^ A more specific sunset date will\nbe announced on the [Google Ads Developer\nblog](//ads-developers.googleblog.com/search/label/mobile_ads_sdk), and updated\non this page with two months notice.\n| **Key Point:** SDK Versions 6.x.x and below have ad serving disabled.\n\nDifferences between supported, deprecated, and sunset\n\n| Term | Supported | Deprecated | Sunset |\n|------------------|----------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| **SDK Versions** | All releases with major release N and N-1, where N is the latest major version. | All releases with major release N-2. | All releases with major release N-3 or below. Releases with major version N-3 will sunset approximately two months after major version N is released. |\n| **Ad serving** | Ads serve to this version. | Ads serve to this version. | Ads **at risk of not serving** to this version. We will regularly review usage of all sunset versions going forward to consider disabling ad serving. The oldest versions with lower usage and higher maintenance costs will be targeted first. When ad serving is disabled, ad requests return a no fill with an error indicating that this version is sunset. |\n| **Support** | Technical SDK support questions are welcomed on the [Google Mobile Ads SDK developer forum](//groups.google.com/group/google-admob-ads-sdk). | Technical SDK support questions specific to this version are no longer supported on the [Google Mobile Ads SDK developer forum](//groups.google.com/group/google-admob-ads-sdk). You will be asked to validate the issue in a supported version to receive full support. | Technical SDK support questions specific to this version are no longer supported on the [Google Mobile Ads SDK developer forum](//groups.google.com/group/google-admob-ads-sdk). You will be asked to validate the issue in a supported version to receive full support. |\n\nLifecycle of a major SDK version\n\nIn general, a new major version will live in the **supported** state for about\ntwo years, and in a **deprecated** state for an additional year before moving\nto a **sunset** state.\n\nThe deprecation and sunset timelines for Google Mobile Ads SDK revolve\naround major SDK releases. We plan to have one major version release in the\nfirst quarter of each year. The release of a new major version triggers changes\nin support for earlier major versions.\n\nWhen a new major version N is released:\n\n- All SDK versions with major version N-2 are considered **deprecated** immediately.\n- All SDKs versions with major version N-3 will **sunset** after approximately two months.\n\nExceptions\n\nThis deprecation schedule provides a framework for predictable lifetimes for an\nSDK version. However, there may be exceptions in the future. This schedule does\nnot preclude us from sunsetting an SDK version at an earlier date, but we are\ncommitted to providing proactive communication with ample lead time for any\nfuture changes."]]
