Apr 22, 2024

Mastering the useThrottle Hook in React

In this blog, we explore how to control function execution frequency efficiently and learn how to optimize performance with React's useThrottle hook.

Author

DayaDayaSoftware Engineer III

Subject Matter Expert

Tarun Bhagchand SoniTarun Bhagchand SoniSenior Software Engineer - II
Mastering the useThrottle Hook in React
Click On The Image Above To Watch How It Works
Click On The Image Above To Watch How It Works

In the fast-paced world of web applications, user interactions can trigger a flurry of events. While responsiveness is crucial, excessive function calls can lead to performance bottlenecks. Enter the useThrottle hook, a powerful tool in React's arsenal for managing execution frequency.


Understanding Throttling

Throttling ensures that a function executes at most once within a specified time interval, regardless of how many times it is called. It is similar to a leaky faucet that only releases water intermittently, preventing a deluge.

Why Use Throttling?

  • Performance Optimization: Throttling prevents repetitive, expensive operations, such as API calls or complex calculations, from overwhelming the browser. This smooths out user experience and enhances application responsiveness.
  • Event Debouncing: It is ideal for scenarios where rapid user input (for example, continuous scrolling, resize events) might trigger unnecessary updates. Throttling ensures they are handled efficiently, minimizing redundant computations.


How Does useThrottle Work?

Let us dissect the provided code:

import { useRef } from 'react';

function useThrottle(cb: () => void, limit: number) {
  const lastRun = useRef(Date.now());

  return function () {
    if (Date.now() - lastRun.current >= limit) {
      cb(); // Execute the callback
      lastRun.current = Date.now(); // Update last execution time
    }
  };
}

Import and Setup:

JavaScript

import { useRef } from 'react';

We import useRef from React to create a reference that persists across re-renders, ideal for tracking the last execution time.

useThrottle Hook Function:

function useThrottle(cb: () => void, limit: number) {
  const lastRun = useRef(Date.now());

  return function () {
    if (Date.now() - lastRun.current >= limit) {
      cb(); // Execute the callback
      lastRun.current = Date.now(); // Update last execution time
    }
  };
}

Parameters:

  • cb: The callback function to be throttled. It takes no arguments and returns nothing (void).
  • limit: The time interval (in milliseconds) between allowed executions.

lastRun Reference:

We create a useRef hook named lastRun to store the timestamp (milliseconds since epoch) of the most recent execution. This ensures the function is called at most once within the specified limit.

Returned Function:

This is the throttled function you will use in your React components. It checks the time difference between the current time (Date.now()) and lastRun.current. If the difference is greater than or equal to limit, it executes the cb function and updates lastRun.current with the current timestamp.



Using useThrottle in React Components

Here is an example of how to use the useThrottle hook in a React component to throttle a scroll event handler:

import { useEffect, useState } from 'react';
import './App.css';
import useThrottle from './hooks/useThrottle';

type Character = {
  id: number;
  name: string;
  image: string;
};

function App() {
  const [data, setData] = useState<Character[] | undefined>([]);
  const [calls, setCalls] = useState(0);
  const [position, setPosition] = useState(0);
  const throttledScroll = useThrottle(handleScroll, 2000);

  function handleScroll() {
    setCalls((c) => c + 1);

    setPosition(
      Math.round(
        ((document.documentElement.scrollTop + document.body.scrollTop) /
          (document.documentElement.scrollHeight -
            document.documentElement.clientHeight)) *
          100
      )
    );
  }

  useEffect(() => {
    fetch(`https://rickandmortyapi.com/api/character`)
      .then((res) => res.json())
      .then((data: { results: Character[] }) => {
        setData(data.results);
      })
      .catch((error) => console.error('Error fetching characters:', error));
  }, []);

  useEffect(() => {
    window.addEventListener('scroll', throttledScroll);
    return () => window.removeEventListener('scroll', throttledScroll);
  }, [throttledScroll]);

  return (
    <div className="container">
      <div className="sticky">
        <p>Calls: {calls}</p>
        <button onClick={() => setCalls(0)}>Reset calls</button>
        <p>Position: {position}%</p>
      </div>
      <div className="character-list">
        {data === undefined && 'Nothing Found.'}
        {data &&
          data.map((character) => (
            <div key={character.id} className="character">
              <img src={character.image} alt={character.name} />
              <div>{character.name}</div>
            </div>
          ))}
      </div>
    </div>
  );
}

export default App;

In this example, the throttledScroll function is created using useThrottle and passed to the scroll event listener. This ensures that the handleScroll function is only called at most every 2000 milliseconds, even if the user scrolls rapidly.

Hire Us Form


Conclusion

The useThrottle hook is a valuable tool for enhancing performance and managing function execution frequency in React applications. By understanding its purpose and implementation, you can make informed decisions about when to use it to improve the responsiveness and efficiency of your web applications.

Subscribe to Our Newsletter

RELATED ARTICLES

More from the engineering frontline.

Dive deep into our research and insights on design, development, and the impact of various trends to businesses.
The Bug That Doesn't Show Up in Code Review: Why Your Flutter Web App Reloads on Safari
The Bug That Doesn't Show Up in Code Review: Why Your Flutter Web App Reloads on Safari
A real-world look at how oversized images can trigger Safari reloads and iOS crashes in Flutter apps and how smarter image decoding prevents them.
From Prompting to Process: What Changed When Flutter Shipped Agent Skills
From Prompting to Process: What Changed When Flutter Shipped Agent Skills
This blog explores how Flutter Agent Skills improve AI-assisted development by combining official framework workflows with project-specific guidance for more consistent development.
Why Everything Your AI Builds Looks the Same
Why Everything Your AI Builds Looks the Same
This blog explores why AI-generated interfaces often look alike and explains how design systems, product context, and reusable engineering practices help teams build distinctive, scalable
How We Built the Missing Bridge from Code to Figma
Technology

Jul 10, 2026

How We Built the Missing Bridge from Code to Figma
This blog explores how AI-generated React apps get turned into fully editable, designer-ready Figma files by reading React Fiber instead of the DOM.
Building a Resilient Hybrid-Cloud Network with WireGuard HA, Route-Based Failover, and Deep Observability
Technology

Jun 27, 2026

Building a Resilient Hybrid-Cloud Network with WireGuard HA, Route-Based Failover, and Deep Observability
A practical breakdown of building resilient AWS-to-on-premises connectivity with WireGuard HA, active-standby failover, and deep packet-forwarding observability.
We Built a 114-Second AWS-to-Azure Failover. Here’s What We Learned
Technology

Jun 19, 2026

We Built a 114-Second AWS-to-Azure Failover. Here’s What We Learned
A practical guide to building a 114-second multi-cloud disaster recovery failover between AWS and Azure — what we built, what broke, and what we learned.
Cloud-Native and Cloud-Agnostic Are Not Ideologies; They Are Business-Stage Decisions
Technology

Jun 12, 2026

Cloud-Native and Cloud-Agnostic Are Not Ideologies; They Are Business-Stage Decisions
This blog explains how organizations can balance speed, scalability, and operational flexibility as they grow from startup to enterprise scale.

The Right Conversation Can Save You Six Months.

Whether you’re navigating AI adoption, modernizing legacy systems, or scaling a product - we start by listening. No pitch deck. No template. A real conversation.