Pure and Impure Functions in JavaScript

Pure and Impure Functions in JavaScript

A dive into the world of pure and impure functions in JavaScript and how they differ.

Mar 2, 2023·

4 min read

Play this article

"Pure" and "Impure" are two terms that are often associated with functions in JavaScript, especially in React Components. This post explains what they are, how they differ, and whether you should try to write pure functions all the time.

Purity and Impurity

A function can be classified as pure or impure depending on two factors

  1. It must be predictable. Same input = same output.

  2. There should be no side effects from calling it.


A function is predictable if, for a given input, the function call produces the same result all the time.

Consider the code snippet below. The function add() will always return 8 if the arguments are 3 and 5. This function is predictable.

const add = (a, b) => a + b;

console.log(add(3, 5)); // 8

console.log(add(3, 5)); // 8

console.log(add(3, 5)); // 8

Now, take a look at this snippet. Since the return value depends on an external variable, the function count() does not return the same value even if the same argument is passed for each function call. This function is unpredictable.

let counter = 0;
const count = num => counter + num;

console.log(count(5)); // 6
console.log(count(5)); // 7
console.log(count(5)); // 8

Side effects

A function is said to have a side effect when

  • the function call causes the mutation(change) of a non-local variable or state.

  • the function body has input/output statements (examples: prompt(), console.log()).

  • the function body has a statement that calls another impure function.

  • function arguments are modified.

A good analogy for side effects is the world of Medicine. A tablet or pill for a disease like the common cold would help assuage the cold but might come with sleepiness or heaviness as a side effect.

Here's a modified version of the count() function from earlier. The counter update happens inside the function this time. Since the function call modifies an external variable, it has a side effect.

let counter = 0;
const count = num => ++counter + num;


Here's another example.

// a function that adds a new key-value pair to an object
function addPropertyToObject(object, key, value) {
    object[key] = value;

const person = {
    name: 'Sunny',
    role: 'Developer'

addPropertyToObject(person, 'age', 25);
/* output:
    age: 25,
    name: 'Sunny',
    role: 'Developer'

The function addPropertyToObject is mutating the person object by adding a new key-value pair, and also has a console.log() statement. So, it has side effects.

Built-In Examples

All built-in methods in JavaScript are not pure. There are both pure and impure functions. Here are a few examples -

Array methods like push() pop() sort() and splice() are considered impure because, behind the scenes, they modify the original array that's passed to the methods as arguments.

On the other hand, filter() , map() , slice() and reduce() do not modify the original array, and is hence considered pure on the condition that their respective callback functions are also pure.

Another great example of an impure function would be Math.random() whose output cannot be predicted during the method call.

Pure or Impure - What's the way to go?

Pure functions have a few solid advantages over impure functions

  1. They are easy to read, test, and debug.

  2. Another advantage is caching. Since they always return the same output for a given input, they can be cached or memoized to improve performance. This can be particularly useful for functions that are computationally expensive or called frequently.

  3. Since they have no side effects, it's easier to modularize and make them reusable.

Although writing pure functions are considered a great practice, sometimes we need some impurity to get things done. Cases involving read/write operations, handling user input, and randomization are a few examples where the functions we write become impure by nature. So, the correct answer is, like in most cases, it depends!


  • Functions can be classified into pure and impure functions.

  • Pure functions are predictable and have no side effects.

  • Built-in methods in JavaScript are a mix of both.

  • Writing pure functions is generally recommended, but some situations require impure functions.

Do spread the word if you got to learn something new today. It would mean the world to me! Have any questions or points to add? Comment away or drop me a DM on Twitter. I'd love to connect :)


Detailed reads

  1. Syncfusion blog post

  2. Scaler blog post

  3. BecomeBetterProgrammer blog post

  4. Beta React Docs - keeping components pure

Standalone reads

  1. Wikipedia definition of Pure Function

  2. Pure and impure functions interview questions

  3. What is a side effect

Did you find this article valuable?

Support Abin John by becoming a sponsor. Any amount is appreciated!