jQuery .noConflict() Method

What You’ll Learn

jQuery.noConflict() gives the global $ name back to another library (or your own code) while jQuery keeps working as jQuery. This tutorial covers the optional removeAll flag, custom aliases, the .ready() $ parameter trick, IIFE wrappers, and when (not) to load two jQuery versions.

Introduction

Many libraries use $ as a shortcut — jQuery, Prototype, and custom helpers alike. When two of them load on one page, the last one to assign window.$ wins and the other breaks.

Since jQuery 1.0, jQuery.noConflict() restores the previous owner of $. jQuery itself stays on window.jQuery (unless you pass true). You keep full jQuery power without fighting over a one-character name.

Pair this with .ready() so callbacks can still receive $ as a local parameter. Browse more helpers in the Utilities hub.

Understanding the jQuery.noConflict() Method

When jQuery starts, it saves any existing window.$ (and window.jQuery). Calling jQuery.noConflict() puts that saved $ back and returns the jQuery object so you can keep a reference.

With jQuery.noConflict(true), both $ and jQuery are restored to their previous owners. Capture the return value if you still need that jQuery build.

📝 Syntax

Signature (jQuery 1.0+):

jQuery.noConflict( [ removeAll ] )

Parameters

• removeAll (optional Boolean) — if true, also release the global jQuery name (restore the previous owner). Default behaves like false: only $ is restored.

Return value

• Object (the jQuery function) — so you can assign a private alias immediately.

Minimal pattern

jQuery.noConflict();
// Other library can use $ again here
jQuery( "div p" ).hide();

Examples Gallery

Examples follow the official jQuery API patterns. Use View Output or Try It Yourself to explore each case.

jQuery.noConflict();
// Do something with jQuery
jQuery( "div p" ).hide();
// Do something with another library's $()
// $( "content" ).style.display = "none";

typeof window.$ may no longer be "function" (jQuery)
jQuery("div p") still hides paragraphs

$ is free for the other library

jQuery.noConflict();
jQuery( document ).ready(function( $ ) {
  // Code that uses jQuery's $ can follow here.
  $( "p" ).addClass( "ready" );
});
// Code that uses other library's $ can follow here.

Inside ready: $ is jQuery
Outside: global $ is not jQuery (after noConflict)

Best of both worlds for page scripts

jQuery.noConflict();
(function( $ ) {
  $(function() {
    // More code using $ as alias to jQuery
    $( "li" ).addClass( "ok" );
  });
})(jQuery);
// Other code using $ as an alias to the other library

Inside IIFE: $ === jQuery
Outside IIFE: $ is the other library (or undefined)

Common pattern for plugins and page modules

var j = jQuery.noConflict();
// Do something with jQuery
j( "div p" ).hide();
// Do something with another library's $()
// $( "content" ).style.display = "none";

j === jQuery function
j("div p") works
Global $ restored for other code

var dom = {};
dom.query = jQuery.noConflict( true );

// Do something with the new jQuery
dom.query( "div p" ).hide();
// window.jQuery / window.$ restored to previous owners

dom.query is your jQuery reference
typeof window.jQuery may be "undefined" (if nothing else claimed it)
Plugins expecting global jQuery may break — use carefully

🚀 Common Use Cases

• jQuery + Prototype — classic conflict; free $ for Prototype after jQuery loads.
• CMS / WordPress themes — many stacks already call jQuery.noConflict() and expect jQuery in theme scripts.
• Custom $ helpers — your page defines $ for DOM shortcuts; jQuery must not overwrite it permanently.
• Plugin bundles — wrap plugin code in (function($){ ... })(jQuery) after noConflict.
• Migration sandboxes — rare dual-jQuery pages during upgrades (prefer one version).
• Namespaced apps — app.$ = jQuery.noConflict(true) when you own the whole page API.

📝 Notes

• Available since jQuery 1.0; still present in modern jQuery 3.x / 4.x.
• $ is only an alias — every API works as jQuery(...).
• Call noConflict after jQuery loads and before scripts that need the other $.
• noConflict(true) can break plugins that require a global jQuery.
• Loading two jQuery versions is discouraged; use only for temporary migrations.
• Not the same as jQuery.sub() (removed API for copying jQuery).
• Document-ready and IIFE patterns let you keep writing $ locally without globals.

💡 Best Practices