jQuery 4 WordPress support has a start date. On 17 November 2026, the WordPress core team published “Preparing for jQuery 4 with WordPress 7.2” on make.wordpress.org. The short version: WordPress 7.2, due on 8 December 2026, ships jQuery Migrate 3.6.0 as the first step toward jQuery 4. The jump to jQuery 4 itself is planned for WordPress 7.3, if testing goes well.
If you run an Elementor site, this matters more than most core updates. Themes, page builders, sliders, popups and form plugins have leaned on jQuery for years. Some of that code still uses functions that jQuery 4 removed. This post explains what is changing, when, and a simple 15-minute check you can run before 7.3 arrives.
What is jQuery, and why does WordPress still ship it?
jQuery is a JavaScript library from 2006 that made it easy to select page elements, run animations and send requests. WordPress bundles it so plugins and themes can load one shared copy instead of each bringing their own.
Modern browsers now do most of what jQuery was built for, so new code often skips it. But WordPress powers millions of sites with older plugins, so core cannot simply remove it. Instead, it updates jQuery carefully, with a safety net called jQuery Migrate.
jQuery 4.0.0 itself came out on 17 January 2026. It was the first major jQuery release in almost ten years. It dropped support for Internet Explorer 10 and older, and it removed a list of old helper functions that had been deprecated for a long time.
What changes in WordPress 7.2 (and what does not)
The important point for site owners: WordPress 7.2 does not switch your site to jQuery 4. The core post says, “WordPress 7.2 will ship with jQuery Migrate 3.6.0 to prepare for updating to jQuery 4.”
jQuery Migrate is a helper script. It restores old behaviour that newer jQuery removed, and in its development build it prints a warning in the browser console each time a plugin uses something deprecated. That gives developers time to find and fix old code while it still works.
Here is the plan the core team shared. Every step after 7.2 depends on test results, so treat the later dates as targets, not promises.
| WordPress version | Planned jQuery change | Status |
|---|---|---|
| 7.2 (8 December 2026) | jQuery Migrate updated to 3.6.0, to surface jQuery 4 problems | Confirmed in the RC builds |
| 7.3 (2027) | Update to the latest jQuery and jQuery Migrate, plus jQuery UI and other dependent libraries | Tentative, depends on testing |
| 7.5 or 7.6 (end of 2027) | jQuery Migrate disabled by default | Tentative, depends on testing |
WordPress 7.2 Release Candidate 1 came out on 17 November 2026, and RC2 is scheduled for 24 November. A Plugin Check issue opened on 18 November also proposes a new check that would warn plugin authors about jQuery 4 problems. The direction is clear: old jQuery code has roughly a year left before the safety net comes off.
Which old jQuery code breaks in jQuery 4?
jQuery 4 removed several helper functions that modern JavaScript now covers. If a plugin or a custom snippet on your site still calls one of these, it will throw an error once jQuery 4 loads without Migrate.
| Removed in jQuery 4 | Modern replacement |
|---|---|
| jQuery.isArray() | Array.isArray() |
| jQuery.parseJSON() | JSON.parse() |
| jQuery.trim() | String.prototype.trim() |
| jQuery.type() | typeof, or Array.isArray() for arrays |
| jQuery.isFunction() | typeof value === “function” |
| jQuery.isNumeric() | A small custom check, such as Number.isFinite() |
| jQuery.now() | Date.now() |
You do not need to read code to benefit from this list. It helps you recognise the names when they show up in console warnings, and it gives you the right words when you contact a plugin author.
How to check your Elementor site in 15 minutes
Do this on a staging copy, never on your live store. If you do not have one yet, create a staging site first, then follow these steps.
- Update the staging site to the WordPress 7.2 release candidate (or to 7.2 once it is out on 8 December). The WordPress Beta Tester plugin can switch a site to the RC channel.
- Turn on script debugging. Add define( ‘SCRIPT_DEBUG’, true ); to wp-config.php. WordPress then loads the full, unminified scripts, including the version of jQuery Migrate that prints warnings.
- Open your key pages in Chrome or Firefox: home, a product page, cart, checkout, a page with a popup, and a page with a form. Press F12 and open the Console tab.
- Look for lines that start with “JQMIGRATE”. Each one names a deprecated feature. Click the file link next to it to see which plugin or theme folder it comes from.
- Click around. Open menus, sliders, tabs, accordions and popups, submit a test form and add a product to the cart. Some code only runs on interaction.
- Write down each warning with the plugin name and the page. That list is your to-do list.
- Turn SCRIPT_DEBUG off again when you are done.
No JQMIGRATE lines at all is a very good sign. A few warnings is normal on an older site, and it does not mean anything is broken today. It means that code needs an update before jQuery 4 arrives.
What to do with the warnings you find
Most fixes are on the plugin author’s side, not yours. A calm, specific report gets the fastest result.
- Update first. Install the latest version of every plugin and theme on staging, then test again. Many authors fix jQuery warnings quietly in routine updates.
- Report what is left. Send the author the exact console line, the plugin version and the page URL. Mention that WordPress 7.3 plans to move to jQuery 4.
- Fix your own snippets. Custom code in a child theme or a code snippets plugin is your responsibility. Swap the old helpers for the replacements in the table above.
- Plan replacements. If a plugin has not been updated in a year or more, start looking for an alternative now rather than in a rush next year.
- Re-test after each change. Clear any caching or minify plugin first, because combined files can hide where a warning comes from.
What this means for Elementor and block editor sites
The bigger trend is clear: WordPress is moving away from old jQuery habits, and the block editor is built on modern JavaScript. That does not make Elementor sites risky. It simply rewards keeping your plugins current and choosing tools that are actively maintained.
It is also a good moment to look at what loads on each page. Every plugin that adds jQuery code is one more thing to test at each major update. Fewer, well-maintained plugins mean faster pages and easier updates.
A quick checklist before WordPress 7.3
- Take a full backup of the live site
- Create or refresh a staging copy
- Update staging to WordPress 7.2 and turn on SCRIPT_DEBUG
- Check the console on your key pages for JQMIGRATE warnings
- Update plugins and themes, then test again
- Report remaining warnings to plugin authors
- Fix custom snippets that use removed jQuery helpers
- Repeat the check when the WordPress 7.3 beta arrives
Frequently asked questions
Will WordPress 7.2 break my site because of jQuery 4? No. WordPress 7.2 does not switch to jQuery 4. It updates jQuery Migrate to 3.6.0, which keeps old code working and shows warnings so developers can fix it before the planned change in 7.3.
When will WordPress switch to jQuery 4? The core team tentatively plans it for WordPress 7.3, depending on test results. jQuery Migrate would then be turned off by default around the end of 2027 (WordPress 7.5 or 7.6), also depending on testing.
How do I see jQuery Migrate warnings? Add define( ‘SCRIPT_DEBUG’, true ); to wp-config.php on a staging site, open your pages, press F12 and read the Console tab. Warnings start with “JQMIGRATE” and link to the file that caused them.
Do I need to remove jQuery from my site? No. jQuery stays in WordPress. You only need old code that uses removed functions to be updated, and in most cases that is the plugin or theme author’s job.
Conclusion
The jQuery 4 WordPress move is slow and well signposted, which is good news. WordPress 7.2 gives everyone a warning system first, and the real switch is planned for 7.3 at the earliest. Run the 15-minute check on staging this month, update what you can, and report the rest. By the time jQuery 4 lands, your Elementor site will be ready.
If you are reviewing plugins anyway, Bright Addons has three free plugins on WordPress.org: Bright Addons for Elementor with 56 free widgets, the Bright Addons Blocks Library with 62 free Gutenberg blocks that load only where used and need no jQuery, and Bright Addons for WooCommerce with 28 free modules. Browse the widgets and blocks, or see Pro plans from $10 a year during Black Friday, until 30 November 2026, with no code needed. Bright Addons Pro for Elementor and Bright Addons Blocks Pro are separate products with the same plans and prices.


