Read from drupal.org, rebuilt every week
Drupal Upgrade Check
Paste your site's core.extension.yml, pick Drupal 11 or 12, and get a quick feel for what the upgrade will need to tackle.
You'll run Upgrade Status on the site before you do the work, of course. This is for before that: what leaves core, what has no release yet, what is ready, from one file every site has and nothing to install. Drupal 10 stops getting security fixes on 9 December 2026. Nothing you paste leaves your browser.
It lives at config/sync/core.extension.yml in your config export, or run drush config:get core.extension and paste what it prints. A plain list of machine names works too, one per line or separated by commas, such as the output of drush pm:list --status=enabled --field=name.
The check runs as soon as there is something in the box.
How to read it
Every line is a fact from drupal.org, not a judgement.
Leaves core. Drupal moves modules and themes out of core on each major release, usually into a contributed project with the same name. If your site uses one, the upgrade needs that project added with Composer first, and the line under the name says whether a stable release exists for the Drupal you chose. The list comes from drupal.org's deprecated and obsolete extensions page and from the module list on each Drupal branch.
No stable release. The maintainer of a contributed module states which Drupal versions each release runs on. If no stable release says it runs on the version you chose, the cell is red here, the same as on the Compatibility Lookup. A test release or a development snapshot is noted, because you can sometimes work with one. The honest reading of a red line is "not yet", and for Drupal 12 that is most of contrib today, five weeks before its first release.
A known security hole. A release exists for your target, but drupal.org has since marked it insecure. Usually the fix is in a newer release that you pick up in the same upgrade. Sometimes there is no fix at all, and the line says so.
On the way out. Still in the Drupal you chose, but marked deprecated or obsolete there, which means it leaves in the next major. Nothing to do for this upgrade; worth knowing before the next one.
Custom, or not on drupal.org. The file lists machine names, and a name I cannot match to a drupal.org project is either your own code or a project outside the 1,100 most used. You probably know which. Submodules are matched to their parent project, so webform_ui reads as Webform.
The file does not say which Drupal you are on now, or which versions of each module you run, so this page cannot. Upgrade Status, installed on the site, sees both and finds deprecated code in your own modules too. This is the quick look before that, or the one you can take on a site you cannot install anything on yet. The data was last rebuilt on 5 November 2026.