jQuery.fx.interval (since jQuery 1.4.3) is a global Number: milliseconds between animation ticks on the legacy timer path. Default is 13. It is a static property — not $el.something().
Remember
jQuery.fx.interval // read → usually 13
jQuery.fx.interval = 50; // write (stop all animations first)
// Ignored when requestAnimationFrame is available
// Deprecated 3.0 · Removed 4.0
Only relevant for legacy timer fallback. Always stop animations before changing the value.
Stop every running animation: $(":animated").stop(true, true).
Assign a number of milliseconds: jQuery.fx.interval = 50.
Start new animations — they use the new tick rate on timer-only browsers.
Reset to 13 when done experimenting (again with no animations running).
On modern browsers with rAF, expect little or no visible change.
Piece
Required?
Role
Type
—
Number (milliseconds)
Default
—
13
Scope
—
One global value for the whole page
Idle first
Yes (to apply)
No animation may be running when you change it
Pseudocode
Pseudocode
// Read
current = jQuery.fx.interval // e.g. 13
// Write (official rule)
if any animation is running:
stop them all first
jQuery.fx.interval = newMs
// Runtime behavior
if browser supports requestAnimationFrame:
jQuery uses rAF — interval is ignored
else:
timer fires every jQuery.fx.interval ms
each tick advances active tweens
Reference
Cheat Sheet
Keep these facts handy when reading legacy jQuery animation code.
Topic
Detail
Syntax
jQuery.fx.interval (read / write Number)
Since
jQuery 1.4.3
Default
13 ms
Deprecated
jQuery 3.0
Removed
jQuery 4.0
rAF
When supported → interval ignored
Change rule
Stop all animations first
Sibling
jQuery.fx.off — disable effects
Try it
Live Preview
Read or set fx.interval, then run a short .animate(). On modern browsers with rAF, both rates may look the same.
Box
Official rule: stop all animations before changing the interval. rAF may ignore the value.
Result
Ready — click Run to read or animate.
Code
jQuery Examples
Short, copy-ready snippets. Open DevTools, or use Try It Yourself for a live editor.
Example 1 — Read the Default
Inspect the global value before changing anything.
Modern browser:
rAF supported — jQuery.fx.interval is ignored for ticks
jQuery.fx.interval = 13
How It Works
Feature-detect. Check for requestAnimationFrame.
rAF path. Browser frames drive tween updates.
Timer path. Only then does fx.interval matter.
Why deprecated. rAF became universal — the property lost purpose.
Example 5 — Prefer jQuery.fx.off (Not Interval Tuning)
For global control today, disable effects with fx.off. Do not ship new code that tunes fx.interval.
jQuery
// Practical sibling global — still supported
$("#off").on("click", function () {
jQuery.fx.off = true;
$("#panel").hide().fadeIn(800); // snaps to end when fx.off is true
$("#status").text("fx.off = true — effects jump to final state.");
});
$("#on").on("click", function () {
jQuery.fx.off = false;
$("#panel").hide().fadeIn(800);
$("#status").text("fx.off = false — normal animated fade.");
});
// Avoid in new code:
// jQuery.fx.interval = 50; // deprecated 3.0, removed 4.0
fx.off = true → fadeIn snaps instantly
fx.off = false → smooth fade
Prefer CSS / Web Animations for new motion; use fx.off for a11y/testing
How It Works
fx.off. Global switch — duration becomes effectively 0.
Demo. Same fadeIn call; behavior depends on the flag.
Interval. Do not use it to “speed up” or “smooth” modern apps.
Migrate. Plan removal before moving to jQuery 4.0.
Edge Cases & Pitfalls
Common mistakes when touching this legacy global.
rAF
No visible change on modern browsers
With requestAnimationFrame, assigning 50 often does nothing to smoothness.
idle
Change mid-animation is ignored
Stop all tweens first. Mid-flight assignment updates the property only.
global
One value for the whole page
You cannot set a different interval per element or per queue.
removed
Gone in jQuery 4.0
Reading or writing the property will fail after upgrade — migrate away.
not duration
Interval ≠ animation duration
Duration still comes from .animate(…, 2000). Interval only sets tick frequency on the timer path.
Compatibility
Browser Support
jQuery.fx.interval existed from jQuery 1.4.3 through 3.x. It is deprecated in 3.0 and removed in 4.0. On browsers with requestAnimationFrame, changing it has no effect.
✓ Deprecated 3.0 · Removed 4.0
jQuery.fx.interval
Legacy timer tuning only. Modern jQuery prefers requestAnimationFrame. Do not depend on this property for new features.
LegacyStatus
Google ChromeAll versions · Desktop & Mobile
Full support
Mozilla FirefoxAll versions · Desktop & Mobile
Full support
Apple SafariAll versions · macOS & iOS
Full support
Microsoft EdgeAll versions · Chromium & Legacy
Full support
Internet ExplorerIE 6+ · Legacy environments
Full support
OperaAll modern versions
Full support
fx.intervalDeprecated
Bottom line: Learn it to understand old codebases. Prefer duration/easing, CSS transitions, Web Animations, or jQuery.fx.off for real control.
Analysis
Performance Notes
Approach
Cost
Best for
Lower interval (e.g. 5)
More timer wakeups
Legacy-only; usually worse on old CPUs
Higher interval (e.g. 50)
Fewer ticks
Choppier motion; rarely worth it today
rAF / CSS transitions
Browser-optimized
New UI motion
Tuning fx.interval is not a modern performance strategy. Let the browser drive frames (rAF / CSS), or turn effects off with jQuery.fx.off.
Remember
Key Takeaways
Role: global ms between ticks on the legacy timer path (default 13).
Status: deprecated in 3.0, removed in 4.0 — ignored when rAF exists.
Rule: stop all animations before changing the value.
Today: use duration/easing, CSS, or jQuery.fx.off — not interval tuning.
One line:jQuery.fx.interval was the legacy animation metronome — learn it for old code; do not build new features on it.
Frequently Asked Questions
jQuery.fx.interval is a global Number: the rate in milliseconds at which jQuery’s animation engine fires update ticks on the legacy timer path. It is a static property on jQuery.fx — not a method on a jQuery collection.
The default is 13 milliseconds — roughly 77 ticks per second when the timer fallback drives animations.
Yes. It was deprecated in jQuery 3.0 and removed in jQuery 4.0. Prefer requestAnimationFrame-driven animation (what modern jQuery already uses) or CSS transitions / the Web Animations API for new work.
No. When requestAnimationFrame is available, jQuery syncs updates to the browser frame loop and ignores fx.interval. The property only mattered on legacy browsers without rAF.
jQuery uses one global interval. Stop every running animation first (for example $(":animated").stop(true, true)), then change the value. A mid-flight assignment does not reconfigure the active timer.
Yes. One jQuery.fx.interval applies to every timer-based jQuery animation on the page. Use duration, easing, CSS transitions, or jQuery.fx.off for other kinds of control.